UN/EDIFACT: Deep Dive into International EDI Standards
Cogential IT works inside the structure that governs every international EDI exchange � the UNB interchange header, UNG functional groups, and UNH message headers � mapping your data to EDIFACT segments and elements so every ORDERS, DESADV, and INVOIC validates cleanly against the directory version your trading partner requires.
Key Capabilities
Interchange Architecture
Build and validate the UNB, UNG, and UNH interchange hierarchy so every message nests correctly from control reference to trailer.
ORDERS / DESADV / INVOIC Mapping
Map purchase orders, dispatch advices, and invoices to the correct EDIFACT message structure for each trading partner.
Directory Version Support
Support legacy and current EDIFACT directories like D.96A and D.01B side by side as partners migrate at their own pace.
Segment-Level Validation
Catch syntax and qualifier errors at the segment and element level before a document ever reaches a trading partner.
Every EDIFACT interchange nests the same way, from the outermost interchange header down to the individual segment, then closes each layer in reverse before the file is complete.
Opens and closes the outermost interchange, identifying sender, receiver, and control reference.
Groups related messages together, such as all purchase orders in a single batch.
Wraps one business document, like an ORDERS purchase order, in its own labeled header and trailer.
Breaks the message into segments like BGM, DTM, and NAD, each built from delimited elements.
Confirms every segment and qualifier matches the directory release your partner requires.
What Is the UN/EDIFACT EDI Standard?
UN/EDIFACT is the primary EDI standard used across international trade, developed and maintained under the United Nations. It defines a strict interchange hierarchy, a UNB header wrapping one or more UNG functional groups, each wrapping one or more UNH messages, so that structured business documents like purchase orders and invoices can move between completely different systems in a predictable, machine-readable format. Within each message, data is broken into segments and elements governed by a specific directory release, such as D.96A or D.01B, that both trading partners must agree on.
Built on the structure every partner already expects
-
Match each trading partner's exact interchange, delimiter, and directory requirements out of the box.
-
Run new messages through segment-level validation before a single document goes live.
-
Support mixed-directory trading relationships without maintaining separate systems for each release.