Errors & Return Reasons

💡
When a credit transfer or direct debit fails, Atlar provides clear failure reasons. The platform captures the return code—whether the issue originates from the Atlar platform or the bank (if forwarded)—to help you quickly identify and resolve problems.

When a payment fails, its status changes to either:

FAILED – The payment could not be processed.
RETURNED – The payment was processed but subsequently returned.

These return reason codes vary across formats and payment schemes, but whenever possible, Atlar delivers failure and return reasons in the ISO 20022 standard. For the Swedish direct debit scheme AUTOGIRO, proprietary codes are used instead.

The tables below list the available ISO 20022 and AUTOGIRO reason codes along with their meanings.

ISO Originator Errors – Credit Transfers & Direct Debits

Reason Code	Description	Additional Info	Suggested Action
AC03	Invalid Creditor Account Number	The originator entered an incorrect IBAN for the beneficiary.	Update the counterparty to reflect the correct IBAN.
BE04	Missing Creditor Address	Either the Originator PSP or the Beneficiary PSP in the transaction is based in a non-EEA SEPA country.	Originator PSP should request the address of the Beneficiary.
BE05	Unrecognised Initiating Party	Technical error or omission to report a CI (Creditor Identifier) amendment.	Correct the Creditor Identifier.
CNOR	Creditor Bank Is Not Registered	The Creditor PSP is not (or is no longer) registered as an SDD scheme participant under this BIC at the CSM.	Contact the Creditor PSP.
MD01	No Mandate	Debtor PSP has cancelled the mandate under the 36-month inactivity rule; * Debtor PSP was unable to obtain a B2B mandate; * Refund for an unauthorised transaction (up to 13 months after the debit date, SDD Core only).	Review the details of the SDD collection and contact the Debtor if this is a refund.
MD02	Missing Mandatory Mandate Information	The mandate amendment is not compliant with the SDD rulebook; * The amended information is incorrect.	Ensure all required mandate details are collected and presented during customer onboarding.
RC04	Invalid or Missing BIC	The originator did not include a valid BIC for a transaction requiring one (e.g., an international payment or a non-EEA SEPA payment).	Add the correct BIC for the counterparty or verify the existing BIC.
RR01	Missing Debtor Account or Identification	Missing details about the Debtor account or identification; * Note: This code cannot be used in some SEPA countries due to data protection—`MS03` may be used as an alternative.	Contact the Debtor for the correct BIC of a non-EEA SDD collection or ask the Creditor PSP to include the correct and complete BIC of the Debtor PSP in the inter-PSP message.
RR02	Missing Debtor Name or Address	Missing Originator name (address optional for EEA SCT transactions); * Missing Originator address for non-EEA SCT transactions; * Note: May not be usable in some SEPA countries for data protection—`MS03` can be used instead.	Originator Bank should complete the Originator’s name and/or address details.
RR03	Missing Creditor Name or Address	Missing Creditor name (address optional for EEA SDD collections); * For non-EEA collections, providing the address is recommended; * Note: May not be usable in some SEPA countries for data protection—`MS03` can be used instead.	Complete the SDD collection with the correct Creditor name and contact the Creditor PSP if needed.
RR04	Regulatory Reason	Note: Cannot be used in some SEPA countries for data protection—`MS03` can be used as an alternative.	Contact the Creditor PSP.
DS02	Order Cancelled	An authorised user cancelled the order (for example, an `EBICS` `VEU/EDS` signature order).	–
DS19	Electronic Signature Permissions Insufficient	The user’s permissions for digital signatures (e.g., `EBICS` `VEU/EDS`) are insufficient to execute the order.	Review the `EBICS` `VEU/EDS` setup and ensure the expected EBICS subscriber has the required signing rights.
DS24	Waiting Time Expired Due to Incomplete Order	Waiting time for `EBICS` `VEU/EDS` signature expired.	Review the `EBICS` `VEU/EDS` setup and ensure the expected EBICS subscriber has the required signing rights.

ISO Debtor Errors – Originator to Contact the Counterparty (Credit Transfers & Direct Debits)

Reason Code	Description	Additional Info	Suggested Action
AC01	Incorrect Account Number	• Debtor provided incorrect data. • Originator used incorrect IBAN data from their customer database. • Originator had a technical issue during processing of the collection.	• Contact the Counterparty to obtain the correct IBAN. • For SDD: If mandate amendment is involved, verify the data provided by the Debtor.
AC04	Closed Account Number	• Counterparty closed their account. Note: This code cannot be used in certain SEPA countries for data protection reasons—`MS03` may be used instead.	• Contact the Counterparty for new account details. • Agree on an alternative payment method.
AC06	Blocked Account	• Account blocked for any financial transaction. • PSP blocked the account or SDD collection due to a court order. • PSP blocked the account (e.g., suspicion of misuse).	• Contact the Counterparty to arrange an alternative account or payment solution.
AC13	Invalid Debtor Account Type	• Debtor (consumer) signed a B2B mandate, which is restricted to non-consumers. • Account type does not support SDD B2B collections. • Debtor provided details for an unsupported account.	• Contact the Debtor to clarify and agree on another payment method. • Consider signing an SDD Core mandate instead.
AG01	Transaction Forbidden	• Counterparty provided an account that cannot receive SCT/SDD collections (e.g., a savings account). Note: Use `AC13` when an SDD B2B collection is presented to a consumer account.	• Contact the Counterparty to agree on another payment account or instrument.
AM04	Insufficient Funds	• Debtor account has insufficient funds. • Creditor failed to provide pre-notification of the SDD collection (date/amount). Note: Cannot be used in some SEPA countries for data protection—`MS03` may be used instead.	• Contact the Counterparty. • Ensure the Debtor provides sufficient funds.
DNOR	Debtor Bank Not Registered	• Debtor PSP is not or is no longer registered as an SDD scheme participant under this BIC at the CSM.	• Ask the Creditor PSP to check the reachability of the Debtor PSP. • Contact the Debtor to arrange an alternative payment method.
MD01	No Mandate	• Debtor PSP cancelled the mandate due to 36-month inactivity. • Debtor PSP could not obtain a B2B mandate. • Debtor cancelled their mandate. • Creditor failed to use a unique mandate reference (UMR) or provided an SDD collection with a UMR inconsistent with the mandate.	• Verify the SDD collection to ensure the UMR is unique and matches the signed mandate. • Contact the Debtor if a refund is required.
MD06	Refund Request by End Customer	• Unconditional refund of an SDD Core collection (up to 8 weeks after debit date). • Discrepancy between pre-notified amount and actual collection. • Unconditional refund right under the Payment Services Directive (PSD).	• Contact the Debtor.
MD07	End Customer Deceased	• Debtor is deceased. Note: Cannot be used in certain SEPA countries for data protection—`MS03` may be used instead.	• Close the agreement with the deceased Counterparty.
MS02	Not Specified – Customer Generated	• Debtor, after receiving pre-notification, refused the collection.	• Contact the Debtor.
MS03	Not Specified – Agent Generated	• Used when national legislation does not allow use of codes such as `AC04`, `AM04`, `MD07`, `RR01`, `RR02`, `RR03`, or `RR04` (e.g., in Germany).	• Contact the Debtor.
RC01	Bank Identifier Incorrect / Invalid BIC	• Originator provided an incomplete BIC for a non-EEA SEPA SDD collection (e.g., BIC8 instead of BIC11).	• Contact the Counterparty to provide the correct BIC for a non-EEA SDD collection.
RR01	Missing Debtor Account or Identification	• Missing details about the Debtor account or identification. Note: Cannot be used in some SEPA countries for data protection—`MS03` may be used instead.	• Contact the Debtor for the correct BIC of a non-EEA SDD collection. • Ask the Creditor PSP to include the correct and complete BIC of the Debtor PSP in the inter-PSP message.
SL01	Specific Service Offered by Debtor Agent	• Debtor-invoked consumer-right rejects such as: – Creditor blocking; – Collection amount limits; – Collection frequency limits. • Other services offered by the Debtor PSP.	• Contact the Debtor.

Autogiro – Mapping

Autogiro reason codes are communicated to Atlar by Bankgirot, the Swedish clearing house. For failed Autogiro collections (Direct Debits), Atlar forwards these reason codes to help you understand what happened to the underlying direct debit.

Reason Code	Definition
CANAMENDCOMM_	Cancelled/Changed Payments Comment Code
REJECTCOMM_	Rejected Payments Comment Code
SPECSTATUS_	Payments Specification Status Code
MANDADVINFO_	Mandate Advice Information Code
MANDADVCOMM_	Mandate Advice Comment Code

Autogiro – Payment Specification Status Codes

These status codes are provided by Bankgirot for Autogiro (Swedish Direct Debits). They indicate the result of a payment attempt and guide the next steps.

Reason Code	Meaning	Suggested Action
SPECSTATUS_0	Approved payment — payment executed	No action needed.
SPECSTATUS_1	Insufficient funds — payment not executed	Contact the debtor to top up the account or agree on an alternative payment method.
SPECSTATUS_2	No connection to Autogiro (e.g., bank account closed), or the payer's bank has not approved the withdrawal (other reason). Payment not executed	Contact the debtor for updated bank account information or agree on an alternative payment method.
SPECSTATUS_9	Renewed funds — payment not executed but a retry will be attempted if an agreement is in place. Note: Renewed funds only applies to incoming payments.	If retries are configured and the funds remain unavailable, contact the debtor to agree on a payment method.

Autogiro – Rejected Payments Comment Codes

These codes are provided by Bankgirot when an Autogiro (Swedish Direct Debit) collection is rejected. They indicate why the payment failed and what action is recommended.

Reason Code	Meaning	Suggested Action
REJECTCOMM_01	Omitted — mandate not found	Ensure that the mandate details have been sent to the bank using Atlar’s dashboard or API. Alternatively, you can migrate active mandates to Atlar by flagging them as active (in this case Atlar will not send the mandates to Bankgirot).
REJECTCOMM_02	Omitted — account not approved or closed	Contact the debtor to arrange an alternative payment method.
REJECTCOMM_04	Incorrect payer number	Verify that the mandate ID is correct and resubmit the collection to Bankgirot.
REJECTCOMM_06	Incorrect period code	Not applicable.
REJECTCOMM_07	Incorrect number for recurring payments	Not applicable.
REJECTCOMM_08 / 09	Amount non-numeric / Ban on outgoing payments	Not applicable.
REJECTCOMM_10	Bankgiro number not found at Bankgirot	Not applicable.
REJECTCOMM_12	Incorrect payment date	The payment date cannot be later than the current year plus two calendar years. Atlar allows scheduling payments up to 60 days in the future—update the payment date accordingly.
REJECTCOMM_13	Payment date passed	The payment date has passed and the debtor did not have sufficient funds. Contact the debtor to top up the account or agree on an alternative payment method.
REJECTCOMM_15	Payee Bankgiro numbers in the opening and transaction records do not match	Not applicable.
REJECTCOMM_24	Amount exceeds maximum allowed	Initiate a new collection with a valid amount. The upper limit is defined in your Autogiro configuration with the bank.

Autogiro – Cancellation/Amendment of Payments Comment Codes

These codes are provided by Bankgirot when an Autogiro (Swedish Direct Debit) payment is cancelled or amended. They indicate why the change occurred and, when relevant, what action is recommended.

Comment Code	Meaning	Suggested Action
CANAMENDCOMM_01	Incorrect payment date	The payment date cannot be later than the current year plus two calendar years.
CANAMENDCOMM_02	Incorrect payer number	Verify that the mandate ID is correct.
CANAMENDCOMM_04	Incorrect transaction code (occurs when `32` or `82` are missing)	Not applicable.
CANAMENDCOMM_05	Incorrect amount	Initiate a new collection with the correct amount. The upper limit is defined during your Autogiro configuration with the bank.
CANAMENDCOMM_06	Incorrect new payment date	The changed payment date is not within Autogiro’s limits. The date cannot be later than the current year plus two calendar years.
CANAMENDCOMM_10	Incorrect payee Bankgiro number (invalid check digit)	Not applicable.
CANAMENDCOMM_11	Payee Bankgiro number missing (zero or blank)	Not applicable.
CANAMENDCOMM_12	Cancelled	Contact the debtor to arrange an alternative payment method or configure a new Autogiro mandate.
CANAMENDCOMM_13	Payment missing, not processed	Not applicable.
CANAMENDCOMM_14	Amended payment date	No action needed.
CANAMENDCOMM_15	Note amended, recurring payment order	No action needed.
CANAMENDCOMM_18	Amended payment date	No action needed.

Autogiro – Mandate Advice Information Codes

These codes are provided by Bankgirot when there are updates or changes to an Autogiro mandate. They indicate why a mandate was added, changed, or cancelled, and help determine any required action.

Information Code	Meaning	Suggested Action
MANDADVINFO_03	Cancellation initiated by the payee	Contact the debtor to agree on an alternative means of payment.
MANDADVINFO_04	New addition initiated by the payee	No action needed.
MANDADVINFO_05	Change of payer number (only permitted for mandates based on bank account number), initiated by payee	No action needed.
MANDADVINFO_10	Cancelled because the payee’s Bankgiro number has been closed (initiated by payee or payee’s bank)	Not applicable.
MANDADVINFO_42	Response to an account inquiry from the bank regarding a new payer in Autogiro	Not applicable.
MANDADVINFO_43	Cancelled/removed due to an unanswered account inquiry	Not applicable.
MANDADVINFO_44	Cancelled because the payer’s Bankgiro number has been closed (initiated by the payer’s bank)	Not applicable.
MANDADVINFO_46	Cancellation initiated by the payer or the payer’s bank	Contact the debtor for another means of payment or configure a new Autogiro mandate.

Autogiro – Mandate Advice Comment Codes

These codes are sent by Bankgirot to indicate issues or updates with an Autogiro mandate. They explain why a mandate was rejected, cancelled, or updated, helping you decide the next action.

Comment Code	Meaning	Suggested Action
MANDADVCOMM_02	Mandate cancelled on the initiative of the payer or the payer’s bank	Contact the debtor for another means of payment or configure a new Autogiro mandate.
MANDADVCOMM_03	Account type not approved for Autogiro	Contact the debtor for the correct account details—for example, use a checking account instead of a savings account.
MANDADVCOMM_04	Mandate not found in Bankgirot’s mandate directory	Make sure the mandate has been sent to Bankgirot and activated. If not, resend the mandate details using Atlar’s API or Dashboard.
MANDADVCOMM_05	Incorrect bank account or personal details	Contact the debtor for the correct details.
MANDADVCOMM_07	Cancelled/removed due to unanswered account inquiry	Not applicable.
MANDADVCOMM_09	Payer Bankgiro number not found at Bankgirot	Not applicable.
MANDADVCOMM_10	The payer number/mandate ID you have specified is already registered in Bankgirot's directory. The combination of payer number/mandate ID and payee Bankgiro number must be unique. Bankgirot ignores the new mandate and the existing mandate remains in use. Has been cancelled and cannot be registered until seven (7) Bank days have passed: The payer number you specified was used for another payer within the last seven (7) Bank days.	Duplicate mandate: Check the payer number and civic number. • If this is a duplicate, no action is needed. • To register a new mandate with the same civic number, change the payer number and resend it to Bankgirot. Cancelled mandate: If you want to reuse the same payer number that was previously cancelled, wait seven (7) Bank days before resending the mandate.
MANDADVCOMM_20	Incorrect civic/company number or agreement on mandate based on Bankgiro number not found	Correct the civic/company number. Contact the debtor if necessary.
MANDADVCOMM_21	Incorrect payer number	Make sure the mandate ID is correct.
MANDADVCOMM_23	Incorrect bank account number	Check the account number against the payer’s mandate form. Contact the debtor to correct the payer’s account number.
MANDADVCOMM_29	Incorrect payee Bankgiro number	Not applicable.
MANDADVCOMM_30	Deregistered payee Bankgiro number	Not applicable.
MANDADVCOMM_32	New mandate	You can now send payment initiations associated with this mandate to Bankgirot.
MANDADVCOMM_33	Cancelled	Not applicable.
MANDADVCOMM_98	Mandate cancelled due to cancelled payer Bankgiro number	Ask the payer to fill in a new mandate with a valid Bankgiro number or agree on another payment method.