|
|
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 providing information for subsequent use by regulatory authorities requiring statistical and other types of data. It also identifies the regulatory authority for which the information is intended followed by the information itself. |
|
|
|
|
|
Function: |
|
To specify sector/subject requirements and conditions. |
|
|
|
EAN
|
*
|
|
|
|
Sector area identification code qualifier |
|
|
M
|
*
|
|
|
|
REQUIREMENT/CONDITION IDENTIFICATION |
|
|
A
|
|
|
|
|
Requirement or condition description identifier |
|
|
M
|
|
|
As no EDIFACT code values exist for this data element it is recommended that nationally agreed codes be formulated to identify the requirements and conditions possible due to regulatory requirements. |
|
|
|
Code list identification code |
|
|
O
|
|
|
|
|
Code list responsible agency code |
|
|
D
|
|
|
|
= |
Assigned by party originating the message |
|
|
|
Requirement or condition description |
|
|
O
|
|
|
|
|
Action request/notification description code |
|
|
N
|
|
|
|
|
|
N
|
|
|
|
Segment Notes: |
|
This segment is used to indicate any requirements and conditions related to the transaction which is being reported to the regulatory authorities.
Example: RCS+25+AB1::86' Code assigned by the message sender indicating that the requirements and conditions relate to regulatory requirements to report the payment of amount in excess of a certain amount. |
|