0. INTRODUCTION
1. SCOPE
   1. Functional definition
   2. Field of application
   3. Principles
2. REFERENCES
3. TERMS AND DEFINITIONS
   1. Standard terms and definitions
4. MESSAGE DEFINITION
   1. Segment clarification
   2. Segment index (alphabetical sequence by tag)
   3. Message structure
      1. Segment table

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.

0010 UNH, Message header

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:

0020 BGM, Beginning of message

A segment to indicate the type and function of the message and to transmit its identifying number.

0030 DTM, Date/time/period

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.

0040 Segment Group 1: RFF-DTM

A group of segments to specify references which apply to the whole message and optionally to specify related dates.

0050 RFF, Reference

A segment to specify a reference for the message.

0060 DTM, Date/time/period

A segment to specify dates related to the reference.

0070 Segment Group 2: NAD-CTA-COM-FTX

A group of segments to identify the parties associated with the message.

0080 NAD, Name and address

A segment to identify the resident bank.

0090 CTA, Contact information

A segment to identify a person or a department for the party to whom communication should be directed.

0100 COM, Communication contact

A segment to specify a communication number for the party, such as phone or fax number.

0110 FTX, Free text

A segment to specify additional free text information related to the party.

0120 Segment Group 3: RFF-CUX-MOA-LOC-SG4

A group of segments to specify the details of the reported account and the details of the reported individual transactions.

0130 RFF, Reference

A segment to specify the reference of the reported account.

0140 CUX, Currencies

A segment to specify the currency of the reported account.

0150 MOA, Monetary amount

A segment to specify the opening balance and the closing balance of the reported account.

0160 LOC, Place/location identification

A segment to specify the relevant country related to the reported account.

0170 Segment Group 4: RCS-FTX-SG5

A group of segments to specify information relating to a transaction or position.

0180 RCS, Requirements and conditions

A segment to specify the reason for the transaction or the type of position.

0190 FTX, Free text

A segment to specify information in clear and free form to provide explanations about the reason for the transaction or the position.

0200 Segment Group 5: MOA-ATT-NAD-SG6-SG7-LOC

A group of segments to specify the amount and details associated with each different reason of transaction or position.

0210 MOA, Monetary amount

A segment to specify the amount, and if necessary the currency, of the transaction or of the position.

0220 ATT, Attribute

A segment to specify the type of the reported amount.

0230 NAD, Name and address

A segment to specify the identification of additional related parties such as the Payor, the Payee or a third party).

0240 Segment Group 6: GIR-QTY-PRI

A group of segments to specify the details related to transactions on financial securities.

0250 GIR, Related identification numbers

A segment to identify the type of securities (shares, bonds, etc).

0260 QTY, Quantity

A segment to specify the quantity of the security.

0270 PRI, Price details

A segment to specify the face value of the security.

0280 Segment Group 7: RFF-DTM

A group of segments to specify the references and dates of the transaction.

0290 RFF, Reference

A segment to specify the serial number of the transaction.

0300 DTM, Date/time/period

A segment to specify the date of the transaction.

0310 LOC, Place/location identification

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.

0320 CNT, Control total

A segment to specify total values for control purposes.

0330 UNT, Message trailer

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.