EU T+1 settlement

T+1 means that securities transactions will settle one business day after the trade date instead of the current two (T+2). This significantly compresses post-trade timelines across allocation, confirmation, funding, FX, and settlement.

Recommendation: Clients should assume that most post-trade activities must be completed on trade date (T) and plan operational changes accordingly. Any current manual processes will need to be removed.

The EU and EEA markets are scheduled to transition to T+1 settlement on 11 October 2027. Market infrastructure changes, client testing, and process adjustments will take place throughout 2026 and 2027.

Recommendation: Treat October 2027 as a fixed regulatory deadline and finalize readiness well ahead of this date.

T+1 applies to transferable securities executed on EU trading venues and settled in EU-registered CSDs, such as equities, bonds and ETFs. OTC trades and most securities financing transactions (SFTs) are not legally mandated but are expected to align as market convention.

Recommendation: Clients should assess both mandated and non-mandated activities to avoid operational fragmentation.

The most significant impacts are earlier trade allocation and confirmation, tighter funding timelines, and reduced tolerance for exceptions. Manual or end-of-day processes that worked under T+2 will likely result in fails under T+1.

Recommendation: Increase automation and straight-through processing (STP) across the trade lifecycle. Make sure that availability of securities and cash as well as current place of safekeeping is known and considered already when a sell order is placed. Make sure to have processes that cater for high-quality counterparty SSI-data.

In a T+1 environment, settlement instructions must reach CSDs by 23:59 CET on trade date to be included in overnight settlement cycles. Late allocations or confirmations can cascade into missed settlement and funding deadlines.

Recommendation: Move allocations and confirmations as close to real-time as possible and no later than late evening on T.

Under the proposed timetable, EU settlement systems will begin settlement processing at 00:00 CET on settlement date, with harmonised DvP and FoP cut-offs later in the day. This maximises the available settlement window but requires readiness overnight.

Recommendation: Ensure systems, controls, and staffing models can support overnight and early-morning processing.

Yes, probably. This is dependent on the changes in the markets. Please see SEBs updated cut-off times below for the markets that have confirmed changes until this day and note that these deadlines are subject to change until the effective date.

SEB’s deadlines are not technical cut-offs; correctly formatted STP instructions received after SEB’s deadline but prior to the CSD cut-off will be processed.

Instructions submitted after the trade-date deadline will miss the first settlement cycles and are more likely to fail, generating operational risk and cash penalties. Opportunities to correct errors on settlement date are significantly reduced.

Recommendation: Aim for early instruction submission and proactive exception management on trade date.

T+1 creates tighter funding windows and may introduce new funding gaps, especially where assets settle on T+1 but cash inflows (e.g. fund subscrip

Recommendation: Implement real-time cash forecasting and review pre-funding arrangements with counterparties and custodians.

FX through Custody FX, the FX and security settlement deadline are combined in the SEB deadline for each market.

FX trades executed through CLS and linked to securities settlement must be submitted and matched in CLS by 22:00 CET, on trade date (T). Delays may result in overdraft charges.

Recommendation: For Custody FX, ensure that settlement instructions are submitted as soon as possible and before the applicable SEB settlement deadlines in each market. For CLS, ensure that cut-off times are aligned with both the underlying securities settlement timelines and CLS deadlines.

With less time to resolve mismatches, the risk of settlement fails increases if processes are not accelerated. The CSDR cash penalty regime remains in force, although temporary relief could be considered if systemic issues arise.

Recommendation: Focus on prevention through better data quality, automation, and earlier matching.

Partial settlement allows a transaction to settle in pieces when full securities or cash are not available, improving overall settlement efficiency. Under T+1, partial settlement is expected to become standard market practice.

Recommendation: Review and update internal policies to support and actively use partial settlement where appropriate.

Allegement reporting helps promptly identify missing or unmatched instructions.

Recommendation: Make full use of this tool to detect and resolve issues before settlement processing begins.

Correct and consistent population of key fields such as Place of Settlement (PSET), Place of Safekeeping (PSAF/SAFE), and transaction type is critical for automation and settlement efficiency. Poor static data is a common root cause of fails. SEB will incorporate the PSET and PSAF coding from client instructions and have that fully reflected through the chain of custody for transactions and holdings.

Recommendation: Conduct a data quality review and align messaging with established SMPG and industry standards.

In a T+1 environment, timely status and repair updates are critical because there is significantly less time to identify, investigate, and resolve settlement issues before the settlement deadline.

SEB will enhance client notifications for trade repairs, providing more timely updates and transparency into trade status and repair activities by giving clients greater visibility into why a trade is in repair and when issues have been resolved. This includes improvements to trade status narratives, repair reason workflows, and more detailed, customizable repair messaging within client reporting.

Recommendation: The objective is to enable clients to consume and act on repair notifications directly, improving operational efficiency, reducing manual investigations, and supporting faster exception management under the compressed T+1 settlement cycle.

For distributions, the ex-date and record date will fall on the same day under T+1, reducing the buffer for processing entitlements. This increases reliance on automated market claims and buyer protection processes.

Recommendation: Ensure corporate actions workflows and system capabilities are compatible with compressed timelines.

If fund subscription and redemption cycles remain longer than securities settlement, asset managers may need to fund positions earlier, increasing liquidity costs. Some funds may consider moving dealing cycles closer to T+1.

Recommendation: Assess the funding and operational impact of current dealing cycles and engage distributors early on potential changes.

No. Europe comprises multiple markets, CSDs, currencies, and operating models, meaning local nuances will remain despite harmonised principles. Clients must account for market-specific differences.

Recommendation: Build a detailed market-by-market impact assessment rather than assuming a single European model.

Industry-wide testing with FMIs, custodians, and counterparties will take place throughout 2027 to validate readiness under real-world conditions. This includes volume, stress, and fail-scenario testing. SEB intends to participate in the industry testing and to offer, but not require, clients to do the same.

Recommendation: Please make sure to inform SEB asap if you would like to perform testing.

In the June 2027 release, T2S will implement functionality requested by the EU T+1 Securities Financing workstream. The so-called T2S gating event will allow participants to instruct T2S to not allow certain transactions (mainly fixed income repo transactions) to settle until the gating event/settlement window occurs at 11.00. Please note that not all markets will support this functionality.

Although go-live is in 2027, 2026 is a critical year for design finalisation, system changes, and early testing. Clients that delay preparation risk operational disruption and higher costs. Please read and assess the recommendations in EU T+1 Implementation Handbook and CSDR RTS on Settlement Discipline requirements.

Recommendation: In addition to what is mentioned in the recommendations of this document, clients should now start readiness programmes, focusing on automation, data quality, liquidity management, and external dependency mapping.