pain.001 sample files
Synthetic ISO 20022 pain.001.001.09 credit transfer files for testing: one accepted SEPA file, and files that each break exactly one rule. All names, IBANs and amounts are fabricated. Download a file, or check it on BankLint in one click to see the finding and the fix.
The rule each file demonstrates is linked from the rule reference. For an annotated walk-through of a valid file, see the pain.001 XML example.
A regression testing set
Three files of the same payment run, for trying a Flow with a bank-accepted baseline: make the first file the baseline, then check the other two.
- Bank-accepted file · pain001-accepted.xmlA clean SEPA file with four payments. Use it as the baseline of a Flow.
- File after a configuration change · pain001-changed-config.xmlThe debtor address switched from structured fields to address lines: compared with the baseline, the change needs review.
- Safe change · pain001-safe-change.xmlDifferent payees and amounts, same configuration: compared with the baseline, nothing to review.
How it works: payment-file regression testing.
Files that fail the XML or ISO 20022 schema check
Each file breaks the pain.001 schema (XSD) or XML itself in one way, the kind of error a bank rejects before reading any payment.
Files that break a SEPA Credit Transfer rule
Valid against the ISO 20022 schema, but each file breaks one SEPA rule of the EPC implementation guidelines: the bank is likely to reject it.
Files that need review or carry information
Files with warnings (REVIEW) that depend on your agreement with the bank, and accepted files with notes for information (PASS).