The accelerated settlement cycle does not forgive delay. Allocations, confirmations, funding, recalls, settlement instructions and exception handling must work earlier, faster and with more evidence than under T+2.
Overview
The move from T+2 to T+1 is not a simple calendar change. It compresses the entire post-trade operating model and forces every participant to complete activities that were already difficult under a longer settlement window: allocation, confirmation, standing settlement instruction validation, FX funding, securities lending recalls, collateral movements, corporate action processing and fail remediation.
Europe, including the EU, the UK and Switzerland, is preparing for a coordinated transition to a T+1 settlement cycle on 11 October 2027. For Swiss and Liechtenstein markets, market-level recommendations have already been published to support readiness and reduce cross-border inconsistencies. The implication for banks, asset managers, brokers and custodians is clear: waiting until the final year means turning a transformation into an emergency.
The institutions most exposed are not necessarily those with the highest trade volumes. The highest risk sits where post-trade still depends on manual matching, email-based exception handling, incomplete SSIs, late trade enrichment, fragmented reconciliation or unclear ownership between front office, middle office, operations, treasury and technology. In a T+1 environment, the margin for rework disappears.
Why T+1 changes the back office
Under T+1, the trade date becomes operationally decisive. Errors that could previously be corrected on the following day must be identified, escalated and resolved almost immediately. Time-zone differences, cross-border portfolios and FX funding chains can reduce the effective operational window even further. This is why T+1 readiness is not only a securities operations topic: it also concerns treasury, liquidity management, data governance, client servicing, outsourcing, vendor platforms and control evidence.
The most visible impact will be on settlement efficiency. Late matching, failed settlement instructions, missing SSIs and unresolved breaks can trigger a chain reaction: higher fails, penalties, manual interventions, liquidity buffers and reputational exposure with counterparties and clients. The less visible impact is on governance. Institutions will need to prove that processes have been redesigned, that exceptions are actively managed, and that root causes are monitored rather than repeatedly corrected case by case.
Corporate actions, buyer protection and market claims also become more sensitive. SwissSPTC recommendations explicitly refer to increased automation, aligned timelines and partial settlement as key operational adaptations. In practical terms, institutions need to move from manual, reactive servicing to automated, pre-controlled processing.
Operational pressure points
The first pressure point is trade enrichment. If trade data is incomplete at capture, the compressed settlement cycle leaves insufficient time for downstream teams to repair it. This includes counterparty data, place of settlement, account details, instrument data, client allocation, FX funding requirements and corporate action flags.
The second pressure point is exception management. A T+1 model requires same-day ownership, prioritization and escalation. Exceptions must be classified by settlement impact, financial exposure and client sensitivity. Dashboards must distinguish between breaks that can be monitored and breaks that can create a fail within hours.
The third pressure point is liquidity. The shorter cycle reduces counterparty risk but can increase intraday funding pressure. Treasury teams need earlier visibility of settlement cash needs, especially across currencies with different operating hours. Liquidity buffers should be based on evidence, not on blanket assumptions.
What readiness should look like
A credible T+1 readiness program starts with an end-to-end impact assessment. It should map all relevant instruments, markets, counterparties, systems, custodians, vendors and outsourced activities. It should then identify where settlement, reconciliation, asset servicing and liquidity processes are still dependent on manual intervention.
The target state should prioritize straight-through processing, automated matching, electronic confirmations, standardized SSIs, early exception detection, partial settlement readiness and disciplined cut-off management. Where manual controls remain necessary, they should be intentional, documented and measured.
Institutions should also establish a T+1 governance forum with representatives from operations, treasury, technology, risk, compliance, client service and business lines. The objective is not to create another project committee. It is to make daily operational readiness visible to decision-makers before go-live pressure starts.
How to move from assessment to execution
The practical sequence is simple but demanding. First, identify the scope. Second, quantify current settlement performance and root causes of fails. Third, redesign trade-date and post-trade activities around the new cut-offs. Fourth, implement automation where it materially reduces settlement risk. Fifth, run internal and market-wide testing. Sixth, establish live-readiness dashboards for senior management.
The institutions that will be ready are those that treat T+1 as a controlled operating model redesign. The institutions that will struggle are those that treat it as a system parameter update.
Our Approach
- T+1 Impact Assessment - Map impacted markets, instruments, counterparties, custodians, vendors, processes and systems across the full post-trade lifecycle.
- Settlement Efficiency Diagnostics - Measure fails, late matching, breaks, missing SSIs, manual repairs, funding delays and root causes by product and counterparty.
- Operating Model Redesign - Redesign trade-date processing, allocation, confirmation, settlement instruction release, exception ownership and escalation paths.
- Automation and Control Evidence - Define STP improvements, dashboards, KPIs, control evidence and management reporting for audit-ready readiness.
- Testing and Go-Live Support - Support internal testing, community testing, dry runs, defect remediation and cut-over planning.
