Scope & reliance —🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Embedded rates, thresholds, and regulatory citations are static reference values that may age — verify against current primary sources and your own data before relying on any output for commercial, legal, or compliance decisions. Deterministic logic · no inference · zero PII · runs offline · CC BY 4.0.
Tool 77 · Core Infrastructure
ISO 20022 Data Truncation & Address Auditor
Detect "silent data loss" in MX payment payloads before they hit legacy systems. Paste any pacs.008 or ISO 20022 MX message to identify XML fields exceeding MT character limits and audit postal addresses against the Swift CBPR+ structured address standard. Swift deferred that requirement on 27 August 2026 from its former 14 November 2026 date and has published no replacement date. All parsing runs in your browser.
⚠️ SWIFT CBPR+ structured address: deferred, no new date: this requirement was dated 14 November 2026 until Swift applied a controlled extension of Standards Release 2026 on 27 August 2026; no replacement date has been published. When it takes effect, unstructured postal addresses will be rejected by SWIFT CBPR+. Hybrid (TwnNm + Ctry present) is the minimum. Fully structured is preferred. There is no separate EPC November-2026 address format mandate. Source: swift.com
Supports any MX message type. The tool will scan all recognised element names and every PstlAdr block.
Truncation Risk Findings
Compares every matched element's text length against legacy MT field limits (35 chars for names/IDs, 140 chars for remittance). Fields that overflow will be silently truncated during MX→MT translation: potentially causing compliance screening failures, STP breaks, or sanctions screening mismatches.
📋
Paste an MX XML message above and click Run Both Checks (or Run Both Checks) to see truncation findings here.
Export
Address Compliance: CBPR+ Structured Address
Checks every <PstlAdr> element in the message against the SWIFT CBPR+ structured address requirement. TwnNm and Ctry are mandatory. StrtNm, BldgNb, and PstCd are strongly recommended. Addresses still using only AdrLine without TwnNm/Ctry will be rejected after the deadline.
CBUAE note: CBUAE compliance depends on issuer bank-ownership status. Results shown for conservative (non-bank) interpretation where 100% cash escrow is required.
🏛️
Paste an MX XML message above and click Run Both Checks to see address audit results here.