What does a rejected payment file cost?#
A file the bank bounces does not fail quietly. Someone diagnoses the reason code, repairs the source data, regenerates, resubmits — and if the repair misses the day's cut-off, settlement slips. For payroll or supplier runs, a slipped day is a phone call you do not want to make. The reason-code reference lists what banks actually send back; almost every format-class entry on it is preventable before submission.
Why is 14 November 2026 non-negotiable?#
Because it is enforced at network level, not by policy. From that date, cross-border payments (CBPR+) carrying fully unstructured postal addresses are rejected, and the interbank MT101 relay retires in favour of pain.001 version 9. The dates come from SWIFT, not from us — every one is cited in the 2026 briefing, and the schedule continues to 2028 on the living roadmap.
What does Pain001 do about it?#
Three things. It turns the data you already have — spreadsheets, ERP exports, legacy SWIFT files — into bank-ready ISO 20022 payment files. It proves each file clean before submission: validation against the bank's official rulebook (ISO 20022 XSD), the account-number checksum your bank runs (ISO 13616 mod-97), and control totals recalculated from the records, never trusted. And it does all of this on your own infrastructure — nothing is uploaded anywhere.
What does it cost?#
Nothing, at any scale, permanently. The core is dual-licensed (Apache-2.0 or MIT); companion packages are Apache-2.0. The nearest commercial reference point — SWIFT's translation SDK — is publicly listed at €10,000–30,000 per year before integration effort. The full landscape, including where commercial platforms genuinely win, is in the comparison.
Is it safe?#
Check rather than trust: payment data never leaves your machines, the dependency inventory is a published SBOM, the code holds 100% branch coverage as a CI gate, and the browser demo invites your security team to falsify the claims with DevTools open.
What is the next step?#
Watch it work: the 60-second demo validates a payment batch and proves it against the official schema, in your browser. Then hand your team the executive brief — one page, print-ready, available in French, German, and Spanish.