AM04 reason code: direct debit returned for insufficient funds
Last updated: 28 October 2026
AM04 means “insufficient funds”: there was not enough money in the payer's account to pay the full amount of the SEPA direct debit. In some countries, such as Germany, banks may report this reason as MS03 instead for data protection reasons.
- Code
- AM04
- Meaning in the rulebook
- Insufficient funds
- ISO name
- Insufficient Funds
- Type of R-transaction
- Reject before or return after the debit
- Schemes
- SEPA Core and SEPA B2B
- Collect again?
- Yes, after contacting the payer and with a new pre-notification
What AM04 means
The payer's bank only pays a direct debit if the account covers it. If the balance, including any agreed overdraft, is not enough for the full amount, the bank returns the direct debit with AM04: before the debit as a reject or shortly afterwards as a return.
As a possible cause on the creditor's side, the European Payments Council mentions a missing or late pre-notification: a payer who does not know when and how much will be collected cannot make sure the account is funded.
In some SEPA countries the bank may not state the reason for data protection reasons and reports MS03 instead. A German savings bank, for example, states that it reports AM04 as MS03.
What the payer and the creditor see
As the payer
Your bank informs you that it did not pay the direct debit; depending on your account terms it may charge a fee for this notice.
On your statement you see the direct debit either not at all or as a debit followed by a reversal.
As the creditor
Your bank debits the amount back, usually with a return fee, and shows AM04 or MS03 as the return reason.
You do not learn the payer's balance; whether it was a one-off shortfall is something to clarify with the payer.
| Date | Transaction | Amount EUR |
|---|---|---|
| 3 Nov | SEPA direct debit collection, 214 itemsMembership fees 11/2026 | +8,560.00 |
| 6 Nov | SEPA direct debit returnMandate M-0412, membership fee 11/2026Return reason AM04 Insufficient funds | −40.00 |
| 6 Nov | Return fee | −3.00 |
Typical causes
- Too little balance or a used-up overdraft on the due date.
- A higher amount than expected, such as an annual invoice instead of a monthly fee.
- No or a late pre-notification from the creditor.
- Several direct debits on the same day that together exceed the balance.
What you can do as the payer
- Check your balance on the due date and which direct debits were due that day.
- Contact the creditor and agree how you will pay: by credit transfer or with a new direct debit on a date when your account is funded.
- Ask about costs: your bank may charge for its notice, and the creditor may pass on return costs if the contract or the applicable law allows it.
What you can do as the creditor
- Contact the payer and agree on a new date.
- Then submit a new collection. Announce the new collection with amount and due date (pre-notification), at least 14 calendar days in advance unless agreed otherwise. If the amount changes, for example because you add the return costs, announce the new amount.
- The collection must reach the payer's bank no later than one bank business day before the due date; your bank tells you its cut-off time.
- If the direct debit comes back for insufficient funds again, request the amount by invoice and consider whether direct debit still suits this payer.
Deadlines
A return for insufficient funds arrives shortly after the due date: under SEPA Core no later than five bank business days afterwards, under SEPA B2B no later than three. Announce a new collection at least 14 calendar days in advance unless agreed otherwise.
Related reason codes
- MS03: reason not specified – how some banks report insufficient funds.
- SL01: block or limit at the payer's bank – the amount exceeds a limit set by the payer.
- MS02: refused by the payer – the customer refused the direct debit.
- AC06: account blocked – the account is blocked for payments.
Frequently asked questions
Can the creditor collect again straight away after AM04?
Yes, under the existing mandate, but only with a new pre-notification: at least 14 calendar days before the new due date unless agreed otherwise. Talk to the payer first, or the direct debit may come back again.
Why do I see MS03 instead of AM04?
Some banks, for example in Germany, do not pass on insufficient funds as AM04 for data protection reasons but report MS03 (“reason not specified”).
Does AM04 exist under SEPA B2B?
Yes. A B2B collection is also only paid if the account is funded; the bank returns it no later than three bank business days after the due date.
Sources
- European Payments Council: Guidance on Reason Codes for SDD R-transactions, EPC173-14 version 8.0 – meaning, use cases and root causes of each code
- European Payments Council: 2025 SDD Core Rulebook, version 1.1 – rules of the SEPA Core scheme, deadlines, pre-notification
- European Payments Council: 2025 SDD B2B Rulebook, version 1.1 – rules of the SEPA B2B scheme
- Sparkasse KölnBonn: SEPA-Rückgabe-Codes bei Lastschriften – in German; AM04, MD07 and RR04 reported as MS03 for data protection reasons, MD02 as MD01