Execution IsOne Event.The Position Remains.
An order screen is the part of a trading platform anybody can see. Beneath it, permission, instruction, execution, position and exposure change on different clocks, and the platform's work is keeping all five describing one client at one instant, while a provider is slow, silent or wrong.
Next Step / Technical Discovery
- One identity across the lifecycle
- Providers are replaceable dependencies
- Current, not end of session
- Every exception has an owner and a state
Where this system fits
A trading platform is the operating system around trading activity: what a client may do, what happened when they did it, and whether account, position and exposure agree afterwards.
- Desks, roles, and the administration an operations team runs.
- The boundary each venue, broker and price feed sits behind.
- The latency budget and availability target it is engineered against.
- Order and execution history still answerable long after the session.
- Market access, client money and permission to trade belong to regulated parties.
- Some decisions have a deadline; past it the answer is wrong.
- A position changes value while nobody is acting on it.
Why an order screen is not a trading platform
- 01
Order entry works. The account disagrees.
A request went out and nothing definite came back. Cancelling risks cancelling a fill; waiting risks a position nobody has counted.
- 02
Exposure is a report, not a number
Risk arrives as a file the next morning, describing a book from a session that has already closed.
- 03
The provider became the product
Client records, order state and risk rules live inside one vendor's platform. Adding a market, or leaving, means rebuilding what customers use.
- 04
Four teams, four versions of one trade
Operations reads the venue report, risk a snapshot, finance the statement, support the screen. Every investigation begins by choosing which to believe.
Actors and boundaries
Trader or client
Submits instructions against whatever the account permits.
Nothing inward. They see order state and position; the limits gating them are set elsewhere.
Trading account
Carries permissions, limits, balance, positions and restrictions.
Owned here. One account record, read the same way by execution, risk and support.
Trading platform
Accepts and works instructions, records executions, moves position and exposure.
All of it: order lifecycle, execution record, position impact, exposure update and operational state.
Execution provider or venue
Accepts or refuses orders and reports fills, on its own protocol.
Nothing inward. Answers are recorded as received; what the order is stays the platform's to say.
Risk operations
Sets limits, restricts accounts, decides what an exceeded threshold means.
Outward. The platform enforces a limit and shows exposure. Where the limit sits is theirs.
Back office and finance
Handles funding, statements, corporate actions and client queries after the session.
Outward for money and the books. The platform hands over the trade record explaining them.
How an order changes state
Five states while an order can still fill, and three that answer it. None erases an execution.
- 01
The instruction exists before the market sees it
A client, an instrument, a size and a price condition, under an identifier the platform issues itself.
- 02
The platform has agreed to work it
Permission, limits and margin are checked before anything leaves. Acceptance is the platform's decision, not the venue's.
- 03
Live in the market, still the platform's problem
The order rests with a provider. Its unfilled quantity is exposure the account has not taken yet.
- 04
Part is a fact, part is still an instruction
Each fill appends an execution record and moves position and exposure; the remainder works on.
- 05
The instruction is spent
Nothing is left to work. The order stops changing; the position it built outlasts it.
- 06
It never reached the market
A check failed here, or the provider refused there. No execution exists, so no position does either.
- 07
The remainder stops, the fills stand
Cancellation reaches unfilled quantity only. Anything already executed is a fact, and cancelling an order cannot unmake it.
- 08
The clock ended it, not a person
Time in force ran out with quantity still working. Earlier fills stand; only the accountability differs.
How much of the platform to own
Three operating models. Which is right depends on what the business intends to own.
- Total. Market access and client state arrive together.
- Partial. Connectivity is theirs, some client state is yours.
- Deliberate. Connectivity sits behind a boundary you drew.
- Their limits, their calculation, their timing.
- Their engine, your parameters.
- Yours to define, and yours to be right about.
- Their support boundary decides what you can answer.
- Shared, and the seam is where escalations stall.
- Yours, including the parts nobody wanted.
- Reaching a market quickly matters more than owning how it works.
- The vendor's model already fits and the gaps are parameters.
- How you trade is the product, or several markets must share one client.
When it fails
Six conditions the market produces regularly. None is settled by deciding what probably happened.
- The venue never returns a final answer
Nothing terminal came back, so the order holds an unresolved marker rather than an inferred status.
The venue is re-asked and its report compared before the order moves. Nothing is resent meanwhile.
- A fill arrives after the order was cancelled
An execution report references an order the platform has already closed out.
The execution is recorded and the position moves. Cancelling ended the instruction, not the trade.
- A working order breaches a limit that changed after acceptance
Exposure is evaluated against limits as they stand now, not as they stood at submission.
The remainder is pulled or held on a rule risk operations wrote beforehand. Fills stand; the breach becomes theirs to close.
- The price feed is late, frozen or gone
Prices carry their own age, and any exposure computed from them inherits it.
The platform says it is working on stale prices instead of showing a current-looking number, and narrows what it accepts.
- The venue's view of an order is not the platform's
Scheduled comparison of open orders and positions against the provider's report.
An operational case opens carrying both records. The platform neither silently adopts the venue's view nor overwrites it.
- An account is restricted while orders are still working
The restriction lands on account state, which every open instruction is evaluated against.
New instructions stop. Working orders follow the restriction's own rule — pulled, or close-only — chosen before the day it mattered.
What you own afterwards
- Order, position, balance and restriction come from one account record, so support, risk and the client are not describing different accounts.
- Position and margin move as executions arrive, so a threshold is something to decide during the session, not explain after it.
- Adding a market or leaving a provider is work inside one adapter. The client record, the order model and the risk rules do not move.
- Operations, risk and finance open one history for a disputed trade: what was instructed, what the venue answered, what the account did.
Related pages
Market Data Systems
The system that identifies, sequences, normalises and qualifies market data, then distributes one current view carrying its source, instrument and time.
Cloud Infrastructure
The operating environment beneath critical software: deployment, isolation, observability and recovery, engineered so failure stays bounded and the service returns to a known state.
Enterprise Platforms
The operating platform a business runs on — domains, roles, workflow and integration engineered as one system with one owner.
Bring a risk view that arrives the next morning, a client record split across three vendors, or an execution nobody can attach to an order.