T+1 Settlement: Why Trade Reconciliation Is Now a Same-Day Control

US markets are already operating on T+1 settlement, and the UK, EU, and Switzerland are preparing for the next major shift.

The burden now falls on the post-trade controls that confirm whether a trade is ready to settle. The previous two-day window gave firms more time to find breaks, correct trade details, chase counterparties, validate settlement instructions, and resolve exceptions before settlement.

That window is now considerably smaller.

Firms now need to find settlement-risk issues while there is still time to act. A trade break, incorrect SSI, missing allocation, or counterparty mismatch can become a settlement blocker much faster once trades have to settle one business day after execution.

Trade reconciliation now has to work as an early settlement-risk control. It needs to identify the breaks, missing details, and instruction issues that could stop a trade from settling cleanly.

This article explains how T+1 changes trade reconciliation, exception management, SSI quality, and the operational controls firms need to reduce failed trades.

What T+1 Settlement Changed for Post-Trade Operations

T+1 means securities transactions settle one business day after the trade date. That shorter cycle changes the operating rhythm across allocations, confirmations, affirmations, SSI validation, funding checks, and exception resolution.

The previous two-day window gave operations teams more room between execution and settlement. A break found the next morning could still be investigated, escalated, and corrected before it affected matching or settlement instruction. Teams also had more time to confirm account details, arrange cash or securities, and resolve counterparty disagreement.

That margin has now narrowed. Allocation details need to move faster. Confirmations and affirmations need tighter cut-offs. SSI checks need to happen before incorrect instructions travel downstream. Funding and inventory checks need clear ownership because delays can create settlement exposure quickly.

This creates a higher control standard for post-trade teams. Reconciliation needs to identify breaks early, show which issues affect settlement readiness, and route exceptions before the remaining window becomes too narrow.

Post-trade operations also need better evidence. Teams need to know when the break appeared, which field failed, who owns the fix, which system needs updating, and whether the trade is clear to settle. Those details have become same-day control requirements.

How T+1 Turns Trade Breaks Into Settlement Blockers

Trade reconciliation compares a firm’s internal trade records with the records held by brokers, custodians, counterparties, clearing venues, and settlement systems. The value of that comparison now depends on timing.

The shorter settlement cycle means unresolved breaks age faster. A trade economics mismatch, incorrect SSI, missing allocation, counterparty disagreement, late affirmation, or funding account mismatch has less time to be found, investigated, and corrected. What may once have been treated as a next-day clean-up issue can now become a direct settlement blocker.

This is where reconciliation becomes a settlement-risk control. If the trade details are wrong, the settlement instruction may be wrong. If the allocation is late, affirmation may be delayed. If the account or funding information is incomplete, the trade may fail even if the economics are correct.

A shrinking settlement cycle forces teams to front-load risk detection and flag breaks immediately. Teams need to see which issues could delay affirmation, disrupt funding, trigger counterparty disputes, or stop a trade from settling cleanly.

The T+1 Trade Reconciliation Process

A strong T+1 reconciliation process needs to find trade breaks early, identify the exceptions that could affect settlement, and move them to resolution quickly.

Achieving this standard requires a structured, seven-step approach:

1. Ingest trade data
   Pull trade records from OMS, EMS, middle-office platforms, custodians, brokers, counterparties, central matching utilities, and settlement systems. The aim is to bring every relevant version of the trade into one controlled view.
   
   
2. Normalise the data
   Standardise identifiers, timestamps, account details, instrument data, currencies, venues, product classifications, and SSI fields. Without this step, firms may create false breaks simply because different systems record the same trade in different formats.
   
3. Match trade records
   Compare the core economics and settlement details of each trade. This includes trade date, settlement date, quantity, price, counterparty, currency, account, place of settlement, and settlement instruction.
   
4. Identify and classify exceptions
   Separate timing differences from genuine breaks. Then classify each exception by break type, severity, owner, and potential settlement impact.
   
5. Prioritise settlement-critical breaks
   Not every break carries the same risk. Teams should focus first on issues that could block affirmation, settlement instruction, funding, delivery, or receipt.
   
6. Route and resolve exceptions
   Send each break to the right team with the trade details, supporting evidence, workflow ownership, and escalation rules. This reduces time lost to manual investigation and unclear responsibility.
   
7. Create an audit trail
   Record the break type, the field affected, the time it was detected, the owner assigned, the action taken, the systems updated, and whether the trade is clear for settlement. That history gives firms the evidence they need to demonstrate control, trace decisions, and show how breaks were resolved before settlement.
   

Common Trade Reconciliation Breaks Under T+1

T+1 turns familiar trade breaks into issues that can delay affirmation, disrupt funding, or block settlement much faster. Compressed settlement timelines make stale SSIs, late allocations, timing breaks, and counterparty mismatches harder to repair before settlement.

These are the issues firms need to identify before they move into the settlement path:

Same-Day Affirmation Raises the Bar for Reconciliation

T+1 also raises the bar for same-day affirmation. Allocations, confirmations, and affirmations need to happen much earlier because there is less time to repair errors before settlement.

The SEC’s T+1 amendments pushed institutional trade processing toward same-day completion. That raises the standard for trade-date controls across the post-trade chain. SIFMA guidance has also pointed to best-practice operating targets such as allocations by 7:00 p.m. ET and affirmation by 9:00 p.m. ET.

That makes late reconciliation much harder to defend. Once the affirmation window has passed, a trade break leaves the team with less time to correct the record, update instructions, contact the counterparty, or resolve a funding issue.

Same-day affirmation changes what reconciliation has to prove, and when it has to prove it. A break found tomorrow may already be too late. Reconciliation therefore needs to happen close to trade date, while there is still enough time to act on what it finds.

Why Manual Reconciliation Struggles After the Move to One-Day Settlement

Manual reconciliation can look workable when volumes are predictable, markets are calm, and exceptions are simple. The problem is that a one-day settlement window leaves much less room for slow processes to catch up.

Many manual reconciliation models still depend on spreadsheets, email-based break chasing, manual file uploads, end-of-day batch processing, and disconnected systems. They also often rely on sampled checks, informal ownership, weak escalation paths, and incomplete audit trails.

This setup can leave teams finding breaks in one place, assigning ownership somewhere else, and tracking resolution separately.

A break may be visible in one team’s spreadsheet while another team works from a different workflow. An exception may be emailed to the right person but never escalated when it remains unresolved. A settlement instruction may be corrected in one system but fail to update everywhere it needs to be.

Manual workflows become less reliable when volume, counterparty disagreement, funding pressure, custody dependencies, FX timing, and time-zone handoffs all converge.

These processes often surface the answer after the settlement window has already narrowed. By then, teams have less room to prevent failed trades.

Data Quality and SSI Accuracy Are Now Settlement-Critical

T+1 is far quicker to expose weak reference data. A longer settlement cycle gave teams more time to repair stale SSIs, missing identifiers, incorrect account details, and inconsistent instrument data.

Those same issues can delay affirmation, disrupt funding, or cause failed settlement once trades have to settle one business day after execution.

SSIs are a clear example of this. If custodian details are stale, the place of settlement is wrong, or the account number is incomplete, the trade may fail even when the economics are correct. The same applies when a counterparty identifier is missing, an LEI is inconsistent, instrument master data differs across systems, or account standing instructions point to the wrong settlement location.

Incorrect account, venue, instrument, or counterparty records can feed multiple workflows and trigger the same break across multiple trades. Teams then spend time repairing repeated exceptions instead of removing the data problem at source.

Reconciliation tools can identify those breaks, but structurally poor data still limits the extent of control the process can provide. Inconsistent, delayed, or fragmented source systems turn reconciliation into a constant repair exercise.

That is why firms need centralised SSI management, stronger reference-data checks, and clear data lineage across the post-trade process. A one-day settlement window leaves no room for bad data. What used to be a minor discrepancy swiftly escalates into funding pressure, missed affirmations, and costly settlement failures.

What Good T+1 Reconciliation Looks Like

Good T+1 reconciliation works as an active settlement-risk control. It helps teams detect breaks earlier, prioritise the exceptions that could affect settlement, assign ownership quickly, and capture evidence as issues are resolved.

A strong T+1 reconciliation process should include:

• Trade-date reconciliation that finds breaks before the settlement window has already narrowed.
• Automated ingestion from internal systems, brokers, custodians, counterparties, and settlement platforms.
• Field-level matching across trade economics, account details, settlement dates, currencies, venues, and SSIs.
• Automated SSI validation to catch stale, incomplete, or incorrect settlement instructions before they cause failures.
• Clear separation of timing breaks from true exceptions, helping teams avoid time lost to false positives.
• Prioritisation by settlement impact, so the most dangerous breaks are handled first.
• Ownership and escalation workflows that show who needs to act, by when, and with what information.
• Real-time or near-real-time dashboards showing open breaks, aging exceptions, and settlement risk.
• Evidence capture for every investigation, including actions taken and changes made.
• Integration with middle-office, back-office, and settlement workflows, so corrections flow through the operating model.
• Management visibility into unresolved breaks before they become failed trades.

How Automation Reduces Settlement Failure Risk

Automation gives firms the speed, consistency, and control discipline needed for T+1. Automated controls surface hidden discrepancies earlier and shorten the time needed to assign and resolve open exceptions.

After the US move to T+1, industry data showed that the transition was smoother than many expected. Around 95% of transactions were meeting affirmation criteria by the 9:00 p.m. ET cutoff, fail rates stayed broadly in line with T+2 norms, and the NSCC Clearing Fund was reduced by roughly 23%. Those results point to the value of stronger preparation, better controls, and earlier trade processing.

For individual firms, automation reduces settlement risk by checking every trade instead of relying on samples. It detects breaks earlier, classifies exceptions consistently, and highlights the issues most likely to affect affirmation, funding, delivery, or receipt.

It also reduces the manual handoffs that slow teams down. Exceptions can be routed to the right owner, escalated when unresolved, and tracked with timestamps and evidence. Managers can monitor completion rates, aging breaks, and settlement exposure before the end-of-day update cycle.

As T+1 expands across more markets, this control discipline becomes even more important. Firms need reconciliation processes that can adapt across jurisdictions while keeping manual strain under control.

What to Look for in a T+1 Reconciliation Solution

A T+1 reconciliation solution should help teams find, prioritise, and resolve settlement-risk issues earlier in the trade lifecycle. It should give operations teams clear control over the breaks that can delay affirmation, disrupt funding, or stop settlement.

Preparing for the Next Wave of T+1

North America is already operating on T+1. The next major wave is now taking shape across the UK, EU, and Switzerland, which are preparing for a coordinated move in 2027.

Cross-border firms cannot treat the next move to one-day settlement as a local market change.

A shorter settlement cycle affects funding, FX, securities lending, custody arrangements, regional operating models, and time-zone handoffs. A break in one market can create pressure elsewhere when data, instructions, or cash are not ready in time.

The US transition gives firms a live operating case to learn from. It showed that one-day settlement is manageable when firms prepare the post-trade process properly and move key controls earlier in the lifecycle.

The next wave of T+1 is bigger than a local compliance project. It is an opportunity to fix fragmented post-trade controls globally before compressed timelines make those weaknesses more expensive.

Conclusion: Reconciliation Now Has to Move at Settlement Speed

T+1 has made reconciliation more time-sensitive, operational, and closely tied to settlement resilience. Firms need to detect and resolve breaks early enough to prevent failed trades, reduce escalations, and protect the settlement process.

Firms need clean data, automated matching, fast exception routing, and audit-ready controls that show how settlement issues were found and resolved.

Learn how Gresham helps capital markets firms strengthen reconciliation, exception management, and post-trade control in a T+1 environment.