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 · 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 mandatory November 2026 SWIFT/EPC structured address standard. All parsing runs in your browser.

⚠ Nov 2026 Mandate Truncation Check Address Audit v1.0
⚠️ SWIFT CBPR+ Deadline: 15 November 2026 — Unstructured postal addresses will be rejected by SWIFT CBPR+ and the EPC. Hybrid (TwnNm + Ctry present) is the minimum. Fully structured is preferred. 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.