Engineering blog
How ISO 20022 actually ships.
Six pillar posts on the topics treasury engineers wake up worried about — the SWIFT MX cutover, the structured-address mandate, per-bank dialect drift, camt.053 reconciliation, AI coding assistants in IDE workflows, and IBAN validation internals.
Using AI coding assistants for ISO 20022 — the MCP wedge
How an MCP server gets ISO 20022 expertise into Claude / Cursor / VS Code without your team having to remember the field paths.
The Nov 14, 2026 structured-address mandate — a deep dive
Every field that changes, every bank that has published readiness guidance, and the deterministic restructurer that gets you to compliant in an afternoon.
SWIFT MX / CBPR+ migration — a treasury engineer's guide
What changes when SWIFT FIN MT messages give way to ISO 20022 MX (CBPR+) on Nov 14, 2026. Concrete code-level deltas, not vendor slides.
Per-bank ISO 20022 dialect drift — the unaccountable moat
ISO 20022 is a single standard; every bank implements a slightly different dialect. The catalog of those differences is a moat that does not show up on a feature comparison sheet.
camt.053 reconciliation patterns — the closed loop
Six carrier fields. One reconciliation key. Practical patterns for matching inbound bank statements to your invoice / order ID ledger.
IBAN validation deep dive — mod-97, country lengths, QR-IBAN, BIC drift
The pure-local mod-97 implementation, the per-country length table, the QR-IBAN range check, and why a valid mod-97 does NOT mean the account exists.