Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D97A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Balance of payment information from customer message

Version:D
Release:97A
Contr. Agency:UN
Revision:2
Date:96-12-13
SOURCE:Joint Statistics Group (JM8)

CONTENTS
Balance of payment information from customer message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction


This message also occurs in the following versions of this standard:
D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

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

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.


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


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

Data element0065BOPINF
0052D
005497A
0051UN

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.

0040 Segment Group 1: RFF-DTM

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

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

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.

0110 Segment Group 3: LIN-SG4-SG5

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.

0130 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).

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.

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

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.

0210 Segment Group 6: AUT-DTM

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)

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

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×3 (M)
├─Segment Group 1 ×2 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 2 ×2 (M)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 3 ×999 (C)
├─LIN Line item ×1 (M)
├─Segment Group 4 ×1 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
└─Segment Group 5 ×10 (M)
──├─RCS Requirements and conditions ×1 (M)
──├─FTX Free text ×10 (C)
──├─MOA Monetary amount ×1 (C)
──└─LOC Place/location identification ×4 (C)
├─Segment Group 6 ×1 (C)
├─AUT Authentication result ×1 (M)
└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.