How to reconcile SEPA bank transfers

Short answer

SEPA reconciliation means matching each incoming euro credit transfer on your bank statement to the invoice it settles, then recording the result. Work from the strongest evidence first: the invoice or RF creditor reference in the remittance information, then the exact amount, then the payer's IBAN and name. Anything partial, combined, duplicated or unreferenced needs a person to decide.

What are SEPA Credit Transfer, SEPA Instant and SEPA Direct Debit?

The Single Euro Payments Area (SEPA) lets businesses send and receive euro payments across participating countries under common rules. Two rulebooks published by the European Payments Council (EPC) matter for receivables.

SEPA Credit Transfer (SCT) is the standard euro bank transfer. Under the 2025 SCT Rulebook, the payer's bank must ensure the amount reaches the payee's bank within one banking business day after it receives the instruction. Most business-to-business invoices in euro are still paid this way. The rulebook in effect is version 1.2 of the 2025 edition, published on 30 September 2026; the EPC says it changes no business or operational rules compared with version 1.1, and the next regular version will not take effect before the end of the third quarter of 2028.

SEPA Instant Credit Transfer (SCT Inst) makes funds available on the payee's account in under ten seconds, at any time of day, on every calendar day of the year. The EPC states that there is no longer a maximum amount at scheme level, although individual banks may still set their own limits.

SEPA Direct Debit (SDD) works the other way round: you, as the creditor, collect money from your customer's account under a mandate they signed. It has its own reconciliation problems, covered in a separate section below.

For reconciliation, both credit transfer schemes carry broadly the same data. The difference is timing: instant payments arrive at weekends and overnight, so a statement cut at midnight or at month-end may contain credits that your team would previously have seen only on the next working day.

What changed under the Instant Payments Regulation?

Regulation (EU) 2024/886 amended the SEPA Regulation (EU) No 260/2012 and entered into force on 8 April 2024. According to the European Central Bank's summary, payment service providers in euro area Member States had to:

Electronic money institutions and payment institutions have later dates (from 9 April 2027), and some non-euro area obligations run to 9 June 2028. Check the ECB table in the sources if you operate outside the euro area.

What does Verification of Payee mean for the payee?

Since 9 October 2025, banks in the euro area must offer payers a check of the payee's name against the IBAN before a credit transfer is authorised. The EPC's Verification of Payee scheme covers both SCT and SCT Inst and returns one of four outcomes: match, close match, no match, or verification not possible. Version 1.1 of the scheme rulebook took effect on 20 September 2026.

Verification of Payee happens before the payment and does not add new fields to your bank statement. Its practical effect on receivables is upstream: if the name printed on your invoice differs from the legal name on your bank account, payers may see a "close match" or "no match" warning and hesitate or call you. Print the exact account-holder name next to your IBAN on every invoice.

What data do you actually get with a SEPA payment?

The quality of SEPA payment reconciliation depends on what the payer typed and what your bank passes on. A SEPA credit transfer can carry the following data points relevant to matching.

The SCT Rulebook lets the remittance field carry either structured or unstructured information, not both, and requires banks along the chain to forward it "in full and without alteration". The EPC recommends that payees adopt the ISO 11649 structured creditor reference as the preferred convention for identifying a payment that refers to a single invoice. An optional Extended Remittance Information (ERI) scheme option allows far more structured data, but only between participating banks and customers who have arranged it, so most small and mid-sized businesses should not assume they will receive it.

How do remittance information and the End-to-End ID differ?

The two fields are easy to confuse, but they serve different parties.

• Remittance information is written for you, the payee. It holds 140 characters, either as free text or as a structured creditor reference, and the rulebook says it must reach you in full and without alteration.
• The End-to-End ID is written by the payer for the payer. The SCT Rulebook says the payer defines its internal structure and that it "can only be expected to be meaningful to the Originator". In the EPC implementation guidelines it is an EndToEndId field of 1 to 35 characters. If the payer does not provide one, it defaults to "Not provided", and then there is nothing to use.

There is one practical exception. The ISO 20022 usage note in the EPC guidelines says that where only one identifier can pass through the chain, the creditor's reference should be quoted in the end-to-end identification. Some payers' ERP systems therefore copy your invoice number or RF reference into the End-to-End ID, not into the remittance field. A good matching routine searches both fields for your reference, and treats a hit in either as reference evidence.

For SEPA direct debits the roles reverse: you create the End-to-End ID when you submit the collection, so it is your key, and it comes back on any return or refund of that collection.

What is an RF creditor reference?

An RF creditor reference follows ISO 11649. It starts with the letters RF, followed by two check digits and up to 21 alphanumeric characters of your own reference. For example, the reference 20260101 becomes RF4720260101. The check digits are calculated with the same modulo-97 method as IBANs, so a single mistyped digit (RF4720260102) fails validation. The EPC recommends that the payer's bank checks the RF reference when the payer enters it, which stops many typing errors before the money is sent, but its implementation guidelines say the bank is not obliged to validate it. Validate the check digits again on your side.

If you invoice in several countries, an RF reference gives you one format that works across SEPA. Print it on the invoice, include it in any QR code or payment link, and ask customers to paste it into the structured reference field rather than the free-text field.

Which bank statement format should you use?

You can reconcile from almost any export, but the format determines how much of the payment data survives.

On the SWIFT network, the coexistence period between MT and ISO 20022 for cross-border payment instructions ended on 22 November 2025. Statement and reporting messages such as MT940 were handled on a separate timetable: banks told clients they would remain available until SWIFT sets an end date, and we could not find a confirmed network-wide retirement date for MT940 as of 5 November 2026. Individual banks are moving on their own schedules; in Germany, for example, Commerzbank says it will switch the statement format of the relevant EBICS connections to camt automatically on 16 November 2026. If your bank offers camt.053, it is usually the better source for reconciliation because the structured reference and end-to-end identification arrive in their own fields.

Where does each matching field sit in a camt.053 file?

ISO 20022 defines camt.053 as the message that tells the account owner about entries booked to the account and gives balance information, while camt.054 notifies single or multiple debit and credit entries. If you open a camt.053 file, the data you need for matching usually sits in these elements of each entry (Ntry). Bank usage guidelines differ in detail, so check yours.

One entry can contain several TxDtls blocks. That is how a batch booking appears: one amount on the statement line, with the individual transactions nested underneath, or delivered separately in a camt.054 if your bank provides one.

Whatever format you use, make sure the export includes, for every line: a unique transaction or booking ID, booking date, amount with sign or credit/debit indicator, currency, counterparty name, counterparty IBAN and the full remittance text.

How do you reconcile SEPA bank transfers, step by step?

The method below is how to match SEPA payments to invoices by hand or with any tool. It works the same whether your statement arrives as CSV, camt.053 or MT940.

1. Fix the period and the balances. Export the statement for a closed period and note the opening and closing balance. Your reconciled bookings must explain the movement between them.
2. Export open receivables for the same date. Include invoice number, customer name, amount still outstanding (not the original amount), currency, any RF reference and the customer's known IBAN.
3. Separate debits from credits. Bank fees, outgoing payments and returns you initiated belong to other ledgers. Only credits can settle customer invoices.
4. Normalise the data. Convert amounts to integer cents, upper-case text, and compare references as whole tokens with spaces, dashes and slashes removed. Never compare money as floating-point numbers.
5. Match on reference first. A valid RF reference or a complete invoice number in the remittance text (or, for some payers, in the End-to-End ID) is the strongest single piece of evidence.
6. Score supporting evidence. Exact amount, matching IBAN and matching payer name each add confidence. A payment that matches only on amount is a coincidence until proven otherwise.
7. Flag exceptions instead of forcing them. Partial payments, overpayments, combined payments, ties between two invoices and payments with no evidence go to a review queue.
8. Approve and allocate. A person confirms each allocation. The allocation must never exceed the invoice's outstanding amount or the transaction's remaining amount.
9. Record the decision. Keep who approved what, when, and for how much, in a log that is appended to and never edited.
10. Post and close. Export the approved allocations to your accounting system, follow up on residual balances, and document every unresolved line.

Which matching rules work, and how do they fail?

No single rule is reliable on its own. The table shows common rules and their typical failure modes.

The cases that cause most errors are these:

• Partial payment. Less than the outstanding amount arrives with a valid reference. Allocate what arrived and leave the remainder open; do not close the invoice.
• Overpayment. More than the outstanding amount arrives. Allocate up to the outstanding amount and treat the excess as a credit balance or refund decision.
• Combined payment. One transfer settles several invoices, often with two invoice numbers in the 140 characters, or none. Split it only where the evidence supports each part.
• Split payment. One invoice is paid by several transfers, sometimes from different accounts. Track the running outstanding amount, not the original invoice total.
• Fees deducted. The credit is slightly short. Under the SCT Rulebook each party pays its own bank, and your bank must credit the full amount unless you have agreed that it may deduct its own fees first. A short credit therefore usually means your own bank's agreed deduction, a payment platform outside the SEPA scheme, or a customer who subtracted their own charges. Decide, under a written policy, whether to write off the difference or chase it; our euro payment fee calculator helps you estimate what a charge should have been.
• Wrong reference. The customer quotes another invoice, a credit note or their own order number. Treat a reference that points to a closed or unrelated invoice as an exception, not a match.
• Duplicate payment. The same invoice is paid twice. The second credit must not be allocated to an invoice that is already fully allocated.
• Returned or recalled payment. A credit later reverses through a return or recall. Under the SCT Rulebook a return carries a reason code; reverse the original allocation explicitly rather than deleting it.

A worked example

A company has five open invoices and receives seven statement lines. Customer names and IBANs below are fictitious.

The open invoices were INV-2026-0101 (€4,200.00), INV-2026-0102 (€1,500.00), INV-2026-0103 (€1,800.00), INV-2026-0104 (€1,200.00) and INV-2026-0105 (€1,200.00).

Three points in this example deserve attention. T2 contains "0102" but not the full invoice number, so a whole-token rule rightly refuses to treat it as a reference match; the IBAN and name carry the suggestion and a person decides whether to write off €15.00. T3 matches two invoices at once, and neither invoice alone explains €3,000.00; the allocation is safe only because both invoices are named and the totals agree. T5 shows why allocations must be capped: without a cap, the duplicate would push INV-2026-0101 to minus €4,200.00.

After review, the invoice summary reads: 0101 fully allocated, 0102 fully allocated with a €15.00 write-off recorded in accounting, 0103 and 0104 fully allocated, 0105 €600.00 outstanding, and two credits (T5, T6) waiting for investigation. You can reproduce cases like these with synthetic files in our free Reconciliation Lab, which runs entirely in your browser.

How does SEPA direct debit reconciliation differ?

With a credit transfer you wait for the customer's data. With a SEPA Direct Debit you created the data yourself when you submitted the collection, so matching the money in is usually easier. The hard part comes afterwards, because a collected amount can still be taken back.

What you receive. Many banks credit a direct debit file as one booked amount, with the individual collections nested in the entry or reported in a camt.054. Reconcile the batch total first, then each collection by its End-to-End ID, which you assigned, or by the mandate reference. The EPC notes that each mandate is uniquely identified by the combination of the Unique Mandate Reference and your Creditor Identifier.

What can come back later. Collections that fail or are disputed normally come back as separate debits that refer to the original collection and give a reason. How long the risk lasts depends on the scheme:

How to handle it in practice.

1. Match the batch credit to the collection file you submitted, not to individual invoices.
2. Allocate each collection to its invoice by your own End-to-End ID or mandate reference.
3. When a return or refund arrives, find the original collection by those references and reverse its allocation with a new log entry. The invoice is open again.
4. Record the reason given, because it decides the next step: re-present, ask for a new mandate, or chase by other means.
5. Do not treat an SDD-paid invoice as permanently settled in your dunning or credit decisions until the refund window has passed.

What controls and audit trail do you need?

Reconciliation is a control in its own right, so it needs controls around it.

• Separation of duties. The person who approves allocations should not be the only person who can edit customer master data such as IBANs.
• Approval for every allocation. Even an exact match on reference, amount and IBAN should be confirmed, because the cost of a wrong allocation is a customer chased for money they already paid.
• Caps. No allocation may exceed the invoice's outstanding amount or the transaction's unallocated amount.
• Append-only log. Record approver, timestamp, invoice, transaction, amount and action. Reversals are new entries, not edits.
• Rule versioning. If matching rules change, record which version produced each suggestion, so you can explain past decisions.
• Safe exports. When exporting to CSV, neutralise cells starting with =, +, - or @, which spreadsheet software may execute as formulas. Remittance text is supplied by third parties.
• Statement integrity. Keep the original bank file unchanged and reconcile from a copy.

What should a month-end SEPA checklist include?

• Statement opening and closing balances agree with the general ledger bank account.
• Every credit is allocated, explicitly marked as unresolved, or posted to a suspense account with an owner.
• Every debit is posted to the right ledger (fees, supplier payments, refunds, returns).
• Partial payments show the correct remaining balance on the invoice.
• Overpayments and duplicates have a documented decision: credit note, refund or allocation to a later invoice.
• Write-offs for deducted charges follow your written threshold and are approved.
• Returns and recalls in the period reverse the original allocation.
• Instant payments received after the statement cut-off are assigned to the correct period by booking date.
• The audit log for the period is exported and stored with the close file.
• Customers who repeatedly pay without references are listed for follow-up through invoice payment tracking.

Manual or automated reconciliation?

Automation is worth having only if it explains itself. A tool that posts matches silently, or shows a confidence percentage without saying why, moves the risk instead of reducing it. Our reconciliation software page sets out what to ask any vendor.

What are the most common SEPA reconciliation mistakes?

• Matching on amount alone because it "usually works".
• Searching for invoice numbers as substrings rather than whole tokens.
• Comparing amounts as floating-point numbers, which produces rounding differences.
• Closing an invoice on a partial payment.
• Allocating the original invoice amount rather than the amount still outstanding.
• Deleting a wrong allocation instead of reversing it with a log entry.
• Reconciling from a CSV that truncates the remittance field without noticing.
• Leaving customer IBANs unmaintained, so a changed account looks like an unknown payer.
• Printing a trading name instead of the account-holder name on invoices, which can trigger Verification of Payee warnings for your customers.

Frequently asked questions

Is SEPA reconciliation different from ordinary bank reconciliation?

The principle is the same: explain every movement on the statement. The difference lies in the data. SEPA credit transfers carry a 140-character remittance field, an optional RF creditor reference and the payer's IBAN, which allow much more precise matching than older domestic formats.

Does SEPA Instant make reconciliation harder?

Not in principle, since the data is broadly the same. In practice, payments arrive at weekends and overnight, so cut-off times and booking dates need more care at month-end.

Should I ask customers to use an RF creditor reference?

If you have many customers or invoice across borders, yes. The EPC recommends the RF reference as the preferred convention for single-invoice payments, and its check digits catch typing errors. Customers paying several invoices at once will still need another method, such as listing the invoice numbers.

What should I do with a payment that has no reference?

Look for supporting evidence such as a known IBAN or name. If there is none, keep it unresolved and contact the payer. Do not allocate it to an invoice simply because the amount matches.

Is camt.053 better than a CSV export?

For reconciliation, usually yes, because the structured reference, end-to-end ID and counterparty details arrive in separate fields. A good CSV export can work, provided it contains the full remittance text and the counterparty IBAN.

Is MT940 being switched off?

The end of MT and ISO 20022 coexistence on 22 November 2025 applied to cross-border payment instructions on SWIFT. As of 5 November 2026 we could not find a confirmed end date for MT940 statements. Ask your bank which formats it will support and when.

How should I handle bank charges deducted from a payment?

First check why the credit is short: SEPA credit transfers follow a shared charging principle, so a deduction is not supposed to happen silently. Allocate what arrived, then apply a written write-off threshold for small differences and query larger ones with the customer. Record the write-off as a separate accounting entry.

Does Verification of Payee guarantee that payments reach the right account?

No. It warns the payer when the name and IBAN do not match, and the payer can still proceed. Keep checking your statement for misdirected or unexplained credits.

Sources

• European Payments Council, SEPA Credit Transfer rulebook and implementation guidelines (2025 rulebook version 1.2 in effect) (accessed 5 November 2026)
• European Payments Council, SEPA Credit Transfer Scheme Rulebook 2025 version 1.0 (PDF) (accessed 5 November 2026)
• European Payments Council, SCT Customer-to-PSP Implementation Guidelines 2025 version 1.0 (PDF) (accessed 5 November 2026)
• European Payments Council, SEPA Instant Credit Transfer (accessed 5 November 2026)
• European Payments Council, SEPA Direct Debit (accessed 5 November 2026)
• European Payments Council, SDD Core rulebook and implementation guidelines (accessed 5 November 2026)
• European Payments Council, Verification Of Payee (VOP) scheme (accessed 5 November 2026)
• ISO, ISO 11649:2009 Structured creditor reference to remittance information (accessed 5 November 2026)
• European Central Bank, Instant Payments Regulation (accessed 5 November 2026)
• EUR-Lex, Regulation (EU) 2024/886 on instant credit transfers in euro (accessed 5 November 2026)
• European Commission, Clarification of requirements of the Instant Payments Regulation (accessed 5 November 2026)
• EUR-Lex, Regulation (EU) No 260/2012 (SEPA Regulation) (accessed 5 November 2026)
• ISO 20022, Message definitions catalogue (accessed 5 November 2026)
• ISO 20022, Bank-to-Customer Cash Management message definition report, Part 2 (PDF) (accessed 5 November 2026)
• Commerzbank, switch from MT formats to camt formats in EBICS (accessed 5 November 2026)
• SWIFT, Global financial community completes switch to ISO 20022 (accessed 5 November 2026)
• BNY, ISO 20022 end of coexistence (PDF, May 2025) (accessed 5 November 2026)