SEPA pain.001 Payment Batch Builder

Turn a list of payments into current ISO 20022 pain.001.001.09 XML, with local validation before you upload it to your bank.

Local: yes. Your input stays on your device and is not sent to an external service for this tool.

Batch settings

Debtor

Payments

Expected columns: name, iban, amount, reference, endToEndId, bic. Imported data stays in your browser.

CreditorIBANAmount EURReferenceEnd-to-end ID

Generation and validation run locally. The XML is not sent to your bank.

What a pain.001 file is

pain.001 is the ISO 20022 Customer Credit Transfer Initiation message: the XML file you upload to your bank's business channel to execute many transfers at once (supplier runs, refunds, salaries). The builder produces version pain.001.001.09, the 2019 release used in current Belgian and SEPA implementation guidance. It reads payments from CSV, Excel, JSON or rows you type, validates each one and writes one batch.

Structure of the generated file

<GrpHdr>   MsgId, CreDtTm, NbOfTxs = 3, CtrlSum = 1835.40, InitgPty
<PmtInf>   PmtInfId, PmtMtd = TRF, BtchBookg = true,
           NbOfTxs = 3, CtrlSum = 1835.40, SvcLvl = SEPA,
           ReqdExctnDt/Dt = 2026-11-02,
           Dbtr, DbtrAcct/IBAN, DbtrAgt/BICFI, ChrgBr = SLEV
  <CdtTrfTxInf>  PmtId/InstrId + EndToEndId
                 Amt/InstdAmt Ccy="EUR"  1210.00
                 Cdtr/Nm, CdtrAcct/IBAN, CdtrAgt
                 RmtInf: Strd/CdtrRefInf (RF) or Ustrd (text, OGM)

NbOfTxs and CtrlSum appear twice (group header and payment information) and must match the transactions exactly; the builder computes them, so a hand-edited total cannot slip through.

Validation rules

  • IBAN checksum per payment, and the BIC of Belgian banks derived from the bank code when you leave it empty.
  • Amounts in euro, positive, at most two decimals.
  • Names trimmed to 70 characters and identifiers to 35 characters, the ISO 20022 limits.
  • Remittance: a valid RF creditor reference goes in the structured field with type SCOR; anything else, including an OGM in +++ form, goes in the 140-character unstructured text.
  • Duplicate EndToEndId values inside one batch produce a warning, as they make reconciliation ambiguous.

Edge cases

  • Execution dates in the past or on a bank holiday are moved or rejected by most banks.
  • Banks may add their own profile rules (character set, batch booking, maximum batch size). Upload a small test file first.
  • Non-euro payments and urgent (instant or priority) transfers are outside this SEPA profile.

Check incoming statements afterwards with the CAMT viewer or bank statement compare, validate accounts with the IBAN checker and create references with the OGM generator.

Frequently asked questions

Which pain.001 version does the builder create?

pain.001.001.09, the ISO 20022 2019 Customer Credit Transfer Initiation message used in current Belgian and SEPA guidance. Check with your bank whether it accepts this version on your channel.

What are NbOfTxs and CtrlSum?

NbOfTxs is the number of transfers and CtrlSum their total amount. Both appear in the group header and in the payment information block and must match the transactions exactly.

Where does the OGM go in pain.001?

This builder puts a valid RF creditor reference in the structured remittance field and other references, including an OGM in +++ form, in the unstructured remittance text. Some banks have their own guidance for OGM, so test a file first.

Can I import payments from Excel?

Yes. CSV, Excel and JSON files can be mapped to payment fields, or you can type rows by hand. Every row is validated before the XML is written.

Are my payment details sent anywhere?

No. The batch is built and validated in your browser and nothing is sent to gratistools.be. You upload the XML to your bank yourself.