LEARN. PRACTICE. GROW.Concept and mechanism
A trade passes through systems with different responsibilities. An order manager records intent; an execution indicates that trading occurred under the reported conditions; subsequent processing prepares and tracks the resulting obligations. Settlement concerns the transfer fulfilling those obligations within the applicable system. Collapsing these stages into one success signal is unsafe. An execution report can be valid while a settlement instruction still awaits data, securities, or cash. Identifying what each confirmation means allows support to communicate precisely what is known and what remains unproven. Examples throughout this pathway are fictional and do not describe procedures of a particular institution.
Guided application
For a project, draw a sequence containing actors, references, expected state, and observable evidence at every boundary. Include business teams when defining acceptance: a receipt message may not prove execution, and affirmation of details does not prove settlement. The DTCC affirmation example is specific to US processing; it does not impose one workflow on every market. PFMI principles address finality within financial market infrastructures, so a dashboard must respect the system-defined point rather than invent it from an ACK. On an incident bridge, assign coordination of the business outcome even when every component responds.
Example: a broker confirmed a purchase, but the custodian has not yet shown delivery. Reporting separates confirmed execution from unconfirmed settlement.
Common pitfalls
ACK treated as finality; affirmation treated as payment; server availability treated as complete flow.
Related topics: Reference and market data · FIX sessions and order state · Post-trade and settlement
Communicate stage, evidence, owner, and next check.
Reference: Principles for Financial Market Infrastructures · DR financial markets technology professional assessment2026.10