| |
|
|
|
| |
|
S |
Old Code |
|
| |
1 |
= |
| Message content accepted |
|
| Content of message is accepted. |
|
|
|
|
|
| |
10 |
= |
| Declaration requested |
|
| Declaration is requested. |
|
|
|
|
|
| + |
33 |
= |
| Transaction rejected |
|
| This transaction is rejected by the recipient application and is a single transaction within a multiple transaction message. |
|
|
|
|
|
| + |
36 |
= |
| Changed information |
|
| Processing of information to note that only changes to existing data are transmitted. |
|
|
|
|
|
| |
37 |
= |
| Complete information |
|
| Processing of information to note that complete data details (not just changes) are transmitted. |
|
|
|
|
|
| |
45 |
= |
| Beneficiary's account number unknown |
|
| The account number of the beneficiary is unknown. |
|
|
|
|
|
| |
46 |
= |
| Payee's account number unknown |
|
| The account number of the payee is unknown. |
|
|
|
|
|
| |
47 |
= |
| Payor' account number unknown |
|
| The account number of the payor is unknown. |
|
|
|
|
|
| |
48 |
= |
| Correspondent bank not possible |
|
| The correspondent bank is not a possible one. |
|
|
|
|
|
| |
49 |
= |
| Execution date not possible |
|
| The execution date cannot be met. |
|
|
|
|
|
| |
50 |
= |
| Value date not possible |
|
| The value date cannot be met. |
|
|
|
|
|
| |
51 |
= |
| Currency code not possible |
|
| The currency code does not exist. |
|
|
|
|
|
| + |
53 |
= |
| Orders executed (on) |
|
| Confirmation that the orders have been executed. |
|
|
|
|
|
| |
54 |
= |
| Transaction(s) effected and advised (on) |
|
| Confirmation that the transaction(s) has(ve) been effected and advised. |
|
|
|
|
|
| |
55 |
= |
| Not yet debited |
|
| The amount(s) has(ve) not yet been debited. |
|
|
|
|
|
| @ |
76 |
= |
| Monetary amount incorrect |
|
| The monetary amount specified is incorrect. |
|
GS1 Description:
Code indicating the fact that the amount stated in a previous message is unknown. |
|
|
|
XE2 |
|
| @ |
77 |
= |
| Payments sent correctly |
|
| Confirmation that the payments have been sent correctly. |
|
|
|
YE6 |
|
| @ |
78 |
= |
| Beneficiary has not received the funds |
|
| The beneficiary has not received the funds as specified. |
|
GS1 Description:
Code indicating the fact that the beneficiary identified in a previous message has not received the funds. |
|
|
|
XD1 |
|
| @ |
81 |
= |
| Confirmation of authorization |
|
| The authorization is confirmed. |
|
|
|
XD8 |
|
| @ |
82 |
= |
| Beneficiary's account closed |
|
| The account of the beneficiary is closed. |
|
GS1 Description:
A code indicating the fact that the account of a beneficiary stated in a previous message is closed. |
|
|
|
XD4 |
|
| @ |
83 |
= |
| Transaction execution pending |
|
| The transaction is awaiting execution. |
|
GS1 Description:
Code indicating the fact that a transaction is pending. |
|
|
|
XE6 |
|
| @ |
85 |
= |
| Party identification not known |
|
| The identification of the party is unknown. |
|
GS1 Description:
Code indicating the fact that the party identification sent in a previous message is unknown. |
|
|
|
XE3 |
|
| @ |
86 |
= |
| Beneficiary unknown |
|
| The beneficiary indicated is unknown. |
|
GS1 Description:
Code indicating the fact that the beneficiary stated in a previous message is unknown. |
|
|
|
XD3 |
|
| @ |
87 |
= |
| Beneficiary's bank unknown |
|
| The indicated beneficiary's bank is unknown. |
|
GS1 Description:
Code indicating the fact that the beneficiary's bank stated in a previous message is unknown. |
|
|
|
XD5 |
|
| + |
94 |
= |
| Delivery point driven scheduling method |
|
| Scheduling method used when for a given delivery point a number of different products are to be delivered. |
|
|
|
|
|
| + |
95 |
= |
| Product driven scheduling method |
|
| Scheduling method used when a given product is to be delivered to a number of different delivery points. |
|
|
|
|
|
| @ |
97 |
= |
| Beneficiary has received funds |
|
| The beneficiary has received the funds. |
|
|
|
YE7 |
|
| @ |
112 |
= |
| Bank branch number and/or details invalid |
|
| The bank branch number and/or details are not valid. |
|
GS1 Description:
The branch number/details provided by the ordering customer are incorrect. |
|
|
|
YH8 |
|
| @ |
113 |
= |
| Message from ordering customer did not contain all data required |
|
| The message received from the ordering customer did not contain all the required data. |
|
GS1 Description:
The message received from the ordering customer did not contain all information which was required by the ordered bank to process the instruction. |
|
|
|
YH9 |
|
| @ |
114 |
= |
| Date of cheque invalid |
|
| The date provided on a cheque is invalid. |
|
|
|
YJ1 |
|
| @ |
115 |
= |
| Totals for transaction do not match details |
|
| Figures for the total transaction do not match those provided for the individual lines of the transaction. |
|
|
|
YJ2 |
|
| @ |
116 |
= |
| Transaction different to normal |
|
| A transaction whose details do not conform to the average details normally contained in the transaction. |
|
|
|
YJ3 |
|
| @ |
117 |
= |
| Method of payment invalid |
|
| The method of payment is not valid. |
|
GS1 Description:
The method of payment indicated by the ordering customer is not valid for the beneficiary. |
|
|
|
YJ4 |
|
| @ |
118 |
= |
| Ordering customer's payment order number invalid |
|
| The payment order number issued by the ordering customer is invalid. |
|
GS1 Description:
The payment order number issued by the ordering customer is invalid (e.g. no value, or duplicates a value already issued). |
|
|
|
YJ5 |
|
| @ |
119 |
= |
| Ordering customer's message control value invalid |
|
| The control value provided by the ordering customer in the control totals segment is invalid. |
|
GS1 Description:
The message control value provided by the ordering customer in the CNT segment is invalid (i.e. the CNT value does not confirm with the sum of the details). |
|
|
|
YJ6 |
|
| @ |
120 |
= |
| Ordering customer's message control quantity invalid |
|
| The control quantity provided by the ordering customer in the control totals segment is invalid. |
|
GS1 Description:
The message control transaction quantity provided by the ordering customer in the CNT segment is invalid (i.e. the CNT transaction quantity does not confirm with the sum of details). |
|
|
|
YJ7 |
|
| @ |
121 |
= |
| Beneficiary's account frozen by legal authorities |
|
| The beneficiary's account has been frozen by legal authorities. |
|
|
|
YJ8 |
|
| @ |
122 |
= |
| Invalid cancellation request because transaction already executed |
|
| The request to cancel a transaction is invalid because the transaction has already been executed. |
|
|
|
YJ9 |
|
| @ |
123 |
= |
| Account holder specified by ordering customer is deceased |
|
| The account holder detailed by the ordering customer is deceased. |
|
|
|
YK1 |
|
| @ |
124 |
= |
| Ordering customer's instruction is a duplicate |
|
| The ordering customer's instruction duplicates an instruction. |
|
GS1 Description:
An instruction from an ordering customer is a duplicate of a previous instruction already processed. |
|
|
|
YK2 |
|
| |
XD6 |
= |
| Financial information incorrect (SWIFT Code) |
|
| Code indicating the fact that the financial information stated in a previous message is unknown. |
|
|
|
|
|
| |
XE1 |
= |
| Other dates not correct (SWIFT Code) |
|
| Code indicating the fact that other dates stated in a previous message is unknown. |
|
|
|
|
|
| |
YE7 |
= |
| Beneficiary has received the funds (SWIFT Code) |
|
| Code indicating the fact that the beneficiary identified in a previous message has received the funds. |
|
|
|
|
|
| |
YF3 |
= |
| Financial information incorrect (SWIFT Code) |
|
| Financial information contained in a previous message is incorrect. |
|
|
|
|
|
| |
YF4 |
= |
| Currency segment contents not correct (SWIFT Code) |
|
| Information contained in the currency segment of a previous message is incorrect. |
|
|
|
|
|
| + |
ZZZ |
= |
| Mutually defined |
|
| Mutually defined indicator. |
|
|
|
|
|
