ISO 20022 Migration
ISO 20022 migration timeline: 2027–2030
| Deadline | What changes | SWIFT in-flow translation |
|---|---|---|
| Jun 2027 — SR2026 | SR2026 goes live in June 2027, not in the usual November release window. MT101 end of coexistence for FI-to-FI over FIN (→ pain.001); structured / hybrid postal addresses become mandatory (Town and Country structured). | Single MT101 auto-translated for a fee; multi-instruction MT101 rejected (NAK) |
| Nov 2027 — E&I | Exceptions & Investigations move to Case Management — camt.110 / camt.111, cancellations camt.056 / camt.029. Statement (MT9xx) receipt capability also required. | No in-flow translation for E&I |
| SR2028 — Nov 2028 | End of coexistence for statements (MT940 / MT942 / MT950 → camt.053 / camt.052), direct debits (MT104 → pain.008 / pacs.003) and charges (MT19x → camt.105 / camt.106). | SWIFT will not convert — ineligible messages rejected (NAK) |
| ~2030 — Securities | Securities migrate from ISO 15022 to ISO 20022; corporate actions become ISO-only and ISO 15022 is decommissioned (ECSDA CSDs). | No SWIFT service — vendor-provided |
ISO 20022 Address Structuring Engine
Structured and hybrid postal addresses are becoming mandatory in CBPR+ and HVPS+. MT party fields and MX address lines often carry the town and country as free text, mixed in with the street, the building and the postcode.
The Address Structuring Engine turns that free text into structured town and country, so outgoing messages meet the new address rules without changing back-office systems. It will be released ahead of the address deadlines, with time for banks to upgrade and test.
Deterministic and auditable
Rule-based over versioned reference data, with no AI model. The same input always produces the same address, and every change can be explained.
On-premise
Runs inside your Prowide deployment. Customer addresses never leave your infrastructure.
In translation and in the Hub
Available as part of MT to MX translation and as a Messaging Hub workflow action that can flag, auto-apply or hold the change for approval.
Automatic bidirectional translation
Prowide's translation engine converts between MT and MX automatically, covering 40+ message pairs with full round-trip fidelity. Translation rules come from the official ISO 20022 mapping specifications, extended with clearing-specific market practices.
FIN / ISO 15022
ISO 20022
TranslatorStandard packages
Every translation starts with a base standard. Clearing-specific translators are layered on top, inheriting the base rules and adding market-specific overrides.
| Standard | Description | Use Case |
|---|---|---|
| ISO | Pure ISO 20022 standard mapping | Generic translation, baseline for all derivatives |
| CBPR+ | Cross-Border Payments and Reporting Plus | SWIFT cross-border payments (the most common) |
| IAP | ISO Accelerator Package | Category 5 securities messages |
| SWIFTGO | SWIFT Go cross-border payments for consumers and small businesses | Payments sent under the SWIFT Go rulebook |
Truncation handling with full traceability
MX fields are richer than MT. When MX data does not fit MT field length limits, the engine truncates it according to SWIFT best practices and marks the field with a '+' indicator. A dedicated API returns a structured report of each truncation: the field, the original content and the truncated result. No business data is silently lost.
Clearing-specific translators
SIC
Swiss Interbank Clearing -- domestic CHF payments with SIC-specific translation rules
RITS
Reserve Bank Information and Transfer System -- AUD high-value payments
CHATS
Clearing House Automated Transfer System -- multi-currency RTGS
SCRIPS / MEPS+
Singapore clearing and MAS Electronic Payment System
T2 / T2S / EBA
Eurosystem T2 for high-value euro payments, T2S for securities settlement, and EBA Clearing EURO1 and STEP1
LYNX
Canada's high-value payment system operated by Payments Canada
FISC
Financial Information Service Co. -- Taiwan domestic payments
Fedwire
US Federal Reserve wire transfer system for high-value domestic payments
And More
New clearing-specific translators are added continuously, or can be configured via JSON on top of a base translator package
A progressive path to ISO 20022
Translation is the shortest path to compliance. It lets you meet MX requirements today without changing your back-office systems.
From there, Prowide supports a progressive migration. Convert proprietary formats directly into MX, move initiation to Messaging Hub message entry one message type at a time, and fade out translation as your processes produce and consume MX natively.
Phase 1 -- Translate
Deploy MT↔MX translation immediately. Back-office systems continue working with MT while the network migrates to MX. The fastest path to compliance.
Phase 2 -- Convert proprietary formats
Map proprietary formats (CSV, flat files, database extracts) directly to MX using custom mapping rules. Skip MT entirely for new flows.
Phase 3 -- Native MX initiation
Progressively replace back-office initiation with Hub message entry -- per message type. Operators create MX instructions natively through the web interface.
Phase 4 -- Fade out translation
As business processes produce and consume MX natively, translation is gradually retired. The engine remains available as a safety net for legacy counterparties.
Choose your deployment model
Prowide Integrator
Embed translation directly into your existing applications. Full programmatic control over every step of the migration pipeline.
Messaging Hub
Deploy a turnkey migration solution with visual configuration, automatic routing, and a web-based operations dashboard.