| Version: | D |
|---|---|
| Release: | 03B |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 2003-12-22 |
| SOURCE: | TBG5 Finance |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, 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 |
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.
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.
The Commercial dispute 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.
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.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
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 element | 0065 | COMDIS |
| 0052 | D | |
| 0054 | 03B | |
| 0051 | UN |
A segment specifying the function and status of the message.
A segment identifying the reference of another message or transaction related to this message.
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.
A segment to specify currencies and relevant details for the rate of exchange.
A group of segments identifying the name and address of the parties involved in the transaction and their contacts.
A segment identifying the name and address of the parties associated with the commercial dispute message.
A segment identifying a person or a department for the party specified in the NAD segment and to whom communication should be directed.
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.
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.
A segment for identifying the reference document to which the commercial dispute refers.
A segment specifying the date and, when required, the time of the related documents in the DOC segment.
A segment giving the monetary amounts of the original document, the amounts that has been paid, the amount that is disputed or adjusted.
A group of segments to indicate the reasons of the dispute, with coded and free text information, related to the reference document.
A segment indicating the reason of the dispute.
A segment with free text information, related to the dispute reasons and the reference document.
A group of segments indicating the actions to be taken and the actions taken.
A segment indicating the actions to be taken, and the actions taken, and specifying the parties involved in these actions.
A segment with free text information, with additional information on the actions to be taken and the actions taken.
A group of segments which may be used when required to provide details of individual line items in the reference document.
A segment identifying a specific line item within the referenced document.
A segment giving the monetary amounts of the original line item, and the amount that is disputed or adjusted.
A group of segments to indicate the reasons of the dispute, with coded and free text information, related to the reference line item.
A segment indicating the reason of the dispute, related to the reference line item.
A segment with free text information, related to the dispute reasons and the reference line item.
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
| AJT | Adjustment details | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| CUX | Currencies | |
| DLI | Document line identification | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| FTX | Free text | |
| INP | Parties and instruction | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| RFF | Reference | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─RFF Reference | ×9 | (C) |
| ├─DTM Date/time/period | ×9 | (C) |
| ├─CUX Currencies | ×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 and 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) |