The released the first version of the document ‘Guidance on Reason Codes for R-transactions’ in September 2018.
To give some background: one of the main benefits of the Credit Transfer ( ) scheme is that the scheme rules streamline exception handling, at both process and dataset level. This allows straight-through-processing and automated exception handling end-to-end. Possible exceptions to the normal execution of a transaction include rejects, returns, recalls and requests for recall by the originator (commonly referenced as ‘R-transactions’ and described in detail in the rulebook).
The rulebook specifies reasons which trigger an R-transaction, i.e. data elements required to convey information to the payer (originator) regarding the R-transaction. These data elements identify the type of the R-transaction; name the initiator of the R-transaction; and detail the reason for the R-transaction.
The correct application of these reason codes by a beneficiary bank (the bank of the payee), informing an originator bank (the bank of the payer), about a failed transaction is crucial to allow the originator to determine its reaction. Therefore, scheme participants must apply the specific R-transaction reason codes described in the rulebook when reporting a failed transaction.
Section 3 of the document provides guidance to scheme participants about the reason codes to report specific transaction issues.