Paying suppliers in one batch: pain.001 files explained

A pain.001 file is the ISO 20022 message a business uploads to its bank to pay many suppliers at once. In the SEPA area it carries euro credit transfers: one paying account, an execution date, and one line per supplier with name, IBAN, amount and payment reference.

Typing supplier payments into online banking one by one is slow and easy to get wrong. A batch file turns a list of approved bills into a single upload that the bank checks and executes. This guide explains what is inside the file, how a payment run works from start to finish, and the controls that keep it safe.

Why pay suppliers in a batch

• Fewer typing errors. IBANs, amounts and references come from the bills you already recorded, not from someone retyping them.
• One approval. A manager reviews and signs the whole run instead of each payment.
• A rhythm. Paying on a fixed day each week or month makes cash flow easier to plan and supplier questions easier to answer.
• Cleaner reconciliation. Each payment carries the supplier's invoice reference, so matching it later is simpler.

A batch run starts from bills you trust. If supplier invoices are not yet recorded in one place, the guide to tracking supplier bills next to customer invoices covers that groundwork.

What is inside a pain.001 file

The file is structured XML in three layers. The European Payments Council publishes implementation guidelines for SEPA credit transfers, and banks publish their own guides on top of them.

Layer	Appears	Holds
Group header	Once per file	A message ID, the creation time, the number of transactions, a control sum of all amounts, and the initiating party
Payment information	One or more per file	The paying company and account, the requested execution date and whether to book the batch as one debit
Credit transfer transaction	One per payment	An end-to-end ID, the amount, the supplier's name and IBAN, and the remittance information

The remittance information is what the supplier sees. It can be free text, such as an invoice number, or a structured creditor reference, such as the international RF reference, which the supplier's software can match without reading. Use the reference the supplier printed on the invoice whenever there is one.

A payment run, step by step

1. Approve the bills. Make sure every bill in the run has been checked and approved for payment.
2. Choose what to pay. Select bills due before the next run, and decide on any partial or held payments.
3. Check the bank details. Compare each IBAN with the supplier record and look into any recent change before paying.
4. Create the file. Generate the pain.001 file from the selected bills, with one execution date for the run.
5. Upload and authorize. Upload the file to the bank, where one or two authorized signers approve it, depending on your bank mandate.
6. Check the result and reconcile. Many banks return a pain.002 status report that says which payments were accepted or rejected. The booking then appears on the bank statement, and each paid bill can be marked as settled.

Statements in the camt.053 format carry the details needed to match those debits back to the bills; the guide to reading a camt.053 bank statement explains how.

Batch booking, execution dates and speed

• Batch booking. A flag in the file asks the bank to show the run as one debit on your statement or as one line per payment. One line is tidy; separate lines are easier to reconcile. Banks handle the flag in slightly different ways.
• Execution date. The requested date is when your account is debited. Set it with the bank's cut-off times in mind.
• Speed. A standard SEPA credit transfer generally reaches the supplier's bank by the end of the next business day. SEPA instant credit transfers arrive within seconds; in the euro area, banks that offer standard credit transfers have also had to offer instant ones since 2025.

Controls that keep a payment run safe

• Treat bank detail changes as a red flag. Changed-bank-details fraud is a common risk. Confirm any change with the supplier through a phone number or contact you already had, never the one in the email asking for the change.
• Use the name check. Since October 2025, banks in the euro area have had to offer a check of the payee's name against the IBAN before a credit transfer is sent. Business users who send several payments as one file can choose to opt out of the check, so find out how your bank applies it to batch files.
• Separate duties. The person who prepares the run should not be the person who approves it at the bank.
• Protect the file. A pain.001 file is plain XML. Create it and upload it without manual edits in between, and keep it out of shared folders.
• Check the control sum. Compare the total in the file with the total of the approved bills before you sign.

Recurring costs such as rent or subscriptions fit well into a regular run once the bills arrive on schedule; see scheduling supplier bills that repeat every month.

Frequently asked questions

What is pain.002?

pain.002 is the ISO 20022 payment status report. A bank uses it to tell you whether a file, or individual payments inside it, were accepted, rejected or are pending. Many banks offer it as a download or send it back through the same channel you used to upload the file.

Is a SEPA credit transfer the same as a SEPA direct debit?

No. With a credit transfer, you push money from your account to the supplier. With a direct debit, the supplier pulls money from your account under a mandate you signed. The guide to SEPA Direct Debit for small businesses explains the other direction.

Can a pain.001 file include non-euro payments?

SEPA credit transfers are in euro. Some banks accept other currencies or international payments in the same message format, under their own rules. Check your bank's implementation guide before mixing payment types in one file.

Which pain.001 version does my bank accept?

It varies. Banks support different versions of the message and publish the ones they accept in their implementation guides. A file built for one bank may need adjusting for another, so test with a small run before switching.