Drop Copies And Independent Order State
A drop copy is a read-only, parallel feed of every execution report a trading session generates — a second source of truth that lets risk, compliance and back-office systems know exactly what happened without depending on the trading system's own bookkeeping being correct.
Prerequisites: The Execution Report State Machine
The trading system that sends orders and receives execution reports is, understandably, the system a firm builds all its own state around — but that same system is also exactly the one that might have a bug, a race condition, or a crash mid-session. If risk management, compliance, and settlement all rely solely on that one system's internal record of what happened, a bug there becomes a bug everywhere at once, with nothing independent to check it against.
A drop copy solves this by giving a separate FIX session a live, read-only copy of every execution report generated on the primary trading session, sent to it in parallel and independently of whatever the trading system itself does with those messages. The drop-copy session cannot send orders — it only receives, silently, everything that happens. Its entire purpose is to exist as a second, independently maintained record of "what actually got filled," built without touching the trading system's own logic at all.
Who actually uses the drop copy
Risk teams use it to compute real-time exposure without trusting the trading system's own P&L calculation to be bug-free. Compliance uses it to reconstruct trading activity for surveillance and audit, especially useful because it's tamper-resistant relative to a system a trader could theoretically manipulate. Back-office and settlement teams use it to reconcile what was actually executed against what the trading blotter claims happened, catching discrepancies that would otherwise only surface at end-of-day settlement — or worse, not surface until a client disputes a trade.
Why independence is the whole point
A drop copy is only useful if it's genuinely independent — fed by the exchange or broker directly, not relayed through the same trading application whose state it's meant to verify. A "drop copy" that's actually generated by re-reading the trading system's own internal database defeats the purpose entirely, because any bug that corrupted the primary record would corrupt this "independent" check the same way. The value comes specifically from the copy being sourced upstream of the trading system's own processing.
A drop copy is a separate, read-only FIX feed of execution reports, sourced independently of the trading system's own state, that gives risk, compliance, and back-office teams a trustworthy record of what actually happened even if the primary trading system has a bug.
A drop copy set up to relay through the same application logic it's meant to independently verify provides false comfort — genuine independence means the feed comes from upstream (the exchange or broker), not from the trading system re-exporting its own internal records.
Related concepts
Practice in interviews
Further reading
- FIX Trading Community, FIX 4.4 Specification, Volume 1