Status reason codes

Clearing process aborted due to timeout.

Clearing process aborted due to a fatal error.

Settlement aborted due to timeout.

Settlement process aborted due to a fatal error.

Transaction stopped due to timeout at the Creditor Agent.

Transaction stopped due to timeout at the Instructed Agent.

Agent of message is not online. Generic usage if it cannot be determined who exactly is not online.

Creditor Agent is not online.

Transaction stopped due to error at the Creditor Agent.

Transaction stopped due to error at the Instructed Agent.

Transaction stopped due to timeout at the Debtor Agent.

Duplicate Concurrent Batch Sequence number– for Settlement Instructions.

Wrong Message Routing Type for Return-of-Funds.

Instruction may not be placed on the Continuous Processing Line settlement processor.

Agreement number not valid (beneficiary).

Settlement Instruction does not exist.

Account number is invalid or missing.

Debtor account number invalid or missing

Creditor account number invalid or missing

Account number specified has been closed on the bank of account's books.

Debtor account number closed.

Account specified is blocked, prohibiting posting of transactions against it.

Creditor account number closed

Branch code is invalid or missing

Account currency is invalid or missing

Debtor account currency is invalid or missing

Creditor account currency is invalid or missing

Account type missing or invalid. Generic usage if cannot specify between group and payment information levels

Debtor account type missing or invalid

Creditor account type missing or invalid

The account details for the counterparty have changed.

Credit or debit card number is invalid.

Requested amount exceeds the limit set by Debtor (Agent)

Request-to-pay Expiry Date and Time has already passed.

Transaction forbidden on this type of account (formerly NoAgreement)

Bank Operation code specified in the message is not valid for receiver

Transaction type not supported/authorized on this account.

Agent country code is missing or invalid. Generic usage if cannot specify between group and payment information levels.

Debtor agent country code is missing or invalid

Creditor agent country code is missing or invalid

Debtor account cannot be debited for a generic reason. Code value may be used in general purposes and as a replacement for AM04 if debtor bank does not reveal its customer's insufficient funds for privacy reasons

Transaction failed due to invalid or missing user or access right

Original payment never received.

Agent of message is suspended from the Real Time Payment system. Generic usage if it cannot be determined who exactly is suspended.

Creditor Agent of message is suspended from the Real Time Payment system.

Payment orders made by transferring funds from one account to another at the same financial institution (bank or payment institution) are not allowed.

Returned payments derived from previously returned transactions are not allowed.

Agent in the payment workflow is incorrect

Request-to-pay has already been accepted by the Debtor.

Specified message amount is equal to zero

Specific transaction/message amount is greater than allowed maximum

Specified message amount is an non processable currency outside of existing agreement

Amount of funds available to cover specified message amount is insufficient.

Duplication

Specified transaction amount is less than agreed minimum.

Amount specified in message has been blocked by regulatory authorities.

Amount received is not the amount agreed or expected

Sum of instructed amounts does not equal the control sum.

Transaction currency is invalid or missing

Amount is invalid or missing

Transaction amount exceeds limits set by clearing system

Transaction amount exceeds limits agreed between bank and client

Transaction amount below minimum set by clearing system

Control Sum at the Group level is invalid

Control Sum at the Payment Information level is invalid

Number of transactions is invalid or missing. Generic usage if cannot specify between group and payment information levels.

Number of transactions at the Group level is invalid or missing

Number of transactions at the Payment Information level is invalid

Transaction amount exceeds limits agreed between bank and client.

Unable to apply zero amount to designated account. For example, where the rules of a service allow the use of zero amount payments, however the back-office system is unable to apply the funds to the account. If the rules of a service prohibit the use of zero amount payments, then code AM01 is used to report the error condition.

Transaction amount exceeds settlement limit.

Size of the attachment exceeds the allowed maximum.

Request To Pay has already been paid by the Debtor.

Request-to-pay has already been refused by the Debtor.

Request-to-pay has already been rejected.

Attachments to the request-to-pay are not supported.

Settlement Cycle Day and Calendar day should be the same.

Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency).

Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).

Party who initiated the message is not recognised by the end customer

End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books

Specification of debtor's address, which is required for payment, is missing/not correct.

Debtor name is missing

Country code is missing or Invalid. Generic usage if cannot specifically identify debtor or creditor

Debtor country code is missing or invalid

Creditor country code is missing or invalid

Country code of residence is missing or Invalid. Generic usage if cannot specifically identify debtor or creditor

Country code of debtor's residence is missing or Invalid

Country code of creditor's residence is missing or Invalid

Identification code missing or invalid. Generic usage if cannot specifically identify debtor or creditor.

Debtor or Ultimate Debtor identification code missing or invalid

Creditor or Ultimate Creditor identification code missing or invalid

Contact details missing or invalid

Charge bearer code for transaction type is invalid

Name length exceeds local rules for payment type.

Name missing or invalid. Generic usage if cannot specifically identify debtor or creditor.

Creditor name is missing

Phone number or email address, or any other proxy, used as the account proxy is unknown or invalid.

Credit transfer is not tagged as an Extended Remittance Information (ERI) transaction but contains ERI.

Value in Requested Execution Date or Requested Collection Date is too far in the future

Value in Requested Execution Date or Requested Collection Date is too far in the past

Element is not to be used at B- and C-Level

Mandate changes are not allowed

Information on mandate changes are missing

Value in Creditor Identifier is incorrect

Creditor Identifier is ambiguous at Transaction Level

Original Debtor Account is not to be used

Original Debtor Agent is not to be used

Content Remittance Information/Structured includes more than 140 characters

Content is incorrect

Element is not allowed

Values in Interbank Settlement Date or Requested Collection Date will be set to the next TARGET day

Number of decimal points not compatible with the currency

Mandatory element is missing.

SDD CORE and B2B not permitted within one message.

Related to a Charge message to convey that the code in Charge Breakdown / Type / Code is not accepted by the receiving party.

Cheque has been presented in cheque clearing and settled on the creditor’s account.

Related to a Charge message to convey that the charge bearer code used in the corresponding Payment message was not debt.

Authorisation is cancelled.

Credit notes are not supported.

Creditor bank is not registered under this BIC in the CSM

Currency of the payment is incorrect

Cancellation requested by the Debtor

Rejection of a payment due to covering FI settlement not being received.

Debtor bank is not registered under this BIC in the CSM

The electronic signature(s) is/are correct

An authorized user has cancelled the order

The user’s attempt to cancel the order was not successful.

The order was rejected by the bank side (for reasons concerning content)

The order was correct and could be forwarded for postprocessing

The order was transferred to VEU

All actions concerning the order could be done by the EBICS bank server

The decompression of the file was not successful

The decryption of the file was not successful

Data signature is required.

Data signature for the format is not available or invalid.

The signer certificate is revoked.

The signer certificate is not valid (revoked or not active).

The signer certificate is not present.

The authority of the signer certification sending the certificate is unknown.

Signer is not allowed to sign this operation type.

Signer is not allowed to sign for this account.

The number of transaction is over the number allowed for this signer.

The certificate is revoked for the first signer.

The certificate is not valid (revoked or not active) for the first signer.

The certificate is not present for the first signer.

The authority of signer certification sending the certificate is unknown for the first signer.

The user is unknown on the server

The same signature has already been sent to the bank

The public key version is not correct. This code is returned when a customer sends signature files to the financial institution after conversion from an older program version (old ES format) to a new program version (new ES format) without having carried out re-initialisation with regard to a public key change.

Order data and signatures don’t match

File cannot be tested, the complete order has to be repeated. This code is returned in the event of a malfunction during the signature check, e.g. not enough storage space.

The user’s rights (concerning his signature) are insufficient to execute the order

The certificate is revoked for the second signer.

The certificate is not valid (revoked or not active) for the second signer.

The certificate is not present for the second signer.

The authority of signer certification sending the certificate is unknown for the second signer.

Waiting time expired due to incomplete order

The order file was deleted by the bank server (for multiple reasons)

The same user has signed multiple times

The user is not yet activated (technically)

Message routed to the wrong environment.

Invalid date (eg, wrong or missing settlement date)

Invalid creation date and time in Group Header (eg, historic date)

Invalid non bank processing date (eg, weekend or local public holiday)

Future date not supported

Associated message, payment information block or transaction was received after agreed processing cut-off date, i.e., date in the past.

Execution Date has been modified in order for transaction to be processed

Message Identification is not unique.

Payment Information Block is not unique.

Transaction is not unique.

End To End ID is not unique.

Instruction ID is not unique.

Payment or charge is a duplicate of another payment or charge.

Correspondent bank not possible.

Balance of payments complementary info is requested

Settlement of the transaction has failed.

Interbank settlement system not available.

Requested execution date of the payment is not accepted.

Expiry date time of the request-to-pay is too far in the future.

Expiry date time of the request-to-pay is already reached.

Expiration of the payment authorisation due to no use for too long.

Extended Remittance Information (ERI) option is not supported.

File Format incomplete or invalid

Syntax error reason is provided as narrative information in the additional reason information.

Payment Type Information is missing or invalid. Generic usage if cannot specify Service Level or Local Instrument code

Service Level code is missing or invalid

Local Instrument code is missing or invalid

Category Purpose code is missing or invalid

Purpose is missing or invalid

End to End Id missing or invalid

Cheque number missing or invalid

File or transaction cannot be processed due to technical issues at the bank side

Clearing request rejected due it being subject to an abort operation.

Original payment is not eligible to be returned given its current status.

No record of request for cancellation found.

Return following a cancellation request.

Returned as a result of fraud.

Cancellation requested following a transaction that was originated fraudulently. The use of the FraudulentOrigin code should be governed by jurisdictions.

In an FI To FI Customer Credit Transfer: The Status Originator transferred the payment to the next Agent or to a Market Infrastructure. The payment transfer is tracked. No further updates will follow from the Status Originator. In a Financial Institution Credit Transfer with cover: The Status Originator performed the account booking and transferred the cover transaction to the next Reimbursement Agent or to a Market Infrastructure. The payment transfer is tracked. No further updates will follow from the Status Originator.

In an FI To FI Customer Credit Transfer: The Status Originator transferred the payment to the next Agent or to a Market Infrastructure. The payment transfer is not tracked. No further updates will follow from the Status Originator. In a Financial Institution Credit Transfer with cover: The Status Originator performed the account booking and transferred the cover transaction to the next Reimbursement Agent or to a Market Infrastructure. The payment transfer is not tracked. No further updates will follow from the Status Originator.

In a FIToFI Customer Credit Transfer: Credit to the creditor’s account may not be confirmed same day. Update will follow from the Status Originator. In a Financial Institution Credit Transfer with cover: Debit/credit to nostro account may not be confirmed same day or Financial Institution Credit Transfer may not be transferred same day. Update will follow from the Status Originator.

In a FIToFI Customer Credit Transfer: Credit to creditor’s account is pending receipt of required documents. The Status Originator has requested creditor to provide additional documentation. Update will follow from the Status Originator. In a Financial Institution Credit Transfer with cover: Status Originator has requested a previous Agent to provide additional information/correct information. Update will follow from the Status Originator.

In a FIToFI Customer Credit Transfer: Credit to the creditor’s account is pending, status Originator is waiting for funds provided via a cover. Update will follow from the Status Originator.

Payment has been delivered to creditor agent with service level.

Payment has been delivered to creditor agent without service level.

The payment has been passed by the Payment Market Infrastructure to the next agent in the payment chain; receipt has not yet been confirmed.

The payment has been received by the next agent via the Payment Market Infrastructure.

Guaranteed Agreement with Correspondent, therefore Correspondent is the liable party

Signature file was sent to the bank but the corresponding original file has not been sent yet.

Expiry date time of the request-to-pay is incorrect.

Invalid Merchant Category Code

Payer’s activation reference is invalid.

Invalid Channel Type

Details not valid for this field.

Payments in instalments are not supported.

No initial request-to-pay has been received.

Cannot schedule instruction for Night Window.

Invalid Use Case Type

No Mandate

Mandate related information data required by the scheme is missing.

Creditor or creditor's agent should not have collected the direct debit

Return of funds requested by end customer

End customer is deceased.

Multiple identical Charge Types in Charge Breakdown

Information missing for the field or cannot be empty.

Reason has not been specified by end customer

Reason has not been specified by agent.

Reason is provided as narrative information in the additional reason information.

Credit transfer is tagged as an Extended Remittance Information (ERI) transaction but does not contain ERI.

No existing agreement for receiving request-to-pay messages.

No response from Beneficiary.

Customer account is not compliant with regulatory requirements, for example FICA (in South Africa) or any other regulatory requirements which render an account inactive for certain processing.

Continuous Processing Line on Hold Instruction.

Requested payment guarantee (by Creditor) related to a request-to-pay cannot be provided.

Recipient side of the request-to-pay (payer or its request-to-pay service provider) is not reachable.

Settlement of the transaction has been completed and is reported by an intermediary agent or Payment Market Infrastructure on behalf of the Creditor Agent. The credited amount is known.

Settlement of the transaction has been completed and is reported by an intermediary agent or Payment Market Infrastructure on behalf of the Creditor Agent. The credited amount is not known.

Requested optional service (for example instalment payments) is not supported.

Type of payment requested in the request-to-pay is not supported by the payer.

Error code used for RTP-initiated CTR when the pacs.008 details are not aligned with the pain.013 request.

Bank identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode).

Bank identifier is invalid or missing. Generic usage if cannot specify between debit or credit account

Debtor bank identifier is invalid or missing

Creditor bank identifier is invalid or missing

BIC identifier is invalid or missing. Generic usage if cannot specify between debit or credit account.

Debtor BIC identifier is invalid or missing

Creditor BIC identifier is invalid or missing

ClearingSystemMemberidentifier is invalid or missing. Generic usage if cannot specify between debit or credit account

Debtor ClearingSystemMember identifier is invalid or missing

Creditor ClearingSystemMember identifier is invalid or missing

Intermediary Agent is invalid or missing

Creditor Scheme Id is invalid or missing

Originator not active any more.

Settlement agreement required.

Participant blocked from SADC-RTGS.

Conflict with R-Message

Further information regarding the intended recipient.

Request-to-pay has been received and can be processed further.

Transaction reference is not unique within the message.

Payer did not recognize the request from Payee Participant,

Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing

Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.

Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.

Regulatory Reason

Regulatory or Central Bank Reporting information missing, incomplete or invalid.

Tax information missing, incomplete or invalid.

Remittance information structure does not comply with rules for payment type.

Remittance information truncated to comply with rules for payment type.

Structured creditor reference invalid or missing.

Character set supplied not valid for the country and payment type.

Invalid or missing identification of a bank proprietary service.

Invalid or missing identification required within a particular country or payment type.

Debtor does not support request-to-pay transactions.

Return following investigation request and no remediation possible.

Request for Cancellation is acknowledged following validation.

Unique End-to-end Transaction Reference (UETR) relating to a payment has been identified as being associated with a Request for Cancellation.

Unique End-to-end Transaction Reference (UETR) relating to a payment has been prevent from traveling across a messaging network.

Request for Cancellation has been forwarded to the payment processing/last payment processing agent.

Request for Cancellation has been acknowledged as delivered to payment processing/last payment processing agent.

Remove Concurrent Batch Processing Line on hold instruction.

Due to specific service offered by the Debtor Agent.

Due to specific service offered by the Creditor Agent.

Due to a specific service offered by the clearing system.

Whitelisting service offered by the Debtor Agent; Debtor has not included the Creditor on its “Whitelist” (yet). In the Whitelist the Debtor may list all allowed Creditors to debit Debtor bank account.

Blacklisting service offered by the Debtor Agent; Debtor included the Creditor on his “Blacklist”. In the Blacklist the Debtor may list all Creditors not allowed to debit Debtor bank account.

Due to Maximum allowed Direct Debit Transactions per period service offered by the Debtor Agent.

Due to Maximum allowed Direct Debit Transaction amount service offered by the Debtor Agent.

Maximum number of credit transactions allowed by the account servicer per service period exceeded.

Maximum total credit amount allowed by the account servicer per service period exceeded.

Whitelisting service offered by payment system operator or financial institution. Debtor is not included on the Creditor side whitelist.

Blacklisting service offered by payment system operator or financial institution. Debtor included on the Creditor side blacklist.

Services are not yet rendered by the Payee Participant (Creditor).

Identifier of the request-to-pay service provider is incorrect.

The transmission of the file was not successful – it had to be aborted (for technical reasons)

There is no data available (for download)

The file cannot be read (e.g. unknown format)

The file format is incomplete or invalid

Token is invalid.

Token used for the sender does not exist.

Token used for the receiver does not exist.

Token required for request is missing.

Token found with counterparty mismatch.

Single Use Token already used.

Token found with suspended status.

Token found with value limit rule violation.

Token expired.

Associated message, payment information block, or transaction was received after agreed processing cut-off time.

The (technical) transmission of the file was successful.

The order was transferred to pass by accompanying note signed by hand

Unknown Creditor.

Payment is not justified.

Referenced transaction not found

Wrong Debtor Agent in charge request message

Wrong Debtor in charge request message