| Version: | D |
|---|---|
| Release: | 97B |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 97-07-25 |
| 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 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 message could be sent by banks to BOP compiler for reporting of the banks' own transactions, aggregated individual customer transactions and portfolio transactions. The message could also be used for reporting the assets and liabilities 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.
The message intends to enable a resident bank to report on:
. their own transactions (including portfolio transactions) . the aggregated customer transactions . their own assets and liabilities position
All those reports are handled within the same structure. The difference stands only in the meanings of the segments. A clear distinction between them is simply realized by an adequate and simple use of qualifiers.
In consequence the message is structured in nested loops giving successively all the requested reports one after the other. The first loop giving the type of report, the nested loops giving the relevant details.
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 Segment Table which indicate 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 | 97B | |
| 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 bank) or, possibly with a second occurrence, the identification of the bank on behalf of which the declaration is made.
A segment to identify the resident bank.
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 relevant to the transactions performed in one currency.
A segment identifying the report line item by a current line number.
A segment to give the opening balance and the closing balance of the account and the currency.
A group of segments to give for each currency the relevant information.
A segment to give the nature of transaction or the type of position. A qualifier allows a clear distinction.
A segment to give information in clear and free form to provide explanations about the nature of the transaction or about the position.
A group of segments to give the amount and details of each different nature of the transaction or the amount and details related to the position.
A segment to give the amount, and if necessary the currency, of the transaction or of the position.
A group of segments to give the identification and the quantity of security.
A segment to identify the type of security (shares, bonds, etc.).
A segment to specify the quantity of security.
A segment to give the face value of the security.
A group of segments to give the references and dates of the transaction.
A segment to give the serial number of the transaction.
A segment to give the day, month and year of the transaction.
A segment to give the identification of 2nd party (either the Payor, the Payee or another party). A second occurrence allows the identification of a 3rd party.
A segment to indicate one of the different countries involved.
A group of segments to specify the details of authentication.
A segment to specify the details of any authentication (validation) procedure applied to the BOPBNK message.
A segment to identify the date and if necessary, the time of validation.
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 | |
| 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 | ×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 | (M) |
| │─├─LIN Line item | ×1 | (M) |
| │─├─MOA Monetary amount | ×2 | (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) |
| │─────├─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) |
| │─────├─NAD Name and address | ×1 | (C) |
| │─────└─LOC Place/location identification | ×4 | (C) |
| ├─Segment Group 8 | ×1 | (C) |
| │─├─AUT Authentication result | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |