Frames | No Frames
Return to Stylus Studio EDIFACT home page.|
Return to Stylus Studio EDIFACT D99A Messages page.
Balance of payment information from customer message
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.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
The Balance of payment information from customer 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.
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.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1. Standard 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 Segment Table which indicates mandatory, conditional and repeating requirements.
0010 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:
0020 BGM, Beginning of message
A segment to indicate the type and function of the message and to transmit its identifying number.
0030 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.
A group of segments to give auxiliary references and the relevant dates for the message itself.
0050 RFF, Reference
A segment to give another reference for the message.
0060 DTM, Date/time/period
A segment to give the period reported in the message (for example day/month/year).
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.
0080 NAD, Name and address
A segment to identify the resident party.
0090 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.
0100 COM, Communication contact
A segment to give a communication number for the party identified in the NAD segment.
A group of segments to accommodate the details corresponding with one credit advice received during the relevant period.
0120 LIN, Line item
A segment identifying the report line item by a current line number.
A group of segments to give references and dates of the corresponding CREADV message (to be extracted from the CREADV message header).
0140 RFF, Reference
A segment to give the serial number of the received CREADV message.
0150 DTM, Date/time/period
A segment to give the day, month & year of the CREADV message.
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.
0170 RCS, Requirements and conditions
A segment to give the nature of each transaction.
0180 FTX, Free text
A segment to give information in clear and free form about the nature of each transaction.
0190 MOA, Monetary amount
A segment to give the amount and the currency of each transaction.
0200 LOC, Place/location identification
A segment to indicate one of the different countries involved in each transaction.
A group of segments to specify the details of authentication.
0220 AUT, Authentication result
A segment to specify the details of any authentication (validation) procedure applied to the BOPINF message.
0230 DTM, Date/time/period
A segment identifying the validation date/time.
0240 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)
4.3. Message structure
4.3.1. Segment table
Return to Stylus Studio EDIFACT D99A Messages page.