AMI-SeCo Urges Swift to Align Securities Messaging Upgrade with June 2027 TARGET Release

Key Takeaways

• The ECB, through AMI-SeCo, has asked Swift to synchronize its deferred SR 2026 securities message upgrade with the TARGET Services June 2027 release.
• The ECB concluded that Swift's currently planned Q1 2027 deployment could severely disrupt testing for the T+1 changes in that release.
• Compliance and operations teams should expect possible timeline shifts and prepare for uncertainty until Swift confirms its final date.

Deep Dive

The ECB, through AMI-SeCo, has asked Swift to synchronize its deferred SR 2026 securities message upgrade with the TARGET Services June 2027 release. The ECB concluded that Swift's currently planned Q1 2027 deployment could severely disrupt testing for the T+1 changes in that release. Compliance and operations teams should expect possible timeline shifts and prepare for uncertainty until Swift confirms its final date.

Swift deferred its Standards Release (SR) 2026 and indicated that the securities-related changes, including those supporting T+1, would be implemented in Q1 2027, with a final date to be confirmed by mid-September 2026. The Eurosystem is proceeding with its November 2026 TARGET Services releases, but the deployment date has moved from November 14 to November 28, 2026. After consulting market stakeholders, the ECB concluded that a Q1 2027 Swift deployment could severely affect testing for the TARGET Services June 2027 release, which contains T+1 changes. AMI-SeCo has therefore asked Swift, by letter, to align the SR 2026 deployment with the June 2027 release. AMI-SeCo also acknowledged that further analysis is needed on the wider implications of this approach.

Important dates are the November 28, 2026 TARGET deployment, Swift's mid-September 2026 confirmation of its final implementation date, the Q1 2027 securities deployment currently envisaged by Swift, and the June 2027 TARGET Services release. Swift's decision is still pending, and the request is not binding on Swift. Firms therefore face two plausible scenarios, and the wider implications of alignment remain unassessed.

Compliance and operational resilience teams should take these steps:
- Monitor Swift's announcement of the final SR 2026 date and any ECB or AMI-SeCo follow-up.
- Reassess T+1 program plans, test schedules, and resource allocation under both an early (Q1 2027) and an aligned (June 2027) scenario.
- Confirm readiness with vendors, custodians, and market infrastructure counterparties for the revised November 28, 2026 TARGET deployment.
- Document change-management decisions and governance approvals to demonstrate prudent oversight.
- Engage with industry associations to provide feedback on the wider implications AMI-SeCo has flagged.

The main risks are operational and execution-related. Compressed or overlapping testing windows increase the chance of defects, settlement failures, and missed T+1 readiness milestones. Conversely, a delay in the securities message upgrade could require rework of build and testing plans already underway. Regulatory risk is moderate: firms are still expected to be T+1 ready, so poor coordination could lead to supervisory scrutiny if settlement efficiency deteriorates after migration.

Source: European Central Bank