|
|
|
This segment group contains information regarding the debit side of this transaction and details which are pertinent to all payments specified in the message. Certain payment details may be provided either in segment group 4 or in segment group 11, but not in both. |
|
|
|
|
|
This segment group contains information regarding the Beneficiaries of the payments. Certain payment details may be provided either in segment group 11 or in segment group 4, but not in both. |
|
|
|
|
|
A group of segments containing the details of payment. |
|
|
|
|
|
|
Function: |
|
To provide free form or coded text information. |
|
| |
|
EAN
|
*
|
|
|
|
|
Text subject code qualifier |
|
|
M
|
|
|
|
= |
Payment detail/remittance information |
|
|
|
|
|
N
|
|
|
|
|
|
|
D
|
|
|
This composite is only used when trading partners have agreed to use mutually defined code values. |
|
|
|
|
|
M
|
|
|
A code identifying standard text agreed between trading partners. |
|
|
|
|
Code list identification code |
|
|
O
|
|
|
|
|
|
Code list responsible agency code |
|
|
D
|
|
|
|
|
|
|
D
|
|
|
This composite is only used if coded text can not be used. |
|
|
|
|
|
M
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
D
|
|
|
ISO 639 two alpha code. |
|
This data element is only used when non coded free text has been provided in data element C108. |
|
|
|
|
|
N
|
|
|
|
Segment Notes: |
|
This segment is used to provide free or coded text information related to the processing of the payment.
Use of this segment in free form is not recommended since in most cases it inhibits automatic processing of the multiple payment order. Coded references to standard texts is an available functionality which enables automatic processing and reduces transmission and processing overheads. Standard texts should be mutually defined among trading partners and can be used to cover legal and other requirements.
Example:
FTX+PMD+++PAYMENT RELATES TO ACCUMULATED INVOICES JAN 1995' |
|
