0.    INTRODUCTION

       This specification provides the definition of the Balance of
       payment information from customer message (BOPINF) to be used
       in Electronic Data Interchange (EDI) between trading partners
       involved in administration, commerce and transport.

1.    SCOPE

1.1   Functional Definition

       Message sent by a payee to its bank on receipt of one specified
       amount as a settlement of a transaction with a non-resident.
       The Balance of Payment (BOP) compiler has to be informed of the
       transaction via the payee's bank.

1.2   Field of Application

       Message sent by a payee to its bank on receipt of one specified
       amount as a settlement of a transaction with a non-resident.The
       Balance of Payment (BOP) compiler has to be informed of the
       transaction via the payee's bank.

1.3   Principles

       In some countries the receipt of an external payment has to be
       reported to the BOP compiler via the customer's resident bank.
       
       It is assumed that the payee is informed about the receipt by a
       CREADV message. As far as this message contains relevant BOP
       data (for instance counterparties and the total amount) the
       payee - by referring in the BOPINF message to the CREADV
       message - refrain from reporting this data to its bank.
       
       For reporting to the BOP compiler the payee's bank has to
       combine the CREADV message and the related BOPINF message in
       order to fill in the BOPCUS message.
       
       The main part of the BOPINF message relates to additional BOP
       information related to corresponding transactions and unknown
       by the payee's bank.
       
       The message contains a main loop introduced by a LIN segment
       which is used to accommodate the reporting of a large number of
       transactions without repeating identical information.
       
       Each loop contains the information related to one transaction
       for which a CREADV has been received and for which a BOP
       information has been requested.

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 Balance of payment information
       from customer message is BOPINF.
       
       Note: Balance of payment information from customer messages
       conforming to this document must contain the following data in
       segment UNH, composite S009:

       Data element  0065 BOPINF
                     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 enterprise) or, possibly with a second
       occurrence, the identification of the enterprise on behalf of
       which the declaration is made.

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

      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-SG4-SG5
       A group of segments to accommodate the details corresponding
       with one credit advice received during the relevant period.

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


      Segment group 4: RFF-DTM
          A group of segments to give references and dates of the
          corresponding CREADV message (to be extracted from the
          CREADV message header).

         RFF, Reference
             A segment to give the serial number of the received
             CREADV message.

         DTM, Date/time/period
             A segment to give the day, month & year of the CREADV
             message.


      Segment group 5: RCS-FTX-MOA-LOC
          A group of segments to give the nature of the transaction,
          the amount and geographical detail. If the payment relates
          to different transactions or consists of composite payments
          each transaction has to be specified by its nature, its
          amount and, if necessary its geographical detail.

         RCS, Requirements and conditions
             A segment to give the nature of each transaction.

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

         MOA, Monetary amount
             A segment to give the amount and the currency of each
             transaction.

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


   Segment group 6: 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 BOPINF message.

      DTM, Date/time/period
          A segment identifying the validation date/time.

   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
          LIN Line item
          LOC Place/location identification
          MOA Monetary amount
          NAD Name and address
          RCS Requirements and conditions
          RFF Reference
          UNH Message header
          UNT Message trailer

 Contents of D.95B