0.    INTRODUCTION

       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.    SCOPE

1.1   Functional Definition

       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.

1.2   Field of Application

       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.

1.3   Principles

       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.

2.    REFERENCES

       See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction,
       Section 1.

3.    TERMS AND DEFINITIONS

       See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction,
       Section 2.

4.    MESSAGE DEFINITION

4.1   Data Segment Clarification

       This section should be read in conjunction with the Branching
       Diagram and the Segment Table which indicate mandatory,
       conditional and repeating requirements.

 | 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:

       Data element  0065 BOPBNK
                     0052 D
                     0054 95B
                     0051 UN

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

   DTM, Date/time/period
       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.


   Segment group 1: RFF-DTM
       A group of segments to give auxiliary references and the
       relevant dates for the message itself.

      RFF, Reference
          A segment to give another reference for the message.

      DTM, Date/time/period
          A segment to give the period reported in the message (for
          example day/month/year).


   Segment group 2: NAD-CTA-COM
       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.

      NAD, Name and address
          A segment to identify the resident bank.

      CTA, Contact information
          A segment to identify a person or a department for the party
          specified in the NAD segment and to whom communication
          should be directed.

      COM, Communication contact
          A segment to give a communication number for the party
          identified in the NAD segment.


   Segment group 3: LIN-MOA-SG4
       A group of segments to accommodate the details relevant to the
       transactions performed in one currency.

      LIN, Line item
          A segment identifying the report line item by a current line
          number.

      MOA, Monetary amount
          A segment to give the opening balance and the closing
          balance of the account and the currency.


      Segment group 4: RCS-FTX-SG5
          A group of segments to give for each currency the relevant
          information.

         RCS, Requirements and conditions
             A segment to give the nature of transaction or the type
             of position. A qualifier allows a clear distinction.

         FTX, Free text
             A segment to give information in clear and free form to
             provide explanations about the nature of the transaction
             or about the position.


         Segment group 5: MOA-SG6-SG7-NAD-LOC
             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.

            MOA, Monetary amount
                A segment to give the amount, and if necessary the
                currency, of the transaction or of the position.


            Segment group 6: GIR-QTY-PRI
                A group of segments to give the identification and the
                quantity of security.

               GIR, Related identification numbers
                   A segment to identify the type of security (shares,
                   bonds, etc).

               QTY, Quantity
                   A segment to specify the quantity of security.

               PRI, Price details
                   A segment to give the face value of the security.


            Segment group 7: RFF-DTM
                A group of segments to give the references and dates
                of the transaction.

               RFF, Reference
                   A segment to give the serial number of the
                   transaction.

               DTM, Date/time/period
                   A segment to give the day, month and year of the
                   transaction.

            NAD, Name and address
                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.

            LOC, Place/location identification
                A segment to indicate one of the different countries
                involved.


   Segment group 8: AUT-DTM
       A group of segments to specify the details of authentication.

      AUT, Authentication result
          A segment to specify the details of any authentication
          (validation) procedure applied to the BOPBNK message.

      DTM, Date/time/period
          A segment to identify the date and if necessary, the time of
          validation.

   UNT, Message trailer
       A service segment ending a message, giving the total number of
       segments in the message and the control reference number of the
       message.

4.2   Data segment index (Alphabetical sequence by tag)

          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

 Contents of D.95B