TPCx reaches end of life December 2026 | Don't wait until partners go dark | Plan Your Migration →
Comparatio logo
Free tool

EDI Viewer

Open an X12 or EDIFACT file and read it in plain English, with the envelope checked for the errors trading partners reject.

  • X12 and EDIFACT
  • Any delimiters
  • Nothing is uploaded

or drop it here. X12 and EDIFACT, any delimiters.

Try a sample

Fictional companies, real structure.

Browse the sample EDI document library →

Runs in your browser. Your file is never uploaded.

What it does

More than a pretty-printer

Reads real files

One long line, one segment per line or wrapped at 80 columns. The delimiters come from the file itself (the ISA for X12, UNA for EDIFACT) instead of being assumed.

Plain-English names

Segments and elements are named, common codes are spelled out (ST is Ship to, 002 is Delivery requested) and dates are readable. Each transaction links to its document guide.

Checks what partners reject

Control numbers and segment counts across ST/SE, GS/GE and ISA/IEA (UNH/UNT and UNB/UNZ for EDIFACT), the fixed-width ISA, and files that are cut short.

Take it with you

Download the document as JSON, as CSV for a spreadsheet, as XML, or as a formatted file with one segment per line.

FAQ

EDI Viewer questions

Is my EDI file uploaded anywhere?

No. The viewer runs entirely in your browser. Your file is read and parsed on your own computer and never sent to Comparatio or anyone else.

Which EDI formats does the viewer support?

ANSI X12 (any version, including 4010 and 5010) and UN/EDIFACT, including EANCOM. It reads the delimiters each file declares, handles the EDIFACT release character, and opens files with several interchanges, groups or transactions.

Why does my trading partner reject a file that looks fine?

Often it is the envelope: a segment count in SE or UNT that no longer matches after an edit, control numbers that differ between header and trailer, or an ISA header that is not exactly 106 characters. The viewer checks each of these and points to the segment.

Does the viewer validate against my partner’s implementation guide?

No. It checks the structure every X12 or EDIFACT file must follow. Partner-specific rules, such as required segments or allowed codes, come from the partner’s guide; Comparatio builds and tests maps against those guides for its customers.

Browse the EDI document guides

Rather not read raw EDI at all?

Comparatio connects your ERP to your trading partners, and our engineers build and run every map.