Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D95B Messages page.
UN/EDIFACT
DRAFT RECOMMENDATION

Direct balance of payment declaration message

This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4.

Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued.

The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags.


Message Type:BOPDIR
Version:D
Release:95B
Contr. Agency:UN
Status:1
Revision:1
Date:95-07-07
SOURCE:Joint Rapporteurs Message Design Group JM8

CONTENTS
Direct balance of payment declaration message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
  5. MESSAGE DEFINITION
    1. Data segment clarification
      1. Header section
      2. Detail section
      3. Summary section
    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 Direct balance of payment declaration message (BOPDIR) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

The message can be sent by non-bank residents to report directly to the Balance of Payments (BOP) compiler on:

. transactions via bank accounts held at a resident bank . transactions via bank accounts held at a non-resident bank . transactions and clearing via accounts with non-bank non-residents . foreign assets and liabilities . information in the context of a BOP-related survey (stocks and flows); for those countries which base their compilation of the BOP on surveys.


1.2. Field of Application

This message is to be applied in the framework of the data collection for the Balance of Payment compilation.


1.3. Principles

The message , which contains 3 parts, is sent by enterprises (non-banks) to the BOP compiler to supply information on amounts received from non-residents via resident banks. This is an alternative route to sending a BOPINF message. Or, as is the case in France, to report on all their transactions, payments and receipts.

This part deals with part 1 of the message.

This message could also be used for reporting on settlements via external bank accounts, current accounts held abroad with non-banks or participation in an international clearing system.

This part deals with part 2 of the message.

Further, this message could also be used for reporting results for all types of BOP-related surveys : either for reporting results of general questionnaires or for specific questionnaires such as the reports on positions (foreign assets and liabilities)

This part deals with part 3 of the message.

Each part is independent from each other. A message can contain one, two or all of them.


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.


4.1.1. Header section

Information to be provided in the Header section:

0010 | UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Direct balance of payment declaration message is BOPDIR.

Note: Direct balance of payment declaration messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065BOPDIR
0052D
005495B
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 other dates and times relevant to the financial transaction (day, month, year).

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.

Part 1 : direct reporting of transactions via resident bank accounts.

This part of the message gives for all the resident bank accounts the requested information. The information is given for each account separately.

0110 Segment Group 3: LIN-FII-SG4

A group of segments to accommodate the details relevant to the transactions performed via one account during the relevant period.

0120 LIN, Line item

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

0130 FII, Financial institution information

A segment giving the identification of the resident's financial institution involved.

0140 Segment Group 4: RCS-FTX-SG5-NAD-SG6-LOC

A group of segments to give the nature and the amount of each transaction processed via one account during the relevant period.

0150 RCS, Requirements and conditions

A segment to give the nature of transaction.

0160 FTX, Free text

A segment to give information in clear and free form about the nature of transaction.

0170 Segment Group 5: RFF-DTM

A group of segments to give references and dates of the transaction.

0180 RFF, Reference

A segment to give the serial number of the transaction.

0190 DTM, Date/time/period

A segment to give the day, month and year of the transaction.

0200 NAD, Name and address

A segment to give the identification of the 2nd party (either the Payor, the Payee or another non-bank party).

0210 Segment Group 6: MOA-CUX

A group of segments to give the amount and the currency details of that transaction.

0220 MOA, Monetary amount

A segment to give the amount of the transaction and the relevant currency.

0230 CUX, Currencies

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

0240 LOC, Place/location identification

A segment to indicate on of the different countries involved in the transaction.


4.1.2. Detail section

Information to be provided in the Detail section:

0250 UNS, Section control

A service segment placed at the start of the detail section to avoid collision.

Part 2 : direct reporting of transactions via accounts held with non-residents.

This part of the message gives for all the accounts held abroad with banks or non-banks the requested information. The information is given for each account separately.

0260 Segment Group 7: LIN-RCS-FII-NAD-MOA-SG8

A group of segments to accommodate the details relevant to the transactions performed via one account during the relevant period.

0270 LIN, Line item

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

0280 RCS, Requirements and conditions

A segment to give the type of the account or the reporting form.

0290 FII, Financial institution information

A segment to identify the non-resident financial institution where the resident's external account is held.

0300 NAD, Name and address

A segment to identify the non-resident non-bank institution where the account is held.

0310 MOA, Monetary amount

A segment to give the opening balance and the closing balance of that account and the relevant currency.

0320 Segment Group 8: RCS-FTX-SG9-SG10-FII-NAD-MOA-LOC

A group of segments to give the type, the amount and the relevant details of each different transaction performed via the account.

0330 RCS, Requirements and conditions

A segment to give the nature of transaction (e.g. exports of goods, transport services, purchase of shares).

0340 FTX, Free text

A segment to give information in clear and free form about the nature of that part of the transaction.

0350 Segment Group 9: GIR-QTY-PRI

A group of segments to give the identification and the quantity of security.

0360 GIR, Related identification numbers

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

0370 QTY, Quantity

A segment to specify the quantity of security.

0380 PRI, Price details

A segment to give the face value of the security.

0390 Segment Group 10: RFF-DTM

A group of segments to give references and dates of the transaction.

0400 RFF, Reference

A segment to give the serial number of the transaction.

0410 DTM, Date/time/period

A segment to give the day, month and year of the transaction.

0420 FII, Financial institution information

A segment to identify the domestic bank related to a specific flow of amount related to the transaction (provisioning or repatriating with an account held locally).

0430 NAD, Name and address

A segment to identify the counterparty.

0440 MOA, Monetary amount

A segment to give the amount and the currency of the transaction.

0450 LOC, Place/location identification

A segment to indicate one of the different countries involved.

Part 3 : direct reporting of BOP-related surveys and of foreign assets and liabilities.

This part of the message gives the requested information for all types of BOP-related surveys : either for reporting results of general questionnaires or for specific questionnaires such as the report on positions (foreign assets and liabilities).

PLEASE NOTE. In the explanation below where survey and type of question is used the same goes for reporting form and type of position.

0460 Segment Group 11: RFF-SG12

A group of segments to give for all type of surveys the relevant information.

0470 RFF, Reference

A segment giving the type of survey.

0480 Segment Group 12: RCS-FTX-SG13

A group of segments to give the relevant information for the specific survey.

0490 RCS, Requirements and conditions

A segment giving the type of question of that survey.

0500 FTX, Free text

A segment for information in clear and free form about the type of question on that reporting form.

0510 Segment Group 13: SEQ-SG14-SG15

A group of segments to provide specific details on the type of question for that specific survey.

0520 SEQ, Sequence details

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

0530 Segment Group 14: GIR-QTY-PRI

A group of segments to give the identification and the quantity of shares.

0540 GIR, Related identification numbers

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

0550 QTY, Quantity

A segment to specify the quantity of shares.

0560 PRI, Price details

A segment to give the face value of the security.

0570 Segment Group 15: MOA-NAD

A group of segments to give the amount/currency and the identity of the non-resident debtor/creditor.

0580 MOA, Monetary amount

A segment giving the amount of the position concerned by the question.

0590 NAD, Name and address

A segment to identify the non-resident debtor or creditor (or more general, in the case of surveys the counterparty).


4.1.3. Summary section

Information to be provided in the Summary section:

0600 Segment group 16: AUT-DTM A group of segments to specify the details of authentication.

0610 AUT, Authentication result

A segment to specify the details of any authentication (validation) procedure applied to the BOPDIR message.

0620 DTM, Date/time/period

A segment to identify the date and if necessary, the time of validation.

0630 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
CUX Currencies
DTM Date/time/period
FII Financial institution information
FTX Free text
GIR Related identification numbers
LIN Line item
LOC Place/location identification
MOA Monetary amount
NAD Name and address
PRI Price details
QTY Quantity
RCS Requirements and conditions
RFF Reference
SEQ Sequence details
UNH Message header
UNS Section control
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)
├─FII Financial institution information ×1 (M)
└─Segment Group 4 ×9999 (M)
──├─RCS Requirements and conditions ×1 (M)
──├─FTX Free text ×10 (C)
──├─Segment Group 5 ×1 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×1 (C)
──├─NAD Name and address ×2 (M)
──├─Segment Group 6 ×1 (M)
──├─MOA Monetary amount ×1 (M)
──└─CUX Currencies ×1 (C)
──└─LOC Place/location identification ×4 (C)
├─UNS Section control ×1 (M)
├─Segment Group 7 ×999 (C)
├─LIN Line item ×1 (M)
├─RCS Requirements and conditions ×1 (M)
├─FII Financial institution information ×1 (C)
├─NAD Name and address ×1 (C)
├─MOA Monetary amount ×2 (M)
└─Segment Group 8 ×9999 (C)
──├─RCS Requirements and conditions ×1 (M)
──├─FTX Free text ×10 (C)
──├─Segment Group 9 ×1 (C)
──├─GIR Related identification numbers ×1 (M)
──├─QTY Quantity ×1 (C)
──└─PRI Price details ×1 (C)
──├─Segment Group 10 ×1 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×1 (C)
──├─FII Financial institution information ×1 (C)
──├─NAD Name and address ×1 (C)
──├─MOA Monetary amount ×1 (M)
──└─LOC Place/location identification ×4 (C)
├─Segment Group 11 ×99 (C)
├─RFF Reference ×1 (M)
└─Segment Group 12 ×99 (M)
──├─RCS Requirements and conditions ×1 (M)
──├─FTX Free text ×1 (C)
──└─Segment Group 13 ×9999 (M)
────├─SEQ Sequence details ×1 (M)
────├─Segment Group 14 ×1 (C)
────├─GIR Related identification numbers ×1 (M)
────├─QTY Quantity ×1 (C)
────└─PRI Price details ×1 (C)
────└─Segment Group 15 ×999 (M)
──────├─MOA Monetary amount ×1 (M)
──────└─NAD Name and address ×1 (C)
├─Segment Group 16 ×1 (C)
├─AUT Authentication result ×1 (M)
└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D95B 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 EDIFACT to XML
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-2016 All Rights Reserved.