SEPA Reason Codes Explained

The Complete Guide for your payments

When you operate in the Single Euro Payments Area (SEPA), smooth payment processing is the backbone of your business. But even in a standardized environment, payments can fail, and when they do, banks return a SEPA Reason Code. These codes are part of the EPC (European Payments Council) Rulebooks, which define how SEPA transactions must behave across Europe.These codes are part of a unified European framework that tells you exactly why a payment was rejected, returned, or stopped. They are essential for compliance, automation, and a seamless customer experience.

What Are SEPA Reason Codes?

SEPA Reason Codes are standardized indicators used by banks and payment institutions when:
  • a SEPA Credit Transfer cannot be processed,
  • a SEPA Instant payment fails,
  • a Direct Debit (SDD Core/B2B) is returned or refused.
Each code corresponds to a specific issue - invalid IBAN, insufficient funds, blocked account, missing mandate, duplication, and dozens of others.This standardization ensures that all European banks speak the same error language.

1. SEPA Credit Transfer (SCT) — EPC Reason Codes

These codes appear when a SEPA Credit Transfer is rejected, returned, or fails during processing.
CodeEPC Description
AC01Incorrect account number format (invalid or non-existing IBAN).
AC03Invalid creditor account number.
AC04Account closed.
AC06Account blocked/frozen.
AG01Transaction forbidden by the debtor agent.
AG02Invalid bank operation code or invalid file format.
AM04Insufficient funds.
AM05Duplicate payment.
AM09Wrong amount.
ARDTTransaction already returned (negative response to recall).
BE04Missing or invalid creditor address (where legally required).
CNORCreditor bank not registered/unknown BIC.
DNORDebtor bank not registered for SEPA.
DUPLDuplicate transaction.
FF01Invalid file format or structural error in the message.
FOCRFollowing cancellation request (positive recall).
FRADFraud — recall initiated due to suspected fraud.
LEGLLegal decision preventing execution.
MS02Not specified by debtor (customer-driven rejection).
MS03Not specified by agent (bank-driven rejection; reason withheld).
NOASNo answer from customer.
NOOROriginal transaction not received.
RC01Bank identifier incorrect (BIC invalid or missing).
RR01Missing debtor account or identification (regulatory).
RR02Missing debtor name or address (regulatory).
RR03Missing creditor name or address (regulatory).
RR04Regulatory reason (AML, sanctions, KYC, etc.).
TECHTechnical error in processing.
TM01Cut-off time exceeded.

2. SEPA Instant Credit Transfer (SCT Inst) - EPC Reason Codes

Instant payments follow the same code structure, but the EPC adds specific instant-processing codes.
CodeEPC Description
AB05Timeout at creditor agent.
AB06Timeout at instructed agent.
AB07Agent offline (unspecified).
AB08Creditor agent offline.
AB09Error at creditor agent.
AB10Error at instructed agent.
AC01Invalid account number (IBAN).
AC03Invalid creditor account.
AC04Account closed.
AC06Blocked account.
AG01Transaction forbidden.
AG02Invalid transaction code/file structure.
AG09Payment not received by creditor agent.
AG10Agent suspended from instant scheme.
AG11Creditor agent suspended from instant scheme.
AM02Amount exceeds allowed instant transfer limit.
AM04Insufficient funds.
AM05Duplicate payment.
AM09Wrong amount.
AM23Amount exceeds settlement limit.
ARDTAlready returned.
BE04Missing/invalid creditor address.
CNORCreditor bank not reachable in SCT Inst.
CUSTCancellation requested by customer.
DNORDebtor bank not reachable in SCT Inst.
DUPLDuplicate instruction.
FF01File formatting error.
FOCRFollowing cancellation/recall request.
FRADFraud — recall initiated.
LEGLLegal reason.
MD07Creditor deceased.
MS02Reject — unspecified debtor reason.
MS03Reject — unspecified agent reason.
NOASNo answer from customer.
NOOROriginal transaction not received.
RC01Invalid or missing BIC.
RR01–RR04Regulatory requirements not met (missing KYC fields).
TECHTechnical problem.
TM01Cut-off or timing rule violation.

3. SEPA Direct Debit (SDD Core & B2B) - EPC Reason Codes

These apply to both Core and B2B schemes unless marked differently.
CodeEPC Description
AC01Invalid debtor account number (IBAN).
AC04Account closed.
AC06Account blocked.
AC13Invalid account type for mandate (e.g., B2B mandate on consumer account).
AG01Direct debit forbidden on this account.
AG02Invalid transaction code / file structure error.
AM04Insufficient funds.
AM05Duplicate collection.
BE05Unknown initiating party (invalid Creditor Identifier).
CNORCreditor bank not registered.
DNORDebtor bank not reachable/registered for SDD.
ED05Settlement failed.
FF01Invalid file format or malformed message.
MD01No mandate exists.
MD02Mandate data invalid or missing.
MD06Debtor claims refund (authorised but disputed). (Core only)
MD07Debtor deceased.
MS02Debtor refuses collection (prior to settlement).
MS03Bank rejects for unspecified reason.
RC01Invalid/missing BIC.
RR01Missing debtor account information (regulatory).
RR02Missing debtor name/address (regulatory).
RR03Missing creditor name/address (regulatory).
RR04Regulatory reason (sanctions, AML, restrictions).
SL01Service-level restriction by debtor bank (e.g., only whitelist collections allowed).
PY01Payment cannot be routed (no clearing path).

Why It Matters for Narvi Clients

At Narvi we process SEPA payments for fintechs, high-velocity businesses, and regulated industries. Understanding reason codes enables our clients to:
  • reduce operational delays,
  • build smarter automated flows,
  • provide better customer support,
  • improve financial predictability.
As your banking and payments partner, we ensure that every SEPA event is logged, explained, and accessible through our platform - so you always know what happened and why.

Official Source Reference (EPC)

All codes in this article are based on the following European Payments Council rulebooks and guidance documents:
  • EPC SEPA Credit Transfer Rulebook
  • EPC SEPA Instant Credit Transfer Rulebook
  • EPC SEPA Direct Debit Core Rulebook
  • EPC SEPA Direct Debit B2B Rulebook
  • EPC “Guidance on Reason Codes for SEPA R-Transactions”
These can be accessed at: https://www.europeanpaymentscouncil.eu/document-libraryThis ensures that all definitions provided above match the authoritative EPC standards used across the SEPA zone.
Prepare for your Business Bank AccountSet up your bank account completely online and access SEPA and SWIFT payments immediately.Learn More & Book a Demo
section

Read next:

Opening a Business Bank Account in the Netherlands

Opening a Dutch bank account will give your company access to financial services such as credit cards and loans, making it easier for you to manage your business finances.

How to Open a Bank Account in Finland?

What are the requirements for setting up a bank account in Finland? And, is there an alternative to traditional banking? We’ll get answers to these questions and more below. Keep reading to learn more!

How to Open a Business Bank Account in the Cayman Islands

Are you dreaming of taking your business global? The Cayman Islands, a beautiful British Overseas Territory located in the Caribbean, might just be the perfect place to make that dream a reality.
section

Narvi Payments Oy Ab es una institución de dinero electrónico (EMI) autorizada. La licencia EMI de Narvi la otorga la Autoridad de Supervisión Financiera de Finlandia (FIN FSA) con el número de registro 3190214-6. La licencia de Narvi tiene validez para todos los países de la Unión Europea.
FinlandConstruido y regulado por Finlandia

© 2025 Narvi. All Rights Reserved.

v1.230.0
SEPA Reason Codes Explained | Narvi Payment