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. 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 act before Swift sets the new date?#
Because the requirement did not change, only its date. In August 2026 Swift deferred the rule that rejects fully unstructured postal addresses in cross-border payments (CBPR+), together with the move from MT101 to pain.001 version 9 between banks, and it will publish the new timing by December 2026. The work behind both lives in your customer master data, and it takes longer than a release cycle. Other dates stand: June 2027 for investigations, November 2027 for CHAPS purpose codes and Fedwire's next release, November 2028 for statements. The sources are cited in the 2026 briefing and the schedule 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, so 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.
Optional and separate: a supported release channel, private profile derivation for your bank's guideline, and integration help, for teams that need a named party with obligations. See the enterprise page; the software itself stays free.
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.