Order Status Reconciliation After a Disconnect

Freeze the uncertain population

List orders submitted, amended or canceled around the interruption, together with their last known local state and message references. Include requests that timed out before acknowledgment. Record a cut-off and make any trading restrictions an explicit operational decision; otherwise new activity can keep changing the population being reconciled.

Recover the session according to its protocol before relying on later messages as a complete history. Sequence continuity and business completeness are different checks. Preserve logs and sequence state, then identify what remains unknown after replay. The resulting list is the work queue for order reconciliation, not a reason to resubmit every missing acknowledgment.

Obtain a complete, scoped view

Use the counterparty's supported order-status, mass-status, execution-history or other approved recovery interface. Specify account, session, instrument and time scope, and record how a multi-message response signals completion. cTrader's FIX specification documents individual and mass order-status messages as one provider example; another dialect may expose different coverage.

Match client and venue order identifiers, amendment chains and report identities. Keep orphan reports visible rather than discarding them because the local order is missing. A status snapshot can establish current order state without supplying every execution price or correction needed by the ledger. Obtain missing detail before creating economic postings.

Resolve differences with evidence

Compare cumulative quantity, remaining quantity, terminal status and current confirmed terms. A canceled order may retain executed quantity while having no remaining executable amount. Do not force every terminal order to satisfy a simplistic total-equals-filled-plus-open equation; use the actual state semantics.

Classify each difference as delayed local processing, missing execution detail, identifier mismatch, stale snapshot, correction or unresolved counterparty discrepancy. Record the proposed adjustment and its evidence before applying it. Reconcile positions and financial records separately after the order population is complete. The final sign-off should include both resolved items and any explicitly restricted, owned exceptions.

Example: current status reveals a missing fill

Locally, fictional order A has total 100 and cumulative quantity 20. The recovered counterparty status reports cumulative quantity 35 and remaining quantity 65. That reveals a 15-unit discrepancy, but it does not identify the missing execution's price or full event identity. The operator requests the relevant execution detail, links it to A and posts it once. Order B is reported canceled with cumulative zero; its pending cancellation task can be closed after identity and response completeness are checked.