Frames | No Frames

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

Commercial dispute 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:COMDIS
Version:D
Release:94B
Contr. Agency:UN
Status:1
Revision:1
Date:94-08-19
SOURCE:Western European EDIFACT Board - MD4

CONTENTS
Commercial dispute 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
    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:
D94A, 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 Commercial dispute message (COMDIS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

A notice of commercial dispute against one or more invoices is usually raised by the buyer to notify the seller that something was found wrong with the goods delivered or the services rendered (goods damaged, delivery incomplete, delivery late, etc.). The dispute must be resolved before the related invoice can be settled.

The message will be used to: - notify a dispute; - correspond about an existing dispute (structured information); - notify the settlement of a dispute.

The message will serve at the same time as the dispute notice and as the dispute answer.

Throughout this document, the term 'Buyer' refers to either the buyer or an Agent acting on behalf of the Buyer, and the term 'Seller' refers either to the seller or an Agent acting on behalf of the Seller.


1.2. Field of Application

This message may be applied for both national and international settlements. It is based on universal practice and is not dependent on the type of business or industry.


1.3. Principles

The usual flow of communication is from buyer to seller: the buyer sends a dispute notice to the seller, and the seller sends back a dispute answer to the buyer. Optionally, the seller may also send a credit note. An alternative flow of communication is from seller to buyer, e.g. if the seller disputes the payment of a related invoice.

If part of the invoice is disputed, then as a consequence the whole invoice will be disputed.

  • One dispute may relate to one or more invoices/credit notes;
  • One dispute may relate to one or more payments;
  • One dispute must relate to one seller;
  • One dispute must relate to one buyer.

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.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Commercial dispute message is COMDIS.

Note: Commercial dispute messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065COMDIS
0052D
005494B
0051UN

0020 BGM, Beginning of message

A segment specifying the function and status of the message.

0030 RFF, Reference

A segment identifying the reference of another message or transaction related to this message.

0040 DTM, Date/time/period

A segment specifying the date and, when required, the time at which the message has been created as well as other dates and times relevant to the transactions.

0050 Segment Group 1: NAD-CTA-COM

A group of segments identifying the name and address of the parties involved in the transaction and their contacts.

0060 NAD, Name and address

A segment identifying the name and address of the parties associated with the commercial dispute message.

0070 CTA, Contact information

A segment identifying a person or a department for the party specified in the NAD segment and to whom communication should be directed.

0080 COM, Communication contact

A segment providing a communication number for the party identified in the NAD segment and optionally for the contact identified in the associated CTA segment.

0090 Segment Group 2: DOC-DTM-MOA-SG3-SG4-SG5

A segment group providing details of all documents, e.g. invoices, payment orders, etc. to which the commercial dispute refers. It includes information on the monetary amounts for each document and on any adjustments (with an indication of the reason for adjustments) and on actions (to be) taken by the parties who are involved.

0100 DOC, Document/message details

A segment for identifying the reference document to which the commercial dispute refers.

0110 DTM, Date/time/period

A segment specifying the date and, when required, the time of the related documents in the DOC segment.

0120 MOA, Monetary amount

A segment giving the monetary amounts of the original document, the amounts that has been paid, the amount that is disputed or adjusted.

0130 Segment Group 3: AJT-FTX

A group of segments to indicate the reasons of the dispute, with coded and free text information, related to the reference document.

0140 AJT, Adjustment details

A segment indicating the reason of the dispute.

0150 FTX, Free text

A segment with free text information, related to the dispute reasons and the reference document.

0160 Segment Group 4: INP-FTX

A group of segments indicating the actions to be taken and the actions taken.

0170 INP, Parties to instruction

A segment indicating the actions to be taken, and the actions taken, and specifying the parties involved in these actions.

0180 FTX, Free text

A segment with free text information, with additional information on the actions to be taken and the actions taken.

0190 Segment Group 5: DLI-MOA-SG6

A group of segments which may be used when required to provide details of individual line items in the reference document.

0200 DLI, Document line identification

A segment identifying a specific line item within the referenced document.

0210 MOA, Monetary amount

A segment giving the monetary amounts of the original line item, and the amount that is disputed or adjusted.

0220 Segment Group 6: AJT-FTX

A group of segments to indicate the reasons of the dispute, with coded and free text information, related to the reference line item.

0230 AJT, Adjustment details

A segment indicating the reason of the dispute, related to the reference line item.

0240 FTX, Free text

A segment with free text information, related to the dispute reasons and the reference line item.

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

AJT Adjustment details
BGM Beginning of message
COM Communication contact
CTA Contact information
DLI Document line identification
DOC Document/message details
DTM Date/time/period
FTX Free text
INP Parties to instruction
MOA Monetary amount
NAD Name and address
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)
├─RFF Reference ×9 (C)
├─DTM Date/time/period ×9 (C)
├─Segment Group 1 ×99 (C)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 2 ×9999 (C)
├─DOC Document/message details ×1 (M)
├─DTM Date/time/period ×9 (C)
├─MOA Monetary amount ×2 (C)
├─Segment Group 3 ×9 (C)
├─AJT Adjustment details ×1 (M)
└─FTX Free text ×9 (C)
├─Segment Group 4 ×9 (C)
├─INP Parties to instruction ×1 (M)
└─FTX Free text ×9 (C)
└─Segment Group 5 ×9999 (C)
──├─DLI Document line identification ×1 (M)
──├─MOA Monetary amount ×2 (C)
──└─Segment Group 6 ×9 (C)
────├─AJT Adjustment details ×1 (M)
────└─FTX Free text ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D94B 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.