Convert an X12 810 invoice to Excel
Drop the 810 as it came off the VAN or the SFTP drop. The invoice is laid out as a table, with the ISA and GS envelope kept in view so you know who sent what.
| # | Description | Qty | Unit | Unit price | VAT % | Net amount |
|---|
| Category | Rate | Taxable base | VAT amount |
|---|
| # | Qualifier | Reference | Amount | Paid |
|---|
| Segment | Element | Value |
|---|
Why a European company ends up reading an 810
An exporter selling into the United States receives American documents back from American buyers, and X12 is what those look like. The 810 is the invoice of that family. It matters here because the same finance clerk who has to issue an XRechnung at home is the one opening an 810 from a US customer in the same week, and every other tool on the market handles one world or the other but not both.
What you get out
Every field below is read from the file itself. Nothing is inferred, and a field the invoice does not carry is left empty rather than filled in with a plausible guess.
- ISA and GS envelope: sender, receiver, control numbers, date
- BIG invoice number and date, plus purchase order references
- N1 loop parties with their identification codes
- IT1 line items with quantity, unit price and product identifiers
- TDS, SAC and TXI amounts, and every other segment in raw form
Questions
My element labels look wrong.
Only the standard-defined ones are labelled. X12 element meaning is frequently agreed between trading partners, so anything partner-specific is shown as the raw segment rather than given a name that might be somebody else's.
Does the file need to be split first?
No. Drop the whole interchange. Multiple ST to SE transactions inside one file are read individually.
Which separators are supported?
They are read from the ISA segment itself, so unusual element, component and segment terminators are handled without a setting.