T+1 settlement will break your operating model — here's how to find out before it does

The UK moves to T+1 securities settlement on 11 October 2027. Most asset managers are treating this as a technology project. Simply: upgrade the settlement system, adjust the SWIFT messages, done. They're wrong.

This is a stress test of your operating model, rather than a menial settlement problem. The firms that pass it won't be the ones with the best technology. They'll be the ones that understand where their operating model actually breaks under pressure.

The hidden assumption in every operating model

Every operating model has a speed assumption baked into its design. It's rarely documented, never measured, but it's there: how long does it take for information to move from one end of the model to the other?

Most asset management operating models were designed for T+3, retrofitted for T+2, and are now being asked to run at T+1. The difference isn't measured in days. It's the elimination of every buffer, every manual check, every “let me get back to you on Monday” that would otherwise have been available.

The question isn't whether you can settle faster. It's asking where your operating model breaks when you remove every buffer.

Three layers, three failure modes

The Architecture Canvas methodology — which opmodal uses to map operating models in insurance and asset management — identifies three layers where T+1 pressure will land. Most firms are only looking at one.

Layer 1: Process — the hand-off problem

Settlement involves dozens of hand-offs: trade confirmation, allocation, FX execution, settlement instruction, custody acknowledgement, reconciliation. Each hand-off has a design-time assumption. Under T+2, a confirmation that takes four hours is, broadly speaking, fine. Under T+1, it's a dangerous bottleneck.

The fix isn't to make each step faster. It's to eliminate steps. The firms that will succeed are the ones asking: “does this hand-off need to exist at all, or is it an artefact of a T+2 world?”

Layer 2: Systems — the interface problem

OMS, EMS, custody, accounting, data warehouse. These systems were built for batch processing. End-of-day files. Overnight reconciliation. The interfaces between them assume they have time that no longer exists.

The Architecture Canvas's “system-to-process mapping” exercise, which connects every process step to the specific system it touches, reveals which interfaces are on the critical path. Most firms have never done this exercise. They're about to discover that their settlement flow touches 14 systems, 9 of which were never designed to talk to each other in real time.

Layer 3: People — the exception problem

An uncomfortable truth is that your ops team handles exceptions by having time. When a trade fails to match, someone investigates, calls the broker, and resolves it. Under T+2, they have hours. Under T+1, they only have minutes.

The exception volume won't change. The time to resolve them will. The firms that haven't mapped their exception-handling workflows — who handles what, how, with which systems, under which escalation paths — will discover their bottlenecks on 12 October 2027, when the settlement failures start to pile up.

The Architecture Canvas approach

At opmodal, we map operating models layer by layer — not function by function.

A function-by-function review looks at the settlements team and asks “are they ready for T+1?” — and in doing so misses the fact that the settlements team depends on the confirmations team, which depends on the trading desk, which depends on the portfolio manager, who's in a different time zone.

A layer-by-layer review asks: “trace a trade from execution to settlement. Where does it touch a system that's batch-only? Where does it cross a team boundary that adds a day? Where does it wait for a person who works 9-to-5 in a different time zone?”

The firms doing this work now, in August 2026, with 14 months to go, will discover their breaking points, fix them, and test them. The firms waiting until Q3 2027 will discover them live.

The litmus test

Ask your operations team one question: “if we had to settle every trade tomorrow morning, what would break first?”

If they can answer immediately, then you're already doing the work. If they need a workshop to figure it out, book the workshop. If they say “nothing would break,” ask someone else.