BOPCUS Balance of payment customer transaction report

TBG7 Statistics

The Balance of payments customer transaction report message (BOPCUS) is sent by banks to the Balance of payments (BOP) compiler for reporting individual customer transactions (debit and credit) processed during a specific time period.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. A service segment starting and uniquely identifying a message. The message type code for the Balance of payment customer transaction report message is BOPCUS. Note: Balance of payment customer transaction report messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 BOPCUS 0052 D 0054 17A 0051 UN

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

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

  4. Segment group 1
    Repeat 9

    1. A segment to specify a reference for the message.

    2. A segment to specify dates related to the reference.

  5. Segment group 2
    Repeat 9

    1. A segment to identify the reporting party (generally the bank) or the bank on behalf of which the declaration is made when the reporting party is a third party.

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

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

    4. A segment to specify free text information relating to the party.

  6. Segment group 3
    Repeat 99999

    1. A segment identifying the transaction by a current line number.

    2. A segment identifying the type of reported transaction.

    3. A segment specifying the identification of the foreign financial institution also involved in the transaction and optionally the account number.

    4. A segment to specify the processing date of the transaction.

    5. Segment group 4
      Repeat 9

      1. A segment to specify the reference for the transaction such as the serial number of the related PAYORD message or the bank reference of the payment order.

      2. A segment to specify the date related to the reference such as the date of the related PAYORD message or the date when the payment order was executed.

    6. Segment group 5
      Repeat 9

      1. A segment to identify the party related to the transaction.

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

      3. A segment to specify a communication number for the contact such as the phone number or fax number.

    7. Segment group 6
      Repeat 1

      1. A segment to specify the monetary amount of the transaction and the currency.

      2. A segment to specify the reference currency (e.g. the currency of the account) and the target currency (e.g. the currency of the transfer) of the payment when they are different.

    8. Segment group 7
      Repeat 99

      1. A segment to specify the reason for the transaction.

      2. A segment to specify information in clear and free form about the reason for the transaction.

      3. A segment to specify the amount and the currency of the transaction.

      4. A segment to indicate the different countries involved in the transaction such as country of origin or destination of goods, direct investment country, donation acting country, payment transaction country (creditor or debtor), or the country in which construction work is done.

      5. Segment group 8
        Repeat 1

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

        2. A segment to specify the quantity of the security.

        3. A segment to specify the face value of the security.

  7. A segment to specify total values for control purposes.

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

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.