⚡ ISO 20022 CBPR+ SR2023 Compliant

Translate MT to MX.
In seconds. Not weeks.

The only MT→ISO 20022 field mapping and translation tool built by payments professionals, for payments professionals. pacs.008 and pacs.009 — done right.

isomtomx — translation preview
MT 103 Input
:20: ACME20241115001
:32A: 241115EUR50000,00
:50K: ACME CORPORATION
:52A: ROYCCAT2XXX
:57A: DEUTDEDBFRA
:59F: MUELLER GMBH
:71A: SHA
:70: INV-2024-9871
8 fields entered
pacs.008.001.08 Output
<InstrId>ACME20241115001</InstrId>
<UETR>97ed4827-7b6f...</UETR>
<IntrBkSttlmDt>2024-11-15</IntrBkSttlmDt>
<IntrBkSttlmAmt Ccy="EUR">50000.00</>
<ChrgBr>SHAR</ChrgBr> ← SHA→SHAR
<Nm>ACME CORPORATION</Nm>
<BICFI>DEUTDEDBFRA</BICFI>
<Ustrd>INV-2024-9871</Ustrd>
✓ 23 elements generated
47+
MT 103 Fields Mapped
34+
MT 202/COV Fields Mapped
100%
CBPR+ SR2023 Aligned
0
VldtnInf Errors* 😉

ISO 20022 migration
is harder than it looks

The SWIFT coexistence period ended November 2025. MT is gone for cross-border. Most teams are still struggling with the details.

📋

Mapping tables are wrong

Free resources online contain errors — wrong intermediary chain ordering, missing Group Header fields, incorrect COV structure. One wrong mapping fails your entire payment.

⏱️

Manual translation is slow

Your team spends hours cross-referencing SWIFT MDRs, CBPR+ guidelines, and ISO schemas to translate a single message. At scale, this is unsustainable.

🔍

Schema validation is opaque

UETR format, IBAN check digits, BIC length rules, date reformatting — small mistakes cause payment rejection with cryptic error codes from your correspondent banks.

Everything you need
for MT→MX migration

Translation

Live MT→MX Translation

Enter MT 103 / MT 202 field values and get a complete, schema-valid pacs.008 / pacs.009 XML output instantly. No copy-paste, no reformatting.

Accuracy

CBPR+ SR2023 Corrected

Built from the authoritative SWIFT CBPR+ usage guidelines. Correct intermediary chain ordering, proper COV structure using UndrlygCstmrCdtTrf, mandatory Group Header.

Validation

Real-Time Field Validation

UETR UUID v4 format check, IBAN mod-97 validation, BIC length rules, ISO date reformatting (YYMMDD→YYYY-MM-DD), charge code translation (SHA→SHAR).

Coverage

MT 202 COV Support

Full MT 202 COV → pacs.009 translation including the linked UndrlygCstmrCdtTrf block with UETR cross-referencing to the underlying pacs.008.

Reference

Field Mapping Reference

Complete field-by-field mapping tables with transformation rules, ISO 20022 data types, obligation levels, and expert notes for every MT tag.

Simple, transparent
subscription pricing.

Start free. Upgrade when you need the full toolkit. Cancel anytime — no lock-in, no annual commitment required. Always includes the latest SWIFT Standards Release updates.

Monthly
Annual Save 20%

Showing monthly prices

Free
$0 / mo
No credit card required · forever free
For individuals evaluating ISO 20022 or learning the MT→MX migration basics.
  • MT 103 → pacs.008 live translator
  • Core field mapping reference
  • Worked examples (read-only)
  • Charge code & date conversion
  • MT 202 / COV → pacs.009
  • XML export & copy
  • Full validation engine
Cancel anytime — no penalty
SWIFT SR updates always included
Upgrade or downgrade instantly
All future CBPR+ corrections included

Built on authoritative
standards

Every field mapping, transformation rule, and validation logic is sourced directly from the official standards bodies — not forums, not guesswork.

ISO 20022:2013 pacs.008.001.08
ISO 20022:2013 pacs.009.001.08
SWIFT CBPR+ SR2023
SWIFT HVPS+ Usage Guidelines
ISO 4217 Currency Codes
ISO 3166-1 Country Codes
ISO 17442 LEI Standard
GLEIF LEI Validation
UUID v4 (UETR) RFC 4122

isoMTOMX Translator

CBPR+ SR2023 · pacs.008.001.08 · pacs.009.001.08

MT 103 — Input Fields SWIFT FIN
Group Header (Generated by System)
Instructing Agent BIC (Your BIC)
InstgAgt
BIC8 or BIC11 — your institution's BIC
Payment Identification
:20: Transaction Reference Number
:20:
Max 35 chars — must be unique per transaction
Settlement Details :32A:
:32A: Value Date (YYMMDD)
:32A: dt
Format: YYMMDD → will convert to YYYY-MM-DD
:32A: Currency
:32A: ccy
ISO 4217 — 3 uppercase letters
:32A: Amount
:32A: amt
Comma or period decimal — will normalise to period
Charge Bearer :71A:
:71A: Details of Charges
:71A:
SHA → SHAR  |  OUR → DEBT  |  BEN → CRED
Ordering Customer — Debtor :50K/F:
Debtor Name
:50K: nm
Max 140 chars in MX (vs 4×35 in MT)
Debtor Account (IBAN or Account No.)
:50A:
IBAN preferred — will detect format
Debtor Country (ISO 2-char)
:50K: ctry
Ordering Institution — Debtor Agent :52A:
:52A: Debtor Agent BIC
:52A:
Strip // prefix if present
Intermediaries (CBPR+ Corrected Chain)
:56A: Intermediary Institution → IntrmyAgt1
:56A:
:54A: Receiver's Correspondent → IntrmyAgt2
:54A:
Account With Institution — Creditor Agent :57A:
:57A: Creditor Agent BIC
:57A:
Beneficiary Customer — Creditor :59F/59:
Creditor Account (IBAN)
:59: acct
IBAN — validate check digits
Creditor Name
:59F: nm
Critical for sanctions screening — do not truncate
Creditor Country
:59F: ctry
Remittance Information :70:
:70: Remittance Information
:70:
Max 140 chars (CBPR+ limit per occurrence)
Sender to Receiver :72:
:72: Free Text Instructions
:72:
○ Fill fields above
pacs.008.001.08 — XML Output ISO 20022
← Enter MT 103 field values on the left to generate pacs.008 XML output here
or

No account? Register free

isoMTOMX

Happy to look into your Feedback, Suggestion or Complaint.
We aim to respond within 1 business day.

Email us at
support@isomtomx.com
Account
Change Password
Subscription
Danger Zone

Permanently delete your account and all associated data. This cannot be undone. Active subscriptions should be cancelled first via Manage Subscription.