Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D96A Messages page. Commercial dispute message
0. INTRODUCTIONThis 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. SCOPE1.1. Functional DefinitionA 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 ApplicationThis 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. PrinciplesThe 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.
2. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONSSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements. 0010 | UNH, Message headerA 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:
0020 BGM, Beginning of messageA segment specifying the function and status of the message. 0030 RFF, ReferenceA segment identifying the reference of another message or transaction related to this message. 0040 DTM, Date/time/periodA 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-COMA group of segments identifying the name and address of the parties involved in the transaction and their contacts. 0060 NAD, Name and addressA segment identifying the name and address of the parties associated with the commercial dispute message. 0070 CTA, Contact informationA 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 contactA 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-SG5A 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 detailsA segment for identifying the reference document to which the commercial dispute refers. 0110 DTM, Date/time/periodA segment specifying the date and, when required, the time of the related documents in the DOC segment. 0120 MOA, Monetary amountA 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-FTXA group of segments to indicate the reasons of the dispute, with coded and free text information, related to the reference document. 0140 AJT, Adjustment detailsA segment indicating the reason of the dispute. 0150 FTX, Free textA segment with free text information, related to the dispute reasons and the reference document. 0160 Segment Group 4: INP-FTXA group of segments indicating the actions to be taken and the actions taken. 0170 INP, Parties to instructionA segment indicating the actions to be taken, and the actions taken, and specifying the parties involved in these actions. 0180 FTX, Free textA segment with free text information, with additional information on the actions to be taken and the actions taken. 0190 Segment Group 5: DLI-MOA-SG6A group of segments which may be used when required to provide details of individual line items in the reference document. 0200 DLI, Document line identificationA segment identifying a specific line item within the referenced document. 0210 MOA, Monetary amountA segment giving the monetary amounts of the original line item, and the amount that is disputed or adjusted. 0220 Segment Group 6: AJT-FTXA 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 detailsA segment indicating the reason of the dispute, related to the reference line item. 0240 FTX, Free textA segment with free text information, related to the dispute reasons and the reference line item. 0250 UNT, Message trailerA 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 structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D96A Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |