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.
1.1 Functional definition
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.
1.2 Field of application
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.
3. TERMS AND DEFINITIONS
3.1 Standard terms and definitions
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1 Data segment clarification
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.