R messages
Table of contents
- 1. General
- 2. How
- 3. Error codes
General
This page defines how to produce R messages with XMLdation Simulator service. General information about R transactions is available here.
How
Transactions are interpreted as R transactions when special name is used for receiving party of transaction. This means
- name of the Creditor for Credit Transfers
- name of the Debtor for Direct Debits
e.g.
<Cdtr> <Nm>ERR{Return Code}</Nm> <PstlAdr> <TwnNm>Tampere</TwnNm> <Ctry>FI</Ctry> </PstlAdr> </Cdtr> |
Error codes
SCT | SDD | ||||||||
Trigger Code (Nm) | Iso Code | Description (en) | Reject | Return | Recall | Reject | Return | Refund | Reversal |
ERRAC01 | AC01 | Format of the account number specified is not correct | x | x | x | ||||
ERRAC04 | AC04 | Account number specified has been closed on the bank of account's books |
| x | x | ||||
ERRAC06 | AC06 | Account specified is blocked, prohibiting posting of transactions against it. |
| x | x | ||||
ERRAG01 | AG01 | Transaction forbidden on this type of account (formerly NoAgreement) |
| x | x | ||||
ERRAG02 | AG02 | Bank Operation code specified in the message is not valid for receiver | x | x | x | ||||
ERRAM04 | AM04 | Amount of funds available to cover specified message amount is |
|
| x | ||||
ERRAM05 | AM05 | Duplication | x | x | x | x | |||
ERRBE04 | BE04 | Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress) |
| x | x | ||||
ERRFF01 | FF01 | Operation/transaction code incorrect, invalid file format | x | ||||||
ERRFOCR | FOCR | Return following a cancellation request |
| x
| x | ||||
ERRMD01 | MD01 | No Mandate |
|
| x | x | x | ||
ERRMD06 | MD06 | Return of funds requested by end customer |
|
| x | ||||
ERRMD07 | MD07 | End customer is deceased. |
| x | x | x | |||
ERRMS02 | MS02 | Reason has not been specified by end customer |
| x | x | x | x | ||
ERRMS03 | MS03 | Reason has not been specified by agent. | x | x | x | x | x | ||
ERRRC01 | RC01 | Bank Identifier coe specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode). | x | x | x | x | |||
ERRRR01 | RR01 | Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing | x | x | x | x | |||
ERRRR02 | RR02 | Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing. | x | x | x | x | |||
ERRRR03 | RR03 | Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing. | x | x | x | x | |||
ERRRR04 | RR04 | Regulatory Reason | x | x | x | x | |||
ERRSL01 | SL01 | Due to specific service offered by the Debtor Agent |
|
| x | x | |||
ERRTM01 | TM01 | Associated message was received after agreed processing cut-off time. | x |