SEPA Direct Debit: Core and B2B Refund Rules

SEPA direct debit lets a biller collect a euro payment from an account after the payer has signed a mandate. Before agreeing to it, check the scheme named on that mandate. Core and B2B have different refund rules, even when the underlying invoice and payment amount look identical.

The European Payments Council, which manages the schemes, describes Core as designed primarily for consumers and B2B as exclusively for business payers. Both can handle a one-off collection or recurring payments. The collection must be in euros and the accounts must be in SEPA, although an account can be held in another SEPA currency. These rules come from the EPC’s direct debit overview ↗, checked October 8, 2026.

The mandate gives permission to collect

A direct debit starts with the biller’s request to the payer for authorization. The mandate can be on paper or electronic. The biller then requests the collection through its payment service provider, or PSP, and the request reaches the payer’s PSP.

That differs from a transfer you initiate yourself. In a direct debit, the biller starts the collection under an existing permission. A mandate is therefore an important record to keep, rather than a routine checkbox to forget once the payment succeeds.

The EPC says the biller stores the original mandate together with changes or cancellation information. Each collection is traceable through the combination of a Unique Mandate Reference and a Creditor Identifier. When investigating an unfamiliar debit, those identifiers help distinguish one authorization from another.

For a recurring service, keep the mandate reference alongside the biller’s name and the relevant account. If the biller changes, or the business uses several accounts, a list based only on familiar brand names can leave you unable to identify which permission covers a particular debit.

Core and B2B compared

Source: European Payments Council: SEPA Direct Debit ↗.

A business account does not automatically make every collection a B2B collection. Read the actual mandate and identify the scheme offered by the biller and supported by the payer’s PSP. The distinction matters before authorization, when the business can still decide whether the arrangement fits its payment controls.

Core’s two refund windows answer different questions

For Core, the EPC describes an eight-week window following the debit date in which the payer can request a refund without explaining why. That is the scheme’s no-questions-asked refund.

The longer period concerns an unauthorized transaction: one that does not relate to the signed mandate. The EPC says a refund can be requested up to 13 months after the debit. These are different grounds, rather than two interchangeable deadlines for any disputed invoice.

Consider an illustrative subscription payment. You recognize the biller and signed a Core mandate, but the amount surprises you. The eight-week route concerns a refund of the collection without requiring a justification. By contrast, a debit with no corresponding authorization raises the separate question of whether the collection was authorized at all.

Keep the date of the debit and the mandate record when contacting your PSP. A disagreement about the service, an incorrect amount and a missing authorization may require different evidence. The payment scheme’s refund process also should not be read as a ruling on the underlying commercial dispute; that is a separate question from matching the debit to a mandate.

B2B checks permission before debiting

In B2B, the payer’s PSP must obtain the payer’s confirmation of mandate data before debiting the account. It stores those data and checks the first and subsequent collections against them and the related verification instructions.

The EPC says the payer is not entitled to a refund for an authorized B2B transaction. It also says payment is deemed final three business days after the debit date; within that period, the payer’s PSP can still return it for specific reasons. This is a defined exception process, not a three-day Core-style refund window.

For a business arranging supplier collections, the practical check is therefore earlier in the process. Confirm that the PSP supports B2B, that the mandate has been registered or confirmed as required, and that the person authorizing it understands the consequences of an authorized collection.

An invoice approval process alone is not enough to prove that a bank has the required B2B mandate information. Treat the supplier relationship, the internal invoice approval and the payment mandate as linked records, with each responsible person clear about their part.

A failed collection has a reason code

Direct debits can generate exception messages called R-transactions. The EPC lists refusals, rejects, returns, refunds and reversals. These messages carry reason codes so the biller and its PSP can determine what happened.

A biller’s screen saying “failed” is only a starting point. Ask which exception occurred and read its reason code before arranging another collection. A rejected request and a refunded debit represent different points in the payment’s history.

This is related to the broader distinction between an approved payment and settlement. A visible status at one stage cannot stand in for the complete record of money movement.

Controls to discuss with your PSP

The EPC says Core payers can ask their PSP to use whitelists or blacklists of billers, limit the number of collections in a period or set a maximum amount per collection. These controls can help a payer manage permissions without assuming every recurring debit will have the same amount.

For a household account, a familiar recurring biller and an unfamiliar creditor should be easy to distinguish. For a business account, keeping the creditor identifier, mandate reference and scheme in the supplier record can make that review more reliable.

Before signing, establish the scheme, the account to be debited, who holds the mandate and where you will obtain the debit record. After a problem, preserve the date, amount, creditor identifier, mandate reference and PSP’s exception reason. Those details give the investigation something more useful than an app screenshot with a single status word.