pain.001.001.05 continues the incremental refinement of the message. Like version 4, it is encountered mostly in specific bank channels rather than as a market-wide choice. Pain001 bundles its official XSD and template so files validate byte-for-byte against what such channels expect.
What to know about this version#
- Introduced refinements to party and account structures on the road to the 2019 rework.
- Migration in either direction is a
migrate_recordscall — no manual re-mapping.
Element structure (all versions share this skeleton)#
Group Header — message id, creation timestamp,NbOfTxs,CtrlSum, initiating party. Pain001 recomputes the control totals from validated records.Payment Information — debtor, debtor account and agent, requested execution date, payment method, charge bearer; one block can carry many transactions.Credit Transfer Transaction — amount and currency, creditor, creditor account and agent, remittance information, end-to-end reference.
Generate and inspect#
pain001 init pain.001.001.05 -o work/ # scaffold a starter CSV
pain001 inspect pain.001.001.05 # list required + optional fields
pain001 -t pain.001.001.05 -d payments.csv -o out/ --dry-run
Records migrate losslessly between supported versions:
from pain001.migration import VersionMapper
records_v9 = VersionMapper("pain.001.001.05", "pain.001.001.09").migrate(records)
See the full version catalogue, or the glossary for the vocabulary used here.