Message Truncation Auditor
Detect silent data loss on the 35-character legacy boundary before your pacs.008 hits a correspondent still translating to MT103. Paste any ISO 20022 MX payload on the left — see exactly which bytes will be discarded by the SWIFT FIN gateway on the right.
Approximately 65% of payment messages still contain unstructured addresses as of March 2026 (SWIFT.com). After 14 November 2026, payment instructions with unstructured addresses face rejection on the CBPR+ path. Hybrid address (town + country minimum) is the compliance floor; fully structured is preferred. Scope exceptions: admi.024, camt.025, camt.052, camt.053, camt.054, camt.060.
Source MX payload and translated MT103 envelope
Truncation findings and remediation guidance
The silent data loss problem
ISO 20022 (pacs.008) carries up to 140-character structured remittance lines and full structured postal addresses across 7+ subfields. When a correspondent on the MT103 side of a corridor receives the message, the SWIFT translation rulebook applies the legacy 4×35-character ceiling. Anything past column 35 is dropped, with no NACK, no warning, and no audit trail.
The original instruction looks delivered. The beneficiary sees a payment land. Reconciliation breaks downstream because the invoice reference is half-gone, the AML team can't pin the originator address, and your sanctions screening signal is silently shorter than what you sent. Auditing the boundary before the message leaves your gateway — and re-mapping the surplus into a structured field MT103 actually understands (:50F:, :59F:, :77B:) — is the only way to keep CBPR+ semantics intact across the legacy hop.
Migrating rails or unlocking trapped capital?
ISO 20022 cutover, A2A migration, FX netting, nostro optimization and real-time fraud — built in production, not slideware. Let's map your move.
Talk to our team →