|
|
|
| |
Function: |
| |
To indicate the type and function of a message and to transmit the identifying number. |
|
| |
|
EAN |
* |
|
|
|
|
|
R |
|
|
|
|
|
|
R |
* |
|
|
|
|
Code list identification code |
|
|
N |
|
|
|
|
|
Code list responsible agency code |
|
|
N |
|
|
|
|
|
|
N |
|
|
|
|
|
DOCUMENT/MESSAGE IDENTIFICATION |
|
|
R |
|
|
|
|
|
|
R |
|
|
Multiple payment order number assigned by the document sender. |
|
The multiple payment order number will be passed to the party ordering the payment on the debit advice or in the statement for the transaction for reconciliation purposes together with the reference number provided in group 4. |
|
For the cancellation of a previously sent Multiple Payment Order message the FINCAN message should be used. |
|
For global unique identification of documents Global Document Type Identifier (GDTI) is available. |
|
|
|
|
|
N |
|
|
|
|
|
|
N |
|
|
|
|
|
|
R |
* |
|
General explanations |
| 7 |
|
= |
|
Duplicate |
| 9 |
|
= |
|
Original |
|
The message function coded, is a critical data element in this segment. It applies to all data indicated in the message. The following definitions apply for the restricted codes: |
|
7 = Duplicate - The message is a duplicate of a previously generated Multiple payment order message. |
|
9 = Original - The original transmission of a Multiple payment order. |
|
|
|
|
|
N |
|
|
|
Segment Notes: |
|
All references other than the document number DE 1004 should be put in the RFF segment.
Example:
BGM+452+233851+9' |
|
