Where do the reason codes in a pain.002 come from?

From ISO 20022's external code sets, in the set named ExternalStatusReason1Code. The codes are kept outside the message schemas so that ISO can add and change them without issuing a new message version; a pain.002 carries one in StsRsnInf/Rsn/Cd. The 2Q2026 edition of the set holds 315 codes.

What does status reason code AM19 mean?

ISO names AM19 InvalidGroupNumberOfTransactions and defines it as: number of transactions at the group level is invalid or missing. It is about the count the file declares for itself — the NbOfTxs in the group header — not about any one payment.

How often does the ISO 20022 status reason code list change?

Quarterly. ISO's own introduction to the code sets says they are maintained on a quarterly basis, with updated sets published by the end of February, May, August and November, and that further releases can follow new message versions. A code list copied into a system therefore goes out of date, and a code a bank sends may be newer than the list an importer was built against.

Is a status reason code the same as a return reason code?

No, although many four-character codes appear in both. Status reasons (ExternalStatusReason1Code, 315 codes) explain a status in a status report such as pain.002. Return reasons (ExternalReturnReason1Code, 104 codes in the same edition) explain why money that was already sent has come back, in a return message. The same letters can carry a differently worded definition in each set.

ISO 20022 Status Reason Codes: The Full List

An ISO 20022 status reason code is the four characters a bank puts beside a status to say why: AC04, AM05, MD01. They come from one list — ISO's external code set ExternalStatusReason1Code — and its 2Q2026 edition holds 315 of them. A pain.002 carries one in StsRsnInf/Rsn/Cd whenever a payment is rejected, and may carry one beside a pending or accepted status too. This page is the whole list, with ISO's own name and definition for every code, so that the code in front of you is here whichever one it is.

It is a list, not a guide. The codes a corporate actually meets — and what each one means in practice — are in the pain.002 reference, which takes the common ones one by one, and the SEPA direct debit codes with the refund rules behind them. Use that page to understand a reject; use this one when the code is not on it.

How to read a code

Most codes are two letters and two digits, and the two letters say what the reason is about. The larger groups in this edition:

Starts with	What the reason is about	Codes
`AB`	Clearing or settlement aborted, timed out or offline	16
`AC`	The account: its number, its state, its type	16
`AG`	An agent in the chain, or what the agreement with the bank allows	14
`AM`	The amount, the currency or a total	23
`BE`	A party: debtor, creditor, their identification or address	21
`CH`	A detail of the instruction: the execution date, mandate changes, the creditor identifier	19
`DS`	The electronic signature: signers, certificates, and what became of a signed order	37
`DU`	Duplication: an identifier already seen	6
`FF`	The file or the message format	13
`MD`	The direct debit mandate	5
`RC`	A bank, BIC or clearing-system identifier	16
`RR`	A regulatory requirement	12
`SL`	A service a bank offers, or a list or limit the customer keeps there	11

That is a reading aid, not a rule: the grouping is a convention ISO follows, and each code's meaning is its definition below, not its prefix. About eighty are four letters with no number — NARR (the reason is in the free text beside it), CUST, DUPL, NOAS — and those have to be looked up.

Two things about using the list:

A bank chooses which codes it sends. No bank uses all 315; each scheme and each bank's implementation guide narrows the set, and some replace a specific code with a general one. The list says what a code means, not that your bank will send it.
Read the text beside the code. StsRsnInf/AddtlInf is free text the bank may add, and with NARR it is the whole answer. The Bank File Reader shows both for every payment in a status report.

The full list

Names and definitions are ISO's, as published; the names are split into words here because ISO writes them as one (ClosedAccountNumber).

Code	ISO's name for it	Official definition
AB01	Aborted Clearing Timeout	Clearing process aborted due to timeout.
AB02	Aborted Clearing Fatal Error	Clearing process aborted due to a fatal error.
AB03	Aborted Settlement Timeout	Settlement aborted due to timeout.
AB04	Aborted Settlement Fatal Error	Settlement process aborted due to a fatal error.
AB05	Timeout Creditor Agent	Transaction stopped due to timeout at the Creditor Agent.
AB06	Timeout Instructed Agent	Transaction stopped due to timeout at the Instructed Agent.
AB07	Offline Agent	Agent of message is not online. Generic usage if it cannot be determined who exactly is not online.
AB08	Offline Creditor Agent	Creditor Agent is not online.
AB09	Error Creditor Agent	Transaction stopped due to error at the Creditor Agent.
AB10	Error Instructed Agent	Transaction stopped due to error at the Instructed Agent.
AB11	Timeout Debtor Agent	Transaction stopped due to timeout at the Debtor Agent.
AB12	Invalid Concurrent Batch	Duplicate Concurrent Batch Sequence number– for Settlement Instructions.
AB13	Invalid Routing Code Utilised	Wrong Message Routing Type for Return-of-Funds.
AB15	Invalid Account Number For Settlement Type	Instruction may not be placed on the Continuous Processing Line settlement processor.
AB21	Invalid Settlement Agreement Number Specified	Agreement number not valid (beneficiary).
AB26	Invalid Batch Settlement Instruction	Settlement Instruction does not exist.
AC01	Incorrect Account Number	Account number is invalid or missing.
AC02	Invalid Debtor Account Number	Debtor account number invalid or missing
AC03	Invalid Creditor Account Number	Creditor account number invalid or missing
AC04	Closed Account Number	Account number specified has been closed on the bank of account's books.
AC05	Closed Debtor Account Number	Debtor account number closed.
AC06	Blocked Account	Account specified is blocked, prohibiting posting of transactions against it.
AC07	Closed Creditor Account Number	Creditor account number closed
AC08	Invalid Branch Code	Branch code is invalid or missing
AC09	Invalid Account Currency	Account currency is invalid or missing
AC10	Invalid Debtor Account Currency	Debtor account currency is invalid or missing
AC11	Invalid Creditor Account Currency	Creditor account currency is invalid or missing
AC12	Invalid Account Type	Account type missing or invalid. Generic usage if cannot specify between group and payment information levels
AC13	Invalid Debtor Account Type	Debtor account type missing or invalid
AC14	Invalid Creditor Account Type	Creditor account type missing or invalid
AC15	Account Details Changed	The account details for the counterparty have changed.
AC16	Card Number Invalid	Credit or debit card number is invalid.
AEML	Amount Exceeds Max Limit	Requested amount exceeds the limit set by Debtor (Agent)
AEXR	Already Expired RTP	Request-to-pay Expiry Date and Time has already passed.
AG01	Transaction Forbidden	Transaction forbidden on this type of account (formerly NoAgreement)
AG02	Invalid Bank Operation Code	Bank Operation code specified in the message is not valid for receiver
AG03	Transaction Not Supported	Transaction type not supported/authorized on this account.
AG04	Invalid Agent Country	Agent country code is missing or invalid. Generic usage if cannot specify between group and payment information levels.
AG05	Invalid Debtor Agent Country	Debtor agent country code is missing or invalid
AG06	Invalid Creditor Agent Country	Creditor agent country code is missing or invalid
AG07	Unsuccesful Direct Debit	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
AG08	Invalid Access Rights	Transaction failed due to invalid or missing user or access right
AG09	Payment Not Received	Original payment never received.
AG10	Agent Suspended	Agent of message is suspended from the Real Time Payment system. Generic usage if it cannot be determined who exactly is suspended.
AG11	Creditor Agent Suspended	Creditor Agent of message is suspended from the Real Time Payment system.
AG12	Not Allowed Book Transfer	Payment orders made by transferring funds from one account to another at the same financial institution (bank or payment institution) are not allowed.
AG13	Forbidden Return Payment	Returned payments derived from previously returned transactions are not allowed.
AGNT	Incorrect Agent	Agent in the payment workflow is incorrect
ALAC	Already Accepted RTP	Request-to-pay has already been accepted by the Debtor.
AM01	Zero Amount	Specified message amount is equal to zero
AM02	Not Allowed Amount	Specific transaction/message amount is greater than allowed maximum
AM03	Not Allowed Currency	Specified message amount is an non processable currency outside of existing agreement
AM04	Insufficient Funds	Amount of funds available to cover specified message amount is insufficient.
AM05	Duplication	Duplication
AM06	Too Low Amount	Specified transaction amount is less than agreed minimum.
AM07	Blocked Amount	Amount specified in message has been blocked by regulatory authorities.
AM09	Wrong Amount	Amount received is not the amount agreed or expected
AM10	Invalid Control Sum	Sum of instructed amounts does not equal the control sum.
AM11	Invalid Transaction Currency	Transaction currency is invalid or missing
AM12	Invalid Amount	Amount is invalid or missing
AM13	Amount Exceeds Clearing System Limit	Transaction amount exceeds limits set by clearing system
AM14	Amount Exceeds Agreed Limit	Transaction amount exceeds limits agreed between bank and client
AM15	Amount Below Clearing System Minimum	Transaction amount below minimum set by 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 invalid or missing. Generic usage if cannot specify between group and payment information levels.
AM19	Invalid Group Number Of Transactions	Number of transactions at the Group level is 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.
AM22	Zero Amount Not Applied	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.
AM23	Amount Exceeds Settlement Limit	Transaction amount exceeds settlement limit.
AMSE	Attachment Maximum Size	Size of the attachment exceeds the allowed maximum.
APAR	Already Paid RTP	Request To Pay has already been paid by the Debtor.
ARFR	Already Refused RTP	Request-to-pay has already been refused by the Debtor.
ARJR	Already Rejected RTP	Request-to-pay has already been rejected.
ATNS	Attachements Not Supported	Attachments to the request-to-pay are not supported.
BDAY	Not Business Day	Settlement Cycle Day and Calendar day should be the same.
BE01	Inconsistent With End Customer	Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency).
BE04	Missing Creditor Address	Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).
BE05	Unrecognised Initiating Party	Party who initiated the message is not recognised by the end customer
BE06	Unknown End Customer	End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books
BE07	Missing Debtor Address	Specification of debtor's address, which is required for payment, is missing/not correct.
BE08	Missing Debtor Name	Debtor name is missing
BE09	Invalid Country	Country code is missing or Invalid. Generic usage if cannot specifically identify debtor or creditor
BE10	Invalid Debtor Country	Debtor country code is missing or invalid
BE11	Invalid Creditor Country	Creditor country code is missing or invalid
BE12	Invalid Country Of Residence	Country code of residence is missing or Invalid. Generic usage if cannot specifically identify debtor or creditor
BE13	Invalid Debtor Country Of Residence	Country code of debtor's residence is missing or Invalid
BE14	Invalid Creditor Country Of Residence	Country code of creditor's residence is missing or Invalid
BE15	Invalid Identification Code	Identification code missing or invalid. Generic usage if cannot specifically identify debtor or creditor.
BE16	Invalid Debtor Identification Code	Debtor or Ultimate Debtor identification code missing or invalid
BE17	Invalid Creditor Identification Code	Creditor or Ultimate Creditor identification code missing or invalid
BE18	Invalid Contact Details	Contact details missing or invalid
BE19	Invalid Charge Bearer Code	Charge bearer code for transaction type is invalid
BE20	Invalid Name Length	Name length exceeds local rules for payment type.
BE21	Missing Name	Name missing or invalid. Generic usage if cannot specifically identify debtor or creditor.
BE22	Missing Creditor Name	Creditor name is missing
BE23	Account Proxy Invalid	Phone number or email address, or any other proxy, used as the account proxy is unknown or invalid.
CERI	Check ERI	Credit transfer is not tagged as an Extended Remittance Information (ERI) transaction but contains ERI.
CH03	Requested Execution Date Or Requested Collection Date Too Far In Future	Value in Requested Execution Date or Requested Collection Date is too far in the future
CH04	Requested Execution Date Or Requested Collection Date Too Far In Past	Value in Requested Execution Date or Requested Collection Date is too far in the past
CH07	Element Is Not To Be Used At B-and C-Level	Element is not to be used at B- and C-Level
CH09	Mandate Changes Not Allowed	Mandate changes are not allowed
CH10	Information On Mandate Changes Missing	Information on mandate changes are missing
CH11	Creditor Identifier Incorrect	Value in Creditor Identifier is incorrect
CH12	Creditor Identifier Not Unambiguously At Transaction-Level	Creditor Identifier is ambiguous at Transaction Level
CH13	Original Debtor Account Is Not To Be Used	Original Debtor Account is not to be used
CH14	Original Debtor Agent Is Not To Be Used	Original Debtor Agent is not to be used
CH15	Element Content Includes More Than140 Characters	Content Remittance Information/Structured includes more than 140 characters
CH16	Element Content Formally Incorrect	Content is incorrect
CH17	Element Not Admitted	Element is not allowed
CH19	Values Will Be Set To Next TARGETday	Values in Interbank Settlement Date or Requested Collection Date will be set to the next TARGET day
CH20	Decimal Points Not Compatible With Currency	Number of decimal points not compatible with the currency
CH21	Required Compulsory Element Missing	Mandatory element is missing.
CH22	COREand B2 Bwithin Onemessage	SDD CORE and B2B not permitted within one message.
CHCO	Unaccepted Charge Code Type	Related to a Charge message to convey that the code in Charge Breakdown / Type / Code is not accepted by the receiving party.
CHQC	Cheque Settled On Creditor Account	Cheque has been presented in cheque clearing and settled on the creditor’s account.
CHRG	Underlying Charge Bearer Was Not Debt	Related to a Charge message to convey that the charge bearer code used in the corresponding Payment message was not debt.
CN01	Authorisation Cancelled	Authorisation is cancelled.
CNNS	Credit Notes Not Supported	Credit notes are not supported.
CNOR	Creditor Bank Is Not Registered	Creditor bank is not registered under this BIC in the CSM
CURR	Incorrect Currency	Currency of the payment is incorrect
CUST	Requested By Customer	Cancellation requested by the Debtor
DC02	Settlement Not Received	Rejection of a payment due to covering FI settlement not being received.
DNOR	Debtor Bank Is Not Registered	Debtor bank is not registered under this BIC in the CSM
DS01	Electronic Signatures Correct	The electronic signature(s) is/are correct
DS02	Order Cancelled	An authorized user has cancelled the order
DS03	Order Not Cancelled	The user’s attempt to cancel the order was not successful.
DS04	Order Rejected	The order was rejected by the bank side (for reasons concerning content)
DS05	Order Forwarded For Postprocessing	The order was correct and could be forwarded for postprocessing
DS06	Transfer Order	The order was transferred to VEU
DS07	Processing OK	All actions concerning the order could be done by the EBICS bank server
DS08	Decompression Error	The decompression of the file was not successful
DS09	Decryption Error	The 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 not available or invalid.
DS0C	Signer Certificate Revoked	The signer certificate is revoked.
DS0D	Signer Certificate Not Valid	The signer certificate is not valid (revoked or not active).
DS0E	Incorrect Signer Certificate	The signer certificate is not present.
DS0F	Signer Certification Authority Signer Not Valid	The authority of the signer certification sending the certificate is unknown.
DS0G	Not Allowed Payment	Signer is not allowed to sign this operation type.
DS0H	Not Allowed Account	Signer is not allowed to sign for this account.
DS0K	Not Allowed Number Of Transaction	The number of transaction is over the number allowed for this signer.
DS10	Signer1 Certificate Revoked	The certificate is revoked for the first signer.
DS11	Signer1 Certificate Not Valid	The certificate is not valid (revoked or not active) for the first signer.
DS12	Incorrect Signer1 Certificate	The certificate is not present for the first signer.
DS13	Signer Certification Authority Signer1 Not Valid	The authority of signer certification sending the certificate is unknown for the first signer.
DS14	User Does Not Exist	The user is unknown on the server
DS15	Identical Signature Found	The same signature has already been sent to the bank
DS16	Public Key Version Incorrect	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.
DS17	Different Order Data In Signatures	Order data and 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	The user’s rights (concerning his signature) are insufficient to execute the order
DS20	Signer2 Certificate Revoked	The certificate is revoked for the second signer.
DS21	Signer2 Certificate Not Valid	The certificate is not valid (revoked or not active) for the second signer.
DS22	Incorrect Signer2 Certificate	The certificate is not present for the second signer.
DS23	Signer Certification Authority Signer2 Not Valid	The 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	The order file was deleted by the bank server (for multiple reasons)
DS26	User Signed Multiple Times	The same user has signed multiple times
DS27	User Not Yet Activated	The user is not yet activated (technically)
DS28	Return For Technical Reason	Message routed to the wrong environment.
DT01	Invalid Date	Invalid date (eg, wrong or missing settlement date)
DT02	Invalid Creation Date	Invalid creation date and time in Group Header (eg, historic date)
DT03	Invalid Non Processing Date	Invalid non bank processing date (eg, weekend or local public holiday)
DT04	Future Date Not Supported	Future date not supported
DT05	Invalid Cut Off Date	Associated message, payment information block or transaction was received after agreed processing cut-off 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 Identification 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 Or Charge	Payment or charge is a duplicate of another payment or charge.
ED01	Correspondent Bank Not Possible	Correspondent bank not possible.
ED03	Balance Info Request	Balance of payments complementary info is requested
ED05	Settlement Failed	Settlement of the transaction has failed.
ED06	Settlement System Not Available	Interbank settlement system not available.
EDNA	Execution Date Not Accepted	Requested execution date of the payment is not accepted.
EDTL	Expiry Date Too Long	Expiry date time of the request-to-pay is too far in the future.
EDTR	Expiry Date Time Reached	Expiry date time of the request-to-pay is already reached.
EOL1	End Of Life	Expiration of the payment authorisation due to no use for too long.
ERIN	ERIOption Not Supported	Extended Remittance Information (ERI) option is not supported.
FF01	Invalid File Format	File Format incomplete or invalid
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 missing or invalid. Generic usage if cannot specify Service Level or Local Instrument code
FF04	Invalid Service Level Code	Service Level code is missing or invalid
FF05	Invalid Local Instrument Code	Local Instrument code is missing or invalid
FF06	Invalid Category Purpose Code	Category Purpose code is missing or invalid
FF07	Invalid Purpose	Purpose is missing or invalid
FF08	Invalid End To End Id	End to End Id missing or invalid
FF09	Invalid Cheque Number	Cheque number missing or invalid
FF10	Bank System Processing Error	File or transaction cannot be processed due to technical issues at the bank side
FF11	Clearing Request Aborted	Clearing request rejected due it being subject to an abort operation.
FF12	Original Transaction Not Eligible For Requested Return	Original payment is not eligible to be returned given its current status.
FF13	Request For Cancellation Not Found	No record of request for cancellation found.
FOCR	Following Cancellation Request	Return following a cancellation request.
FR01	Fraud	Returned as a result of fraud.
FRAD	Fraudulent Origin	Cancellation requested following a transaction that was originated fraudulently. The use of the FraudulentOrigin code should be governed by jurisdictions.
G000	Payment Transferred And Tracked	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.
G001	Payment Transferred And Not Tracked	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.
G002	Credit Debit Not Confirmed	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.
G003	Credit Pending Documents	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.
G004	Credit Pending Funds	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.
G005	Delivered With Service Level	Payment has been delivered to creditor agent with service level.
G006	Delivered WIthout Service Level	Payment has been delivered to creditor agent without service level.
G007	Payment Passed By Payment Market Infrastructure	The payment has been passed by the Payment Market Infrastructure to the next agent in the payment chain; receipt has not yet been confirmed.
G008	Payment Received By Next Agent Via Payment Market Infrastructure	The payment has been received by the next agent via the Payment Market Infrastructure.
GUAG	Guaranteed Agreement Breached	Guaranteed Agreement with Correspondent, therefore Correspondent is the liable party
ID01	Corresponding Original File Still Not Sent	Signature file was sent to the bank but the corresponding original file has not been sent yet.
IEDT	Incorrect Expiry Date Time	Expiry date time of the request-to-pay is incorrect.
IMCC	Invalid Merchant Category Code	Invalid Merchant Category Code
INAR	Invalid Activation Reference	Payer’s activation reference is invalid.
INCT	Invalid Channel Type	Invalid Channel Type
INDT	Invalid Details	Details not valid for this field.
IPNS	Instalment Payments Not Supported	Payments in instalments are not supported.
IRNR	Initial RTPNever Received	No initial request-to-pay has been received.
ISWS	Invalid Settlement Window	Cannot schedule instruction for Night Window.
IUCT	Invalid Use Case Type	Invalid Use Case Type
MD01	No Mandate	No Mandate
MD02	Missing Mandatory Information In Mandate	Mandate related information data required by the scheme is missing.
MD05	Collection Not Due	Creditor or creditor's agent should not have collected the direct debit
MD06	Refund Request By End Customer	Return of funds requested by end customer
MD07	End Customer Deceased	End customer is deceased.
MICT	Multiple Identical Charge Types	Multiple identical Charge Types in Charge Breakdown
MINF	Missing Information	Information missing for the field or cannot be empty.
MS02	Not Specified Reason Customer Generated	Reason has not been specified by end customer
MS03	Not Specified Reason Agent Generated	Reason has not been specified by agent.
NARR	Narrative	Reason is provided as narrative information in the additional reason information.
NERI	No ERI	Credit transfer is tagged as an Extended Remittance Information (ERI) transaction but does not contain ERI.
NOAR	Non Agreed RTP	No existing agreement for receiving request-to-pay messages.
NOAS	No Answer From Customer	No response from Beneficiary.
NOCM	Not Compliant Generic	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.
NOFR	Outstanding Funding For Settlement	Continuous Processing Line on Hold Instruction.
NOPG	No Payment Guarantee	Requested payment guarantee (by Creditor) related to a request-to-pay cannot be provided.
NRCH	Payer Or Payer RTPSPNot Reachable	Recipient side of the request-to-pay (payer or its request-to-pay service provider) is not reachable.
OBO1	Settlement Completed Reported On Behalf Of Creditor Agent With Amount	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.
OBO2	Settlement Completed Reported On Behalf Of Creditor Agent Without Amount	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.
OSNS	Optional Service Not Supported	Requested optional service (for example instalment payments) is not supported.
PINS	Type Of Payment Instrument Not Supported	Type of payment requested in the request-to-pay is not supported by the payer.
PNRT	Payment Not Aligned With RTPRequest	Error code used for RTP-initiated CTR when the pacs.008 details are not aligned with the pain.013 request.
RC01	Bank Identifier Incorrect	Bank identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode).
RC02	Invalid Bank Identifier	Bank identifier is invalid or missing. Generic usage if cannot specify between debit or credit account
RC03	Invalid Debtor Bank Identifier	Debtor bank identifier is invalid or missing
RC04	Invalid Creditor Bank Identifier	Creditor bank identifier is invalid or missing
RC05	Invalid BICIdentifier	BIC identifier is invalid or missing. Generic usage if cannot specify between debit or credit account.
RC06	Invalid Debtor BICIdentifier	Debtor BIC identifier is invalid or missing
RC07	Invalid Creditor BICIdentifier	Creditor BIC identifier is invalid or missing
RC08	Invalid Clearing System Member Identifier	ClearingSystemMemberidentifier is invalid or missing. Generic usage if cannot specify between debit or credit account
RC09	Invalid Debtor Clearing System Member Identifier	Debtor ClearingSystemMember identifier is invalid or missing
RC10	Invalid Creditor Clearing System Member Identifier	Creditor ClearingSystemMember identifier is invalid or missing
RC11	Invalid Intermediary Agent	Intermediary Agent is invalid or missing
RC12	Missing Creditor Scheme Id	Creditor Scheme Id is invalid or missing
RC13	Participant Not An Active Memberof RTGS	Originator not active any more.
RC15	Participant Not Active Member Settlement Type	Settlement agreement required.
RC16	Participant Not Active Memberof SADCRTGS	Participant blocked from SADC-RTGS.
RCON	RMessage Conflict	Conflict with R-Message
RECI	Receiver Customer Information	Further information regarding the intended recipient.
REPR	RTPReceived Can Be Processed	Request-to-pay has been received and can be processed further.
RF01	Not Unique Transaction Reference	Transaction reference is not unique within the message.
RQNR	Request Not Recognized	Payer did not recognize the request from Payee Participant,
RR01	Missing Debtor Account Or Identification	Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing
RR02	Missing Debtor Name Or Address	Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR03	Missing Creditor Name Or Address	Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR04	Regulatory Reason	Regulatory Reason
RR05	Regulatory Information Invalid	Regulatory or Central Bank Reporting information missing, incomplete or invalid.
RR06	Tax Information Invalid	Tax information missing, incomplete or invalid.
RR07	Remittance Information Invalid	Remittance information structure does not comply with rules for payment type.
RR08	Remittance Information Truncated	Remittance information truncated to comply with rules for payment type.
RR09	Invalid Structured Creditor Reference	Structured creditor reference invalid or missing.
RR10	Invalid Character Set	Character set supplied not valid for the country and payment type.
RR11	Invalid Debtor Agent Service ID	Invalid or missing identification of a bank proprietary service.
RR12	Invalid Party ID	Invalid or missing identification required within a particular country or payment type.
RTNS	RTPNot Supported For Debtor	Debtor does not support request-to-pay transactions.
RUTA	Return Upon Unable To Apply	Return following investigation request and no remediation possible.
S000	Valid Request For Cancellation Acknowledged	Request for Cancellation is acknowledged following validation.
S001	UETRFlagged For Cancellation	Unique End-to-end Transaction Reference (UETR) relating to a payment has been identified as being associated with a Request for Cancellation.
S002	Network Stop Of UETR	Unique End-to-end Transaction Reference (UETR) relating to a payment has been prevent from traveling across a messaging network.
S003	Request For Cancellation Forwarded	Request for Cancellation has been forwarded to the payment processing/last payment processing agent.
S004	Request For Cancellation Delivery Acknowledgement	Request for Cancellation has been acknowledged as delivered to payment processing/last payment processing agent.
SBRN	Settlement Batch Removal Notification	Remove Concurrent Batch Processing Line on hold instruction.
SL01	Specific Service Offered By Debtor Agent	Due to specific service offered by the Debtor Agent.
SL02	Specific Service Offered By Creditor Agent	Due to specific service offered by the Creditor Agent.
SL03	Serviceof Clearing System	Due to a specific service offered by the clearing system.
SL11	Creditor Not On Whitelist Of Debtor	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.
SL12	Creditor On Blacklist Of Debtor	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.
SL13	Maximum Number Of Direct Debit Transactions Exceeded	Due to Maximum allowed Direct Debit Transactions per period service offered by the Debtor Agent.
SL14	Maximum Direct Debit Transaction Amount Exceeded	Due to Maximum allowed Direct Debit Transaction amount service offered by the Debtor Agent.
SL15	Maximum Number Of Credit Transactions Exceeded	Maximum number of credit transactions allowed by the account servicer per service period exceeded.
SL16	Maximum Credit Transactions Amount Exceeded	Maximum total credit amount allowed by the account servicer per service period exceeded.
SL17	Debtor Not On Whitelist Of Creditor Side	Whitelisting service offered by payment system operator or financial institution. Debtor is not included on the Creditor side whitelist.
SL18	Debtor On Blacklist Of Creditor Side	Blacklisting service offered by payment system operator or financial institution. Debtor included on the Creditor side blacklist.
SNRD	Service Not Rendered	Services are not yet rendered by the Payee Participant (Creditor).
SPII	RTPService Provider Identifier Incorrect	Identifier of the request-to-pay service provider is incorrect.
TA01	Transmisson Aborted	The transmission of the file was not successful – it had to be aborted (for technical reasons)
TD01	No Data Available	There is no data available (for download)
TD02	File Non Readable	The file cannot be read (e.g. unknown format)
TD03	Incorrect File Structure	The file format is incomplete or invalid
TK01	Token Invalid	Token is invalid.
TK02	Sender Token Not Found	Token used for the sender does not exist.
TK03	Receiver Token Not Found	Token used for the receiver does not exist.
TK09	Token Missing	Token required for request is missing.
TKCM	Token Counterparty Mismatch	Token found with counterparty mismatch.
TKSG	Token Single Use	Single Use Token already used.
TKSP	Token Suspended	Token found with suspended status.
TKVE	Token Value Limit Exceeded	Token found with value limit rule violation.
TKXP	Token Expired	Token expired.
TM01	Invalid Cut Off Time	Associated message, payment information block, or transaction was received after agreed processing cut-off time.
TS01	Transmission Successful	The (technical) transmission of the file was successful.
TS04	Transfer To Sign By Hand	The order was transferred to pass by accompanying note signed by hand
UCRD	Unknown Creditor	Unknown Creditor.
UPAY	Undue Payment	Payment is not justified.
UTNV	Underlying Transaction Not Valid	Referenced transaction not found
WGDA	Wrong Debtor Agent	Wrong Debtor Agent in charge request message
WGDB	Wrong Debtor	Wrong Debtor in charge request message

What is not on this list

Statuses. ACCP, ACSC, PART, RJCT and the rest are a different set (ExternalPaymentGroupStatus1Code and ExternalPaymentTransactionStatus1Code); they are in the pain.002 reference.
Return reasons. A payment that was executed and then sent back carries a code from ExternalReturnReason1Code. Many are spelt the same as a status reason; they are a separate list of 104.
A bank's own codes. Rsn/Prtry carries a proprietary reason that no ISO list explains; the bank's implementation guide does.

Keeping it current

ISO maintains the external code sets quarterly — new editions by the end of February, May, August and November — so this page is tied to an edition: 2Q2026, file version 3, read on 11 October 2026. The table is generated from ISO's published file rather than typed, and it is regenerated when the edition changes. If a bank sends you a code that is not here, the list has probably moved on: the code lookup searches the same table.