Trade Confirmation vs Trade Affirmation

Trade confirmation and trade affirmation are related post-trade steps, but they are not automatically the same event. A confirmation communicates or records the economic terms of a transaction, while affirmation generally represents agreement or validation of those terms by the relevant parties or workflow. The exact meaning, participants, timing and system names vary by market, asset class and institution. This article gives a high-level operations explanation using fictional records and is not a settlement instruction or investment recommendation.

Confirmation in the post-trade workflow

A confirmation helps the parties see the terms that were captured for the trade. It may include instrument, quantity, price, side, currency, dates, counterparty, account and settlement details appropriate to the transaction. Operations teams compare the confirmation to the source instruction or execution record and investigate differences. A confirmation that was sent is not proof that every party agreed or that settlement will complete.

Affirmation in the post-trade workflow

Affirmation generally indicates that the relevant party or process has reviewed and agreed to the terms needed for the next stage. In some workflows it is performed by an investment manager, broker, custodian or matching service; in others, the terms may be matched through a platform. The analyst follows the applicable process and records the status. They should not call a trade affirmed when only a confirmation was generated.

The difference at a glance

• Confirmation: communicates or records the trade terms for review.
• Affirmation: indicates agreement or validation by the relevant party or workflow.
• Matching: compares records and can reveal a break before settlement.
• Settlement: moves cash or securities according to the authorised instruction and applicable market process.
• Exception: requires evidence, ownership, ageing and escalation rather than an assumed status change.

A fictional mismatch

A fictional confirmation shows a settlement date one day later than the investment manager's source instruction. The operations analyst compares the two records, checks the market and account context available under policy, and routes the mismatch for an authorised decision. They do not alter the date because a later settlement appears convenient. The case remains unaffirmed until the relevant party or workflow confirms the corrected terms. The parties and dates are invented.

Preventing confirmation and affirmation breaks

Break prevention starts before the confirmation is sent. The source instruction, captured trade, reference data and counterparty details should use controlled fields and a clear owner. After the confirmation, matching status should distinguish not sent, sent, received, disputed, affirmed and rejected when those states apply. Ageing reports help the team focus on breaks that could affect settlement. The analyst should avoid closing a case because a later system shows a different status without tracing the relationship between the records.

• Compare the economic terms before calling a record matched.
• Check the source and recipient for the confirmation.
• Record who affirmed or rejected the terms through the authorised workflow.
• Escalate a date, account, counterparty or currency mismatch.
• Confirm the downstream settlement impact after a correction.

Read the trade lifecycle guide

See a worked trade settlement break

Explore securities operations roles

For an interview answer, distinguish the communication of terms from agreement, then explain how a mismatch is evidenced and escalated before settlement. Use the institution's current terminology because workflows differ. Centaur Careers publishes this article for education; it is not investment, trading, legal or settlement advice.