SDD refunds: money with a return path
Eight weeks no-questions-asked, thirteen months if unauthorised — why collected money stays provisional, and what that does to operations.
L0 Explain simply
The most surprising fact about direct debits: the money can simply come back. Under SDD Core you can ask your bank to reverse a collection within eight weeks — no reason required, no argument with the company first. As an analogy: it is a shop with a receipt-free return window; you can bring the purchase back and sort out the disagreement afterwards. And if a collection was never authorised at all — no valid mandate behind it — the window stretches to thirteen months. These rights exist because a pull payment happens without your action each time; the safety valve compensates for the standing permission you gave.
L1 Core concepts
SDD has a whole family of ways a collection fails or unwinds, sorted by the same question you already know from credit transfers: had settlement happened yet? Before settlement, a bank or clearing mechanism can reject a collection, and the debtor can refuse it. After settlement, the debtor's bank can return it within a short scheme window, the debtor can demand a refund, and the creditor itself can send a reversal to give back money it should not have collected. Each event travels back through the same clearing path as the collection, carrying a reason code — and each means the creditor's cash position just moved backwards.
L2 Practitioner view
For a collections business, R-transactions are a portfolio-quality dashboard. High rejects point to stale account data; refusals and refunds point to customers who did not expect the collection — a pre-notification or mandate-management failure. Operations must treat collected funds as provisional through the refund window: revenue recognised on due date can walk out eight weeks later. A refund is also not a dispute resolution — the debtor gets the money back and the underlying claim survives, so the creditor must chase the invoice separately. In B2B the calculus differs: the debtor's bank checked the mandate, authorised collections are final, and the residual risk shifts from refunds to pre-settlement rejects and refusals.
L3 Technical details
The mechanics: refund requests flow from the debtor through their bank and back along the chain, debiting the creditor's account with value adjustments the rulebook prescribes. Returns by the debtor's bank must happen within a short scheme-defined window of interbank business days after settlement; refunds of authorised collections are honoured up to eight weeks after the debit date, and claims of unauthorised collection — no valid mandate — up to thirteen months, a right anchored in EU payment-services law and reflected in the scheme. Every R-transaction carries an ISO reason code; the EPC publishes dedicated guidance on SDD reason codes, with values like MD01 (no valid mandate) carrying sharp compliance meaning: an MD01 refund claim is an allegation the collection should never have happened.
L4 Standards & sources
The refund and R-transaction procedures, windows, and value-dating rules are defined in the EPC's 2025 SDD Core rulebook version 1.1 (EPC016-06): the unconditional eight-week refund for authorised collections, the thirteen-month path for unauthorised ones, and the obligations each PSP has in the chain. The B2B rulebook (EPC222-07) removes the refund right for authorised collections and makes the debtor bank's mandate check mandatory instead — protection moves from after-the-fact refunds to before-the-fact verification. The EPC's guidance on reason codes for SDD R-transactions standardises how failures are labelled across the scheme.
Sources & standards2
- Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · 2025 v1.1 — refund and R-transaction sections
- Scheme-specific rule2025 v1.1 (EPC222-07)
2025 SEPA Direct Debit Business-to-Business rulebook version 1.1 (EPC222-07) ↗ — European Payments Council · 2025 v1.1 — refund provisions
SEE THE PAYMENT MOVE
Read the steps as text
- 01ProcessingAsha Traders confirms the mandateAsha Traders (creditor / biller)
Before pulling any money, the biller checks it holds a valid mandate that Riya signed authorising these collections. The mandate — not the invoice — is what permits the pull; no mandate means no right to debit.
- 05Clearing obligationThe CSM calculates obligationsSTEP2-T (CSM)
On the due date the CSM validates the collection and includes it in a clearing cycle, calculating who owes whom. In a pull this obligation runs from the debtor's bank to the creditor's bank — the reverse of a credit transfer.
Clearing produces obligations only. Nordbank does not have Asha Traders' money yet — that waits for settlement.
- 06SettlementPositions settle in central bank moneyBank Alfa (debtor bank) → Nordbank (creditor bank)
The calculated positions settle across the banks' accounts at the central bank. Money moves from Bank Alfa (debtor side) to Nordbank (creditor side) — funds flowing debtor to creditor even though the instruction came from the creditor.
- DR Bank Alfa settlement account — EUR 480.00
- CR Nordbank settlement account — EUR 480.00
- 07PostingBank Alfa debits RiyaBank Alfa (debtor bank)
Bank Alfa books the debit against Riya's account for the collected amount. This is the customer-facing side of the pull: money leaves the debtor's account because the mandate authorised it.
- DR Riya's current account at Bank Alfa — EUR 480.00
- 08PostingNordbank credits Asha TradersNordbank (creditor bank)
Nordbank credits the biller's account. The collection is complete end to end: debtor debited, banks settled, creditor credited — with the funds having travelled from Riya to Asha Traders.
- CR Asha Traders' account at Nordbank — EUR 480.00
Sources for this topic2
- Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council
- Scheme-specific rule2025 v1.1 (EPC222-07)
2025 SEPA Direct Debit Business-to-Business rulebook version 1.1 (EPC222-07) ↗ — European Payments Council
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.