Don't ignore R-codes in SEPA Direct Debits
Knowing your R-codes helps you resolve failed SEPA Direct Debit faster. A failed SEPA Direct Debit is not a dead end, but a data point. The R-code attached to every rejection tells you precisely what went wrong, and that distinction determines what your team should do next. Get the mapping right and you collect faster, with far less manual intervention.
What R-codes are
When a SEPA Direct Debit instruction is rejected or returned, the debtor's bank attaches a standardized reason code, also known as an R-code. These include, for example:
- AM04 — insufficient funds
- MD01 — no valid mandate
- AC13 — invalid debtor account type
The same code can come back through different R-transaction types, for example:
- Reject
- Return
- Refund
- Reversal
The distinction matters because the type and the code together define both the urgency and the correct remediation path.
One code set, many interpretations
This is where things get more complicated in practice. While the European Payments Council (EPC) rulebooks define the codes, individual banks and national banking communities apply them with varying degrees of precision.
A code that one German bank uses to signal a closed account may be used by a Belgian bank to signal a blocked account. Some banks default to a generic code when a more specific one exists.
If your Failure Management logic treats every rejection with the same code identically, regardless of the sending bank or country, you risk misrouting a meaningful share of cases — for example, retrying payments that should be escalated, or escalating payments that simply need a mandate update.
Matching the code to the right follow-up action
This is where understanding R-codes starts to pay off. Consider three contrasting examples:
AC13: invalid debtor account type
The account is linked to a B2B mandate, but the account itself does not allow B2B direct debit transactions. A simple retry will fail again.
The correct action is to contact the debtor: if they are a consumer (or the account is a consumer account), switch to a Core mandate; if they are a business, collect a new B2B mandate on a business account. Twikey’s Failure Management module can trigger that outreach automatically.
MS03: reason not specified
The rejection is likely transient. A timed retry after a configurable interval, on a different banking day, is the appropriate first step before any customer contact.
In practice, this often means there is no money on the account, but for privacy reasons some banks and countries do not want to share that information explicitly.
MD01: no valid mandate
The mandate reference is missing or unrecognized by the debtor’s bank. Before retrying, your team needs to verify the mandate record, check for data-entry errors, and potentially re-enroll the customer.
Automatic retries here only waste collection attempts. For Core mandates, MD01 usually means the debtor revoked the mandate or it expired after 36 months without use; ask the customer to sign a new one.
Each scenario demands a different workflow. Failure Management in Twikey lets you define those workflows per code, per transaction type, and where relevant, per bank, so the right action fires automatically when a rejection arrives (we also have a full list of all R-codes).
What better failure management actually delivers
Mapping R-codes to precise follow-up logic produces two compounding benefits.
1. Faster eventual collection
Payments that fail for recoverable reasons — such as temporary insufficient funds (AM04, or MS03 in Belgium) — re-enter the collection cycle on the right timeline rather than sitting in a manual review queue. Fewer failures turn into write-offs.
2. Less repetitive work
Your team stops micro-managing individual rejections and starts managing by exception. When the system handles the recoverable cases automatically, finance operations capacity shifts toward the edge cases that genuinely require human judgment.
The goal is a Failure Management setup that simply works: rejections are triaged, follow-up actions fire, and your team’s attention is reserved for the situations where it adds real value.
Where to go from here
If you want to see how Twikey maps R-codes to automated follow-up workflows, the Failure Management product page covers the full configuration options.
Or book a demo to walk through your current rejection patterns with one of our integration specialists.

