EDIFACT COMDIS — Commercial Dispute
COMDIS states disputed amounts, reason codes, and references to INVOIC, DESADV, or contract so parties can resolve in workflow.
✦ What It Does
Less ubiquitous than CREADV but used where structured dispute lifecycle is mandated.
May integrate with retailer supplier portals for case IDs in RFF.
Legal and collections teams may export COMDIS history for audit.
⚡ When It's Used
- Invoice line rejected in three-way match.
- ASN quantity dispute at receiving.
- Pricing disagreement vs. contract.
- Deduction challenged with counter-evidence.
- Cross-border VAT dispute documentation.
Who Uses EDIFACT COMDIS
European retail & brands
Common in EDIFACT-first programs where commercial dispute flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Dispute document function.
MOA
Disputed monetary amounts.
RFF
Invoice, PO, and case references.
FTX
Narrative dispute explanation.
Related Messages
Need Help with EDIFACT COMDIS?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert