UN/EDIFACT — INVOIC, ORDERS, DESADV & More

EDIFACT Viewer — Read Any UN/EDIFACT File Online

Drop in a raw UN/EDIFACT file and see every segment labeled in plain English — UNA/UNB service string advice and interchange header, UNH message header, and every data segment through UNT/UNZ. Common across European and international commercial trade.

Drag & drop your EDIFACT file here

Up to 50MB — parsed entirely in your browser

Never uploaded, no account needed Exports to CSV, Excel, JSON & XML

or try it instantly — Try With a Sample File, no upload needed:

No file parsed yet — upload an EDIFACT file or load a sample above to see results here.

What Is an EDIFACT Viewer?

UN/EDIFACT (United Nations rules for Electronic Data Interchange For Administration, Commerce and Transport) is the international EDI standard used heavily across Europe, Asia, and global logistics — where ANSI X12 is more common in North America. Like X12, a raw EDIFACT file is a wall of delimited text with no visual structure. An EDIFACT viewer parses the file's own service-string-advice (UNA) or default delimiters, splits it into segments, and labels each one — UNB interchange header, UNH message header, and every business segment through UNT and UNZ.

Read the Full Guide: How the Viewer Works, Envelope Structure, and More

How This Viewer Reads an EDIFACT File

EDIFACT files may optionally begin with a UNA segment — the service string advice — which explicitly spells out the six special characters the file uses: component separator, element separator, decimal notation, release character, reserved character, and segment terminator. If no UNA segment is present, the EDIFACT default delimiters apply (+ for elements, ' for segment termination, : for components). This tool checks for a UNA segment first and falls back to the defaults automatically, so both styles of file are handled without any manual configuration.

After splitting, each segment (UNB, UNH, BGM, DTM, NAD, LIN, MOA, and more) is matched against an EDIFACT segment dictionary to attach a plain-English label, exactly as with X12 files — with unrecognized segments still shown and flagged rather than silently dropped.

The EDIFACT Envelope Structure, Explained

  • UNA — optional service string advice, defining the delimiter characters for the whole interchange.
  • UNB / UNZ — the interchange envelope, identifying sender, receiver, date/time, and the overall interchange.
  • UNH / UNT — the message envelope. Each UNH/UNT pair is one logical document — one invoice, one order, one dispatch advice.
  • Data segments — everything between UNH and UNT: BGM (beginning of message / document type), DTM (dates), NAD (name and address), LIN (line item), MOA (monetary amount), and dozens more, specific to the message type named in the UNH segment (e.g. "INVOIC", "ORDERS", "DESADV").

Which EDIFACT Message Types Can You View?

Because this viewer parses structurally rather than hardcoding one message type, it works on any well-formed EDIFACT interchange. Commonly viewed message types include:

EDIFACT vs. X12: Quick Orientation

If you're not sure which standard your file uses, this viewer's auto-detection will tell you immediately after upload (look at the "Standard Detected" field). For the fuller comparison of when each standard is used and how their structures differ, see X12 vs EDIFACT: Formats, Delimiters and Use Cases. If your file turns out to be X12 instead, use the dedicated X12 EDI Viewer.

Also Known As

People also search for this as an "EDIFACT viewer convertor," or land here after typing "edifact file won't open" — all describe the same task this tool handles.

Related Guides

New to EDI generally? Start with What Is an EDI File? and EDI Delimiters Explained for a deeper technical look at UNA and default delimiter handling.

Frequently Asked Questions

Does this work without a UNA segment?

Yes — if no UNA service string advice is present, the tool falls back to the EDIFACT default delimiters automatically.

Which EDIFACT message types are supported?

Any well-formed EDIFACT interchange, since the parser reads structurally rather than hardcoding one message type. INVOIC, ORDERS, and DESADV are the most commonly viewed.

Is my EDIFACT file uploaded to a server?

No. All parsing happens locally in your browser using JavaScript. The file is never transmitted anywhere.

Can I export what I view here?

Yes — the same CSV, Excel, and JSON export buttons shown after parsing are available on this page.

Does this work on Mac, iPhone, or Chromebook, and with different EDIFACT versions?

Yes on device — it runs in any modern browser on Windows, Mac, Chromebook, or iPad. It also reads structurally, so D.96A, D.01B, and other EDIFACT versions all display correctly. It currently views one file at a time, with no bulk/batch upload feature.

Can I convert EDIFACT to XML here?

Yes. Export options are CSV, Excel, JSON and XML. For EDIFACT specifically, the XML output preserves each segment's tag and description as attributes with its data elements as child nodes — useful when mapping UN/EDIFACT messages into an XML-based integration layer.