Directory   Messages   Segments   Composites   Data elements   Codes Meaning of the change indicators
  UN/EDIFACT  D.03A (Batch) Syntax version 3 Issue date 2003-06-23  
  Message type specification BOPCUS
 
 
BOPCUS 2 Balance of payment customer transaction report message  
  Date:
2003-06-10

Source:
TBG7 Statistics

0. INTRODUCTION
This specification provides the definition of the Balance of payment customer transaction report message (BOPCUS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.

1. SCOPE

1.1 Functional definition
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.

1.2 Field of application
The Balance of payment customer transaction 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.

1.3 Principles
The structure of the BOPCUS message is related to the structure of the finance messages (PAYORD / PAYMUL / PAYEXT).

The BOPCUS message can also be used to provide a copy of the relevant contents of a corresponding BOPINF or CREADV message.

2. REFERENCES
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.
 
  Generated by GEFEG.FX  
  http://www.gefeg.com