| Version: | D |
|---|---|
| Release: | 04A |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 2004-05-18 |
| SOURCE: | TBG7 Statistics |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, 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 customer transaction report message (BOPCUS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The Balance of payments customer transaction report message (BOPCUS) is sent by banks to the Balance of payments (BOP) compiler for reporting individual customer transactions (debit and credit) processed during a specific time period.
The Balance of payment customer transaction report 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.
The structure of the BOPCUS message is related to the structure of the finance messages (PAYORD / PAYMUL / PAYEXT).
The BOPCUS message can also be used to provide a copy of the relevant contents of a corresponding BOPINF or CREADV message.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Balance of payment customer transaction report message is BOPCUS.
Note: Balance of payment customer transaction report messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | BOPCUS |
| 0052 | D | |
| 0054 | 04A | |
| 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 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.
A segment to specify a reference for the message.
A segment to specify dates related to the reference.
A group of segments to identify the parties associated with the message.
A segment to identify the reporting party (generally the bank) or the bank on behalf of which the declaration is made when the reporting party is a third party.
A segment to identify a person or a department for the party to whom communication should be directed.
A segment to specify a communication number for the party, such as phone number, E-mail or fax number.
A segment to specify free text information relating to the party.
A group of segments to provide the transaction details corresponding to a payment ordered via a PAYORD/PAYMUL/PAYEXT message or to a BOPINF message received during the relevant period.
A segment identifying the transaction by a current line number.
A segment identifying the type of reported transaction.
A segment specifying the identification of the foreign financial institution also involved in the transaction and optionally the account number.
A segment to specify the processing date of the transaction.
A segment group to specify references and dates relating to the transaction.
A segment to specify the reference for the transaction such as the serial number of the related PAYORD message or the bank reference of the payment order.
A segment to specify the date related to the reference such as the date of the related PAYORD message or the date when the payment order was executed.
A group of segments identifying the parties related to the transaction such as the Payee and the Payor and, for a declaration on behalf of a third party, their "declaring agent".
A segment to identify the party related to the transaction.
A segment to identify a person or a department for the party and to whom communication should be directed.
A segment to specify a communication number for the contact such as the phone number or fax number.
A group of segments to specify the monetary amount of the transaction and any relevant currencies.
A segment to specify the monetary amount of the transaction and the currency.
A segment to specify the reference currency (e.g. the currency of the account) and the target currency (e.g. the currency of the transfer) of the payment when they are different.
A group of segments to specify the reason for the transaction. Where the transaction relates to different transactions such as for example composite payments the details of each part of the transaction can be individually specified.
A segment to specify the reason for the transaction.
A segment to specify information in clear and free form about the reason for the transaction.
A segment to specify the amount and the currency of the transaction.
A segment to indicate the different countries involved in the transaction such as country of origin or destination of goods, direct investment country, donation acting country, payment transaction country (creditor or debtor), or the country in which construction work is done.
A group of segments to specify the details related to transactions on financial securities.
A segment to identify the type of security (shares, bonds, etc.).
A segment to specify the quantity of the security.
A segment to specify the face value of the security.
A segment to specify total values for control purposes.
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.
| ATT | Attribute | |
| BGM | Beginning of message | |
| CNT | Control total | |
| COM | Communication contact | |
| CTA | Contact information | |
| CUX | Currencies | |
| DTM | Date/time/period | |
| FII | Financial institution information | |
| FTX | Free text | |
| GIR | Related identification numbers | |
| LIN | Line item | |
| LOC | Place/location identification | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| PRI | Price details | |
| QTY | Quantity | |
| 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 | ×9 | (M) |
| ├─Segment Group 1 | ×9 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| ├─Segment Group 2 | ×9 | (M) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─CTA Contact information | ×1 | (C) |
| │─├─COM Communication contact | ×9 | (C) |
| │─└─FTX Free text | ×99 | (C) |
| ├─Segment Group 3 | ×99999 | (M) |
| │─├─LIN Line item | ×1 | (M) |
| │─├─ATT Attribute | ×1 | (C) |
| │─├─FII Financial institution information | ×9 | (C) |
| │─├─DTM Date/time/period | ×1 | (C) |
| │─├─Segment Group 4 | ×9 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×1 | (C) |
| │─├─Segment Group 5 | ×9 | (C) |
| │─│─├─NAD Name and address | ×1 | (M) |
| │─│─├─CTA Contact information | ×1 | (C) |
| │─│─└─COM Communication contact | ×9 | (C) |
| │─├─Segment Group 6 | ×1 | (C) |
| │─│─├─MOA Monetary amount | ×1 | (M) |
| │─│─└─CUX Currencies | ×1 | (C) |
| │─└─Segment Group 7 | ×99 | (C) |
| │───├─RCS Requirements and conditions | ×1 | (M) |
| │───├─FTX Free text | ×99 | (C) |
| │───├─MOA Monetary amount | ×1 | (C) |
| │───├─LOC Place/location identification | ×9 | (C) |
| │───└─Segment Group 8 | ×1 | (C) |
| │─────├─GIR Related identification numbers | ×1 | (M) |
| │─────├─QTY Quantity | ×1 | (C) |
| │─────└─PRI Price details | ×1 | (C) |
| ├─CNT Control total | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |