| Version: | D |
|---|---|
| Release: | 03A |
| Contr. Agency: | UN |
| Revision: | 3 |
| Date: | 2003-06-10 |
| 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 Bank transactions and portfolio transactions report message (BOPBNK) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
The Bank transactions and portfolio transactions report message (BOPBNK) can be sent by banks to the BOP compiler for reporting the banks' own transactions, aggregated individual customer transactions and portfolio transactions. The message can also be used for reporting the asset and liability positions of the banks.
The Bank transactions and portfolio transactions 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.
All reports (on the banks' own transactions, on their aggregated customer transactions, or on their own assets and liabilities position) are handled within the same structure. The difference between the types of report are specified by the use of appropriate qualifier codes.
In consequence the message is structured in nested loops giving successively all the requested reports one after the other. The first loop is for providing the type of report and the nested loops within are for providing all the relevant details.
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 Bank transactions and portfolio transactions report message is BOPBNK.
Note: Bank transactions and portfolio transactions report messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | BOPBNK |
| 0052 | D | |
| 0054 | 03A | |
| 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 resident bank.
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 or fax number.
A segment to specify additional free text information related to the party.
A group of segments to specify the details of the reported account and the details of the reported individual transactions.
A segment to specify the reference of the reported account.
A segment to specify the currency of the reported account.
A segment to specify the opening balance and the closing balance of the reported account.
A segment to specify the relevant country related to the reported account.
A group of segments to specify information relating to a transaction or position.
A segment to specify the reason for the transaction or the type of position.
A segment to specify information in clear and free form to provide explanations about the reason for the transaction or the position.
A group of segments to specify the amount and details associated with each different reason of transaction or position.
A segment to specify the amount, and if necessary the currency, of the transaction or of the position.
A segment to specify the type of the reported amount.
A segment to specify the identification of additional related parties such as the Payor, the Payee or a third party).
A group of segments to specify the details related to transactions on financial securities.
A segment to identify the type of securities (shares, bonds, etc).
A segment to specify the quantity of the security.
A segment to specify the face value of the security.
A group of segments to specify the references and dates of the transaction.
A segment to specify the serial number of the transaction.
A segment to specify the date of the transaction.
A segment to identify countries involved in the transaction, such country of origin or destination of the goods, direct investment country, donation acting country, payment transaction country (creditor or debtor) or the country in which the construction work is done.
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 | |
| FTX | Free text | |
| GIR | Related identification numbers | |
| 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 | ×999 | (M) |
| │─├─RFF Reference | ×1 | (M) |
| │─├─CUX Currencies | ×1 | (C) |
| │─├─MOA Monetary amount | ×9 | (C) |
| │─├─LOC Place/location identification | ×1 | (C) |
| │─└─Segment Group 4 | ×999 | (M) |
| │───├─RCS Requirements and conditions | ×1 | (M) |
| │───├─FTX Free text | ×1 | (C) |
| │───└─Segment Group 5 | ×9999 | (M) |
| │─────├─MOA Monetary amount | ×1 | (M) |
| │─────├─ATT Attribute | ×1 | (C) |
| │─────├─NAD Name and address | ×1 | (C) |
| │─────├─Segment Group 6 | ×1 | (C) |
| │─────│─├─GIR Related identification numbers | ×1 | (M) |
| │─────│─├─QTY Quantity | ×1 | (C) |
| │─────│─└─PRI Price details | ×1 | (C) |
| │─────├─Segment Group 7 | ×1 | (C) |
| │─────│─├─RFF Reference | ×1 | (M) |
| │─────│─└─DTM Date/time/period | ×1 | (C) |
| │─────└─LOC Place/location identification | ×9 | (M) |
| ├─CNT Control total | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |