|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4. Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued. The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags. |
| Message Type: | BOPINF |
|---|---|
| Version: | D |
| Release: | 96A |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 2 |
| Date: | 95-11-23 |
| SOURCE: | Joint Statistics Group (JM8) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
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.
Message sent by a payee to its bank on receipt of one specified amount as a settlement of a transaction with a non-resident. The Balance of Payment (BOP) compiler has to be informed of the transaction via the payee's bank.
The Balance of payment information from customer message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
In some countries the receipt of an external payment has to be reported to the BOP compiler via the customer's resident bank.
It is assumed that the payee is informed about the receipt by a CREADV message. As far as this message contains relevant BOP data (for instance counterparties and the total amount) the payee - by referring in the BOPINF message to the CREADV message - refrain from reporting this data to its bank.
For reporting to the BOP compiler the payee's bank has to combine the CREADV message and the related BOPINF message in order to fill in the BOPCUS message.
The main part of the BOPINF message relates to additional BOP information related to corresponding transactions and unknown by the payee's bank.
The message contains a main loop introduced by a LIN segment which is used to accommodate the reporting of a large number of transactions without repeating identical information.
Each loop contains the information related to one transaction for which a CREADV has been received and for which a BOP information has been requested.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
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:
| Data element | 0065 | BOPINF |
| 0052 | D | |
| 0054 | 96A | |
| 0051 | UN |
A segment to indicate the type and function of the message and to transmit its identifying number.
A segment to specify the date and, when required, the time at which the message has been created as well as specification of other process dates.
A group of segments to give auxiliary references and the relevant dates for the message itself.
A segment to give another reference for the message.
A segment to give the period reported in the message (for example day/month/year).
A group of segments to give the identification of the reporting agent (generally the enterprise) or, possibly with a second occurrence, the identification of the enterprise on behalf of which the declaration is made.
A segment to identify the resident party.
A segment to identify a person or a department for the party specified in the NAD segment and to whom communication should be directed.
A segment to give a communication number for the party identified in the NAD segment.
A group of segments to accommodate the details corresponding with one credit advice received during the relevant period.
A segment identifying the report line item by a current line number.
A group of segments to give references and dates of the corresponding CREADV message (to be extracted from the CREADV message header).
A segment to give the serial number of the received CREADV message.
A segment to give the day, month & year of the CREADV message.
A group of segments to give the nature of the transaction, the amount and geographical detail. If the payment relates to different transactions or consists of composite payments each transaction has to be specified by its nature, its amount and, if necessary its geographical detail.
A segment to give the nature of each transaction.
A segment to give information in clear and free form about the nature of each transaction.
A segment to give the amount and the currency of each transaction.
A segment to indicate one of the different countries involved in each transaction.
A group of segments to specify the details of authentication.
A segment to specify the details of any authentication (validation) procedure applied to the BOPINF message.
A segment identifying the validation date/time.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| AUT | Authentication result | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FTX | Free text | |
| LIN | Line item | |
| LOC | Place/location identification | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| RCS | Requirements and conditions | |
| RFF | Reference | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×3 | (M) |
| ├─Segment Group 1 | ×2 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| ├─Segment Group 2 | ×2 | (M) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─CTA Contact information | ×1 | (C) |
| │─└─COM Communication contact | ×5 | (C) |
| ├─Segment Group 3 | ×999 | (C) |
| │─├─LIN Line item | ×1 | (M) |
| │─├─Segment Group 4 | ×1 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×1 | (C) |
| │─└─Segment Group 5 | ×10 | (M) |
| │───├─RCS Requirements and conditions | ×1 | (M) |
| │───├─FTX Free text | ×10 | (C) |
| │───├─MOA Monetary amount | ×1 | (C) |
| │───└─LOC Place/location identification | ×4 | (C) |
| ├─Segment Group 6 | ×1 | (C) |
| │─├─AUT Authentication result | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |