Pain001
Try the demo ›

Message reference

pain.001.001.05 Reference: Generate and Validate

pain.001.001.05 — a maintenance release on the road to 2019. Element structure, version notes, and version migration.

1 min read Last reviewed

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_records call — no manual re-mapping.

Element structure (all versions share this skeleton)#

  • <GrpHdr> Group Header — message id, creation timestamp, NbOfTxs, CtrlSum, initiating party. Pain001 recomputes the control totals from validated records.
  • <PmtInf> Payment Information — debtor, debtor account and agent, requested execution date, payment method, charge bearer; one block can carry many transactions.
  • <CdtTrfTxInf> 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 can be reshaped between supported versions. The mapper renames and defaults fields to match the target version; elements the target does not model are not carried over, so re-validate after migrating:

from pain001.migration import VersionMapper
rows = VersionMapper().migrate_rows(
    rows, "pain.001.001.05", "pain.001.001.09"
)

See the full version catalogue, or the glossary for the vocabulary used here.