On 11 October 2027, the EU, the United Kingdom and Switzerland plan to move securities settlement from two business days after the trade to one. The United States made the same change on 28 May 2024. For firms with European activity, the question is no longer whether, but whether their systems are ready.
T+1 sounds like a small change. It halves the time between a trade and its settlement. Every process that sits in that window, from allocation and confirmation to funding, currency and securities lending, now has half the time. Problems that used to be solved overnight move into the working day.
Here are five places to look first.
1. Map every process that assumes a day in between
Start with an inventory, not a project plan. List every step between trade capture and settlement, and mark the ones that rely on the time T+2 gave you: a batch that runs overnight, a manual check the next morning, an email to a custodian, a spreadsheet someone fills in before lunch.
Most firms find that the risk is not in the trading platform itself, but in the small manual steps around it. Those are the ones to automate or move earlier.
2. Move confirmation and allocation earlier in the day
Under T+1, trades need to be allocated, confirmed and matched on trade date. Late allocations are the most common reason a trade misses the shorter window. Look at when allocations arrive from investment managers, how confirmations are matched, and which exceptions wait for the next day.
The target is simple to state: every trade allocated, confirmed and matched before the end of trade date.
3. Find the batch jobs that become too slow
Many post-trade systems were designed around end-of-day batches. With one day less, a batch that finished comfortably overnight may now sit in the critical path. Measure how long each job really takes on a busy day, not an average one, and decide which must become intraday or event-driven.
The same applies to data. Static data, settlement instructions and reference data must be correct before the trade, not fixed afterwards.
4. Rehearse funding and currency for the shorter window
For cross-border trades, the currency trade that funds a securities purchase has less time to settle. Treasury and operations teams need to know their cut-off times with each counterparty and each settlement system, and test what happens when a market is closed or a payment arrives late.
Run the rehearsal on a normal day and on the worst day you can imagine: month-end, a holiday in one market, a large corporate action.
5. Measure settlement fails before and after
You cannot manage what you do not measure. Record today's settlement fail rate by market, counterparty and reason. After the change, measure it again. The difference tells you where the remaining work is, and gives you evidence for your management and your regulator.
Where technology helps
Most of the work is operational, but technology decides how hard it is. Event-driven processing instead of overnight batches, automated matching, clean reference data and good monitoring all reduce the number of trades that need a person to look at them. AI agents can help with the remaining exceptions: sorting breaks by likely cause and drafting the fix, while a person approves what is sent.
T+1 rewards firms that treat it as an engineering problem early, rather than an operations problem late.