Trade Break Before Settlement: A Worked Investigation

A trade break before settlement is an unresolved difference between records that should describe the same transaction. In this worked example, an internal record and a queued instruction show 100 practice shares, while a counterparty confirmation shows 10. No settlement failure has occurred in this packet: the instruction is still queued. An operations analyst should quantify the break, check the original evidence and possible amendments, log the exception, and route the decision to the authorised owner. The analyst should not overwrite a source record or declare the trade agreed simply to make records match.

Every company name, instrument, reference, date, price and status below is fictional. The exercise teaches an investigation method; it is not a rule for any exchange, clearing system, counterparty or employer. The example uses a simplified gross amount of quantity multiplied by price, with taxes and fees excluded.

Download the four source records and try the case

Download the CSV first and compare the rows for simulated trade SIM-1042. Work out which fields match, which differ, the numerical size of each difference, and whether the available evidence lets you close the exception. Keep the answer key closed until you have written a short case note.

Download the fictional trade-break source records (CSV)

• Execution note SIM-EX-01: buy 100 Practice Share P units at INR 250, gross INR 25,000; approval of the original execution still needs checking.
• Internal capture SIM-INT-02: buy 100 units at INR 250, gross INR 25,000; confirmation remains pending.
• Counterparty confirmation SIM-CP-03: buy 10 units at INR 250, gross INR 2,500; marked unmatched.
• Queued settlement instruction SIM-SET-04: 100 units and INR 25,000; its release depends on the employer's control and approval process.

Step 1: identify and calculate the trade break

First confirm that the rows refer to the same simulated trade: reference SIM-1042, instrument, buy side, trade date and exercise settlement date. Then compare the economic fields. The quantity difference between 100 and 10 is 90 shares. At INR 250 per share, the simplified gross-amount difference is INR 22,500. The price does not differ. This points the investigation toward quantity, allocation or record version, but it does not prove which party's record is wrong.

Step 2: trace evidence without forcing a match

The execution note and internal capture both show 100, but a second internal record is not independent proof that the counterparty confirmation is a typo. Check the approved execution, allocation history, any amendments, the record versions and whether all four rows truly belong to the same instruction. Ask the designated trade owner or counterparty contact to verify the disputed quantity through the approved channel. A ten-share allocation, stale confirmation or capture error would lead to different corrective action.

See where confirmation and settlement sit in the trade lifecycle

Step 3: log the exception and escalate the decision

A useful exception log records the source IDs, 90-share and INR 22,500 differences, time found, current status, evidence checked, owner, deadline and next action. Refer the queued instruction to the authorised settlement-control owner. Whether processing is paused depends on the team's procedure and delegated authority; the learner in this case cannot release, cancel or alter a real instruction. Keep both original records visible so another reviewer can retrace the issue.

Step 4: verify resolution and close the trail

When the authorised parties establish the agreed trade details, any correction must follow their controlled process. Compare the revised confirmation with the approved trade and settlement instruction, record the change and approval, and check the final status. If the break cannot be resolved by the applicable cut-off, escalate it rather than closing it as a timing difference by guesswork. This is why a good answer ends with a verification step, not merely a request for a corrected file.

Download the worked answer key and model note (TXT)

Self-check your investigation

1. Did you match the identifiers and scope before comparing quantities?
2. Did you calculate both 90 shares and INR 22,500 gross without adding unsupported fees?
3. Did you test allocation, amendment, version and capture possibilities rather than assuming a typo?
4. Did you state what to record and who must decide on the queued instruction?
5. Did you require an authorised correction, a recheck and a final audit trail before closure?

Give yourself one point per item you can explain aloud. The five-point score is a learning aid, not an employer assessment. A common weak answer is to change 10 to 100 immediately: that erases the evidence of the mismatch and claims an authority the analyst may not have.

Learn the broader reconciliation process for unmatched records

Explore the investment banking operations analyst role

How this practice connects to a course decision

If this kind of comparison, evidence handling and escalation interests you, inspect the current Financial Operations Masterclass curriculum for trade settlement and reconciliation practice. Ask how learners receive feedback on an exception note and what the programme actually covers. A fictional exercise on this page does not establish job readiness or a particular employer outcome.

Review the Financial Operations Masterclass curriculum

For market context, SEBI's investor education asks investors to retain and check trade confirmations. This case is an original operations learning example, not a quotation from a provider or a statement of a universal settlement procedure.

Read SEBI's investor guidance on trade confirmations