BTA / Delivery desk
Trading Alert States: Publication, Receipt and Account Action
Keep instruction versions and account acknowledgements separate so a cancellation cannot silently erase an earlier fill.
One instruction, several histories
An original instruction needs a stable family identifier. A transport message may also have a channel ID, while a broker order has another ID. Retain all three where available. A change to direction, validity or a target is an amendment to a particular instruction, not evidence that the first version never existed. The family history preserves the terms a reader actually saw.
Draw the communication history separately from the account history. Publication, dispatch, endpoint acceptance and display tell you about a message. Submission, acceptance, rejection, partial fill and confirmed cancellation tell you about an order. Some events will be unavailable. A gap should remain a gap rather than being filled with a provider timestamp that happens to look plausible.
A cancellation request is not a completed cancellation
Consider an invented sequence: an instruction is published at second 0, an order is accepted at second 5, a provider cancellation appears at second 7, a partial fill occurs at second 8, and cancellation of the remaining quantity is confirmed at second 9. The sample teaches a race between systems; it is not observed data for a named platform. The instruction's cancellation does not make the partially filled quantity disappear.
Attach amendments and cancellation requests to their known effective version. Record which component is authorised to change an existing order. A subscriber notification is not necessarily permission for a connector to modify exposure, and a connector acknowledgement is not necessarily the broker's final state. When those authorities are unclear, the conclusion is unresolved.
Retain uncertainty instead of favourable reconstruction
An order submission without an acknowledgement is neither a confirmed rejection nor a confirmed fill. Repeatedly resubmitting because a screen is blank can create additional exposure. This publication cannot prescribe an account-specific recovery action. The evidence task is to obtain the missing response, preserve the unresolved identifier and use the actual responsible system's documented procedure.
At review time, join the whole instruction family, including cancelled, expired and unmatched messages. Deduplicate retries without deleting them from the operational record. Keep research reference fills and actual account executions separate. A tidy reconstructed history is not more reliable than an untidy original history that honestly exposes a missing acknowledgement.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Instruction family | Original ID, version and amendment authority |
| Account event | Order ID, state, quantity and acknowledgement |
| Unknown transition | Missing artifact and responsible system |
Continue the Investigation
Source Boundaries
Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.