Code | Message | Description |
---|---|---|
AC01 | Account Identifier incorrect (i.e. invalid IBAN of the Debtor) | Specified account number is either incorrect or invalid. |
AC02 | Invalid Debtor Account Number | Debtor account number is either invalid or missing. |
AC03 | Invalid Creditor Account Number | Creditor account number is either invalid or missing. |
AC04 | Account closed | Specified account is closed. |
AC05 | Closed Debtor Account Number | Debtor account is closed. |
AC06 | Account blocked | Specified account is blocked, posting of transactions is prohibited. |
AC07 | Closed Creditor Account Number | Creditor account is closed. |
AC08 | Invalid Branch Code | Branch code is either invalid or missing. |
AC09 | Invalid Account Currency | Account currency is either invalid or missing. |
AC10 | Invalid Debtor Account Currency | Debtor account currency is either invalid or missing. |
AC11 | Invalid Creditor Account Currency | Creditor account currency is either invalid or missing. |
AC12 | Invalid Account Type | Account type is either invalid or missing. |
AC13 | Debtor account is a consumer account | Debtor account type is invalid. Used for SDD B2B collections only. |
AC14 | Invalid Creditor Account Type | Creditor account type is either invalid or missing. |
AG01 | Direct Debit forbidden on this account for regulatory reasons | Submitted transaction is forbidden for this type of account for regulatory reasons. |
AG02 | Operation code/transaction code/sequence type incorrect, invalid file format | 1) Bank operation code specified in the message is invalid; 2) Sequence type is incorrect; 3) SDD schemes: specified identification code of the scheme is incorrect. |
AG03 | Transaction Not Supported | Specified transaction type is not supported or is not authorized on this account. |
AG04 | Invalid Agent Country | Agent country code is either invalid or missing. |
AG05 | Invalid Debtor Agent Country | Debtor agent country code is either invalid or missing. |
AG06 | Invalid Creditor Agent Country | Creditor agent country code is either invalid or missing. |
AG07 | Unsuccessful Direct Debit | Debtor account cannot be debited for a generic reason. Reason code 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. |
AG08 | Invalid Access Rights | Transaction has failed due to invalid or missing user or access rights. |
AGNT | Incorrect Agent | Agent in the payment workflow is incorrect. |
AM01 | Zero Amount | Transaction amount is equal to zero. |
AM02 | Not Allowed Amount | Transaction amount is greater than allowed maximum. |
AM03 | Not Allowed Currency | Specified currency code cannot be processed. |
AM04 | Insufficient Funds | Available balance is not sufficient to cover the amount of the debit entry. |
AM05 | Duplicate collection | Same SDD collection had been processed in the near past. |
AM06 | Too Low Amount | Transaction amount is less than agreed minimum. |
AM07 | Blocked Amount | Amount of funds available to cover specified transaction amount is insufficient. |
AM09 | Wrong Amount | Received amount has not been agreed or expected. |
AM10 | Invalid Control Sum | Sum of instructed amounts does not equal the control sum. |
AM11 | Invalid Transaction Currency | Transaction currency is either invalid or missing. |
AM12 | Invalid Amount | Transaction amount is either invalid or missing. |
AM13 | Amount Exceeds Clearing System Limit | Transaction amount exceeds the limit set by a clearing system. |
AM14 | Amount Exceeds Agreed Limit | Transaction amount exceeds limit agreed between bank and client. |
AM15 | Amount Below Clearing System Minimum | Transaction amount is below minimum value of a clearing system. |
AM16 | Invalid Group Control Sum | Control Sum at the Group level is invalid. |
AM17 | Invalid Payment Info Control Sum | Control sum at the Payment Information level is invalid. |
AM18 | Invalid Number Of Transactions | Number of transactions is either invalid or missing. |
AM19 | Invalid Group Number of Transactions | Number of transactions at the Group level is either invalid or missing. |
AM20 | Invalid Payment Info Number Of Transactions | Number of transactions at the Payment Information level is invalid. |
AM21 | Limit Exceeded | Transaction amount exceeds limits agreed between bank and client. |
ARDT | Transaction has already been returned | Specified transaction has already been returned. |
BE01 | Inconsistent With End Customer | Identification of end customer is not consistent with associated account number. |
BE04 | Missing Creditor Address | Specification of creditor's address, which is required for payment, is either missing or incorrect. |
BE05 | Identifier of the Creditor Incorrect | Creditor identifier is not correct or has been changed without an amendment had been reported. |
BE06 | Unknown End Customer | Specified end customer is not known at associated Sort/National Bank Code or does no longer exist. |
BE07 | Missing Debtor Address | Specification of debtor's address, which is required for payment, is either missing or incorrect. |
BE08 | Missing Debtor Name | Debtor name is missing. |
BE09 | Invalid Country | Country code is either invalid or missing. |
BE10 | Invalid Debtor Country | Debtor country code is either invalid or missing. |
BE11 | Invalid Creditor Country | Creditor country code is is either invalid or missing. |
BE12 | Invalid Country Of Residence | Country code of residence is either invalid or missing. |
BE13 | Invalid Debtor Country Of Residence | Country code of debtor's residence is either invalid or missing. |
BE14 | Invalid Creditor Country Of Residence | Country code of creditor's residence is either invalid or missing. |
BE15 | Invalid Identification Code | Identification code is either invalid or missing. |
BE16 | Invalid Debtor Identification Code | Debtor or Ultimate Debtor identification code is either invalid or missing. |
BE17 | Invalid Creditor Identification Code | Creditor or Ultimate Creditor identification code is either invalid or missing. |
BE18 | Invalid Contact Details | Contact details are either invalid or missing. |
BE19 | Invalid Charge Bearer Code | Charge bearer code for transaction type is invalid. |
BE20 | Invalid Name Length | Name length exceeds local rules for specified payment type. |
BE21 | Missing Name | Name is either invalid or missing. |
BE22 | Missing Creditor Name | Creditor name is missing. |
CNOR | Creditor Bank is not registered under this BIC in the CSM | Creditor bank is not registered under this BIC at the CSM. Contact the creditor bank. |
CURR | Incorrect Currency | Currency of the payment is incorrect. |
CUST | Requested by Customer | Cancellation is requested by the debtor. |
CUTA | Cancel Upon Unable to Apply | Cancellation requested because an investigation request has been received and no remediation is possible. |
DNOR | Debtor Bank is not registered under this BIC in the CSM | Debtor Bank is not registered under this BIC in the CSM. Contact debtor to agree on another means of payment. |
DS01 | Electronic Signatures Correct | Electronic signature is correct. |
DS02 | Order Cancelled | An authorized user has cancelled the order. |
DS03 | Order Not Cancelled | User’s attempt to cancel the order was not successful. |
DS04 | Order Rejected | Order has been rejected by the bank side (for reasons concerning content). |
DS05 | Order Forwarded For Post processing | Order is correct and can be forwarded for post processing. |
DS06 | Transfer Order | Order was transferred to VEU. |
DS07 | Processing OK | All actions concerning the order could be done by the EBICS bank server. |
DS08 | Decompression Error | Decompression of the file was not successful. |
DS09 | Decryption Error | Decryption of the file was not successful. |
DS0A | Data Sign Requested | Data signature is required. |
DS0B | Unknown Data Sign Format | Data signature for the format is invalid or not available. |
DS0C | Signer Certificate Revoked | Signer certificate is revoked. |
DS0D | Signer Certificate Not Valid | Signer certificate is not valid (is either revoked or not active). |
DS0E | Incorrect Signer Certificate | Signer certificate is not present. |
DS0F | Signer Certification Authority Signer Not Valid | Authority of the signer certification sending the certificate is unknown. |
DS0G | Not Allowed Payment | Signer is not allowed to sign an operation of the specified type. |
DS0H | Not Allowed Account | Signer is not allowed to sign for the specified account. |
DS0K | Not Allowed Number Of Transaction | Transaction number is over the number allowed for this signer. |
DS10 | Signer 1 Certificate Revoked | Certificate is revoked for the first signer. |
DS11 | Signer 1 Certificate Not Valid | Certificate is not valid (is either revoked or not active) for the first signer. |
DS12 | Incorrect Signer 1 Certificate | Certificate is not present for the first signer. |
DS13 | Signer Certification Authority Signer 1 Not Valid | Authority of signer certification sending the certificate is unknown for the first signer. |
DS14 | User Does Not Exist | User does not exist within the system. |
DS15 | Identical Signature Found | Same signature has already been sent to the bank. |
DS16 | Public Key Version Incorrect | 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 reinitialisation with regard to a public key change. |
DS17 | Different Order Data In Signatures | Order data in signatures don’t match. |
DS18 | Repeat Order | 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. |
DS19 | Electronic Signature Rights Insufficient | User’s rights (concerning his signature) are insufficient to execute the order. |
DS20 | Signer 2 Certificate Revoked | Certificate is revoked for the second signer. |
DS21 | Signer 2 Certificate Not Valid | Certificate is not valid (is either revoked or not active) for the second signer. |
DS22 | Incorrect Signer 2 Certificate | Certificate is not present for the second signer. |
DS23 | Signer Certification Authority Signer 2 Not Valid | Authority of signer certification sending the certificate is unknown for the second signer. |
DS24 | Waiting Time Expired | Waiting time expired due to incomplete order. |
DS25 | Order File Deleted | Order file has been deleted by the bank server (for multiple reasons). |
DS26 | User Signed Multiple Times | Same user has signed multiple times. |
DS27 | User Not Yet Activated | User is not yet activated (technically). |
DT01 | Invalid Date | Invalid date (e.g. wrong settlement date). |
DT02 | Invalid Creation Date | Invalid creation date and time in Group Header. |
DT03 | Invalid Non Processing Date | Invalid non-processing date (e.g. weekend or local public holiday). |
DT04 | Future Date Not Supported | Future date is not supported. |
DT05 | Invalid Cut Off Date | Associated message, payment information block or transaction was received after agreed processing cutoff date, i.e., date in the past. |
DT06 | Execution Date Changed | Execution date has been modified in order for transaction to be processed. |
DU01 | Duplicate Message ID | Message ID is not unique. |
DU02 | Duplicate Payment Information ID | Payment Information Block is not unique. |
DU03 | Duplicate Transaction | Transaction is not unique. |
DU04 | Duplicate End To End ID | End To End ID is not unique. |
DU05 | Duplicate Instruction ID | Instruction ID is not unique. |
DUPL | Duplicate Payment | Submitted payment is a duplicate of another payment. |
ED01 | Correspondent Bank Not Possible | Correspondent bank is not possible. |
ED03 | Balance Info Request | Сomplementary balance information is requested. |
ED05 | Settlement Failed | Settlement of the transaction has failed. |
EMVL | EMV Liability Shift | Card payment is fraudulent and was not processed with EMV technology for an EMV card. |
FF01 | File Format incomplete or invalid | 1) XML file was not filled out completely or is inorrect; 2) There is a syntax error in the file; 3) Creditor bank or its intermediary bank did not complete a XSD check before submitting the file into the scheme. |
FF02 | Syntax Error | Syntax error reason is provided as narrative information in the additional reason information. |
FF03 | Invalid Payment Type Information | Payment Type Information is either invalid or missing. |
FF04 | Invalid Service Level Code | Service Level code is either invalid or missing. |
FF05 | Operation code/transaction code type incorrect (Direct Debit Type (CORE, COR1) incorrect) | SDD Core: specified identification code of the scheme (i.e. local instrument) is incorrect. |
FF06 | Invalid Category Purpose Code | Category Purpose code is either invalid or missing. |
FF07 | Invalid Purpose | Purpose is either invalid or missing. |
FF08 | Invalid End To End Id | End to End ID is either invalid or missing. |
FF09 | Invalid Cheque Number | Cheque number is either invalid or missing. |
FF10 | Bank System Processing Error | File or transaction cannot be processed due to technical issues at the bank side. |
FOCR | Following Cancellation Request | Designation for a return on the basis of a recall request. |
FRAD | Payment effected fraudulently | Payment is fraudulent originated. |
ID01 | Corresponding Original File Still Not Sent | Signature file was sent to the bank but the corresponding original file has not been sent yet. |
LEGL | Legal Decision | Rejection on legal grounds. |
MD01 | No mandate | 1) Mandate does not exist; 2) B2B mandate have not been confirmed by the debtor; 3) Refund transaction is unauthorised (For SDD Core collections only); 4) Mandate has been cancelled. |
MD02 | Mandate data missing or incorrect | 1) Mandate data in the mandate related information is not identical to those in the mandate (amendments had not been communicated); 2) Mandate data is not consistent with version that has been already received for the UMR; 3) In case of mandate amendment: the original IBAN and the IBAN in the collection are the same. |
MD03 | Invalid File Format For Other Reason Than Grouping Indicator | File format is either incomplete or invalid. |
MD05 | Collection Not Due | Creditor or creditor's agent should not have collected the direct debit. |
MD06 | Disputed authorized transaction | Unconditional refund of a transaction. Used for SDD Core collections only. |
MD07 | Debtor Deceased | Debtor has deceased. Used for SDD Core collections only. |
MD08 | No Mandate Service By Agent | Receiving agent does not offer specified mandate service. |
MD09 | No Mandate Service On Customer | Account is not open to specified mandate service. |
MD10 | No Mandate Service For Specified | Account is not open to specified mandate service for this particular creditor. |
MD11 | Unrecognised Agent | Agent to whom the message needs to be forwarded cannot be located. |
MD12 | Not Unique Mandate Reference | Mandate identification is not unique to the creditor. |
MD13 | Incorrect Customer Authentication | There is a problem with the customer authentication. |
MD14 | Incorrect Agent | Agent in the payment workflow is incorrect. |
MD15 | Incorrect Currency | Specified currency is incorrect. |
MD16 | Requested By Customer | Cancellation/amendment is requested by the debtor. |
MD17 | Requested By Initiating Party | Cancellation/amendment is requested by the creditor. |
MS02 | Refusal by the Debtor | Reason has not been specified by end customer. |
MS03 | Reason not specified | Reason has not been specified by agent. |
NARR | Narrative | Reason is provided as narrative information in the additional reason information. |
NOAS | No Answer From Customer | There is no response from payee. |
NOOR | No Original Transaction Received | Original credit transfer has never been received. |
PART | Partial Rejection Of Bulks | Bulks are partially rejected. |
PINL | PIN Liability Shift | Card payment is fraudulent and was processed as EMV transaction without PIN verification. |
PY01 | The Beneficiary Or The Ordering Bank Is Not Participant In The EBA | Transaction cannot be processed because the beneficiary and/or the ordering bank is not reported as a direct or indirect participant in the EBA. |
RC01 | Bank Identifier (BIC) Incorrect | Specified bank identifier code is mal-formatted or incorrect. |
RC02 | Invalid Bank Identifier | Bank identifier is either invalid or missing. |
RC03 | Invalid Debtor Bank Identifier | Debtor bank identifier is either invalid or missing. |
RC04 | Invalid Creditor Bank Identifier | Creditor bank identifier is either invalid or missing. |
RC05 | Invalid BIC Identifier | BIC identifier is either invalid or missing. |
RC06 | Invalid Debtor BIC Identifier | Debtor BIC identifier is either invalid or missing. |
RC07 | Invalid Creditor BIC Identifier | Creditor BIC identifier is either invalid or missing. |
RC08 | Invalid Clearing System Member Identifier | Clearing System Member identifier is either invalid or missing. |
RC09 | Invalid Debtor Clearing System Member Identifier | Debtor Clearing System Member identifier is either invalid or missing. |
RC10 | Invalid Creditor Clearing System Member Identifier | Creditor Clearing System Member identifier is either invalid or missing. |
RC11 | Invalid Intermediary Agent | Intermediary Agent is either invalid or missing. |
RC12 | Missing Creditor Scheme Id | Creditor Scheme ID is either invalid or missing. |
RF01 | Not Unique Transaction Reference | Transaction reference is not unique within the message. |
RJCT | Complete Rejection Of Bulks | Bulks are rejected completely. |
RR01 | Regulatory Reason | Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing. |
RR02 | Regulatory Reason | Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing. |
RR03 | Regulatory Reason | Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing. |
RR04 | Regulatory Reason | Only to be used for Regulatory Reason other than RR01, RR02 or RR03. |
RR05 | Regulatory Information Invalid | Regulatory or Central Bank Reporting information is either missing, incomplete or invalid. |
RR06 | Tax Information Invalid | Tax information is either missing, incomplete or invalid. |
RR07 | Remittance Information Invalid | Remittance information structure does not comply with rules for specified payment type. |
RR08 | Remittance Information Truncated | Remittance information is truncated to comply with rules for specified payment type. |
RR09 | Invalid Structured Creditor Reference | Structured creditor reference is either invalid or missing. |
RR10 | Invalid Character Set | Supplied character set is not valid for specified country and payment type. |
RR11 | Invalid Debtor Agent Service ID | Identification of a bank proprietary service is either invalid or missing. |
RR12 | Invalid Party ID | Identification required within specified country or payment type is either invalid or missing. |
SL01 | Specific Service offered by the Debtor Bank | All debtor-invoked consumer-right rejects creditor blocking, collection amount limitations and collection frequency limitations. |
SL02 | Specific Service offered by Creditor Agent | Due to specific service offered by the Creditor Agent. |
SVNR | Service Not Rendered | Card payment is returned since rendered cash amount was not correct or goods or a service was not rendered to the customer, e.g. in an ecommerce situation. |
TA01 | Transmisson Aborted | Transmission of the file was not successful and had to be aborted for technical reasons. |
TD01 | No Data Available | There is no data available for downloading. |
TD02 | File Non Readable | File cannot be read (e.g. unknown format). |
TD03 | Incorrect File Structure | File format is either incomplete or invalid. |
TECH | Technical problems resulting in erroneous credit transfer | Techinal problems resulting in erroneous SDDs. |
TM01 | Invalid Cut Off Time | Associated message was received after agreed processing cutoff time. |
TS01 | Transmission Successful | Technical transmission of the file was successful. |
TS04 | Transfer To Sign By Hand | Order was transferred to pass by accompanying note signed by hand. |
UPAY | Undue Payment | Payment is not justified. |
VR01 | Transaction data integrity validation error | Transaction data has not been validated by the processor. |
XD19 | Incorrect IBAN | IBAN format is invalid. Issued if the country code is a valid ISO or SEPA country code but structure of IBAN or check digits is incorrect. |
XD75 | Unauthorised element in the following combination | There is an unauthorised element in the following combination. |
XT13 | Incorrect file structure | Transaction contains at least one unsupported field or at least one mandatory field is missing from the transaction. |
XT27 | Incorrect BIC | Transaction contains at least one element with a BIC that is not SEPA-reachable. |
XT33 | Incorrect XML field | The content of at least one XML element is not in the format required. The invalid XML field is indicated by the error code. |
XT43 | Incorrect type of direct debit | Type of direct debit is incorrect. |
XT53 | Verification of the creditor identifier failed | Verification of creditor indentifiers in structure/checksum has failed. |
XT73 | Invalid Country Code | Two characters forming the country code do not constitute a valid ISO or SEPA country code. |
XT74 | Invalid underlying original transaction | Underlying original transaction is invalid. Further check is required. |
XT75 | Invalid status of underlying original transaction | Status of underlying original transaction is invalid. No further action is required. |
XT77 | The originally instructed amount was not found or does not match the original transaction amount | The originally instructed amount was not found or does not match the original transaction amount. |
XT78 | Amount validation failed | Transaction amount validation has failed. |
XT79 | Debtor Agent is not permitted to receive direct debits | Debtor agent is not permitted to receive direct debits. |
XT80 | Creditor Agent is not permitted to send direct debits | Creditor agent is not permitted to send direct debits. |
XT85 | No Settlement Cycle Available | Settlement cycles are not available. |
XT90 | Invalid use of a Technical BIC | Technical BIC usage is not valid. |
XT99 | Direct debit rejected for other reasons | Credit transfer was rejected for other reasons. |
XX01 | Processing Cancelled | Transaction processing has been cancelled by a customer. |
Code | Message | Description |
---|---|---|
0 | Refer to payer | Reason for non-payment need to be established from the payer. |
1 | Instruction canceled | Paying bank has cancelled an instruction. |
2 | Payer deceased | Account holder is deceased (used in the event of a representative payee, guardian, or trustee). |
3 | Account transferred | Account has been transferred to a new bank or building society. |
4 | Advance notice disputed | Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded. |
5 | No Account | Account number is not recognised at the paying bank. |
6 | No Instruction | Instruction does not exist on paying bank's database. |
7 | Amount differs | Payer states the amount of the direct debit differs from the amount in the advance notiice to payer. |
8 | Amount not yet due | Payers states date of debiting is in advance of the due date specified in the advance notice to the payer. |
9 | Presentation overdue | 1) Payer states date of presentation is more than 3 working days after due date in advance notice to payer; 2) Re-presentation of unpaid direct debit is more than one month from original direct debit processing day. |
A | Service user differs | Identity of service user differs from DDI. |
B | Account Closed | Payer has closed an account for an unknown reason. |
C | Account transferred to a different branch of bank/building society | New account details need to be supplied to the service user. |
D | Advance notice disputed | Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded. |
E | Instruction amended | Paying bank will advise amendment via ADDACS message. |
F | Invalid account type | Paying bank dose not allow direct debits on this type of account. |
G | Bank will not accept Direct Debits on this type of Account | Paying bank does not allow direct debits on this type of account. |
H | Instruction has expired | Occurs when a service user attempts to convert a DDI which is shown as expired on the paying bank's database. |
I | Payer reference is not unique | Paying bank has matched the DDI to an existing DDI with a similar reference that has more or fewer characters. |
K | Instruction canceled by paying bank | Paying bank has cancelled the DDI. |
L | Incorrect payer's Account Details | 1) The sort code or account number has failed the modulus check; 2) The sort code does not exist; 3) The account number is not all numeric or is all zeros; 4) The account type is invalid. |
M | Transaction Code/User Status incompatible | Transaction codes, which are not allowed whilst in this status, have been sent. |
N | Transaction disallowed at payer's branch | Paying banks have disallowed the set-up of DDIs at the branch in field 1 of the transaction. Service user should refer back to their payer and obtain a DDI for a different account. |
O | Invalid reference | The reference in one of the DDI record fields does not comply with the AUDDIS rules. |
P | Payer's Name not present | Validation has detected that payer's name field is blank. A payer's name should always be entered. |
Q | Servise user's name blank | Validation has detected that servise user's name field is blank. A servise user's company or tranding name should always be entered. |
R | Instruction re-instated | Paying bank may re-instate a cancelled DDI up to two months from cancelation. |
V | Transaction data integrity validation error | Transaction data has not been validated by the processor. |
X | Processing Cancelled | Transaction processing has been cancelled by a customer. |
Code | Message | Description |
---|---|---|
AC01 | Account Identifier incorrect (i.e. invalid IBAN of the Debtor) | Specified account number is either incorrect or invalid. |
AC02 | Invalid Debtor Account Number | Debtor account number is either invalid or missing. |
AC03 | Invalid Creditor Account Number | Creditor account number is either invalid or missing. |
AC04 | Account closed | Specified account is closed. |
AC05 | Closed Debtor Account Number | Debtor account is closed. |
AC06 | Account blocked | Specified account is blocked, posting of transactions is prohibited. |
AC07 | Closed Creditor Account Number | Creditor account is closed. |
AC08 | Invalid Branch Code | Branch code is either invalid or missing. |
AC09 | Invalid Account Currency | Account currency is either invalid or missing. |
AC10 | Invalid Debtor Account Currency | Debtor account currency is either invalid or missing. |
AC11 | Invalid Creditor Account Currency | Creditor account currency is either invalid or missing. |
AC12 | Invalid Account Type | Account type is either invalid or missing. |
AC13 | Debtor account is a consumer account | Debtor account type is invalid. Used for SDD B2B collections only. |
AC14 | Invalid Creditor Account Type | Creditor account type is either invalid or missing. |
AG01 | Direct Debit forbidden on this account for regulatory reasons | Submitted transaction is forbidden for this type of account for regulatory reasons. |
AG02 | Operation code/transaction code/sequence type incorrect, invalid file format | 1) Bank operation code specified in the message is invalid; 2) Sequence type is incorrect; 3) SDD schemes: specified identification code of the scheme is incorrect. |
AG03 | Transaction Not Supported | Specified transaction type is not supported or is not authorized on this account. |
AG04 | Invalid Agent Country | Agent country code is either invalid or missing. |
AG05 | Invalid Debtor Agent Country | Debtor agent country code is either invalid or missing. |
AG06 | Invalid Creditor Agent Country | Creditor agent country code is either invalid or missing. |
AG07 | Unsuccessful Direct Debit | Debtor account cannot be debited for a generic reason. Reason code 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. |
AG08 | Invalid Access Rights | Transaction has failed due to invalid or missing user or access rights. |
AGNT | Incorrect Agent | Agent in the payment workflow is incorrect. |
AM01 | Zero Amount | Transaction amount is equal to zero. |
AM02 | Not Allowed Amount | Transaction amount is greater than allowed maximum. |
AM03 | Not Allowed Currency | Specified currency code cannot be processed. |
AM04 | Insufficient Funds | Available balance is not sufficient to cover the amount of the debit entry. |
AM05 | Duplicate collection | Same SDD collection had been processed in the near past. |
AM06 | Too Low Amount | Transaction amount is less than agreed minimum. |
AM07 | Blocked Amount | Amount of funds available to cover specified transaction amount is insufficient. |
AM09 | Wrong Amount | Received amount has not been agreed or expected. |
AM10 | Invalid Control Sum | Sum of instructed amounts does not equal the control sum. |
AM11 | Invalid Transaction Currency | Transaction currency is either invalid or missing. |
AM12 | Invalid Amount | Transaction amount is either invalid or missing. |
AM13 | Amount Exceeds Clearing System Limit | Transaction amount exceeds the limit set by a clearing system. |
AM14 | Amount Exceeds Agreed Limit | Transaction amount exceeds limit agreed between bank and client. |
AM15 | Amount Below Clearing System Minimum | Transaction amount is below minimum value of a clearing system. |
AM16 | Invalid Group Control Sum | Control Sum at the Group level is invalid. |
AM17 | Invalid Payment Info Control Sum | Control sum at the Payment Information level is invalid. |
AM18 | Invalid Number Of Transactions | Number of transactions is either invalid or missing. |
AM19 | Invalid Group Number of Transactions | Number of transactions at the Group level is either invalid or missing. |
AM20 | Invalid Payment Info Number Of Transactions | Number of transactions at the Payment Information level is invalid. |
AM21 | Limit Exceeded | Transaction amount exceeds limits agreed between bank and client. |
ARDT | Transaction has already been returned | Specified transaction has already been returned. |
BE01 | Inconsistent With End Customer | Identification of end customer is not consistent with associated account number. |
BE04 | Missing Creditor Address | Specification of creditor's address, which is required for payment, is either missing or incorrect. |
BE05 | Identifier of the Creditor Incorrect | Creditor identifier is not correct or has been changed without an amendment had been reported. |
BE06 | Unknown End Customer | Specified end customer is not known at associated Sort/National Bank Code or does no longer exist. |
BE07 | Missing Debtor Address | Specification of debtor's address, which is required for payment, is either missing or incorrect. |
BE08 | Missing Debtor Name | Debtor name is missing. |
BE09 | Invalid Country | Country code is either invalid or missing. |
BE10 | Invalid Debtor Country | Debtor country code is either invalid or missing. |
BE11 | Invalid Creditor Country | Creditor country code is is either invalid or missing. |
BE12 | Invalid Country Of Residence | Country code of residence is either invalid or missing. |
BE13 | Invalid Debtor Country Of Residence | Country code of debtor's residence is either invalid or missing. |
BE14 | Invalid Creditor Country Of Residence | Country code of creditor's residence is either invalid or missing. |
BE15 | Invalid Identification Code | Identification code is either invalid or missing. |
BE16 | Invalid Debtor Identification Code | Debtor or Ultimate Debtor identification code is either invalid or missing. |
BE17 | Invalid Creditor Identification Code | Creditor or Ultimate Creditor identification code is either invalid or missing. |
BE18 | Invalid Contact Details | Contact details are either invalid or missing. |
BE19 | Invalid Charge Bearer Code | Charge bearer code for transaction type is invalid. |
BE20 | Invalid Name Length | Name length exceeds local rules for specified payment type. |
BE21 | Missing Name | Name is either invalid or missing. |
BE22 | Missing Creditor Name | Creditor name is missing. |
CNOR | Creditor Bank is not registered under this BIC in the CSM | Creditor bank is not registered under this BIC at the CSM. Contact the creditor bank. |
CURR | Incorrect Currency | Currency of the payment is incorrect. |
CUST | Requested by Customer | Cancellation is requested by the debtor. |
CUTA | Cancel Upon Unable to Apply | Cancellation requested because an investigation request has been received and no remediation is possible. |
DNOR | Debtor Bank is not registered under this BIC in the CSM | Debtor Bank is not registered under this BIC in the CSM. Contact debtor to agree on another means of payment. |
DS01 | Electronic Signatures Correct | Electronic signature is correct. |
DS02 | Order Cancelled | An authorized user has cancelled the order. |
DS03 | Order Not Cancelled | User’s attempt to cancel the order was not successful. |
DS04 | Order Rejected | Order has been rejected by the bank side (for reasons concerning content). |
DS05 | Order Forwarded For Post processing | Order is correct and can be forwarded for post processing. |
DS06 | Transfer Order | Order was transferred to VEU. |
DS07 | Processing OK | All actions concerning the order could be done by the EBICS bank server. |
DS08 | Decompression Error | Decompression of the file was not successful. |
DS09 | Decryption Error | Decryption of the file was not successful. |
DS0A | Data Sign Requested | Data signature is required. |
DS0B | Unknown Data Sign Format | Data signature for the format is invalid or not available. |
DS0C | Signer Certificate Revoked | Signer certificate is revoked. |
DS0D | Signer Certificate Not Valid | Signer certificate is not valid (is either revoked or not active). |
DS0E | Incorrect Signer Certificate | Signer certificate is not present. |
DS0F | Signer Certification Authority Signer Not Valid | Authority of the signer certification sending the certificate is unknown. |
DS0G | Not Allowed Payment | Signer is not allowed to sign an operation of the specified type. |
DS0H | Not Allowed Account | Signer is not allowed to sign for the specified account. |
DS0K | Not Allowed Number Of Transaction | Transaction number is over the number allowed for this signer. |
DS10 | Signer 1 Certificate Revoked | Certificate is revoked for the first signer. |
DS11 | Signer 1 Certificate Not Valid | Certificate is not valid (is either revoked or not active) for the first signer. |
DS12 | Incorrect Signer 1 Certificate | Certificate is not present for the first signer. |
DS13 | Signer Certification Authority Signer 1 Not Valid | Authority of signer certification sending the certificate is unknown for the first signer. |
DS14 | User Does Not Exist | User does not exist within the system. |
DS15 | Identical Signature Found | Same signature has already been sent to the bank. |
DS16 | Public Key Version Incorrect | 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 reinitialisation with regard to a public key change. |
DS17 | Different Order Data In Signatures | Order data in signatures don’t match. |
DS18 | Repeat Order | 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. |
DS19 | Electronic Signature Rights Insufficient | User’s rights (concerning his signature) are insufficient to execute the order. |
DS20 | Signer 2 Certificate Revoked | Certificate is revoked for the second signer. |
DS21 | Signer 2 Certificate Not Valid | Certificate is not valid (is either revoked or not active) for the second signer. |
DS22 | Incorrect Signer 2 Certificate | Certificate is not present for the second signer. |
DS23 | Signer Certification Authority Signer 2 Not Valid | Authority of signer certification sending the certificate is unknown for the second signer. |
DS24 | Waiting Time Expired | Waiting time expired due to incomplete order. |
DS25 | Order File Deleted | Order file has been deleted by the bank server (for multiple reasons). |
DS26 | User Signed Multiple Times | Same user has signed multiple times. |
DS27 | User Not Yet Activated | User is not yet activated (technically). |
DT01 | Invalid Date | Invalid date (e.g. wrong settlement date). |
DT02 | Invalid Creation Date | Invalid creation date and time in Group Header. |
DT03 | Invalid Non Processing Date | Invalid non-processing date (e.g. weekend or local public holiday). |
DT04 | Future Date Not Supported | Future date is not supported. |
DT05 | Invalid Cut Off Date | Associated message, payment information block or transaction was received after agreed processing cutoff date, i.e., date in the past. |
DT06 | Execution Date Changed | Execution date has been modified in order for transaction to be processed. |
DU01 | Duplicate Message ID | Message ID is not unique. |
DU02 | Duplicate Payment Information ID | Payment Information Block is not unique. |
DU03 | Duplicate Transaction | Transaction is not unique. |
DU04 | Duplicate End To End ID | End To End ID is not unique. |
DU05 | Duplicate Instruction ID | Instruction ID is not unique. |
DUPL | Duplicate Payment | Submitted payment is a duplicate of another payment. |
ED01 | Correspondent Bank Not Possible | Correspondent bank is not possible. |
ED03 | Balance Info Request | Сomplementary balance information is requested. |
ED05 | Settlement Failed | Settlement of the transaction has failed. |
EMVL | EMV Liability Shift | Card payment is fraudulent and was not processed with EMV technology for an EMV card. |
FF01 | File Format incomplete or invalid | 1) XML file was not filled out completely or is inorrect; 2) There is a syntax error in the file; 3) Creditor bank or its intermediary bank did not complete a XSD check before submitting the file into the scheme. |
FF02 | Syntax Error | Syntax error reason is provided as narrative information in the additional reason information. |
FF03 | Invalid Payment Type Information | Payment Type Information is either invalid or missing. |
FF04 | Invalid Service Level Code | Service Level code is either invalid or missing. |
FF05 | Operation code/transaction code type incorrect (Direct Debit Type (CORE, COR1) incorrect) | SDD Core: specified identification code of the scheme (i.e. local instrument) is incorrect. |
FF06 | Invalid Category Purpose Code | Category Purpose code is either invalid or missing. |
FF07 | Invalid Purpose | Purpose is either invalid or missing. |
FF08 | Invalid End To End Id | End to End ID is either invalid or missing. |
FF09 | Invalid Cheque Number | Cheque number is either invalid or missing. |
FF10 | Bank System Processing Error | File or transaction cannot be processed due to technical issues at the bank side. |
FOCR | Following Cancellation Request | Designation for a return on the basis of a recall request. |
FRAD | Payment effected fraudulently | Payment is fraudulent originated. |
ID01 | Corresponding Original File Still Not Sent | Signature file was sent to the bank but the corresponding original file has not been sent yet. |
LEGL | Legal Decision | Rejection on legal grounds. |
MD01 | No mandate | 1) Mandate does not exist; 2) B2B mandate have not been confirmed by the debtor; 3) Refund transaction is unauthorised (For SDD Core collections only); 4) Mandate has been cancelled. |
MD02 | Mandate data missing or incorrect | 1) Mandate data in the mandate related information is not identical to those in the mandate (amendments had not been communicated); 2) Mandate data is not consistent with version that has been already received for the UMR; 3) In case of mandate amendment: the original IBAN and the IBAN in the collection are the same. |
MD03 | Invalid File Format For Other Reason Than Grouping Indicator | File format is either incomplete or invalid. |
MD05 | Collection Not Due | Creditor or creditor's agent should not have collected the direct debit. |
MD06 | Disputed authorized transaction | Unconditional refund of a transaction. Used for SDD Core collections only. |
MD07 | Debtor Deceased | Debtor has deceased. Used for SDD Core collections only. |
MD08 | No Mandate Service By Agent | Receiving agent does not offer specified mandate service. |
MD09 | No Mandate Service On Customer | Account is not open to specified mandate service. |
MD10 | No Mandate Service For Specified | Account is not open to specified mandate service for this particular creditor. |
MD11 | Unrecognised Agent | Agent to whom the message needs to be forwarded cannot be located. |
MD12 | Not Unique Mandate Reference | Mandate identification is not unique to the creditor. |
MD13 | Incorrect Customer Authentication | There is a problem with the customer authentication. |
MD14 | Incorrect Agent | Agent in the payment workflow is incorrect. |
MD15 | Incorrect Currency | Specified currency is incorrect. |
MD16 | Requested By Customer | Cancellation/amendment is requested by the debtor. |
MD17 | Requested By Initiating Party | Cancellation/amendment is requested by the creditor. |
MS02 | Refusal by the Debtor | Reason has not been specified by end customer. |
MS03 | Reason not specified | Reason has not been specified by agent. |
NARR | Narrative | Reason is provided as narrative information in the additional reason information. |
NOAS | No Answer From Customer | There is no response from payee. |
NOOR | No Original Transaction Received | Original credit transfer has never been received. |
PART | Partial Rejection Of Bulks | Bulks are partially rejected. |
PINL | PIN Liability Shift | Card payment is fraudulent and was processed as EMV transaction without PIN verification. |
PY01 | The Beneficiary Or The Ordering Bank Is Not Participant In The EBA | Transaction cannot be processed because the beneficiary and/or the ordering bank is not reported as a direct or indirect participant in the EBA. |
RC01 | Bank Identifier (BIC) Incorrect | Specified bank identifier code is mal-formatted or incorrect. |
RC02 | Invalid Bank Identifier | Bank identifier is either invalid or missing. |
RC03 | Invalid Debtor Bank Identifier | Debtor bank identifier is either invalid or missing. |
RC04 | Invalid Creditor Bank Identifier | Creditor bank identifier is either invalid or missing. |
RC05 | Invalid BIC Identifier | BIC identifier is either invalid or missing. |
RC06 | Invalid Debtor BIC Identifier | Debtor BIC identifier is either invalid or missing. |
RC07 | Invalid Creditor BIC Identifier | Creditor BIC identifier is either invalid or missing. |
RC08 | Invalid Clearing System Member Identifier | Clearing System Member identifier is either invalid or missing. |
RC09 | Invalid Debtor Clearing System Member Identifier | Debtor Clearing System Member identifier is either invalid or missing. |
RC10 | Invalid Creditor Clearing System Member Identifier | Creditor Clearing System Member identifier is either invalid or missing. |
RC11 | Invalid Intermediary Agent | Intermediary Agent is either invalid or missing. |
RC12 | Missing Creditor Scheme Id | Creditor Scheme ID is either invalid or missing. |
RF01 | Not Unique Transaction Reference | Transaction reference is not unique within the message. |
RJCT | Complete Rejection Of Bulks | Bulks are rejected completely. |
RR01 | Regulatory Reason | Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing. |
RR02 | Regulatory Reason | Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing. |
RR03 | Regulatory Reason | Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing. |
RR04 | Regulatory Reason | Only to be used for Regulatory Reason other than RR01, RR02 or RR03. |
RR05 | Regulatory Information Invalid | Regulatory or Central Bank Reporting information is either missing, incomplete or invalid. |
RR06 | Tax Information Invalid | Tax information is either missing, incomplete or invalid. |
RR07 | Remittance Information Invalid | Remittance information structure does not comply with rules for specified payment type. |
RR08 | Remittance Information Truncated | Remittance information is truncated to comply with rules for specified payment type. |
RR09 | Invalid Structured Creditor Reference | Structured creditor reference is either invalid or missing. |
RR10 | Invalid Character Set | Supplied character set is not valid for specified country and payment type. |
RR11 | Invalid Debtor Agent Service ID | Identification of a bank proprietary service is either invalid or missing. |
RR12 | Invalid Party ID | Identification required within specified country or payment type is either invalid or missing. |
SL01 | Specific Service offered by the Debtor Bank | All debtor-invoked consumer-right rejects creditor blocking, collection amount limitations and collection frequency limitations. |
SL02 | Specific Service offered by Creditor Agent | Due to specific service offered by the Creditor Agent. |
SVNR | Service Not Rendered | Card payment is returned since rendered cash amount was not correct or goods or a service was not rendered to the customer, e.g. in an ecommerce situation. |
TA01 | Transmisson Aborted | Transmission of the file was not successful and had to be aborted for technical reasons. |
TD01 | No Data Available | There is no data available for downloading. |
TD02 | File Non Readable | File cannot be read (e.g. unknown format). |
TD03 | Incorrect File Structure | File format is either incomplete or invalid. |
TECH | Technical problems resulting in erroneous credit transfer | Techinal problems resulting in erroneous SDDs. |
TM01 | Invalid Cut Off Time | Associated message was received after agreed processing cutoff time. |
TS01 | Transmission Successful | Technical transmission of the file was successful. |
TS04 | Transfer To Sign By Hand | Order was transferred to pass by accompanying note signed by hand. |
UPAY | Undue Payment | Payment is not justified. |
VR01 | Transaction data integrity validation error | Transaction data has not been validated by the processor. |
XD19 | Incorrect IBAN | IBAN format is invalid. Issued if the country code is a valid ISO or SEPA country code but structure of IBAN or check digits is incorrect. |
XD75 | Unauthorised element in the following combination | There is an unauthorised element in the following combination. |
XT13 | Incorrect file structure | Transaction contains at least one unsupported field or at least one mandatory field is missing from the transaction. |
XT27 | Incorrect BIC | Transaction contains at least one element with a BIC that is not SEPA-reachable. |
XT33 | Incorrect XML field | The content of at least one XML element is not in the format required. The invalid XML field is indicated by the error code. |
XT43 | Incorrect type of direct debit | Type of direct debit is incorrect. |
XT53 | Verification of the creditor identifier failed | Verification of creditor indentifiers in structure/checksum has failed. |
XT73 | Invalid Country Code | Two characters forming the country code do not constitute a valid ISO or SEPA country code. |
XT74 | Invalid underlying original transaction | Underlying original transaction is invalid. Further check is required. |
XT75 | Invalid status of underlying original transaction | Status of underlying original transaction is invalid. No further action is required. |
XT77 | The originally instructed amount was not found or does not match the original transaction amount | The originally instructed amount was not found or does not match the original transaction amount. |
XT78 | Amount validation failed | Transaction amount validation has failed. |
XT79 | Debtor Agent is not permitted to receive direct debits | Debtor agent is not permitted to receive direct debits. |
XT80 | Creditor Agent is not permitted to send direct debits | Creditor agent is not permitted to send direct debits. |
XT85 | No Settlement Cycle Available | Settlement cycles are not available. |
XT90 | Invalid use of a Technical BIC | Technical BIC usage is not valid. |
XT99 | Direct debit rejected for other reasons | Credit transfer was rejected for other reasons. |
XX01 | Processing Cancelled | Transaction processing has been cancelled by a customer. |
Code | Message | Description |
---|---|---|
0 | Refer to payer | Reason for non-payment need to be established from the payer. |
1 | Instruction canceled | Paying bank has cancelled an instruction. |
2 | Payer deceased | Account holder is deceased (used in the event of a representative payee, guardian, or trustee). |
3 | Account transferred | Account has been transferred to a new bank or building society. |
4 | Advance notice disputed | Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded. |
5 | No Account | Account number is not recognised at the paying bank. |
6 | No Instruction | Instruction does not exist on paying bank's database. |
7 | Amount differs | Payer states the amount of the direct debit differs from the amount in the advance notiice to payer. |
8 | Amount not yet due | Payers states date of debiting is in advance of the due date specified in the advance notice to the payer. |
9 | Presentation overdue | 1) Payer states date of presentation is more than 3 working days after due date in advance notice to payer; 2) Re-presentation of unpaid direct debit is more than one month from original direct debit processing day. |
A | Service user differs | Identity of service user differs from DDI. |
B | Account Closed | Payer has closed an account for an unknown reason. |
C | Account transferred to a different branch of bank/building society | New account details need to be supplied to the service user. |
D | Advance notice disputed | Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded. |
E | Instruction amended | Paying bank will advise amendment via ADDACS message. |
F | Invalid account type | Paying bank dose not allow direct debits on this type of account. |
G | Bank will not accept Direct Debits on this type of Account | Paying bank does not allow direct debits on this type of account. |
H | Instruction has expired | Occurs when a service user attempts to convert a DDI which is shown as expired on the paying bank's database. |
I | Payer reference is not unique | Paying bank has matched the DDI to an existing DDI with a similar reference that has more or fewer characters. |
K | Instruction canceled by paying bank | Paying bank has cancelled the DDI. |
L | Incorrect payer's Account Details | 1) The sort code or account number has failed the modulus check; 2) The sort code does not exist; 3) The account number is not all numeric or is all zeros; 4) The account type is invalid. |
M | Transaction Code/User Status incompatible | Transaction codes, which are not allowed whilst in this status, have been sent. |
N | Transaction disallowed at payer's branch | Paying banks have disallowed the set-up of DDIs at the branch in field 1 of the transaction. Service user should refer back to their payer and obtain a DDI for a different account. |
O | Invalid reference | The reference in one of the DDI record fields does not comply with the AUDDIS rules. |
P | Payer's Name not present | Validation has detected that payer's name field is blank. A payer's name should always be entered. |
Q | Servise user's name blank | Validation has detected that servise user's name field is blank. A servise user's company or tranding name should always be entered. |
R | Instruction re-instated | Paying bank may re-instate a cancelled DDI up to two months from cancelation. |
V | Transaction data integrity validation error | Transaction data has not been validated by the processor. |
X | Processing Cancelled | Transaction processing has been cancelled by a customer. |