Home / DPA Insights / Post-Trade Operations
Europe Is About to Lose a Day. We have Seen Where to Find It
On 11 October 2027, the UK, the EU and Switzerland moved to T+1 securities settlement. For operations teams, that isn’t just a policy change. It’s a morning that disappears.
From 11 October 2027, the UK, the EU and Switzerland settle securities on T+1. For operations teams, it is a morning that disappears. In the markets that moved first, settlement got faster. Daily custodian reconciliation did not. The checks were not the slow part. Getting the data ready was. Ask which steps need an analyst at all, not how analysts can go faster. File preparation and the first round of matching did not. A workflow must tell unsettled trades apart from real breaks. Otherwise it is technically correct and operationally useless. The firms that cope best will be the ones that stopped spending the morning getting ready to work.
We have already watched that morning disappear once.
A day gone, a process unchanged
When T+1 arrived in the markets that moved first, a client’s operations team faced a simple problem. Settlement got faster. Their daily custodian reconciliation didn’t. Every day, they compared accounting records with custodian files, checking quantities, amounts, security identifiers and settlement status.
The checks weren’t the slow part. Getting the data ready was. Files were copied, reformatted and lined up by hand before anyone could compare a single trade.
The work wasn’t the problem. The preparation was
We didn’t ask how analysts could go faster. We asked which steps needed an analyst at all. File preparation didn’t. Neither did the first round of matching. So, we built a workflow to clean custodian files, built a matching key from trade details to run the first pass on its own.
The mismatch that wasn’t
The first version cried wolf. It flagged every unmatched trade as a break, but many were simply trades that hadn’t settled yet. So, the workflow learned to tell the two apart. That took several rounds of testing, because small format quirks and blank fields kept raising false alarms.
Technically correct, operationally useless.
Analysts now start the day with a short list of real exceptions, sorted by cause, instead of a pile of files.
| Step | Before | After |
|---|---|---|
| File preparation | Copied, reformatted and lined up by hand | The workflow cleans custodian files |
| First round of matching | Done by analysts | A matching key built from trade details runs the first pass |
| Unsettled trades | First version flagged them as breaks | The workflow tells them apart from real breaks |
| How the day starts | A pile of files | A short list of real exceptions, sorted by cause |
What Europe can take from this
Most T+1 planning focuses on trade day. Allocations, confirmations, funding. Those matter. But a shorter cycle also squeezes the checks that come after, and those often run on manual prep nobody has ever measured.
The firms that cope best won’t be the ones whose people work fastest. They will be the ones who stopped spending the morning getting ready to work.
How much of your morning goes on getting ready?
If your team is planning for T+1, we can walk through where manual preparation sits in your post-trade checks before anyone talks about tooling.
Book a working sessionFrequently asked questions
When does Europe move to T+1 settlement?
The UK, the EU and Switzerland move to T+1 securities settlement on 11 October 2027. For operations teams, that is not just a policy change. It is a morning that disappears.
How does T+1 affect daily custodian reconciliation?
A shorter cycle also squeezes the checks that come after trade day. When T+1 arrived in the markets that moved first, settlement got faster but daily custodian reconciliation did not. Teams still compared accounting records with custodian files, checking quantities, amounts, security identifiers and settlement status.
What is the slowest part of custodian reconciliation?
Not the checks. Getting the data ready. Files were copied, reformatted and lined up by hand before anyone could compare a single trade.
How do you take manual work out of custodian reconciliation?
Ask which steps need an analyst at all. In this case, file preparation and the first round of matching did not. A workflow cleans the custodian files, and a matching key built from trade details runs the first pass on its own. Analysts start the day with a short list of real exceptions, sorted by cause.
Why does automated matching flag false breaks?
Because many unmatched trades have simply not settled yet. The first version flagged every unmatched trade as a break. The workflow had to learn to tell the two apart. That took several rounds of testing, because small format quirks and blank fields kept raising false alarms.
What should European firms add to their T+1 planning?
Most T+1 planning focuses on trade day: allocations, confirmations, funding. Those matter. But the checks that come after trade day often run on manual preparation that nobody has ever measured.
