Integration & B2B
EDI viewer & validator (X12 + EDIFACT)
Parse an X12 or EDIFACT interchange into named segments and elements, and check the control references and segment counts actually agree — the usual reason a partner rejects a file.
Inspection files can contain the original data and identifiers. Review them before sharing; downloads are processed locally. This is a parser inspection, not certification.
JSON exports the existing parser representation with raw segments, validation findings and document context; it is not universal EDI synthesis. CSV is a lossy element/component table without raw segments or validation findings. Formula-like cells and leading-zero values receive a protective apostrophe. Import CSV columns as text; use JSON for exact string values and context.
Baseline vs revision
The interchange above is the baseline. Compare revisions of the same X12 004010 document class: 850, 810 or 856. One interchange and one matching functional group are required, with unique document IDs and ST controls. Lines use PO101/IT101; header parties use unique N101 qualifiers. ASN shipment/order/pack/item hierarchy uses HL IDs and parent paths; renumbering counts as deletion/insertion. REF/DTM qualifiers must be unique within each loop; repeated PID and same-qualifier references/dates stop comparison. Line-level parties and implementation overrides are outside this profile. Invoice summaries begin at TDS. This is segment/value comparison, not business reconciliation or full partner-guide validation.
Handles both ANSI X12 and UN/EDIFACT, detected automatically. Parsed entirely in your browser — EDI files carry real trading-partner data, prices and addresses, and this one never leaves the page. The dictionary covers both envelopes in full, plus the segments common to 850, 810, 856 and 997 on the X12 side and ORDERS, INVOIC, DESADV and CONTRL on the EDIFACT side. Unknown segments are still parsed and shown, just without element names.
More in this category
These exist because the underlying problem is real. If the numbers you just put in look uncomfortable, that is usually worth a conversation.
Stay ahead of the integration layer.
Integronauts Signal — practical enterprise integration, API and agentic AI thinking. The tools stay free either way.
Integronauts Signal is launching soon.
Practical enterprise integration, APIs, agentic AI and emerging architecture. Sign-up opens when the list does — nothing to enter yet.