|
|
| Function: |
| To indicate the type and function of a message and to transmit the identifying number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document/message name, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code list responsible agency, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Multiple payment order number assigned by the document sender. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Segment Notes: |
All references other than the document number DE 1004 should be put in the RFF segment.
DE 1004: It is recommended that the length of the document number be restricted to a maximum of 17 characters and that the number is unique. 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.
DE 1225: 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.
Example :
BGM+452+233851+9'
|
|