Free tool · EDI viewer
EDI viewer: read X12 and EDIFACT files in your browser.
Paste or open an EDI file to read X12 850 purchase orders, 855 acknowledgments, 856 ship notices and 810 invoices, or EDIFACT ORDERS, ORDRSP, DESADV and INVOIC, as a plain order table. Check the envelope and export the lines to Excel, CSV or JSON. Free, and the file never leaves your device.
Or drop a file here: .edi, .x12, .txt, .edifact … up to 20 MB Ctrl + Enter shows the input.
Why this viewer
Made for the orders your customers send.
01
Your data stays on your device
The viewer reads the file in your browser. Nothing is uploaded, so you can open live orders and invoices from your trading partners.
02
X12 and EDIFACT, detected for you
ANSI X12 in any version, such as 004010 or 005010, and UN/EDIFACT, such as D.96A or D.01B. The separators are read from the ISA or UNA segment.
03
Order table, checks and export
See every line with item numbers, quantities and prices, check segment counts and control numbers, and export the lines to Excel, CSV or JSON.
Order messages
X12 and EDIFACT, message by message.
850 · ORDERS
Purchase order
The buyer orders items with quantities, prices and delivery dates.
855 · ORDRSP
Order acknowledgment
The supplier accepts, changes or rejects each line of the order.
860 · ORDCHG
Order change
The buyer changes quantities, dates or lines of an order already sent.
856 · DESADV
Ship notice (ASN)
What was shipped, in which package (SSCC) and for which order.
810 · INVOIC
Invoice
The invoiced lines, allowances and charges, tax and the total.
997 · CONTRL
Functional acknowledgment
The file arrived and could be read. It does not mean the order is accepted.
EDI 850 and EDIFACT ORDERS
What is in an EDI 850 purchase order?
An 850 is one purchase order in ANSI X12. It sits inside an envelope (ISA and GS), starts with ST, ends with SE and has one PO1 segment per order line. The EDIFACT ORDERS message carries the same content under other segment names. Choose either sample in the viewer above to see it as an order table.
X12 850
Purchase order
ST*850*0001~BEG*00*SA*4500012345**20261103~N1*ST*Harbor Industrial Supply DC 2*92*DC02~PO1*1*120*EA*0.42**VP*BLT-M8-40*BP*100234~PID*F****Hex bolt M8 x 40 mm, zinc plated~CTT*1~SE*7*0001~
EDIFACT ORDERS
Purchase order
UNH+1+ORDERS:D:96A:UN:EAN008'BGM+220+PO-88231+9'DTM+137:20261103:102'NAD+BY+4012345000009::9'LIN+1++4012345111118:EN'QTY+21:25:PCE'PRI+AAA:18.40'UNS+S'CNT+2:1'UNT+10+1'
X12 850
EDIFACT ORDERS
What it holds
ISA, GS … GE, IEA
UNA, UNB … UNZ
The envelope: sender and receiver IDs, date, control numbers and the separators.
ST … SE
UNH … UNT
Start and end of one order. The trailer counts the segments in between.
BEG
BGM, DTM
Order number, order type and order date.
CUR
CUX
Currency.
REF, PER, DTM
RFF, CTA, DTM
References, the buyer’s contact and the requested delivery date.
N1, N3, N4
NAD
Parties such as buyer, ship-to and seller, with their IDs and address.
PO1
LIN, QTY, PRI
One order line: item number, quantity, unit and price.
PO1 (VP, BP, UP)
PIA
More item numbers: the supplier’s, the buyer’s, a UPC or a GTIN.
PID
IMD
Item description.
CTT
UNS, CNT
Summary: the number of lines.
Orders by email and PDF
Not every customer can send EDI.
EDI works for the large accounts that have set it up. Most other customers still send purchase orders by email, as a PDF or as a spreadsheet, and someone types them into the ERP. Mercura reads those orders and creates the sales order in your ERP, so they are processed like the orders that come in over EDI.
FAQ
Questions about EDI files.
An EDI file is a business document, such as a purchase order or an invoice, in a standard text format that systems exchange directly. The two common standards are ANSI X12, used mostly in North America, and UN/EDIFACT, used mostly in Europe and in international trade.
Both describe the same documents with segments and elements, but with different names and separators. X12 numbers its documents (850 purchase order, 810 invoice) and usually separates elements with * and segments with ~. EDIFACT names them (ORDERS, INVOIC) and uses + and ' by default. The viewer detects which one you have.
The 850 is the X12 purchase order. It carries the PO number and date (BEG), the parties such as buyer and ship-to (N1 loop), one PO1 segment per order line with quantity, unit, price and item numbers, and a CTT segment with the number of lines. Its EDIFACT counterpart is ORDERS.
They follow the 850 in the order cycle: the 855 acknowledges the purchase order line by line, the 856 ship notice (ASN) lists what was shipped in which package, and the 810 is the invoice. In EDIFACT they are ORDRSP, DESADV and INVOIC.
Paste or open the file above and choose CSV, Excel or JSON. You get one row per line item with the line number, item numbers, description, quantity, unit, unit price, amount and date. Acknowledgments (997, CONTRL) export their results instead. The conversion runs in your browser.
No. The viewer reads the file in your browser, and nothing from it is sent to Mercura or anyone else. Our analytics only receive counts, such as the message type and the number of lines, never the content.
It checks the envelope: that every ISA, GS and ST (or UNB, UNG and UNH) has its closing segment, that the segment and message counts match, and that the control numbers agree. For orders and invoices it also compares line counts and totals. It does not check a trading partner's implementation guide.
X12 850, 855, 856, 810, 860 and 997, and EDIFACT ORDERS, ORDRSP, DESADV, INVOIC, ORDCHG and CONTRL. Any other X12 or EDIFACT message opens in the segment view.
Mercura reads the purchase orders that arrive by email or as PDF and creates the sales order in your ERP, so they are processed like the orders that come in over EDI.