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 COLREQ
 
 
COLREQ 2 Request for a documentary collection message  
  Date:
2003-06-10

Source:
TBG5 Finance

0. INTRODUCTION
This specification provides the definition of the Request for a documentary collection message (COLREQ) 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 is sent by the Principal to the Remitting Bank and is used to request the Remitting Bank to initiate a Documentary Collection order, or to inform the Remitting Bank that the Principal has initiated a direct documentary collection order.

1.2 Field of application
The Request for a documentary collection 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
Unless otherwise specified, the documentary collection is issued subject to the Uniform Customs and Practices for Documentary Credits, International Chamber of Commerce, Paris, France, which are in effect on the date of issue.

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.

The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:

-   Where a choice of code or text is given only the code element should be used whenever possible.
-   Data that is not necessary to meet the functional requirements of the message should not be included.
-   Free text information within the message should be avoided as this inhibits automatic processing.
 
  Generated by GEFEG.FX  
  http://www.gefeg.com