Copper Oven Bakery: ANSI X12 810 invoice
ANSI X12 810 invoice for Copper Oven Bakery. Version 004010 transaction set 810 for invoice INV-BAK-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 13.79, and a TDS segment of 28965 in implied-decimal cents, which is 289.65 CAD. SE declares 13 segments and 13 are present.
edi
application/edi-x12
- Kit
- restaurant-bakery
- Schema Version
- 1
- Synthetic
- true
- As Of
- 2026-09-08
- Currency
- CAD
- Tax Name
- GST
Binary edi: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Kit
- restaurant-bakery
- Schema Version
- 1
- Synthetic
- true
- As Of
- 2026-09-08
- Currency
- CAD
- Tax Name
- GST
- Tax Rate
- 0.05
- Standard
- ANSI X12 004010
- Transaction Set
- 810
- Control Number
- 810002
- Segments
- 13
- Declared Segments
- 13
- Segment Terminator
- ~
- Line Endings
- CRLF
- Encoding
- ASCII
Testing contract
Expected to pass- Scenario
- Read ansi x12 810 invoice into a procure-to-pay import, three-way match and reconciliation workflow for Copper Oven Bakery.
- Expected result
- Version 004010 transaction set 810 for invoice INV-BAK-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 13.79, and a TDS segment of 28965 in implied-decimal cents, which is 289.65 CAD. SE declares 13 segments and 13 are present.
What is a .edi file?
EDI (Electronic Data Interchange), in the ANSI X12 family, is a structured plain-text format for exchanging business documents like purchase orders (850) and invoices (810) between trading partners. It is built from segments (ISA, GS, ST, …) separated by delimiters, with tightly specified element positions. It underpins much of B2B supply-chain and retail commerce.
How to use this file
Use an example X12 EDI file to test EDI parsers and translators, segment/element extraction, and mapping from EDI to JSON or XML. The parties and values here are synthetic.
How to use this file for testing
“Copper Oven Bakery: ANSI X12 810 invoice” is a deterministic Novus Examples fixture for Data import, Conversion testing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: ASCII · CRLF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.
Code examples
from pydifact.segmentcollection import Interchange # EDIFACT
inter = Interchange.from_file("edi-810-invoice.edi")
for seg in inter.segments:
print(seg.tag, seg.elements)Related files
- ediAlder Table Bistro: ANSI X12 810 invoiceANSI X12 810 invoice for Alder Table Bistro. Version 004010 transaction set 810 for invoice INV-BST-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 15.69, and a TDS segment of 32953 in implied-decimal cents, which is 329.53 CAD. SE declares 13 segments and 13 are present.
- ediAlder Table Bistro: ANSI X12 810 invoice with a wrong SE segment countANSI X12 810 invoice with a wrong SE segment count for Alder Table Bistro. Identical to edi-810-invoice.edi except for one element: SE declares 11 segments where 13 are present between ST and SE inclusive. The ISA, GS, GE and IEA control numbers, every data segment and the TDS total of 32953 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.
- ediAlder Table Bistro: ANSI X12 850 purchase orderANSI X12 850 purchase order for Alder Table Bistro. Version 004010 transaction set 850 for PO-BST-1002, control number 850002. 3 PO1 segments carry quantity, X12 unit code, unit price, the supplier item code (VP) and the buyer item code (BP); CTT declares 3 line items and SE declares 14 segments, which is the number actually present between ST and SE inclusive.
- ediAlder Table Bistro: ANSI X12 856 despatch adviceANSI X12 856 despatch advice for Alder Table Bistro. Version 004010 transaction set 856 for supplier delivery note DN-BST-3002 against PO-BST-1002, control number 856002. The shipment, order and item hierarchy uses HL segments, and the SN1 quantities are the quantities actually delivered, so line 2 reports 16 where the 850 ordered 20.
- xmlAlder Table Bistro: Factur-X CII invoice XMLFactur-X CII invoice XML for Alder Table Bistro. UN/CEFACT Cross Industry Invoice for INV-BST-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 10.38 and a DuePayableAmount of 217.98 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.
- pdfAlder Table Bistro: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Alder Table Bistro. Invoice INV-BST-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 207.60, GST 10.38, 217.98 CAD due. This is the only file in the set that carries its data twice in one container.
Generated by generation/restaurant_procurement.py. Free for any use, no attribution required, license.