Demivolt logo

AC03 Return Code: Meaning, Causes and What to Do

Published 19 November 2026

AC03 means an invalid creditor account number, tied to a wrong IBAN. See how it differs from AC01 and MS03, what causes it and how to fix and prevent it.

AC03 Return Code: Meaning, Causes and What to Do

AC03 Return Code: Meaning, Causes and What to Do

Finance worker reviewing a returned payment

AC03 is a payment reason code that points to a wrong beneficiary account identifier, in practice a wrong IBAN. Under the European Payments Council’s (EPC) SEPA Credit Transfer rules, AC03 is used on a Request for Recall by the Originator (RFRO), where the payer says a transfer went to the wrong IBAN. It is not a routine bank rejection. If AC03 appears in your statement, your payment file or a message from your payment provider, the fix starts with the IBAN you used.

This guide is for finance teams, founders and payment operations staff at businesses that send and receive euro payments. It explains what AC03 means, how it differs from AC01 and MS03, and how to deal with it and stop it recurring.

DemivoltKeep Business IBANs AccurateDemivolt offers business accounts with dedicated IBANs and SEPA payments, supporting clear payment operations for businesses.Visit

TL;DR

  • AC03 means “Invalid Creditor Account Number”: the beneficiary account identifier is wrong. In EPC SEPA Credit Transfer (SCT) rules it is linked to a recall request after a payment went to a wrong IBAN.
  • AC01 is the code for an invalid or incorrect account identifier, such as an IBAN that does not exist at the beneficiary’s provider. It can be a reject or a return.
  • MS03 means “Not Specified Reason Agent Generated”, a limited fallback, not a diagnosis.
  • Code definitions depend on the scheme, so check the rulebook or guidance that governs the payment before you act.
  • Most AC03 cases are preventable by validating IBANs at entry and keeping beneficiary data clean.

Table of Contents

What the AC03 return code means

R-transaction codes are the standard reason codes that banks and payment institutions attach when a payment is rejected, returned, refunded or recalled. They come from the ISO 20022 external code lists, and each payment scheme decides which codes it allows and in which situations.

For euro payments, the relevant scheme is SEPA Credit Transfer. In the EPC’s September 2026 guidance, AC03 carries the meaning “Invalid Creditor Account Number” and is assigned to an RFRO. In plain terms:

  1. Your business sent a SEPA credit transfer.
  2. You, as the originator, entered or selected the wrong IBAN for the beneficiary.
  3. You ask your provider to recall the payment, and AC03 is the reason given for that request.

That is why AC03 behaves differently from a typical failed payment. A reject or return happens when the system or the receiving provider stops the payment. An AC03 recall starts with you, after the money has already left your account and possibly reached someone else’s.

The code is also used in other schemes. The Nordic Payments Council’s guidance for its NCT scheme applies AC03 to a recall request in the same way, and Saudi Arabia’s central bank lists AC03 in its return and rejection code appendix as a wrong IBAN in an SCT. The wording is close across these sources, but each is a separate rulebook.

AC03 versus AC01: which one are you looking at?

Both codes concern the beneficiary account, so they are easily confused. The difference is who raises them, when, and what the next step is.

AC01 AC03
Meaning Invalid or incorrect account identifier, for example an invalid IBAN or one not found at the beneficiary’s provider Invalid creditor account number: a wrong IBAN was used for the payment
Typical trigger The IBAN fails a check or does not exist The IBAN was valid enough to be processed but belonged to the wrong party
Where it appears Reject or return of the payment Request for recall by the originator
Who acts The receiving provider or system flags the problem The sender asks for the money back
Next step Obtain the correct IBAN from the beneficiary and resend Contact the beneficiary to confirm the IBAN, then manage the recall

The EPC guidance describes AC01 as something that may be either a reject or a return, and the Nordic guidance recommends contacting the beneficiary for the correct IBAN in that case. For AC03 it recommends better internal checks and care when entering or selecting the beneficiary IBAN.

The practical consequence is that the two codes lead to different workflows. AC01 is a data correction: the money usually comes back or never left, and you resend. AC03 is a recovery: the money may sit with a third party, and getting it back depends on that party and their provider.

A note on other schemes

The same four letters can have a slightly different definition elsewhere. In the Saudi dictionary, AC01 is described as an incorrectly formatted account number, whereas AC03 is specifically a wrong IBAN in an SCT. That is a different framing from the EPC’s, even though the codes line up. When a code reaches you, work out which scheme it came from (SEPA, SWIFT, a local clearing system) and read that scheme’s guidance rather than assuming.

What MS03 means and why it shows up

MS03 is often grouped with AC03 in searches, but it says almost nothing about the cause. It stands for “Not Specified Reason Agent Generated”. The EPC permits it as a reject or return reason only when national legislation prevents the use of AC04 or RR01 to RR04, and it asks providers to limit its use.

The “agent generated” part matters. In the Saudi rulebook, MS02 means the reason was not specified by the end customer, while MS03 means it was not specified by the agent, which is the bank or payment provider. So MS03 tells you the provider chose not to state a specific reason, usually for legal reasons.

If you receive MS03:

  • Do not assume the IBAN is wrong. The code gives no evidence either way.
  • Ask your payment provider for the underlying detail they are allowed to share.
  • Keep your own records of the payment: reference, amount, date and beneficiary details.

What causes an AC03 case

The EPC’s description is blunt: the originator selected or entered a wrong IBAN. In business settings, that usually comes down to one of these:

  • Manual typing errors. A transposed digit in a 22-character IBAN is easy to make and easy to miss. A payment can fail the IBAN checksum, but some errors still produce another valid IBAN.
  • Outdated supplier records. A supplier changes provider, and your ERP or accounting system still holds the old IBAN.
  • Wrong selection from a list. Beneficiary lists with similar names lead to the wrong entry being chosen.
  • Imported or converted data. Bulk uploads and conversions from old national account numbers can introduce errors at scale.
  • Fraudulent change requests. An email asking you to update bank details should be verified through a known contact before you change the record.

In each case, the EPC guidance points to the originator’s processes: improving issuance processes and taking care when selecting or entering the IBAN.

What to do when a payment went to the wrong IBAN

Speed matters, because the longer the money sits with the wrong recipient, the harder it is to recover. Follow this order.

  1. Stop further payments to that beneficiary. Pause any scheduled or recurring payment that uses the same record, so the error does not repeat.
  2. Confirm what actually happened. Compare the IBAN you used with the one the beneficiary gave you. Check whether the payment was executed, pending or already returned.
  3. Contact the intended beneficiary. Ask them to confirm the correct IBAN in writing, ideally from an established contact channel. The EPC guidance itself lists this check: the originator confirms the IBAN with the beneficiary and verifies the database the IBAN came from.
  4. Contact your payment provider and request a recall. Give the reason as a wrong IBAN. The provider passes the request to the beneficiary’s provider, which then deals with the account holder who received the funds.
  5. Document everything. Keep the payment confirmation, both IBANs, timestamps and all correspondence.
  6. Resend only after the recall outcome is clear. Paying again too early can leave you having paid twice.

A recall is a request, not a guarantee. The party who received the money has to agree in most cases, so recovery depends on them and on their provider. For a fuller walkthrough of the first hours, see our guide on what to do if you send money to the wrong IBAN.

What to include in your report to the provider

A clear case file shortens the investigation. As a working checklist, include:

  • the payment reference and your own internal reference;
  • the execution date, amount and currency;
  • the IBAN you used and the IBAN you intended;
  • the beneficiary’s name as you hold it in your records;
  • how the IBAN was entered or selected (manual entry, file upload, saved beneficiary);
  • the reason code or message you received, copied exactly.

If you send payments in bulk, also name the file and batch. Our guides on validating a SEPA pain.001 file and on avoiding SEPA rejections in six steps show where data errors enter payment files.

How to prevent AC03 and AC01 cases

Because the cause sits with the originator, prevention is mostly process design. The Nordic guidance recommends better internal checks, and the following controls put that into practice.

Validate IBANs before you save them

An IBAN carries a country code, two check digits and the account identifier. Checking the structure and checksum catches many typing errors before they become payments. Our free IBAN Validator lets a team check an IBAN before adding it to a supplier record.

Verify changes out of band

Treat every request to change bank details as a control event. Confirm it by calling a number you already hold, not one in the email. Record who approved it.

Separate who enters from who approves

A four-eyes rule on new beneficiaries and on changed details removes a large share of one-person errors. Role-based permissions make this enforceable rather than a matter of habit.

Pay a small test amount to new high-value beneficiaries

For a first large payment to a new supplier, confirm receipt of a small payment first. It costs little and proves the IBAN reaches the right party.

Keep structured data clean at source

Most bulk errors start in the ERP or in the spreadsheet that feeds it. Lock fields, avoid copying from PDFs, and keep one master supplier list.

Know what a payment costs before you resend

A corrected resend is another payment, and the fees on it should be predictable. Our free SEPA Fee Calculator helps you estimate it.

Cross-border payments: what changes

AC03 and AC01 are SEPA-world codes. Outside the euro area, international payments run over SWIFT, with their own status messages and tracking. If a cross-border payment goes astray, a unique transaction reference allows you and your provider to trace it. Our articles on tracking a payment with SWIFT gpi and which references to request instead of an MT103 explain what to ask for.

Cross-border payments: what changes

Also keep in mind that account identifiers differ between systems. A UK-based business paying euros uses an IBAN, but sort code and account number details do not convert automatically and should be converted using the receiving party’s own confirmed details.

Our perspective

Return codes look like a technical subject, but for finance teams they raise an operational one: how many hands touch a beneficiary’s bank details before money moves?

We see AC03 as a process signal. The scheme guidance places responsibility with the originator’s selection and entry of the IBAN, so the strongest control is one that sits before the payment, not after it. That means validating IBANs, restricting who can add or change beneficiaries, and keeping a payment trail you can hand to your provider in minutes.

This is why we build business accounts around a dedicated IBAN in the company’s own name, role-based user permissions and a real-time dashboard. Demivolt is an Electronic Money Institution authorised by the Bank of Lithuania (licence No. 77) and a direct SEPA participant through CENTROlink, so we issue IBANs on our own infrastructure. A dedicated client manager is free and can help your team understand a return or recall when it happens.

Each business has different payment flows, and we review each one individually. The aim is simple: fewer wrong payments, and a clear route to resolve the ones that do occur.

Demivolt Team

Business accounts built for clean payment operations

If your team sends SEPA, SWIFT and T2 payments regularly, a regulated business payment account gives you the controls above in one place: sub-accounts for separating flows, role-based permissions for entry and approval, and a dashboard to follow each payment. Demivolt business accounts support 31 currencies with currency exchange, and receiving customer payments directly into your business IBAN is part of the Payments service.

As examples for lower-risk businesses based in Lithuania, SEPA In is 0 € and SEPA Out is 0.40 € per payment; fees for other jurisdictions, business models and risk profiles are set case by case. Review times for applications typically run to a few business days for low- to medium-risk businesses and may be longer for higher-risk ones.

Demivolt

See how Demivolt business accounts and Payments work, or contact us to speak with a client manager.

FAQ

What does the AC03 return code mean?

AC03 means “Invalid Creditor Account Number”. In EPC SEPA Credit Transfer guidance it is used on a recall request when the sender says a payment went to a wrong IBAN. The cause is the account identifier used for the beneficiary.

What is the difference between AC01 and AC03?

AC01 flags an invalid or incorrect account identifier, such as an IBAN that does not exist at the beneficiary’s provider, and may be a reject or return. AC03 is raised by the sender in a recall request after a payment went to a wrong IBAN. AC01 usually means correct the data and resend, while AC03 means recover the funds.

What does the MS03 return code mean?

MS03 means “Not Specified Reason Agent Generated”. It is a limited fallback that the EPC allows only where national legislation prevents using more specific codes. It does not indicate that your IBAN or data was wrong.

Can I get money back after an AC03 recall?

A recall is a request passed from your provider to the beneficiary’s provider, and the outcome depends on the party that received the funds. Act quickly, give your provider the full payment details and keep all correspondence. Your provider or client manager can tell you the current status.

Do return codes mean the same thing in every payment scheme?

Not always. The codes come from a shared ISO 20022 list, but each scheme sets when and how they are used, and wording differs between the EPC, the Nordic scheme and national systems. Read the guidance for the scheme that processed your payment.

Sources

This article is for general information only and does not constitute financial, legal or tax advice. Demivolt UAB is an electronic money institution authorised and regulated by the Bank of Lithuania (EMI licence No. 77).