ISO 20022 Migration
The financial industry is in the midst of the largest messaging standard change in decades. ISO 20022 replaces the legacy MT format with richer, structured XML messages -- but the transition is not a simple switch.
Counterparties, market infrastructures, and internal systems will migrate at different speeds. During the coexistence period, your institution must handle both formats simultaneously -- translating between them accurately, preserving business data, and complying with evolving usage guidelines from SWIFT and regional clearings.
The complexity multiplies when you consider that each clearing system (CBPR+, SIC, RITS, LYNX, T2, and others) has its own translation rules, market practices, and compliance requirements layered on top of the base ISO standard.
Data truncation risk
MX fields are richer than MT -- translating back to MT may require truncation with full traceability of what was lost
Clearing-specific rules
Each market infrastructure adds its own translation requirements on top of the base ISO standard
Coexistence complexity
Counterparties migrate at different speeds -- your system must handle both formats for years
Compliance pressure
CBPR+ usage guidelines evolve with each release -- keeping translation rules current is an ongoing effort
Prowide's translation engine converts between MT and MX formats automatically, covering 40+ message pairs with full round-trip fidelity. The engine is standards-driven -- translation rules are derived from the official ISO 20022 mapping specifications and extended with clearing-specific market practices.
FIN / ISO 15022
ISO 20022
Every translation starts with a base standard. Clearing-specific translators are then 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 low-value payments | Small cross-border payments |
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
T2S / EBA
TARGET2-Securities pan-European securities settlement and Euro Banking Association E1-S1 euro clearing
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
ISO 20022 migration is not a big-bang cutover. Translation is the shortest and most immediate path -- it lets you comply with MX requirements today, without changing your back-office systems. But translation is just the starting point.
Prowide supports a progressive migration that goes well beyond MT↔MX translation. Proprietary formats produced by your core systems -- such as CSV files, flat files, or database extracts -- can be converted directly into MX instructions using custom mapping rules, bypassing MT entirely.
Then, progressively and per message type, the Messaging Hub's message entry capabilities can replace certain back-office initiation flows -- allowing operators to create MX messages natively through the Hub's web interface, reducing dependency on legacy systems one message type at a time.
The end goal: fade out translation as your business processes start producing and consuming MX natively. Prowide accompanies you through every phase -- from day-one translation to full native ISO 20022 adoption.
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.
When translating from MX to MT, some data may not fit within the MT field length constraints. The Prowide translation engine handles this gracefully with automatic truncation and full traceability.
Truncated fields are marked with a '+' indicator so downstream systems know the content was shortened. The original untruncated content is always available through a dedicated API that returns a structured report of exactly what was trimmed and where.
This approach ensures that no business data is silently lost -- every truncation is documented and recoverable.
Automatic detection
The engine identifies fields that exceed MT length limits and truncates them according to SWIFT best practices
Evidence marker
Truncated content is flagged with a '+' character, making it immediately visible to downstream systems and operators
Full audit trail
A structured report details every truncation -- which field was affected, the original content, and the truncated result
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.