EDIFACT CONTRL — Syntax Acknowledgment
CONTRL confirms UNA/UNB/UNG/UNH envelopes were syntactically parsed and accepted or lists segment and element errors.
✦ What It Does
UCI elements report UNB interchange status; UC segments drill into message-level issues.
Always distinct from APERAK: CONTRL is envelope and syntax; APERAK is application semantics.
Trading partners require CONTRL within SLA for every inbound file.
⚡ When It's Used
- EDI translator validates file after receipt from VAN or AS2.
- Resend loop triggered on UC rejection codes.
- Batch monitoring alerts missing CONTRL.
- Upgrade window testing new directory release.
- Partner certification checklist item.
Who Uses EDIFACT CONTRL
European retail & brands
Common in EDIFACT-first programs where syntax acknowledgment 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.
UCI
Interchange response and action codes.
UCM / UCS / UCD
Message, segment, and composite data error pointers.
UNZ / UNH linkage
Counters reconciling to received control totals.
BGM (subset)
Some implementations wrap response metadata in BGM.
Related Messages
Need Help with EDIFACT CONTRL?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert