← All insights

How to reconcile SEPA batch files with your accounting software

To reconcile a SEPA Core batch file, treat the pain.008 file you submitted as your list of expected collections and match each one to your invoice records (1).

How to reconcile SEPA batch files with your accounting software

To reconcile a SEPA Core batch file, treat the pain.008 file you submitted as your list of expected collections and match each one to your invoice records (1). The Creditor's Reference identifies each collection in a unique way for a given creditor and must be returned in any exception handling step, so keep it in your accounting record (2). The general rule is that the Due Date, Settlement Date and debit date are the same date, provided the collection carries a valid Due Date, both PSPs can settle on it, the clearing system is open and the debtor's PSP is willing to debit.

How do I reconcile a SEPA Core batch file against my accounting software?

The pain.008 message is used to transport the Direct Debit Collection instruction from the Creditor to the Creditor PSP and caters for bulk and single instructions, so the file you submitted lists the collection instructions you expect (1). The Core message carries bulk or single collection instructions, with the Local Instrument set to Core, so each collection in it can be matched one by one.

The mandate reference is case insensitive, so compare it ignoring case (1). According to the European Payments Council (EPC) Customer-to-PSP implementation guidelines, positions 1 and 2 of the creditor identifier hold the ISO country code, positions 3 and 4 the check digits, positions 5 to 7 the Creditor Business Code (set to ZZZ when not used) and positions 8 up to 35 the country-specific identifier, and the data element is case and space insensitive. According to the European Payments Council (EPC) implementation guidelines, only EUR is allowed, the amount must be 0.01 or more and 999999999.99 or less, and the fractional part has a maximum of two digits. The remittance information is intended to let an entry be matched to items such as invoices.

Rebeam's reconciliation reporting is described as helping your finance team match collections to the records in your business (3).

Rebeam says collections can be submitted through an API integration or batch files (4).

Reconciliation checks for each collection in a SEPA Core batch file

Check

Rule it rests on

How to verify

Confirm the file type

The pain.008 message carries bulk or single Core collection instructions, with Local Instrument set to Core

Check the message name and local instrument in the file you submitted

Match on the Creditor's Reference

It identifies each collection uniquely for the creditor and must be returned in any exception step

Find the same reference on the invoice or ledger line and keep it for exceptions

Compare the mandate reference

The Unique Mandate Reference is case insensitive

Compare it with the customer's mandate record, ignoring upper and lower case

Check the creditor identifier

Country code, check digits, business code (ZZZ if unused), then the national identifier, up to 35 positions

Compare the identifier in the file with the one on your own account record

Compare the amount

Euro only, from 0.01 to 999999999.99, with at most two decimals

Compare each amount with the invoice or instalment amount in your accounting software

Use the remittance information

It is meant to let an entry be matched to items such as commercial invoices

Check that the invoice number or contract reference in the remittance text matches your receivable

Which dates do I match on, and when should the money arrive?

Settlement days follow the TARGET calendar (2). The creditor's PSP must get the collection to the debtor's PSP at the latest one inter-PSP business day before the Due Date, and not earlier than 14 calendar days before it. When your own account is credited is outside the scope of the scheme, so confirm that timing with your bank. The general rule is that the Due Date, Settlement Date and debit date are the same day, and it applies when the collection carries a valid Due Date, both PSPs can settle on it, the clearing system is open and the debtor's PSP is willing to debit.

How do rejected, returned and refunded collections show up, and how do I tie them back to the original?

According to the European Payments Council (EPC) Customer-to-PSP implementation guidelines, a reject is carried in a pain.002 payment status report using the code RJCT, and the Original Message Name Identification must begin with pain.008, with the addition of a variant number and version number optional (1).

The Creditor's Reference must be returned in every exception step, which is what lets you link a return or refund to the collection it belongs to (2). The latest date for settlement of Returns is five inter-PSP business days after the settlement date of the collection presented to the debtor PSP. Within an eight-week period from the debit, refunds are provided to the debtor on a no-questions-asked basis, and a claim for an unauthorised transaction must be presented within 13 months of the debit date.

Your PSP debits you for a rejected or returned collection only if your account has already been credited (2). Collections can fail, be returned or be refunded, so your team should watch for those items (3). Rejects, Returns and Refunds are cleared and settled through the same clearing system as the original collection, unless participants agree otherwise (2).

Do bank fees change the amount I reconcile for each collection?

The amount in the file is the instructed amount, before deduction of charges, and it must be carried unchanged through the transaction chain (1). Only euro is allowed, and the charge bearer is set so that charges follow the rules agreed in the service level or scheme.

Under the shared charging principle, the creditor and the debtor are charged separately and individually by their own PSPs (2). The basis and level of those charges are set by each participant in line with applicable law.

Sources

  1. Customer-to-PSP Implementation, European Payments Council (EPC), Published on 30 September 2026
  2. 2025 SEPA Direct Debit Core Scheme Rulebook 2025 Version 1.2, European Payments Council, Date issued: 30 September 2026
  3. rebeam.pro
  4. www.rebeam.pro