Frames | No Frames
Return to Stylus Studio EDIFACT home page.|
Return to Stylus Studio EDIFACT D02A Messages page.
Balance of payment information from customer message
This specification provides the definition of the Balance of payment information from customer message (BOPINF) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1.1. Functional definition
The Balance of payment information from customer message is sent from a customer to the customer's bank in order to inform the customer's bank of information relating to one or more external payments which have been received in settlement of transactions with non-residents and which must be reported on by the bank to the responsible authority for Balance of Payment reporting purposes.
1.2. Field of application
The Balance of payment information from customer message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
In some countries the receipt of an external payment by a customer has to be reported to the authority responsible for the compilation of Balance of Payments (BOP) statistics via the customer's resident bank.
It is assumed that the customer has previously been informed of the external payment receipt by means of a credit advice (CREADV) message sent by the customer's bank. This means that the customer need only report in the BOPINF message any required Balance of Payment information relating to the transaction which was not contained in the credit advice message as long as a reference to the received credit advice message is included. The main function of the BOPINF message therefore is to provide additional Balance of Payment information related to the external payment and which is unknown by the customer's bank.
For onwards periodic reporting to the authority responsible for the compilation of Balance of Payments statistics the customer's bank has to combine the contents of any referenced CREADV messages with the related BOPINF messages in order to prepare the Balance of payment customer transaction report message (BOPCUS).
The message has been designed with a main detail loop each repetition of which should be used to provide information related to a single credit advice.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1. Standard terms and definitions
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1. Segment clarification
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
0010 UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Balance of payment information from customer message is BOPINF.
Note: Balance of payment information from customer messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of message
A segment to indicate the type and function of the message and to transmit its identifying number.
0030 DTM, Date/time/period
A segment to specify the date and, when required, the time of the creation of the message and optionally to specify other process dates which apply to the whole message.
A group of segments to specify references which apply to the whole message and optionally to specify related dates.
0050 RFF, Reference
A segment to specify a reference for the message.
0060 DTM, Date/time/period
A segment to specify dates related to the reference.
A group of segments to identify the parties associated with the message.
0080 NAD, Name and address
A segment to identify the reporting party and in addition to identify the customer when the reporting party is a third party.
0090 CTA, Contact information
A segment to identify a person or a department for the party to whom communication should be directed.
0100 COM, Communication contact
A segment to specify a communication number for the party.
0110 FTX, Free text
A segment to specify free text information relating to the party.
A group of segments to identify a referenced credit advice message together with any associated transaction details.
0130 RFF, Reference
A segment to specify the reference number of the referenced credit advice message.
0140 DTM, Date/time/period
A segment to specify any dates relating to the referenced credit advice message.
A group of segments to specify the nature of transactions associated with the referenced credit advice, together with any associated amounts and geographical details.
0160 RCS, Requirements and conditions
A segment to specify the nature of a transaction.
0170 FTX, Free text
A segment to specify additional free text information relating to the nature of the transaction.
0180 MOA, Monetary amount
A segment to specify an amount and associated currency for the transaction such as the debit flow amount or the credit flow amount.
0190 LOC, Place/location identification
A segment to identify a country involved in the transaction such as country of origin or country of destination.
0200 CNT, Control total
A segment to specify total values for control purposes such as total value of credit items.
0210 UNT, Message trailer
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
4.2. Segment index (alphabetical sequence by tag)
4.3. Message structure
4.3.1. Segment table
Return to Stylus Studio EDIFACT D02A Messages page.