Guides · Updated 2026-10-18
Payment-file regression testing after SAP or TMS changes
Payment-file regression testing compares a new payment file with one the bank already accepted and reports configuration-level differences, such as a changed charge bearer, service level, message version or address mode, while ignoring ordinary differences like other payees, amounts or counts.
Why a raw XML diff does not work
Two payment runs never contain the same payments. A line-by-line diff of two pain.001 files is full of different names, amounts, references and counts, so a real configuration change is easy to miss.
Compare facts, not lines
BankLint extracts semantic facts from each file: which codes are used (payment method, service level, charge bearer), how accounts and agents are identified, how addresses are structured, whether control sums are present, which message version and encoding are used, and which elements appear. It compares these facts with the facts of the bank-accepted baseline.
| Kind of fact | Example | Default when it changes |
|---|---|---|
| Configuration | Charge bearer, service level, debtor address mode | REVIEW |
| Structure | Message version, encoding, elements present | REVIEW |
| Control | Control sum present | REVIEW |
| Payment mix | Currencies or remittance styles used by the payees | INFO |
| Volatile | Number of transactions, identifier shapes | EXPECTED |
Names, IBANs, amounts and references are never stored or compared. Only facts from closed code lists and structural modes are kept.
How it works in BankLint
You can try it with the synthetic accepted file and the changed-configuration file: the second one changes the debtor address mode and is reported for review.
- Create a Flow for one payment route, for example "SAP company code 1000 → house bank, SEPA".
- Validate a file the bank accepted and promote the PASS run to the baseline.
- After every configuration change, validate the new file in the same Flow.
- Read the result: changes to review, and blocking changes if you protected a fact.
- Ignore a change you intended (with a reason), or promote the new file as the next baseline once the bank accepts it.
Questions
Does BankLint store my payment files for the comparison?
No. The baseline is a set of sanitized facts taken from the accepted run. The file itself is never stored, so you upload each new file again.
Will a different set of payees raise a review?
No. Facts that change with the payment population default to INFO or EXPECTED. REVIEW is reserved for strong configuration signals.
Validate a pain.001 fileFree, no account needed, files are not stored.