|
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: | BOPCUS |
|---|---|
| Version: | D |
| Release: | 94B |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 1 |
| Date: | 94-08-19 |
| 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 customer transaction report message (BOPCUS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
Message sent by banks to the Balance of payment (BOP) compiler for reporting - one by one - individual customer transactions (debit and credit) processed during a specific time period. Actually, this transaction information can be distilled - one by one- from PAYORD / PAYMUL / PAYEXT and BOPINF messages respectively.
This message is to be applied in the framework of the data collection for the Balance of Payment compilation.
The content of BOPCUS is extracted from the PAYORD messages and the related messages (PAYMUL / PAYEXT) by the banks.
Sometimes the BOPCUS message could also contain a copy of the relevant segments of the corresponding BOPINF - CREADV messages.
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 of the reporting bank.
Each loop contains all the information related to one transaction processed via the reporting bank.
Note : If the explanation below is refers to a payment order, please read it as a payment or a receipt.
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 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 | 94B | |
| 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 other dates and times relevant to the financial transaction (day, month, year).
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.
A group of segments to give the identification of the reporting agent (generally the bank) or, possibly with a second occurence, the identification of the bank 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 communication number for the party identified in the NAD segment.
A group of segments to accommodate the details corresponding with one payment ordered via a PAYORD / PAYMUL / PAYEXT message or with BOPINF message received during the relevant period.
A segment identifying the line item by a current line number.
A segment giving the identification of the other financial institution abroad involved in the transaction and possibly the account number.
A segment to give the processing date of the transaction.
A segment group to give references and dates of the corresponding PAYORD message or the payment order. A second optional occurrence allows the specification of another reference to the same information.
A segment to give the serial number of the PAYORD related message or the bank reference of the payment order.
A segment to give the day, month & year when the related PAYORD message was emitted or when the payment order was performed.
A group of segments giving the identification (and possible details) of the Payee and the Payor and, for declaration on behalf of somebody else, their "declaring agent" .
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 give the total amount of the payment and the relevant currencies.
A segment to give the total amount of the payment and the relevant currency.
A segment to give 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 providing brief structured cross references to transactions to which the Payment Order relates.
A segment providing brief structured cross reference to transaction to which the Payment Order relates.
A segment identifying the date of issue of the document described in the preceding DOC segment group 7.
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 transaction.
A segment to give information in clear and free form about the nature of transaction.
A segment to give the amount and the currency of the transaction.
A segment to indicate one of the different countries involved in the 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 BOPCUS 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 | |
| CUX | Currencies | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| FII | Financial institution information | |
| 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 | ×9999 | (M) |
| │─├─LIN Line item | ×1 | (M) |
| │─├─FII Financial institution information | ×1 | (C) |
| │─├─DTM Date/time/period | ×1 | (C) |
| │─├─Segment Group 4 | ×2 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×1 | (C) |
| │─├─Segment Group 5 | ×4 | (C) |
| │─│─├─NAD Name and address | ×1 | (M) |
| │─│─├─CTA Contact information | ×1 | (C) |
| │─│─└─COM Communication contact | ×5 | (C) |
| │─├─Segment Group 6 | ×1 | (C) |
| │─│─├─MOA Monetary amount | ×1 | (M) |
| │─│─└─CUX Currencies | ×1 | (C) |
| │─├─Segment Group 7 | ×10 | (C) |
| │─│─├─DOC Document/message details | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×1 | (C) |
| │─└─Segment Group 8 | ×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 9 | ×1 | (C) |
| │─├─AUT Authentication result | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |
