Suggestion: Provide [r]eason in Journal related to MarketOrders
Keywords: ui, esi, wallet, journal, market, marketOrders
Note: Brokers Fee / Transaction Tax / Market (Escrow/Transaction) entries in journal/wallet would contain MarketOrderID in Reason field
As a dutiful “backoffice” accountant for my corp, I need to reconcile my trader’s MER for our portfolio…
When attempting to calculate the “cost” of a MarketOrder, there is currently no direct ‘link’ between the many Brokers Fee/Taxes back to an original order; currently need to pull the transactions table and associate the DATE/TIME & CLIENT & VALUE (if it matches) against the Journal row.
Ideally, the [r] would = marketOrderID… however, it needn’t be anything more than a unique id per character. Then, downloading Journal entries in ESI would enable association for all items related to a single order.
Similar to how Bounty payments include a [r]eason raw string of typeIDs and count (eg 23955:10,23958:9,23959:8,)… and when the [r] is hovered in the client, it shows an enriched table of “rat” x2 due to a typeID lookup…
… it would be nice if (in client) when one hovers over the [r], instead of the raw marketOrderID, the UI would provide an enriched hover dialog containing the Order details:
- Order ACTIVE or INACTIVE … opt. enhance to:
** Open [aka unfilled]
** Partially Filled [aka still open]
** Filled [aka filled/closed]
** Cancelled [aka closed/unfilled or partial]
- typeID of order
- expiry date (if ACTIVE)
Thank you for your consideration,