T+1 equity settlement took effect in the United States on May 28, 2024, compressing the standard settlement window from T+2 to T+1 for most US equity and corporate bond transactions. The regulatory announcement generated a significant amount of industry commentary about technology upgrades and systemic readiness. What generated less attention was what happens operationally on the desks that were already running their reconciliation workflow on a manual email-to-spreadsheet process with T+2 slack. That process does not work on T+1. This article is about what actually needs to change, not on paper but in daily workflow.
What the Compression Actually Removes
Under T+2, an equity trade executed on Monday settles on Wednesday. That gave the ops desk all of Monday afternoon, all of Tuesday, and Wednesday morning to reconcile the confirm, identify any breaks, communicate with the counterparty, and issue or confirm the settlement instruction. In practice, most well-run desks completed reconciliation by close of business Tuesday, which left Wednesday as a buffer for unexpected counterparty disputes.
Under T+1, the same Monday trade settles Tuesday. The ops desk has Monday afternoon and Tuesday morning before the cutoff. Monday afternoon is when most same-day confirm emails arrive. Tuesday morning is the last window for break identification and resolution before settlement instructions are final.
The buffer is gone. A desk that was reconciling by end of day T+1 under the old cycle and relying on T+2 as a safety day is now reconciling on the only day there is. A desk that was doing reconciliation on T+2 morning is no longer reconciling at all in any meaningful sense; settlement instruction is already in progress when they start.
The Morning Routine That Breaks First
The most common T+1 failure mode is not technical. It is the morning routine. A typical manual reconciliation workflow looks like this: confirms arrive by email on trade date, the ops analyst downloads them after opening, enters fields into the position spreadsheet by cross-referencing the blotter, identifies mismatches, sends counterparty emails requesting corrections, and waits for responses.
Under T+2, counterparty corrections requested on trade date could be resolved on T+1 and still leave the desk with a day of buffer. Under T+1, a counterparty email correction request sent on trade date at 4pm may not receive a response until T+1 morning, which is also the same day settlement instructions are finalized. If the confirm is wrong and the counterparty is slow to respond, the position settles incorrectly.
The morning routine that had slack now has none. Anything that required "I'll send a note today and handle it tomorrow" needs a same-day or same-hour resolution workflow instead.
Confirm Receipt Time Matters More Than It Did
Under T+2, a confirm that arrived by email at 5pm on trade date was fine. There was time to process it the next morning. Under T+1, a confirm received at 5pm on trade date gives the desk overnight to spot a discrepancy, but that analysis needs to happen in the early morning of settlement day, not at noon. If the desk's process is to work through confirms sequentially as bandwidth allows, late-arriving confirms that get processed last will be the ones most likely to miss the resolution window.
The operational response to this is prioritization: confirms on positions with the largest settlement exposure should be matched first, regardless of arrival time. That sounds obvious but it requires that the matching process is structured enough to support it. In a spreadsheet workflow, confirms typically get processed in the order they were received. Reordering the queue by risk exposure requires a different tool or a dedicated step in the process.
A secondary response is early confirm requests. For positions where the counterparty historically sends confirms late in the afternoon, a desk running T+1 settlement has an incentive to reach out and request earlier transmission. Some counterparties will accommodate this; others operate on their own schedule. Knowing which counterparties are systematically late confirm senders, and which of those late confirms are on high-value positions, is a piece of operational data that is invisible on a spreadsheet but straightforward to surface with automated ingest tracking.
What Has to Change in the Matching Step
The T+2 reconciliation workflow could absorb a partial matching run on trade date followed by a cleanup run on T+1 morning. That cadence does not work for T+1. The effective approach is to run matching as soon as confirms arrive and surface breaks immediately, not at a scheduled batch time.
This means the matching step needs to run continuously during market hours rather than as an end-of-day batch. A confirm that arrives at 2pm on trade date should be matched against the position record at 2pm, not at 6pm or 8am the following morning. If there is a discrepancy, the desk needs those hours for counterparty resolution, not to discover the discrepancy later.
Continuous matching also means alert delivery needs to change. An end-of-day break report is insufficient when the break needs to be resolved within hours. Alerts for breaks on T+1 positions should fire at the time of match failure, routed to whoever on the desk is responsible for that counterparty or instrument type. Waiting for a scheduled report means the desk may have already lost several hours of resolution window before the break is visible.
Affirmation Deadlines Are Now a Hard Constraint
DTC's Institutional Delivery system requires affirmation of institutional trades by 11:30am ET on settlement date for guaranteed settlement status. Under T+2, that affirmation deadline was T+2 morning, which typically meant trade date plus two nights for the desk to complete matching and submit the affirmation. Under T+1, the affirmation deadline is trade date plus one night.
The practical consequence is that any break discovered after 11:30am on T+1 day either misses the affirmation deadline, goes to extended settlement, or fails. Extended settlement is not just an operational inconvenience; it carries interest charges and may trigger reporting obligations depending on the position size and the regulatory framework the desk operates under. The 11:30am DTC affirmation deadline is not a soft target.
Desks that were not paying close attention to the DTC affirmation deadline under T+2, because there was time to catch misses before settlement, need to treat that deadline as a hard constraint under T+1. The reconciliation and break-resolution workflow needs to be complete before 11:30am on settlement date, which means it needs to start earlier, run faster, or both.
The Desks Where This Is Not a Problem
Some desks transitioned to T+1 without significant operational change. The common characteristic of those desks is that their reconciliation was already running close to real-time on trade date. If confirms were being matched and breaks surfaced within hours of execution, the T+1 compression did not remove any meaningful operational window because the desk was not relying on T+2 for buffer time.
The desks where T+1 created genuine operational stress are those where reconciliation had been running on a next-morning batch cadence, relying on the two-day settlement window as insurance. That workflow is not compatible with T+1 for equities. It remains workable for instruments that still settle T+2, but as T+1 expands to cover more instrument types over time, the cadence needs to change across the book.
The question worth asking now, before the next settlement cycle compression, is whether the current reconciliation process could handle T+0 settlement on a subset of positions. Same-day settlement is not a near-term regulatory requirement for most instruments, but the trend in global settlement policy is toward shorter cycles. Building the operational capability to match confirms and resolve breaks within hours of execution is the preparation for whatever cycle compression comes next, and it is the capability that eliminates the 4pm fail under the current T+1 framework.
