Settlement cycles are the least glamorous subject in capital markets. They are also the constraint that quietly determines how much cash a firm must hold idle, how much counterparty risk sits on the books overnight, and how many people are awake at 2 a.m. reconciling breaks. When the North American markets moved from T+2 to T+1, most retail investors noticed nothing. Operations teams rebuilt half their workflow.
Why a single day matters so much
The intuition that “one day faster” is a marginal change misses what the day was being used for. Under T+2, the gap between trade and settlement absorbed an enormous amount of slack: allocation errors got caught, FX for cross-border purchases got arranged, securities lending recalls got processed, and mismatched standing settlement instructions got repaired. Compressing to T+1 does not remove that work. It removes the buffer in which the work happened.
The effect is asymmetric. A domestic institution trading domestic equities absorbs the change with modest process tightening. A European asset manager buying US equities faces something closer to a structural problem: the FX to fund the purchase now has to be executed and settled in a window that may not overlap with the liquidity hours of the currency pair involved.
Where the pressure actually lands
- Affirmation deadlines. Trade allocation and affirmation must complete on trade date. Batch processes that ran overnight now have to run intraday, which usually means they have to be rewritten rather than rescheduled.
- Funding and FX. Pre-funding requirements rise. Some managers hold a standing currency buffer rather than trying to execute FX inside the compressed window — a real cost that shows up as drag on returns.
- Securities lending. Recalls that used to have a comfortable margin now need to be issued near-immediately, which raises the operational cost of running a lending programme at all.
- Fails management. Less time to repair a break means more breaks reach settlement. Fail rates ticked up initially in every market that has made this transition.
The automation forcing function
What makes shortened settlement interesting as a case study is that it works as a mandate for automation that no internal business case could have produced. For years, operations leaders have argued for replacing manual affirmation and email-based instruction repair. The projects lost every budget cycle to something revenue-facing. A regulatory deadline does what a cost-benefit analysis could not.
The measurable outcomes have been consistent across markets: same-day affirmation rates climbing well above 90%, standing settlement instruction databases finally getting cleaned, and a meaningful reduction in the manual touch rate per trade. The initial spike in fails typically normalises within a couple of quarters, and post-transition fail rates often end up below the pre-transition baseline — because the automation that the deadline forced was genuinely better than the manual process it replaced.
What comes next
The obvious question is whether T+0 — atomic settlement — is the destination. Technically it is achievable; several tokenised settlement pilots have demonstrated it. Economically it is far less clearly desirable. Netting is the reason. Under a T+1 regime with end-of-day netting, a broker settling ten thousand offsetting trades moves a small fraction of the gross notional. Under true atomic settlement, every trade is funded gross, and the intraday liquidity requirement explodes.
Faster settlement reduces counterparty risk and increases liquidity risk. There is no cycle length that minimises both, only a choice about which one you would rather manage.
The likely equilibrium is not T+0 everywhere but T+0 as an option for participants who want it and can fund it, sitting alongside a netted default cycle for everyone else. That is a messier answer than a headline reform, which is usually a sign it is the right one.