Datasets for import testing

Alder Table Bistro: Operating chart PNG

Operating chart PNG for Alder Table Bistro. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Juniper Corner Cafe: Operating chart PNG

Operating chart PNG for Juniper Corner Cafe. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Copper Oven Bakery: Operating chart PNG

Operating chart PNG for Copper Oven Bakery. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Ember Lane Pizza: Operating chart PNG

Operating chart PNG for Ember Lane Pizza. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Cedar Street Tacos: Operating chart PNG

Operating chart PNG for Cedar Street Tacos. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Willow Event Kitchen: Operating chart PNG

Operating chart PNG for Willow Event Kitchen. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Harbour Kitchen Group: Operating chart PNG

Operating chart PNG for Harbour Kitchen Group. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Fieldnote Supply Shop: Operating chart PNG

Operating chart PNG for Fieldnote Supply Shop. A 1440 by 900 RGB chart with 12 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Tern Client Services: Operating chart PNG

Operating chart PNG for Tern Client Services. A 1440 by 900 RGB chart with 4 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Alder Books Reconciliation: Operating chart PNG

Operating chart PNG for Alder Books Reconciliation. A 1440 by 900 RGB chart with 24 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Pine Assembly Workshop: Operating chart PNG

Operating chart PNG for Pine Assembly Workshop. A 1440 by 900 RGB chart with 6 labeled source-derived observations in units.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Cobalt Operations Team: Operating chart PNG

Operating chart PNG for Cobalt Operations Team. A 1440 by 900 RGB chart with 8 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Juniper Fitness and Clinic Administration: Operating chart PNG

Operating chart PNG for Juniper Fitness and Clinic Administration. A 1440 by 900 RGB chart with 3 labeled source-derived observations in slots.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Harbour House Stay: Operating chart PNG

Operating chart PNG for Harbour House Stay. A 1440 by 900 RGB chart with 6 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Fieldnote Learning Centre: Operating chart PNG

Operating chart PNG for Fieldnote Learning Centre. A 1440 by 900 RGB chart with 3 labeled source-derived observations in completions.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Willow Community Fund: Operating chart PNG

Operating chart PNG for Willow Community Fund. A 1440 by 900 RGB chart with 3 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Pine Property Services: Operating chart PNG

Operating chart PNG for Pine Property Services. A 1440 by 900 RGB chart with 12 labeled source-derived observations in USD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Juniper Workspace Cloud: Operating chart PNG

Operating chart PNG for Juniper Workspace Cloud. A 1440 by 900 RGB chart with 6 labeled source-derived observations in USD/month.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Bank Statement (PDF)

A one-page monthly bank statement: account summary and a dated transaction table with running balances. Synthetic data for testing PDF statement parsers, table extraction, and OCR.

File: PDF · Financial · 1 page
Use case: PDF editor testingData import

HL7 v2 ADT^A01 Admission Message

An HL7 v2.5 ADT^A01 patient-admission message: pipe/caret-delimited segments (MSH, EVN, PID, PV1, allergies, diagnosis). A fixture for testing healthcare integration engines and HL7 parsers. The patient is fictional.

File: HL7 · Healthcare
Use case: Data importConversion testing

X12 EDI 850 Purchase Order

An ANSI X12 850 purchase order: ISA/GS/ST envelope with BEG, N1, and PO1 line items. A fixture for testing EDI parsers and translators. Paired with the 810 invoice for the same order.

File: EDI · Edi
Use case: Data importConversion testing· Conversion set

X12 EDI 810 Invoice

An ANSI X12 810 invoice that references the 850 purchase order: ISA/GS/ST envelope with BIG, IT1 line items, and a total. The invoice twin of the purchase order, for testing EDI document flows.

File: EDI · Edi
Use case: Data importConversion testing· Conversion set

Alder Table Bistro: Workflow and import guide

Workflow and import guide for Alder Table Bistro. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Alder Table Bistro: Operating report PDF

Operating report PDF for Alder Table Bistro. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=11,652.45 CAD; Net menu sales=15,780.80 CAD; Menu items sold=1,092.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Juniper Corner Cafe: Workflow and import guide

Workflow and import guide for Juniper Corner Cafe. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Juniper Corner Cafe: Operating report PDF

Operating report PDF for Juniper Corner Cafe. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=8,715.93 CAD; Net menu sales=10,234.74 CAD; Menu items sold=1,204.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Copper Oven Bakery: Workflow and import guide

Workflow and import guide for Copper Oven Bakery. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Copper Oven Bakery: Operating report PDF

Operating report PDF for Copper Oven Bakery. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Ember Lane Pizza: Workflow and import guide

Workflow and import guide for Ember Lane Pizza. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Ember Lane Pizza: Operating report PDF

Operating report PDF for Ember Lane Pizza. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=15,061.21 CAD; Net menu sales=25,954.50 CAD; Menu items sold=1,428.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Cedar Street Tacos: Workflow and import guide

Workflow and import guide for Cedar Street Tacos. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Cedar Street Tacos: Operating report PDF

Operating report PDF for Cedar Street Tacos. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Willow Event Kitchen: Workflow and import guide

Workflow and import guide for Willow Event Kitchen. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Willow Event Kitchen: Operating report PDF

Operating report PDF for Willow Event Kitchen. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=7,900.99 CAD; Net menu sales=28,781.90 CAD; Menu items sold=1,652.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Harbour Kitchen Group: Workflow and import guide

Workflow and import guide for Harbour Kitchen Group. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Harbour Kitchen Group: Operating report PDF

Operating report PDF for Harbour Kitchen Group. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=7,897.76 CAD; Net menu sales=26,214.00 CAD; Menu items sold=1,764.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Fieldnote Supply Shop: Workflow and import guide

Workflow and import guide for Fieldnote Supply Shop. Documents 9 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Fieldnote Supply Shop: Operating report PDF

Operating report PDF for Fieldnote Supply Shop. Three readable pages summarize the same model, chart, source tables and usage instructions. Gross item sales=942.00 USD; Refunded amount=80.00 USD; Orders=12.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Tern Client Services: Workflow and import guide

Workflow and import guide for Tern Client Services. Documents 9 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Tern Client Services: Operating report PDF

Operating report PDF for Tern Client Services. Three readable pages summarize the same model, chart, source tables and usage instructions. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.

File: PDF · Business Kits · 3 pages
Use case: Data import

Alder Books Reconciliation: Workflow and import guide

Workflow and import guide for Alder Books Reconciliation. Documents 6 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Alder Books Reconciliation: Operating report PDF

Operating report PDF for Alder Books Reconciliation. Three readable pages summarize the same model, chart, source tables and usage instructions. Net cash change=5,236.00 USD; Journal debits=9,364.00 USD; Journal credits=9,364.00 USD.

File: PDF · Business Kits · 3 pages
Use case: Data import

Pine Assembly Workshop: Workflow and import guide

Workflow and import guide for Pine Assembly Workshop. Documents 11 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Pine Assembly Workshop: Operating report PDF

Operating report PDF for Pine Assembly Workshop. Three readable pages summarize the same model, chart, source tables and usage instructions. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Cobalt Operations Team: Workflow and import guide

Workflow and import guide for Cobalt Operations Team. Documents 5 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Cobalt Operations Team: Operating report PDF

Operating report PDF for Cobalt Operations Team. Three readable pages summarize the same model, chart, source tables and usage instructions. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Juniper Fitness and Clinic Administration: Workflow and import guide

Workflow and import guide for Juniper Fitness and Clinic Administration. Documents 5 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Juniper Fitness and Clinic Administration: Operating report PDF

Operating report PDF for Juniper Fitness and Clinic Administration. Three readable pages summarize the same model, chart, source tables and usage instructions. Available slots=24.00 slots; Occupied slots=16.00 slots; Booking records=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Harbour House Stay: Workflow and import guide

Workflow and import guide for Harbour House Stay. Documents 7 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Harbour House Stay: Operating report PDF

Operating report PDF for Harbour House Stay. Three readable pages summarize the same model, chart, source tables and usage instructions. Occupied room nights=48.00 nights; Room revenue=6,840.00 USD; Ancillary revenue=672.00 USD.

File: PDF · Business Kits · 3 pages
Use case: Data import

Fieldnote Learning Centre: Workflow and import guide

Workflow and import guide for Fieldnote Learning Centre. Documents 5 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Fieldnote Learning Centre: Operating report PDF

Operating report PDF for Fieldnote Learning Centre. Three readable pages summarize the same model, chart, source tables and usage instructions. Enrollments=18.00 records; Passed completions=9.00 learners; Available course seats=30.00 seats.

File: PDF · Business Kits · 3 pages
Use case: Data import

Willow Community Fund: Workflow and import guide

Workflow and import guide for Willow Community Fund. Documents 8 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Willow Community Fund: Operating report PDF

Operating report PDF for Willow Community Fund. Three readable pages summarize the same model, chart, source tables and usage instructions. Pledged support=2,850.00 USD; Received support=1,800.00 USD; Outstanding pledges=1,050.00 USD.

File: PDF · Business Kits · 3 pages
Use case: Data import

Pine Property Services: Workflow and import guide

Workflow and import guide for Pine Property Services. Documents 6 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Pine Property Services: Operating report PDF

Operating report PDF for Pine Property Services. Three readable pages summarize the same model, chart, source tables and usage instructions. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Juniper Workspace Cloud: Workflow and import guide

Workflow and import guide for Juniper Workspace Cloud. Documents 6 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Juniper Workspace Cloud: Operating report PDF

Operating report PDF for Juniper Workspace Cloud. Three readable pages summarize the same model, chart, source tables and usage instructions. Active monthly recurring revenue=235.00 USD; Paid invoices=649.00 USD; Outstanding invoices=19.00 USD.

File: PDF · Business Kits · 3 pages
Use case: Data import

Alder Table Bistro: Purchase order PDF

Purchase order PDF for Alder Table Bistro. Purchase order PO-BST-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 313.84, GST 15.69 and 329.53 CAD payable. Line 2 orders 20 kg of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Alder Table Bistro: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Alder Table Bistro. Goods-received note GRN-BST-2002 against PO-BST-1002, recording supplier delivery note DN-BST-3002 on 2026-08-14. Line 2 records 16 kg delivered against 20 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Alder Table Bistro: Supplier invoice PDF

Supplier invoice PDF for Alder Table Bistro. Invoice INV-BST-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 313.84, GST 15.69 and 329.53 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 kg.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Alder Table Bistro: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Alder Table Bistro. A second document issued under invoice number INV-BST-5002, dated 2026-08-17 with 2 lines totalling 294.46 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 329.53 CAD. Both are listed on statement STM-BST-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Alder Table Bistro: Credit note PDF

Credit note PDF for Alder Table Bistro. Credit note CN-BST-7002 dated 2026-08-29 against invoice INV-BST-5004 dated 2026-08-28: 5 l at 7.79, net 38.95 and 40.90 CAD including GST. Goods-received note GRN-BST-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Alder Table Bistro: Statement of account PDF

Statement of account PDF for Alder Table Bistro. Statement STM-BST-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 1559.75 CAD. The printed ageing analysis totals 1566.76 CAD, which is 7.01 CAD more, because credit note CN-BST-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Alder Table Bistro: Remittance advice PDF

Remittance advice PDF for Alder Table Bistro. Remittance advice REM-BST-8001 dated 2026-09-05, covering all 13 documents on both statements. 1120.68 CAD is paid and 1765.18 CAD is withheld, against statement balances of 2885.86 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Alder Table Bistro: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Alder Table Bistro. OASIS UBL 2.1 Invoice for INV-BST-5001 with 3 InvoiceLine elements, a TaxTotal of 10.38 on a taxable amount of 207.60, and a PayableAmount of 217.98 CAD. OrderReference names PO-BST-1001 and DespatchDocumentReference names GRN-BST-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Alder Table Bistro: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Alder Table Bistro. OASIS UBL 2.1 CreditNote for CN-BST-7002 with type code 381, a BillingReference to invoice INV-BST-5004 dated 2026-08-28, one CreditNoteLine of 5 l and a PayableAmount of 40.90 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-BST-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Alder Table Bistro: Factur-X CII invoice XML

Factur-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.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Alder Table Bistro: Factur-X hybrid invoice PDF

Factur-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.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Alder Table Bistro: ANSI X12 850 purchase order

ANSI 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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Alder Table Bistro: ANSI X12 856 despatch advice

ANSI 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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Alder Table Bistro: ANSI X12 810 invoice

ANSI 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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Alder Table Bistro: ANSI X12 810 invoice with a wrong SE segment count

ANSI 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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Alder Table Bistro: Procure-to-pay chain README

Procure-to-pay chain README for Alder Table Bistro. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Juniper Corner Cafe: Purchase order PDF

Purchase order PDF for Juniper Corner Cafe. Purchase order PO-CAF-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 332.22, GST 16.61 and 348.83 CAD payable. Line 2 orders 21 l of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Juniper Corner Cafe: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Juniper Corner Cafe. Goods-received note GRN-CAF-2002 against PO-CAF-1002, recording supplier delivery note DN-CAF-3002 on 2026-08-14. Line 2 records 17 l delivered against 21 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Juniper Corner Cafe: Supplier invoice PDF

Supplier invoice PDF for Juniper Corner Cafe. Invoice INV-CAF-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 332.22, GST 16.61 and 348.83 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 l.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Juniper Corner Cafe: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Juniper Corner Cafe. A second document issued under invoice number INV-CAF-5002, dated 2026-08-17 with 2 lines totalling 291.50 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 348.83 CAD. Both are listed on statement STM-CAF-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Juniper Corner Cafe: Credit note PDF

Credit note PDF for Juniper Corner Cafe. Credit note CN-CAF-7002 dated 2026-08-29 against invoice INV-CAF-5004 dated 2026-08-28: 5 each at 1.52, net 7.60 and 7.98 CAD including GST. Goods-received note GRN-CAF-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Juniper Corner Cafe: Statement of account PDF

Statement of account PDF for Juniper Corner Cafe. Statement STM-CAF-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 1449.94 CAD. The printed ageing analysis totals 1460.86 CAD, which is 10.92 CAD more, because credit note CN-CAF-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Juniper Corner Cafe: Remittance advice PDF

Remittance advice PDF for Juniper Corner Cafe. Remittance advice REM-CAF-8001 dated 2026-09-05, covering all 13 documents on both statements. 1235.99 CAD is paid and 1940.07 CAD is withheld, against statement balances of 3176.06 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Juniper Corner Cafe: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Juniper Corner Cafe. OASIS UBL 2.1 Invoice for INV-CAF-5001 with 3 InvoiceLine elements, a TaxTotal of 16.53 on a taxable amount of 330.69, and a PayableAmount of 347.22 CAD. OrderReference names PO-CAF-1001 and DespatchDocumentReference names GRN-CAF-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Juniper Corner Cafe: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Juniper Corner Cafe. OASIS UBL 2.1 CreditNote for CN-CAF-7002 with type code 381, a BillingReference to invoice INV-CAF-5004 dated 2026-08-28, one CreditNoteLine of 5 each and a PayableAmount of 7.98 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-CAF-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Juniper Corner Cafe: Factur-X CII invoice XML

Factur-X CII invoice XML for Juniper Corner Cafe. UN/CEFACT Cross Industry Invoice for INV-CAF-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 16.53 and a DuePayableAmount of 347.22 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Juniper Corner Cafe: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Juniper Corner Cafe. Invoice INV-CAF-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 330.69, GST 16.53, 347.22 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Juniper Corner Cafe: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Juniper Corner Cafe. Version 004010 transaction set 850 for PO-CAF-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Juniper Corner Cafe: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Juniper Corner Cafe. Version 004010 transaction set 856 for supplier delivery note DN-CAF-3002 against PO-CAF-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 17 where the 850 ordered 21.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Juniper Corner Cafe: ANSI X12 810 invoice

ANSI X12 810 invoice for Juniper Corner Cafe. Version 004010 transaction set 810 for invoice INV-CAF-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 16.61, and a TDS segment of 34883 in implied-decimal cents, which is 348.83 CAD. SE declares 13 segments and 13 are present.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Juniper Corner Cafe: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Juniper Corner Cafe. 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 34883 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Juniper Corner Cafe: Procure-to-pay chain README

Procure-to-pay chain README for Juniper Corner Cafe. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Copper Oven Bakery: Purchase order PDF

Purchase order PDF for Copper Oven Bakery. Purchase order PO-BAK-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 275.86, GST 13.79 and 289.65 CAD payable. Line 2 orders 22 each of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Copper Oven Bakery: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Copper Oven Bakery. Goods-received note GRN-BAK-2002 against PO-BAK-1002, recording supplier delivery note DN-BAK-3002 on 2026-08-14. Line 2 records 18 each delivered against 22 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Copper Oven Bakery: Supplier invoice PDF

Supplier invoice PDF for Copper Oven Bakery. Invoice INV-BAK-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 275.86, GST 13.79 and 289.65 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 each.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Copper Oven Bakery: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Copper Oven Bakery. A second document issued under invoice number INV-BAK-5002, dated 2026-08-17 with 2 lines totalling 282.03 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 289.65 CAD. Both are listed on statement STM-BAK-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Copper Oven Bakery: Credit note PDF

Credit note PDF for Copper Oven Bakery. Credit note CN-BAK-7002 dated 2026-08-29 against invoice INV-BAK-5004 dated 2026-08-28: 5 kg at 4.94, net 24.70 and 25.94 CAD including GST. Goods-received note GRN-BAK-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Copper Oven Bakery: Statement of account PDF

Statement of account PDF for Copper Oven Bakery. Statement STM-BAK-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 1395.48 CAD. The printed ageing analysis totals 1396.87 CAD, which is 1.39 CAD more, because credit note CN-BAK-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Copper Oven Bakery: Remittance advice PDF

Remittance advice PDF for Copper Oven Bakery. Remittance advice REM-BAK-8001 dated 2026-09-05, covering all 13 documents on both statements. 946.62 CAD is paid and 1189.60 CAD is withheld, against statement balances of 2136.22 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Copper Oven Bakery: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Copper Oven Bakery. OASIS UBL 2.1 Invoice for INV-BAK-5001 with 3 InvoiceLine elements, a TaxTotal of 8.27 on a taxable amount of 165.41, and a PayableAmount of 173.68 CAD. OrderReference names PO-BAK-1001 and DespatchDocumentReference names GRN-BAK-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Copper Oven Bakery: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Copper Oven Bakery. OASIS UBL 2.1 CreditNote for CN-BAK-7002 with type code 381, a BillingReference to invoice INV-BAK-5004 dated 2026-08-28, one CreditNoteLine of 5 kg and a PayableAmount of 25.94 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-BAK-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Copper Oven Bakery: Factur-X CII invoice XML

Factur-X CII invoice XML for Copper Oven Bakery. UN/CEFACT Cross Industry Invoice for INV-BAK-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 8.27 and a DuePayableAmount of 173.68 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Copper Oven Bakery: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Copper Oven Bakery. Invoice INV-BAK-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 165.41, GST 8.27, 173.68 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Copper Oven Bakery: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Copper Oven Bakery. Version 004010 transaction set 850 for PO-BAK-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Copper Oven Bakery: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Copper Oven Bakery. Version 004010 transaction set 856 for supplier delivery note DN-BAK-3002 against PO-BAK-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 18 where the 850 ordered 22.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Copper Oven Bakery: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Copper Oven Bakery. 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 28965 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Copper Oven Bakery: Procure-to-pay chain README

Procure-to-pay chain README for Copper Oven Bakery. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Ember Lane Pizza: Purchase order PDF

Purchase order PDF for Ember Lane Pizza. Purchase order PO-PIZ-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 446.60, GST 22.33 and 468.93 CAD payable. Line 2 orders 23 kg of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Ember Lane Pizza: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Ember Lane Pizza. Goods-received note GRN-PIZ-2002 against PO-PIZ-1002, recording supplier delivery note DN-PIZ-3002 on 2026-08-14. Line 2 records 19 kg delivered against 23 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Ember Lane Pizza: Supplier invoice PDF

Supplier invoice PDF for Ember Lane Pizza. Invoice INV-PIZ-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 446.60, GST 22.33 and 468.93 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 kg.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Ember Lane Pizza: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Ember Lane Pizza. A second document issued under invoice number INV-PIZ-5002, dated 2026-08-17 with 2 lines totalling 406.14 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 468.93 CAD. Both are listed on statement STM-PIZ-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Ember Lane Pizza: Credit note PDF

Credit note PDF for Ember Lane Pizza. Credit note CN-PIZ-7002 dated 2026-08-29 against invoice INV-PIZ-5004 dated 2026-08-28: 5 each at 0.52, net 2.60 and 2.73 CAD including GST. Goods-received note GRN-PIZ-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Ember Lane Pizza: Statement of account PDF

Statement of account PDF for Ember Lane Pizza. Statement STM-PIZ-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 2166.98 CAD. The printed ageing analysis totals 2177.90 CAD, which is 10.92 CAD more, because credit note CN-PIZ-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Ember Lane Pizza: Remittance advice PDF

Remittance advice PDF for Ember Lane Pizza. Remittance advice REM-PIZ-8001 dated 2026-09-05, covering all 13 documents on both statements. 1450.33 CAD is paid and 1823.85 CAD is withheld, against statement balances of 3274.18 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Ember Lane Pizza: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Ember Lane Pizza. OASIS UBL 2.1 Invoice for INV-PIZ-5001 with 3 InvoiceLine elements, a TaxTotal of 12.19 on a taxable amount of 243.81, and a PayableAmount of 256.00 CAD. OrderReference names PO-PIZ-1001 and DespatchDocumentReference names GRN-PIZ-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Ember Lane Pizza: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Ember Lane Pizza. OASIS UBL 2.1 CreditNote for CN-PIZ-7002 with type code 381, a BillingReference to invoice INV-PIZ-5004 dated 2026-08-28, one CreditNoteLine of 5 each and a PayableAmount of 2.73 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-PIZ-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Ember Lane Pizza: Factur-X CII invoice XML

Factur-X CII invoice XML for Ember Lane Pizza. UN/CEFACT Cross Industry Invoice for INV-PIZ-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 12.19 and a DuePayableAmount of 256.00 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Ember Lane Pizza: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Ember Lane Pizza. Invoice INV-PIZ-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 243.81, GST 12.19, 256.00 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Ember Lane Pizza: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Ember Lane Pizza. Version 004010 transaction set 850 for PO-PIZ-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Ember Lane Pizza: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Ember Lane Pizza. Version 004010 transaction set 856 for supplier delivery note DN-PIZ-3002 against PO-PIZ-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 19 where the 850 ordered 23.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Ember Lane Pizza: ANSI X12 810 invoice

ANSI X12 810 invoice for Ember Lane Pizza. Version 004010 transaction set 810 for invoice INV-PIZ-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 22.33, and a TDS segment of 46893 in implied-decimal cents, which is 468.93 CAD. SE declares 13 segments and 13 are present.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Ember Lane Pizza: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Ember Lane Pizza. 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 46893 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Ember Lane Pizza: Procure-to-pay chain README

Procure-to-pay chain README for Ember Lane Pizza. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Cedar Street Tacos: Purchase order PDF

Purchase order PDF for Cedar Street Tacos. Purchase order PO-TRK-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 99.36, GST 4.97 and 104.33 CAD payable. Line 2 orders 24 kg of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Cedar Street Tacos: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Cedar Street Tacos. Goods-received note GRN-TRK-2002 against PO-TRK-1002, recording supplier delivery note DN-TRK-3002 on 2026-08-14. Line 2 records 20 kg delivered against 24 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Cedar Street Tacos: Supplier invoice PDF

Supplier invoice PDF for Cedar Street Tacos. Invoice INV-TRK-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 99.36, GST 4.97 and 104.33 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 kg.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Cedar Street Tacos: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Cedar Street Tacos. A second document issued under invoice number INV-TRK-5002, dated 2026-08-17 with 2 lines totalling 48.13 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 104.33 CAD. Both are listed on statement STM-TRK-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Cedar Street Tacos: Credit note PDF

Credit note PDF for Cedar Street Tacos. Credit note CN-TRK-7002 dated 2026-08-29 against invoice INV-TRK-5004 dated 2026-08-28: 5 each at 0.21, net 1.05 and 1.10 CAD including GST. Goods-received note GRN-TRK-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Cedar Street Tacos: Statement of account PDF

Statement of account PDF for Cedar Street Tacos. Statement STM-TRK-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 472.24 CAD. The printed ageing analysis totals 481.61 CAD, which is 9.37 CAD more, because credit note CN-TRK-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Cedar Street Tacos: Remittance advice PDF

Remittance advice PDF for Cedar Street Tacos. Remittance advice REM-TRK-8001 dated 2026-09-05, covering all 13 documents on both statements. 635.20 CAD is paid and 384.78 CAD is withheld, against statement balances of 1019.98 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Cedar Street Tacos: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Cedar Street Tacos. OASIS UBL 2.1 Invoice for INV-TRK-5001 with 3 InvoiceLine elements, a TaxTotal of 9.38 on a taxable amount of 187.70, and a PayableAmount of 197.08 CAD. OrderReference names PO-TRK-1001 and DespatchDocumentReference names GRN-TRK-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Cedar Street Tacos: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Cedar Street Tacos. OASIS UBL 2.1 CreditNote for CN-TRK-7002 with type code 381, a BillingReference to invoice INV-TRK-5004 dated 2026-08-28, one CreditNoteLine of 5 each and a PayableAmount of 1.10 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-TRK-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Cedar Street Tacos: Factur-X CII invoice XML

Factur-X CII invoice XML for Cedar Street Tacos. UN/CEFACT Cross Industry Invoice for INV-TRK-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 9.38 and a DuePayableAmount of 197.08 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Cedar Street Tacos: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Cedar Street Tacos. Invoice INV-TRK-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 187.70, GST 9.38, 197.08 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Cedar Street Tacos: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Cedar Street Tacos. Version 004010 transaction set 850 for PO-TRK-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Cedar Street Tacos: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Cedar Street Tacos. Version 004010 transaction set 856 for supplier delivery note DN-TRK-3002 against PO-TRK-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 20 where the 850 ordered 24.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Cedar Street Tacos: ANSI X12 810 invoice

ANSI X12 810 invoice for Cedar Street Tacos. Version 004010 transaction set 810 for invoice INV-TRK-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 4.97, and a TDS segment of 10433 in implied-decimal cents, which is 104.33 CAD. SE declares 13 segments and 13 are present.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Cedar Street Tacos: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Cedar Street Tacos. 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 10433 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Cedar Street Tacos: Procure-to-pay chain README

Procure-to-pay chain README for Cedar Street Tacos. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Willow Event Kitchen: Purchase order PDF

Purchase order PDF for Willow Event Kitchen. Purchase order PO-CAT-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 198.21, GST 9.92 and 208.13 CAD payable. Line 2 orders 25 kg of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Willow Event Kitchen: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Willow Event Kitchen. Goods-received note GRN-CAT-2002 against PO-CAT-1002, recording supplier delivery note DN-CAT-3002 on 2026-08-14. Line 2 records 21 kg delivered against 25 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Willow Event Kitchen: Supplier invoice PDF

Supplier invoice PDF for Willow Event Kitchen. Invoice INV-CAT-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 198.21, GST 9.92 and 208.13 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 kg.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Willow Event Kitchen: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Willow Event Kitchen. A second document issued under invoice number INV-CAT-5002, dated 2026-08-17 with 2 lines totalling 144.60 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 208.13 CAD. Both are listed on statement STM-CAT-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Willow Event Kitchen: Credit note PDF

Credit note PDF for Willow Event Kitchen. Credit note CN-CAT-7002 dated 2026-08-29 against invoice INV-CAT-5004 dated 2026-08-28: 5 each at 1.14, net 5.70 and 5.99 CAD including GST. Goods-received note GRN-CAT-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Willow Event Kitchen: Statement of account PDF

Statement of account PDF for Willow Event Kitchen. Statement STM-CAT-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 981.44 CAD. The printed ageing analysis totals 991.60 CAD, which is 10.16 CAD more, because credit note CN-CAT-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Willow Event Kitchen: Remittance advice PDF

Remittance advice PDF for Willow Event Kitchen. Remittance advice REM-CAT-8001 dated 2026-09-05, covering all 13 documents on both statements. 1088.50 CAD is paid and 896.30 CAD is withheld, against statement balances of 1984.80 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Willow Event Kitchen: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Willow Event Kitchen. OASIS UBL 2.1 Invoice for INV-CAT-5001 with 3 InvoiceLine elements, a TaxTotal of 14.79 on a taxable amount of 295.84, and a PayableAmount of 310.63 CAD. OrderReference names PO-CAT-1001 and DespatchDocumentReference names GRN-CAT-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Willow Event Kitchen: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Willow Event Kitchen. OASIS UBL 2.1 CreditNote for CN-CAT-7002 with type code 381, a BillingReference to invoice INV-CAT-5004 dated 2026-08-28, one CreditNoteLine of 5 each and a PayableAmount of 5.99 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-CAT-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Willow Event Kitchen: Factur-X CII invoice XML

Factur-X CII invoice XML for Willow Event Kitchen. UN/CEFACT Cross Industry Invoice for INV-CAT-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 14.79 and a DuePayableAmount of 310.63 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Willow Event Kitchen: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Willow Event Kitchen. Invoice INV-CAT-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 295.84, GST 14.79, 310.63 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Willow Event Kitchen: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Willow Event Kitchen. Version 004010 transaction set 850 for PO-CAT-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Willow Event Kitchen: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Willow Event Kitchen. Version 004010 transaction set 856 for supplier delivery note DN-CAT-3002 against PO-CAT-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 21 where the 850 ordered 25.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Willow Event Kitchen: ANSI X12 810 invoice

ANSI X12 810 invoice for Willow Event Kitchen. Version 004010 transaction set 810 for invoice INV-CAT-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 9.92, and a TDS segment of 20813 in implied-decimal cents, which is 208.13 CAD. SE declares 13 segments and 13 are present.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Willow Event Kitchen: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Willow Event Kitchen. 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 20813 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Willow Event Kitchen: Procure-to-pay chain README

Procure-to-pay chain README for Willow Event Kitchen. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Harbour Kitchen Group: Purchase order PDF

Purchase order PDF for Harbour Kitchen Group. Purchase order PO-GRP-1002 dated 2026-08-12 to Harbour Food Supply: 3 lines, net 309.92, GST 15.49 and 325.41 CAD payable. Line 2 orders 26 each of ING-03, which is the line the delivery note and the invoice later disagree about.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Harbour Kitchen Group: Delivery note and goods-received note PDF

Delivery note and goods-received note PDF for Harbour Kitchen Group. Goods-received note GRN-GRP-2002 against PO-GRP-1002, recording supplier delivery note DN-GRP-3002 on 2026-08-14. Line 2 records 22 each delivered against 26 ordered and is marked 'short delivery'. A goods-in note under the table explains each line in words.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Harbour Kitchen Group: Supplier invoice PDF

Supplier invoice PDF for Harbour Kitchen Group. Invoice INV-GRP-5002 dated 2026-08-14, due 2026-09-13: 3 lines, net 309.92, GST 15.49 and 325.41 CAD due. Line 2 bills the ordered quantity even though the goods-received note records a short delivery of 4 each.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Harbour Kitchen Group: Supplier invoice PDF reusing an invoice number

Supplier invoice PDF reusing an invoice number for Harbour Kitchen Group. A second document issued under invoice number INV-GRP-5002, dated 2026-08-17 with 2 lines totalling 266.99 CAD. The first document of that number is dated 2026-08-14 with 3 lines totalling 325.41 CAD. Both are listed on statement STM-GRP-6002 and both are inside its closing balance.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Harbour Kitchen Group: Credit note PDF

Credit note PDF for Harbour Kitchen Group. Credit note CN-GRP-7002 dated 2026-08-29 against invoice INV-GRP-5004 dated 2026-08-28: 5 l at 1.90, net 9.50 and 9.98 CAD including GST. Goods-received note GRN-GRP-2004 records only 3 units returned, so the credit is 2 units too large.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Harbour Kitchen Group: Statement of account PDF

Statement of account PDF for Harbour Kitchen Group. Statement STM-GRP-6002 for Harbour Food Supply at 2026-08-31: 8 transactions closing at 1333.12 CAD. The printed ageing analysis totals 1342.11 CAD, which is 8.99 CAD more, because credit note CN-GRP-7001 is listed in the transactions but was never applied to the buckets.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing+1

Harbour Kitchen Group: Remittance advice PDF

Remittance advice PDF for Harbour Kitchen Group. Remittance advice REM-GRP-8001 dated 2026-09-05, covering all 13 documents on both statements. 1041.96 CAD is paid and 1608.28 CAD is withheld, against statement balances of 2650.24 CAD. Every withheld document is listed again below the table with the reason it was not paid.

File: PDF · Procure To Pay · 1 page
Use case: Data importPDF editor testing

Harbour Kitchen Group: UBL 2.1 invoice XML

UBL 2.1 invoice XML for Harbour Kitchen Group. OASIS UBL 2.1 Invoice for INV-GRP-5001 with 3 InvoiceLine elements, a TaxTotal of 13.10 on a taxable amount of 261.93, and a PayableAmount of 275.03 CAD. OrderReference names PO-GRP-1001 and DespatchDocumentReference names GRN-GRP-2001, both of which exist in this folder.

File: XML · Procure To Pay · UTF-8
Use case: Data importConversion testing+1

Harbour Kitchen Group: UBL 2.1 credit note XML

UBL 2.1 credit note XML for Harbour Kitchen Group. OASIS UBL 2.1 CreditNote for CN-GRP-7002 with type code 381, a BillingReference to invoice INV-GRP-5004 dated 2026-08-28, one CreditNoteLine of 5 l and a PayableAmount of 9.98 CAD. It carries the same over-credit as credit-note.pdf: 2 units more than GRN-GRP-2004 records returned.

File: XML · Procure To Pay
Use case: Data importConversion testing+1

Harbour Kitchen Group: Factur-X CII invoice XML

Factur-X CII invoice XML for Harbour Kitchen Group. UN/CEFACT Cross Industry Invoice for INV-GRP-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 13.10 and a DuePayableAmount of 275.03 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.

File: XML · Procure To Pay
Use case: Data importConversion testing+1· Paired fixture

Harbour Kitchen Group: Factur-X hybrid invoice PDF

Factur-X hybrid invoice PDF for Harbour Kitchen Group. Invoice INV-GRP-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 261.93, GST 13.10, 275.03 CAD due. This is the only file in the set that carries its data twice in one container.

File: PDF · Procure To Pay · 1 page
Use case: Data importConversion testing+1· Paired fixture

Harbour Kitchen Group: ANSI X12 850 purchase order

ANSI X12 850 purchase order for Harbour Kitchen Group. Version 004010 transaction set 850 for PO-GRP-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.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Harbour Kitchen Group: ANSI X12 856 despatch advice

ANSI X12 856 despatch advice for Harbour Kitchen Group. Version 004010 transaction set 856 for supplier delivery note DN-GRP-3002 against PO-GRP-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 22 where the 850 ordered 26.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Harbour Kitchen Group: ANSI X12 810 invoice

ANSI X12 810 invoice for Harbour Kitchen Group. Version 004010 transaction set 810 for invoice INV-GRP-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 15.49, and a TDS segment of 32541 in implied-decimal cents, which is 325.41 CAD. SE declares 13 segments and 13 are present.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing

Harbour Kitchen Group: ANSI X12 810 invoice with a wrong SE segment count

ANSI X12 810 invoice with a wrong SE segment count for Harbour Kitchen Group. 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 32541 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.

File: EDI · Procure To Pay · ASCII
Use case: Data importConversion testing+1

Harbour Kitchen Group: Procure-to-pay chain README

Procure-to-pay chain README for Harbour Kitchen Group. Names all 28 files in this folder, tabulates the seven-step chain from price list to remittance advice, and states all 6 deliberate disagreements with the exact numbers and the assertion that detects each. It also separates those defects from three traps that are modelling rather than errors: case price against unit price, the unreachable contract tier at 250 units, and the two legitimate tax-total conventions.

File: MD · Procure To Pay · UTF-8
Use case: Data importError handling

Alder Table Bistro: Costing report PDF

Costing report PDF for Alder Table Bistro. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (1574.81 CAD) and the 5 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Alder Table Bistro: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Alder Table Bistro. A 110-line guide naming all 31 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Juniper Corner Cafe: Costing report PDF

Costing report PDF for Juniper Corner Cafe. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (1538.14 CAD) and the 2 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Juniper Corner Cafe: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Juniper Corner Cafe. A 109-line guide naming all 30 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Copper Oven Bakery: Costing report PDF

Costing report PDF for Copper Oven Bakery. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (623.44 CAD) and the 2 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Copper Oven Bakery: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Copper Oven Bakery. A 109-line guide naming all 30 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Ember Lane Pizza: Costing report PDF

Costing report PDF for Ember Lane Pizza. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (3110.43 CAD) and the 2 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Ember Lane Pizza: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Ember Lane Pizza. A 110-line guide naming all 31 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Cedar Street Tacos: Costing report PDF

Costing report PDF for Cedar Street Tacos. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (2559.57 CAD) and the 3 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Cedar Street Tacos: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Cedar Street Tacos. A 109-line guide naming all 30 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Willow Event Kitchen: Costing report PDF

Costing report PDF for Willow Event Kitchen. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (2106.63 CAD) and the 2 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Willow Event Kitchen: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Willow Event Kitchen. A 109-line guide naming all 30 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Harbour Kitchen Group: Costing report PDF

Costing report PDF for Harbour Kitchen Group. A 3-page report whose first page begins "Recipe and plate costing". Page 1 lists the 6 purchase packs with their converted unit costs and opens the per-dish costing, which runs through page 2 for all 4 menu items. Page 3 carries the period cost of goods sold (3241.08 CAD) and the 4 yield tests.

File: PDF · Restaurant Costing · 3 pages
Use case: Data importOCR testing· Conversion set

Harbour Kitchen Group: Folder guide and deliberate-defect index

Folder guide and deliberate-defect index for Harbour Kitchen Group. A 110-line guide naming all 31 files in the folder, the rounding rule used at every step, and each of the 5 files that deliberately disagree with another, with the exact figures on both sides of each disagreement.

File: MD · Restaurant Costing · UTF-8
Use case: Data import

Fieldnote Supply Shop: Order export workbook

Order export workbook for Fieldnote Supply Shop. One worksheet named Orders with a header row and 12 data rows carrying the same values as orders-export.csv. Numeric columns are stored as text so the 5-decimal tax_rate and the leading-zero-free ids survive a round trip unchanged.

File: XLSX · Ecommerce Documents · 12 rows
Use case: Data import· Conversion set

Fieldnote Supply Shop: Settlement statement PDF

Settlement statement PDF for Fieldnote Supply Shop. A readable settlement statement whose first page summary reads Gross sales 922.00, Net payable 661.01, and whose second page lists all 41 transaction lines. Negative amounts are shown in accounting parentheses rather than with a minus sign.

File: PDF · Ecommerce Documents · 2 pages
Use case: Data import· Paired fixture

Fieldnote Supply Shop: Order confirmation PDF

Order confirmation PDF for Fieldnote Supply Shop. A single-page buyer confirmation for ORD-003. It lists 2 items, a merchandise subtotal of 120.00, no promotion, sales tax of 9.90 at the US-TX rate 0.08250 and an order total of 129.90.

File: PDF · Ecommerce Documents · 1 page
Use case: Data import

Fieldnote Supply Shop: Credit note PDF

Credit note PDF for Fieldnote Supply Shop. A one-page credit note reversing the whole of line LINE-007 on order ORD-004: merchandise 32.00, tax 3.28 and a total credit of 35.28. It states on its face that the order promotion is not reversed.

File: PDF · Ecommerce Documents · 1 page
Use case: Data import

Fieldnote Supply Shop: Document set README

Document set README for Fieldnote Supply Shop. 37 files, 3 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Ecommerce Documents
Use case: Data import

Pine Assembly Workshop: Shipment export workbook

Shipment export workbook for Pine Assembly Workshop. One worksheet named Shipments with a header row and 16 data rows carrying the same values as shipments-export.csv. Weights are stored as text, so the trailing zero in a figure such as 24.400 survives the round trip instead of being displayed as a shorter number.

File: XLSX · Logistics Shipping · 16 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Bill of lading BOL-2026-0001 PDF

Bill of lading BOL-2026-0001 PDF for Pine Assembly Workshop. A one-page straight bill of lading for North loop. The consignment table lists 4 shipments and closes on a Total row reading 8 pieces, 97.600 kg and 544.00 USD declared value.

File: PDF · Logistics Shipping · 1 page
Use case: Data import

Pine Assembly Workshop: Bill of lading BOL-2026-0004 PDF

Bill of lading BOL-2026-0004 PDF for Pine Assembly Workshop. A one-page straight bill of lading for West loop. The consignment table lists 4 shipments and closes on a Total row reading 20 pieces, 244.000 kg and 1,360.00 USD declared value.

File: PDF · Logistics Shipping · 1 page
Use case: Data import

Pine Assembly Workshop: Packing list PDF

Packing list PDF for Pine Assembly Workshop. A one-page packing list for BOL-2026-0003. The carton-contents table closes on a Total of 12.200 kg and the consignment table on 16 cartons weighing 195.200 kg.

File: PDF · Logistics Shipping · 1 page
Use case: Data import

Pine Assembly Workshop: Freight rating workbook

Freight rating workbook for Pine Assembly Workshop. Two worksheets: Rate sheet (2 zone rows) and Freight charges (16 rated shipments). The second sheet is derived entirely from the first plus shipments-export.csv, so the workbook carries both the inputs and the result of the same calculation.

File: XLSX · Logistics Shipping · 16 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Carrier freight invoice PDF

Carrier freight invoice PDF for Pine Assembly Workshop. A one-page freight invoice listing the 13 delivered consignments and closing on a Total due row of 861.19 USD. The rate basis is printed in the footnote, so the document carries everything needed to re-rate it.

File: PDF · Logistics Shipping · 1 page
Use case: Data import

Pine Assembly Workshop: Proof of delivery PDF

Proof of delivery PDF for Pine Assembly Workshop. A one-page delivery confirmation for SHIP-07. The record table states 4 pieces delivered against 4 expected, 48.800 kg gross and 16 actual minutes against 15 planned.

File: PDF · Logistics Shipping · 1 page
Use case: Data import

Pine Assembly Workshop: Customs commercial invoice PDF

Customs commercial invoice PDF for Pine Assembly Workshop. A one-page commercial invoice for the BOL-2026-0004 export. The line table totals 1,360.00 USD over 20 units and the valuation table walks goods plus freight to a customs value of 1,748.08 and a total charges payable of 133.29.

File: PDF · Logistics Shipping · 1 page
Use case: Data import· Conversion set

Pine Assembly Workshop: Document set README

Document set README for Pine Assembly Workshop. 30 files, 2 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Logistics Shipping
Use case: Data import

Tern Client Services: Timesheet export workbook

Timesheet export workbook for Tern Client Services. One worksheet named Time entries with 24 data rows carrying the same values as timesheet-export.csv. Amounts are stored as text with two decimals so a value such as 100.00 is not displayed as 100 after a round trip.

File: XLSX · Professional Services Billing · 24 rows
Use case: Data import· Conversion set

Tern Client Services: Project timesheet PDF

Project timesheet PDF for Tern Client Services. A one-page timesheet for PROJECT-3. The entry table lists 8 lines and closes on a Total row of 32 hours and 3,200.00.

File: PDF · Professional Services Billing · 1 page
Use case: Data import

Tern Client Services: Fee schedule PDF

Fee schedule PDF for Tern Client Services. A one-page rate card listing the same 5 codes as fee-schedule.csv with the standard rate at 100.00 per hour and mileage at 0.62 per kilometre. The notes state that COST is internal and never billed.

File: PDF · Professional Services Billing · 1 page
Use case: Data import

Tern Client Services: Progress bill PDF

Progress bill PDF for Tern Client Services. A one-page progress bill for PROJECT-3 against a 4,000.00 budget. It states 3,200.00 of work completed, 80.00 percent of budget, nothing previously billed, 3,200.00 payable in cash and 800.00 of budget remaining.

File: PDF · Professional Services Billing · 1 page
Use case: Data import

Tern Client Services: Retainer statement PDF

Retainer statement PDF for Tern Client Services. A one-page retainer statement. The movement table replays the three ledger entries to a closing balance of 0.00 and the invoice table shows 4,000.00 of the 7,200.00 billed taken from the retainer, leaving 3,200.00 in cash. Draws are printed in accounting parentheses.

File: PDF · Professional Services Billing · 1 page
Use case: Data import

Tern Client Services: Expense claim PDF

Expense claim PDF for Tern Client Services. A one-page expense claim. The line table closes on 221.57 and the allocation table splits the same figure into 146.32 of mileage and 75.25 of receipted items across the three projects.

File: PDF · Professional Services Billing · 1 page
Use case: Data import· Conversion set

Tern Client Services: Sales pipeline workbook

Sales pipeline workbook for Tern Client Services. Two worksheets: Deals (12 rows, the same data as pipeline-export.csv) and By stage (4 rows). The By stage sheet is derived from the Deals sheet, so its amount column sums to the same 34500.00 and its share_of_pipeline_percent column sums to 100.00.

File: XLSX · Professional Services Billing
Use case: Data import· Conversion set

Tern Client Services: Document set README

Document set README for Tern Client Services. 27 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Professional Services Billing
Use case: Data import

Pine Property Services: Payment application workbook

Payment application workbook for Pine Property Services. Three worksheets: Schedule of values (13 rows), Continuation G703 (15 rows) and Summary G702 (11 rows). The three are the same application at three levels of detail and agree exactly: 3858.00 of original contract, 3248.00 completed and stored and 1582.20 due.

File: XLSX · Construction Billing
Use case: Data import· Conversion set

Pine Property Services: Change order PDF

Change order PDF for Pine Property Services. A one-page change order adding 420.00 to the contract. The effect table walks the contract sum from 3,858.00 to 4,278.00 and the scope note states the retainage held against it, 42.00.

File: PDF · Construction Billing · 1 page
Use case: Data import

Pine Property Services: Conditional lien waiver PDF

Conditional lien waiver PDF for Pine Property Services. A one-page conditional waiver on progress payment for 1,582.20. The payment table walks 3,248.00 completed and stored through 324.80 of retainage and 1,341.00 of previous certificates to the amount of this payment, and a Rights not waived section states that the 324.80 of retainage is not released.

File: PDF · Construction Billing · 1 page
Use case: Data import

Pine Property Services: Certificate for payment PDF

Certificate for payment PDF for Pine Property Services. A one-page certificate reproducing all 11 numbered lines of the application and certifying 1,582.20. The note explains why line 9 (1,189.80) and the continuation sheet's balance column (865.00) differ by the 324.80 of retainage.

File: PDF · Construction Billing · 1 page
Use case: Data import

Pine Property Services: Document set README

Document set README for Pine Property Services. 23 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Construction Billing
Use case: Data import

Willow Community Fund: Donation receipt PDF, pure gift

Donation receipt PDF, pure gift for Willow Community Fund. A one-page receipt for RCPT-2026-0001. The deductible table starts at 100.00 gross, deducts nothing and ends at 100.00 deductible. The statement of goods and services says in words what the table says in figures.

File: PDF · Nonprofit Giving · 1 page
Use case: Data import

Willow Community Fund: Donation receipt PDF, quid pro quo gift

Donation receipt PDF, quid pro quo gift for Willow Community Fund. A one-page receipt for RCPT-2026-0009. The deductible table starts at 300.00 gross, deducts 25.50 of benefits and ends at 274.50 deductible. The statement of goods and services says in words what the table says in figures.

File: PDF · Nonprofit Giving · 1 page
Use case: Data import

Willow Community Fund: Pledge and receipt workbook

Pledge and receipt workbook for Willow Community Fund. Two worksheets: Instalments (18 rows) and Receipts (9 rows). Every paid instalment on the first sheet has a receipt on the second for the same amount, and the unpaid instalments have none, which is why the sheets total 2850.00 and 1800.00.

File: XLSX · Nonprofit Giving
Use case: Data import· Conversion set

Willow Community Fund: Grant reporting workbook

Grant reporting workbook for Willow Community Fund. Two worksheets: Grant register (3 rows) and Budget vs actual (10 rows). The budget column of the second sheet rolls up to the awarded column of the first, 4500.00, and the pending grant appears on the register with no budget sheet rows at all.

File: XLSX · Nonprofit Giving
Use case: Data import· Conversion set

Willow Community Fund: Annual donor acknowledgement letter PDF

Annual donor acknowledgement letter PDF for Willow Community Fund. A one-page acknowledgement for DON-01. The gift table lists 2 receipts and closes on 400.00 gross, 25.50 of benefits and 374.50 deductible, and the closing paragraph quotes the whole-organisation figures.

File: PDF · Nonprofit Giving · 1 page
Use case: Data import

Willow Community Fund: Document set README

Document set README for Willow Community Fund. 24 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Nonprofit Giving
Use case: Data import

Fieldnote Learning Centre: Course fee schedule PDF

Course fee schedule PDF for Fieldnote Learning Centre. A one-page fee card listing the same 3 courses as fee-schedule.csv, with the instalment threshold of 250.00 and the bursary rules printed underneath. The capping rule for fixed awards is the one the invoice register depends on.

File: PDF · Education Administration · 1 page
Use case: Data import· Conversion set

Fieldnote Learning Centre: Enrolment workbook

Enrolment workbook for Fieldnote Learning Centre. Two worksheets: Enrolments (18 rows) and Fees (3 rows). Learner identifiers are stored as text, so LEARN-01 keeps its leading zero rather than being coerced, and the score column is text for the same reason a grade of 100 must not become 1.0E+02.

File: XLSX · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Gradebook workbook, one sheet per course

Gradebook workbook, one sheet per course for Fieldnote Learning Centre. 3 worksheets, one per course, named for the course rather than numbered: Spreadsheet basics, Customer service, Workshop safety orientation. Each holds the 6 results for that course, so the workbook carries the same 18 rows as gradebook-export.csv split three ways.

File: XLSX · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Learner transcript PDF

Learner transcript PDF for Fieldnote Learning Centre. A one-page transcript for LEARN-05 listing 2 enrolments. One is a completed pass and one is incomplete with a score of 75, above the pass mark, recorded as incomplete rather than as a pass. The fee table closes on 575.00 gross, 120.00 of bursary and 455.00 net.

File: PDF · Education Administration · 1 page
Use case: Data import

Fieldnote Learning Centre: Learner statement of account PDF

Learner statement of account PDF for Fieldnote Learning Centre. A one-page statement for LEARN-03 covering 2 invoices. The invoice table closes on 525.00 gross, (262.50) of bursary and 262.50 payable, and the composition table breaks each gross fee into tuition, materials and registration.

File: PDF · Education Administration · 1 page
Use case: Data import

Fieldnote Learning Centre: Document set README

Document set README for Fieldnote Learning Centre. 24 files, 2 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Education Administration
Use case: Data import

Cobalt Operations Team: Payroll register workbook

Payroll register workbook for Cobalt Operations Team. One worksheet with the 8 employee rows and the TOTAL row, the same values as payroll-register.csv. Amounts are stored as text with two decimals, so a net pay ending in a zero cent is not displayed short and cannot be silently re-rounded by a recalculation.

File: XLSX · Payroll Hr · 9 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Payslip PDF for EMP-03

Payslip PDF for EMP-03 for Cobalt Operations Team. A one-page payslip for Team member 3. The period table runs 1,008.00 gross through three deductions to 734.16 net, the employer-cost table shows 30.24, 77.11 and 63.00 that are not deducted from pay, and the year-to-date table shows 5 periods at 3,670.80 net.

File: PDF · Payroll Hr · 1 page
Use case: Data import· Conversion set

Cobalt Operations Team: Payslip PDF for EMP-08

Payslip PDF for EMP-08 for Cobalt Operations Team. A one-page payslip for Team member 8. The period table runs 1,428.00 gross through three deductions to 1,057.56 net, the employer-cost table shows 42.84, 109.24 and 63.00 that are not deducted from pay, and the year-to-date table shows 5 periods at 5,287.80 net.

File: PDF · Payroll Hr · 1 page
Use case: Data import· Conversion set

Cobalt Operations Team: Leave workbook

Leave workbook for Cobalt Operations Team. Two worksheets: Balances (9 rows including TOTAL) and Requests (4 rows). The approved requests on the second sheet are the approved_future_hours on the first; the pending ones are not, which is visible by comparing the two sheets side by side.

File: XLSX · Payroll Hr
Use case: Data import· Conversion set

Cobalt Operations Team: Hours and payroll workbook

Hours and payroll workbook for Cobalt Operations Team. Two worksheets: Shifts (48 rows) and Register (9 rows). The Register sheet is derived entirely from the Shifts sheet plus the declared rates, so the workbook carries the input and the output of one payroll run and both total 9072.00 gross.

File: XLSX · Payroll Hr
Use case: Data import· Conversion set

Cobalt Operations Team: Payroll summary PDF

Payroll summary PDF for Cobalt Operations Team. A one-page summary of the run. The employee table closes on 9,072.00 gross, (2,422.56) of deductions and 6,649.44 net; the deduction analysis splits the same 2,422.56 three ways; and the employer cost table adds 1,470.17 of employer contributions to reach 10,542.17.

File: PDF · Payroll Hr · 1 page
Use case: Data import

Cobalt Operations Team: Document set README

Document set README for Cobalt Operations Team. 29 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Payroll Hr
Use case: Data import

Juniper Workspace Cloud: Mid-cycle upgrade invoice PDF

Mid-cycle upgrade invoice PDF for Juniper Workspace Cloud. A one-page invoice for INV-2609-02 showing all three lines of a mid-cycle upgrade: the 49.00 Team recurring charge, the (24.50) credit for the unused days and the 49.50 Studio charge, totalling 74.00.

File: PDF · Saas Billing · 1 page
Use case: Data import

Juniper Workspace Cloud: Annual contract invoice PDF

Annual contract invoice PDF for Juniper Workspace Cloud. A one-page invoice billing 1,069.20 in advance for twelve months of the Studio plan, with the discount arithmetic (99.00 x 12 less 10 percent) and the deferred-revenue treatment stated on the face of the invoice.

File: PDF · Saas Billing · 1 page
Use case: Data import

Juniper Workspace Cloud: Subscription billing workbook

Subscription billing workbook for Juniper Workspace Cloud. Five worksheets carrying the whole set: Invoice register (17 rows), September lines (9), MRR movement (6), Usage bill (6) and Revenue recognition (15). Amounts are stored as text so a reader cannot silently change a cent through a float conversion.

File: XLSX · Saas Billing · 53 rows
Use case: Data import

Juniper Workspace Cloud: Document set README

Document set README for Juniper Workspace Cloud. 24 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Saas Billing
Use case: Data import

Alder Books Reconciliation: Month-end ledger pack workbook

Month-end ledger pack workbook for Alder Books Reconciliation. Five worksheets: Chart of accounts (9 rows), General ledger (66), Trial balance (10), Bank statement (24) and Aged debtors (9). The trial balance sheet totals 13100.00 on each side and the bank statement sheet closes on the same cash figure.

File: XLSX · Accounting Ledgers · 118 rows
Use case: Data import

Alder Books Reconciliation: Month-end close pack PDF

Month-end close pack PDF for Alder Books Reconciliation. A two-page close pack: page one carries the 10-row trial balance totalling 13,100.00 on each side and the receivables ageing summing to 800.00; page two states the bank reconciliation and the budget variance of 2,136.00.

File: PDF · Accounting Ledgers · 2 pages
Use case: Data import

Alder Books Reconciliation: Document set README

Document set README for Alder Books Reconciliation. 33 files, 5 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

File: MD · Accounting Ledgers
Use case: Data import

Alder Table Bistro: Printed menu

Printed menu for Alder Table Bistro. A one page food menu with 3 sections (Starters, Mains, Sides) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Alder Table Bistro". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Alder Table Bistro: Printed menu as a Word document

Printed menu as a Word document for Alder Table Bistro. The same 4 dishes and 3 sections as printed-menu.pdf, laid out as 3 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Alder Table Bistro: Allergen menu

Allergen menu for Alder Table Bistro. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Alder Table Bistro: Drinks list

Drinks list for Alder Table Bistro. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Alder Table Bistro: Daily specials insert

Daily specials insert for Alder Table Bistro. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Alder Table Bistro: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Alder Table Bistro. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Alder Table Bistro: Set lunch

Set lunch for Alder Table Bistro. A fixed price page at 31.00 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 35.50 CAD, so the page states a saving of 4.50 CAD. Plate cost for the bundle is 4.33 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Alder Table Bistro: Children's plates

Children's plates for Alder Table Bistro. A one page children's menu: the same 4 dishes as smaller portions at 60 percent of the menu price, rounded to the nearest 0.05. The prices are 14.40, 6.90, 7.80, 7.50 CAD, and every one already lands on a five cent step, so no row on the page is rounded.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Alder Table Bistro: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Alder Table Bistro. Intentionally wrong. MENU-02 Tomato soup is printed at 12.50 CAD where plate-costs.csv carries 11.50 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Alder Table Bistro: Menu folder guide

Menu folder guide for Alder Table Bistro. A 80 line guide naming every one of the 19 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Juniper Corner Cafe: Printed menu

Printed menu for Juniper Corner Cafe. A one page food menu with 2 sections (Espresso bar, All day kitchen) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Juniper Corner Cafe". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Juniper Corner Cafe: Printed menu as a Word document

Printed menu as a Word document for Juniper Corner Cafe. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Juniper Corner Cafe: Allergen menu

Allergen menu for Juniper Corner Cafe. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Juniper Corner Cafe: Drinks list

Drinks list for Juniper Corner Cafe. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Juniper Corner Cafe: Daily specials insert

Daily specials insert for Juniper Corner Cafe. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Juniper Corner Cafe: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Juniper Corner Cafe. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Juniper Corner Cafe: Breakfast set

Breakfast set for Juniper Corner Cafe. A fixed price page at 13.50 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 15.25 CAD, so the page states a saving of 1.75 CAD. Plate cost for the bundle is 2.22 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Juniper Corner Cafe: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Juniper Corner Cafe. Intentionally wrong. MENU-02 Oat latte is printed at 6.50 CAD where plate-costs.csv carries 5.50 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Juniper Corner Cafe: Menu folder guide

Menu folder guide for Juniper Corner Cafe. A 78 line guide naming every one of the 18 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Copper Oven Bakery: Printed menu

Printed menu for Copper Oven Bakery. A one page food menu with 2 sections (Bread counter, Viennoiserie and sweet) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Copper Oven Bakery". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Copper Oven Bakery: Printed menu as a Word document

Printed menu as a Word document for Copper Oven Bakery. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Copper Oven Bakery: Allergen menu

Allergen menu for Copper Oven Bakery. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Copper Oven Bakery: Drinks list

Drinks list for Copper Oven Bakery. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Copper Oven Bakery: Daily specials insert

Daily specials insert for Copper Oven Bakery. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Copper Oven Bakery: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Copper Oven Bakery. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Copper Oven Bakery: Pastry box of three

Pastry box of three for Copper Oven Bakery. A fixed price page at 11.50 CAD covering 3 dishes that are already on the printed menu. The same items ordered separately come to 13.50 CAD, so the page states a saving of 2.00 CAD. Plate cost for the bundle is 1.24 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Copper Oven Bakery: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Copper Oven Bakery. Intentionally wrong. MENU-02 Butter croissant is printed at 5.25 CAD where plate-costs.csv carries 4.25 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Copper Oven Bakery: Menu folder guide

Menu folder guide for Copper Oven Bakery. A 78 line guide naming every one of the 18 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Ember Lane Pizza: Printed menu

Printed menu for Ember Lane Pizza. A one page food menu with 2 sections (Classic pizzas, House pizzas) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Ember Lane Pizza". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Ember Lane Pizza: Printed menu as a Word document

Printed menu as a Word document for Ember Lane Pizza. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Ember Lane Pizza: Allergen menu

Allergen menu for Ember Lane Pizza. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Ember Lane Pizza: Drinks list

Drinks list for Ember Lane Pizza. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Ember Lane Pizza: Daily specials insert

Daily specials insert for Ember Lane Pizza. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Ember Lane Pizza: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Ember Lane Pizza. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Ember Lane Pizza: Two pizza family deal

Two pizza family deal for Ember Lane Pizza. A fixed price page at 33.00 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 37.00 CAD, so the page states a saving of 4.00 CAD. Plate cost for the bundle is 4.79 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Ember Lane Pizza: Children's pizzas

Children's pizzas for Ember Lane Pizza. A one page children's menu: the same 4 dishes as smaller portions at 60 percent of the menu price, rounded to the nearest 0.05. The prices are 10.20, 12.00, 11.10, 10.80 CAD, and every one already lands on a five cent step, so no row on the page is rounded.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Ember Lane Pizza: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Ember Lane Pizza. Intentionally wrong. MENU-02 Pepperoni pizza is printed at 21.00 CAD where plate-costs.csv carries 20.00 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Ember Lane Pizza: Menu folder guide

Menu folder guide for Ember Lane Pizza. A 80 line guide naming every one of the 19 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Cedar Street Tacos: Printed menu

Printed menu for Cedar Street Tacos. A one page food menu with 2 sections (Tacos, Bowls) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Cedar Street Tacos". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Cedar Street Tacos: Printed menu as a Word document

Printed menu as a Word document for Cedar Street Tacos. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Cedar Street Tacos: Allergen menu

Allergen menu for Cedar Street Tacos. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Cedar Street Tacos: Drinks list

Drinks list for Cedar Street Tacos. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Cedar Street Tacos: Daily specials insert

Daily specials insert for Cedar Street Tacos. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Cedar Street Tacos: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Cedar Street Tacos. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Cedar Street Tacos: Two plate combo

Two plate combo for Cedar Street Tacos. A fixed price page at 22.50 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 25.50 CAD, so the page states a saving of 3.00 CAD. Plate cost for the bundle is 3.29 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Cedar Street Tacos: Children's plates

Children's plates for Cedar Street Tacos. A one page children's menu: the same 4 dishes as smaller portions at 60 percent of the menu price, rounded to the nearest 0.05. The prices are 8.10, 6.60, 8.70, 7.20 CAD, and every one already lands on a five cent step, so no row on the page is rounded.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Cedar Street Tacos: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Cedar Street Tacos. Intentionally wrong. MENU-02 Bean taco trio is printed at 12.00 CAD where plate-costs.csv carries 11.00 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Cedar Street Tacos: Menu folder guide

Menu folder guide for Cedar Street Tacos. A 80 line guide naming every one of the 19 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Willow Event Kitchen: Printed menu

Printed menu for Willow Event Kitchen. A one page food menu with 2 sections (Buffet service, Delivered service) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Willow Event Kitchen". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Willow Event Kitchen: Printed menu as a Word document

Printed menu as a Word document for Willow Event Kitchen. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Willow Event Kitchen: Allergen menu

Allergen menu for Willow Event Kitchen. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Willow Event Kitchen: Drinks list

Drinks list for Willow Event Kitchen. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Willow Event Kitchen: Daily specials insert

Daily specials insert for Willow Event Kitchen. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Willow Event Kitchen: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Willow Event Kitchen. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Willow Event Kitchen: Two portion buffet package

Two portion buffet package for Willow Event Kitchen. A fixed price page at 35.00 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 39.00 CAD, so the page states a saving of 4.00 CAD. Plate cost for the bundle is 3.20 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Willow Event Kitchen: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Willow Event Kitchen. Intentionally wrong. MENU-02 Vegetarian buffet portion is printed at 19.00 CAD where plate-costs.csv carries 18.00 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Willow Event Kitchen: Menu folder guide

Menu folder guide for Willow Event Kitchen. A 78 line guide naming every one of the 18 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Harbour Kitchen Group: Printed menu

Printed menu for Harbour Kitchen Group. A one page food menu with 2 sections (Burgers, Sides and salads) and 4 dishes, prices right aligned in CAD and an allergen number after every dish. First page text begins "Harbour Kitchen Group". Every price is the menu_price_cad in plate-costs.csv and every allergen number is a Y column in allergen-matrix.csv.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Harbour Kitchen Group: Printed menu as a Word document

Printed menu as a Word document for Harbour Kitchen Group. The same 4 dishes and 2 sections as printed-menu.pdf, laid out as 2 two column Word tables with the price cell right aligned, so the identical layout can be read through a different parser. Core properties are stamped to 2026-09-08 and the package timestamps are fixed, so two runs produce identical bytes.

File: DOCX · Restaurant Menus
Use case: Data importConversion testing· Conversion set

Harbour Kitchen Group: Allergen menu

Allergen menu for Harbour Kitchen Group. A landscape page carrying 4 dishes against the 14 declarable allergens, Y for declared and a hyphen for not declared, with a second table naming the ingredient behind every Y. The grid reproduces allergen-matrix.csv in the costing folder cell for cell.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Harbour Kitchen Group: Drinks list

Drinks list for Harbour Kitchen Group. A one page list with 4 lines by the glass and 4 by the bottle. Where a drink is sold both ways the glass price is the bottle price divided by 5 pours and rounded up to the next 0.25, which the page states. Drinks sit outside the shared ingredient costing study, so no plate cost is claimed for any of them.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Conversion set

Harbour Kitchen Group: Daily specials insert

Daily specials insert for Harbour Kitchen Group. A dated single page for service on 2026-08-28, inside the costing period 2026-08-20 to 2026-09-02. 2 dishes from the printed menu at 85 percent of the menu price rounded to the nearest 0.05, with the menu price and the saving shown beside each.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing· Paired fixture

Harbour Kitchen Group: Daily specials insert dated outside the period

Daily specials insert dated outside the period for Harbour Kitchen Group. Intentionally wrong. The same page as daily-specials-insert.pdf with one change: the service date reads 2026-10-14, which is 42 days after the costing period ends on 2026-09-02. Every price on the page is still correct, so only the date can catch it.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Harbour Kitchen Group: Burger and fries set

Burger and fries set for Harbour Kitchen Group. A fixed price page at 26.50 CAD covering 2 dishes that are already on the printed menu. The same items ordered separately come to 30.00 CAD, so the page states a saving of 3.50 CAD. Plate cost for the bundle is 3.87 CAD.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Harbour Kitchen Group: Children's plates

Children's plates for Harbour Kitchen Group. A one page children's menu: the same 4 dishes as smaller portions at 60 percent of the menu price, rounded to the nearest 0.05. The prices are 11.10, 11.70, 6.90, 7.20 CAD, and every one already lands on a five cent step, so no row on the page is rounded.

File: PDF · Restaurant Menus · 1 page
Use case: Data importOCR testing

Harbour Kitchen Group: Printed menu with a price the costing denies

Printed menu with a price the costing denies for Harbour Kitchen Group. Intentionally wrong. MENU-02 Chicken burger is printed at 20.50 CAD where plate-costs.csv carries 19.50 CAD, a difference of 1.00. The printed figure is the proposed_price in the shared menu_price_changes table, effective 2026-09-15, so this is the shape a menu takes when it is reprinted early. Every other price matches printed-menu.pdf.

File: PDF · Restaurant Menus · 1 page
Use case: Data importError handling· Paired fixture

Harbour Kitchen Group: Menu folder guide

Menu folder guide for Harbour Kitchen Group. A 80 line guide naming every one of the 19 files in this folder, the two costing files each price was read from, the rule behind every derived price, and all 5 deliberate defects with the figure on both sides of each disagreement.

File: MD · Restaurant Menus · UTF-8
Use case: Data import

Tern Client Services: Master services agreement (PDF)

Master services agreement (PDF) for Tern Client Services. 16 numbered clauses and 35 sub-clauses between Tern Client Services and Tern Events, effective 5 January 2026 for 24 months to 4 January 2028, with a 60 day non-renewal notice that expires on 5 November 2027. Clause 3.1 sets the rate at 100.00 USD per hour, which is the rate the crm-services timesheet export bills at, and clause 10.2 caps liability at 9,000.00 USD, the sum of the three statement-of-work values. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 3 pages
Use case: Data import· Paired fixture

Tern Client Services: Master services agreement (DOCX)

Master services agreement (DOCX) for Tern Client Services. 16 numbered clauses and 35 sub-clauses between Tern Client Services and Tern Events, effective 5 January 2026 for 24 months to 4 January 2028, with a 60 day non-renewal notice that expires on 5 November 2027. Clause 3.1 sets the rate at 100.00 USD per hour, which is the rate the crm-services timesheet export bills at, and clause 10.2 caps liability at 9,000.00 USD, the sum of the three statement-of-work values. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Tern Client Services: Mutual non-disclosure agreement (PDF)

Mutual non-disclosure agreement (PDF) for Tern Client Services. A mutual NDA in 8 clauses and 10 sub-clauses, effective 10 November 2025 and running 36 months to 9 November 2028. It predates the master services agreement by 56 days, which is why clause 7.3 of MSA-2026-01 keeps it alive alongside. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 2 pages
Use case: Data import· Paired fixture

Tern Client Services: Mutual non-disclosure agreement (DOCX)

Mutual non-disclosure agreement (DOCX) for Tern Client Services. A mutual NDA in 8 clauses and 10 sub-clauses, effective 10 November 2025 and running 36 months to 9 November 2028. It predates the master services agreement by 56 days, which is why clause 7.3 of MSA-2026-01 keeps it alive alongside. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Tern Client Services: Statement of work SOW-2026-01 (PDF)

Statement of work SOW-2026-01 (PDF) for Tern Client Services. A statement of work for PROJECT-1 Website refresh under MSA-2026-01, with three deliverables whose allocations of 400.00, 900.00 and 700.00 USD sum to the 2,000.00 USD not-to-exceed value, each with a testable acceptance criterion. Fees recorded to date are 1,600.00 USD, which is 16 hours at 100.00 USD and the exact amount of invoice SVCINV-1. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Paired fixture

Tern Client Services: Statement of work SOW-2026-01 (DOCX)

Statement of work SOW-2026-01 (DOCX) for Tern Client Services. A statement of work for PROJECT-1 Website refresh under MSA-2026-01, with three deliverables whose allocations of 400.00, 900.00 and 700.00 USD sum to the 2,000.00 USD not-to-exceed value, each with a testable acceptance criterion. Fees recorded to date are 1,600.00 USD, which is 16 hours at 100.00 USD and the exact amount of invoice SVCINV-1. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Tern Client Services: Statement of work SOW-2026-03

Statement of work SOW-2026-03 for Tern Client Services. A statement of work for PROJECT-3 Booking setup under MSA-2026-01, with three deliverables whose allocations of 800.00, 2200.00 and 1000.00 USD sum to the 4,000.00 USD not-to-exceed value, each with a testable acceptance criterion. Fees recorded to date are 3,200.00 USD, which is 32 hours at 100.00 USD and the exact amount of invoice SVCINV-3.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Conversion set

Tern Client Services: Statement of work SOW-2026-02

Statement of work SOW-2026-02 for Tern Client Services. The second statement of work under the same master agreement. Its three deliverable allocations of 600.00, 1500.00 and 900.00 USD sum to the 3,000.00 USD not-to-exceed value, and the 2,400.00 USD recorded to date is 24 hours at 100.00 USD, the exact amount of invoice SVCINV-2.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Conversion set

Tern Client Services: Independent contractor agreement (PDF)

Independent contractor agreement (PDF) for Tern Client Services. An independent contractor agreement with Sample specialist 1, running 1 July 2026 to 30 June 2027 at 60.00 USD per recorded hour. The contractor has recorded 16 hours on PROJECT-1, so fees payable to date are 960.00 USD. That number is the box 1 figure on the matching 1099-NEC slip in the tax set, and it is deliberately not the 1,600.00 USD the same hours were billed to the client at. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 2 pages
Use case: Data import· Paired fixture

Tern Client Services: Independent contractor agreement (DOCX)

Independent contractor agreement (DOCX) for Tern Client Services. An independent contractor agreement with Sample specialist 1, running 1 July 2026 to 30 June 2027 at 60.00 USD per recorded hour. The contractor has recorded 16 hours on PROJECT-1, so fees payable to date are 960.00 USD. That number is the box 1 figure on the matching 1099-NEC slip in the tax set, and it is deliberately not the 1,600.00 USD the same hours were billed to the client at. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Cobalt Operations Team: Employment offer letter (PDF)

Employment offer letter (PDF) for Cobalt Operations Team. An offer letter for Team member 5 at 28.00 USD per paid hour, starting 10 August 2026. The shift table reproduces the six rostered days the people-operations model holds for EMP-05, whose paid hours sum to 42 and whose base pay sums to 1,176.00 USD, the same number the wave-one payroll register pays. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 2 pages
Use case: Data import· Paired fixture

Cobalt Operations Team: Employment offer letter (DOCX)

Employment offer letter (DOCX) for Cobalt Operations Team. An offer letter for Team member 5 at 28.00 USD per paid hour, starting 10 August 2026. The shift table reproduces the six rostered days the people-operations model holds for EMP-05, whose paid hours sum to 42 and whose base pay sums to 1,176.00 USD, the same number the wave-one payroll register pays. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Cobalt Operations Team: Termination letter (PDF)

Termination letter (PDF) for Cobalt Operations Team. A termination letter for Team member 7, last day 15 September 2026. The final payment table pays one rostered cycle of 42 hours at 32.00 USD, which is 1,344.00 USD and the exact base pay the people-operations model records for EMP-07, plus the same amount again as pay in lieu of notice, giving 2,688.00 USD. Accrued leave is zero because the leave register holds no request for EMP-07. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Paired fixture

Cobalt Operations Team: Termination letter (DOCX)

Termination letter (DOCX) for Cobalt Operations Team. A termination letter for Team member 7, last day 15 September 2026. The final payment table pays one rostered cycle of 42 hours at 32.00 USD, which is 1,344.00 USD and the exact base pay the people-operations model records for EMP-07, plus the same amount again as pay in lieu of notice, giving 2,688.00 USD. Accrued leave is zero because the leave register holds no request for EMP-07. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Tern Client Services: Amendment to the master services agreement (PDF)

Amendment to the master services agreement (PDF) for Tern Client Services. A two-clause amendment effective 1 September 2026 that raises the expense cap in clause 4.1 from 250.00 to 400.00 USD and extends the acceptance window in clause 5.1 from ten to fifteen business days for SOW-2026-03 only. It deliberately leaves the original agreement wording intact, so the two documents state different caps and only the amendment date tells a reader which applies. The DOCX twin in the same directory carries the identical text.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Paired fixture

Tern Client Services: Amendment to the master services agreement (DOCX)

Amendment to the master services agreement (DOCX) for Tern Client Services. A two-clause amendment effective 1 September 2026 that raises the expense cap in clause 4.1 from 250.00 to 400.00 USD and extends the acceptance window in clause 5.1 from ten to fifteen business days for SOW-2026-03 only. It deliberately leaves the original agreement wording intact, so the two documents state different caps and only the amendment date tells a reader which applies. The PDF twin in the same directory carries the identical text.

File: DOCX · Contracts Agreements
Use case: Data import· Paired fixture

Tern Client Services: Deliverable acceptance certificate

Deliverable acceptance certificate for Tern Client Services. An acceptance certificate under MSA-2026-01 clause 5.2 accepting D1 and D2 of SOW-2026-01, an allocation of 1,300.00 USD, and leaving D3 at 700.00 USD outstanding. The two figures sum to the 2,000.00 USD not-to-exceed value on the statement of work.

File: PDF · Contracts Agreements · 1 page
Use case: Data import· Conversion set

Tern Client Services: Contract register workbook

Contract register workbook for Tern Client Services. A two-sheet workbook: Contracts holds the 11 register rows and Rate card holds the 5 priced terms, including both expense caps with their effective-from and effective-to dates so the amendment is visible as a date range rather than a contradiction.

File: XLSX · Contracts Agreements
Use case: Data import· Conversion set

Tern Client Services: contracts document set README

Document set README for Tern Client Services. 30 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Contracts Agreements
Use case: Data import

Pine Property Services: Policy schedule with endorsements (PDF)

Policy schedule with endorsements (PDF) for Pine Property Services. A policy schedule for POL-2026-GL-0001 covering 6 locations at 2,700,000.00 USD total insured value and 4 vehicles, with 4 endorsements. The property premium is the total insured value at 0.85 per 1000, which is 2,295.00 USD; base premium 7,040.00 plus endorsements 590.00 gives a subtotal of 7,630.00, and fees of 115.00 plus tax at 3.5 percent brings the total payable to 8,016.08 USD. The DOCX twin in the same directory carries the identical text.

File: PDF · Insurance Documents · 2 pages
Use case: Data import· Paired fixture

Pine Property Services: Policy schedule with endorsements (DOCX)

Policy schedule with endorsements (DOCX) for Pine Property Services. A policy schedule for POL-2026-GL-0001 covering 6 locations at 2,700,000.00 USD total insured value and 4 vehicles, with 4 endorsements. The property premium is the total insured value at 0.85 per 1000, which is 2,295.00 USD; base premium 7,040.00 plus endorsements 590.00 gives a subtotal of 7,630.00, and fees of 115.00 plus tax at 3.5 percent brings the total payable to 8,016.08 USD. The PDF twin in the same directory carries the identical text.

File: DOCX · Insurance Documents
Use case: Data import· Paired fixture

Pine Property Services: Policy workbook

Policy workbook for Pine Property Services. A six-sheet workbook holding the coverages, endorsements, premium chain, instalments, locations and vehicles that the policy schedule PDF prints. Sheet order matches the order the schedule presents them in, and every figure is the same value as the matching CSV.

File: XLSX · Insurance Documents
Use case: Data import· Conversion set

Pine Property Services: Certificate of insurance (PDF)

Certificate of insurance (PDF) for Pine Property Services. A certificate of insurance issued 8 September 2026 for policy POL-2026-GL-0001, certifying cover from 1 April 2026 to 31 March 2027 to the manager of PROP-3. The issue date precedes the expiry by 204 days, which is the ordering a valid certificate has and the ordering the deliberately broken certificate in this directory does not. The DOCX twin in the same directory carries the identical text.

File: PDF · Insurance Documents · 1 page
Use case: Data import· Paired fixture

Pine Property Services: Certificate of insurance (DOCX)

Certificate of insurance (DOCX) for Pine Property Services. A certificate of insurance issued 8 September 2026 for policy POL-2026-GL-0001, certifying cover from 1 April 2026 to 31 March 2027 to the manager of PROP-3. The issue date precedes the expiry by 204 days, which is the ordering a valid certificate has and the ordering the deliberately broken certificate in this directory does not. The PDF twin in the same directory carries the identical text.

File: DOCX · Insurance Documents
Use case: Data import· Paired fixture

Pine Property Services: Certificate of insurance whose expiry precedes its issue date

Certificate of insurance whose expiry precedes its issue date for Pine Property Services. A certificate issued 8 September 2026 that certifies a policy period ending 31 March 2026, which is 161 days earlier. The document is otherwise a well formed certificate with the same layout, the same limits and the same endorsement wording as the valid one, so only the date comparison catches it. Days of cover remaining reads -161.

File: PDF · Insurance Documents · 1 page
Use case: Data importError handling· Conversion set

Pine Property Services: First notice of loss claim form (PDF)

First notice of loss claim form (PDF) for Pine Property Services. A claim form for FNOL-2026-0003, reporting an escape of water at PROP-6 on 6 August 2026, the same date and property the trades-property model records work order WO-06 against, and the one work order in that model whose completion inspection result is follow-up rather than pass. The three estimate lines of 14,200.00, 2,600.00 and 1,600.00 USD sum to the 18,400.00 USD estimated loss the settlement statement then works from. The DOCX twin in the same directory carries the identical text.

File: PDF · Insurance Documents · 1 page
Use case: Data import· Paired fixture

Pine Property Services: First notice of loss claim form (DOCX)

First notice of loss claim form (DOCX) for Pine Property Services. A claim form for FNOL-2026-0003, reporting an escape of water at PROP-6 on 6 August 2026, the same date and property the trades-property model records work order WO-06 against, and the one work order in that model whose completion inspection result is follow-up rather than pass. The three estimate lines of 14,200.00, 2,600.00 and 1,600.00 USD sum to the 18,400.00 USD estimated loss the settlement statement then works from. The PDF twin in the same directory carries the identical text.

File: DOCX · Insurance Documents
Use case: Data import· Paired fixture

Pine Property Services: Claim settlement statement

Claim settlement statement for Pine Property Services. A seven-line settlement calculation with a running balance. Assessed loss 18,400.00 USD, less 15.0 percent recoverable depreciation of 2,760.00, gives an actual cash value of 15,640.00; less the 1,000.00 USD deductible the net first payment is 14,640.00 USD. Releasing the held depreciation later brings total recovery to 17,400.00 USD, which is the assessed loss less the deductible.

File: PDF · Insurance Documents · 1 page
Use case: Data import· Conversion set

Pine Property Services: Insurance renewal application (PDF)

Insurance renewal application (PDF) for Pine Property Services. A renewal application for the 2027 policy year. It asks for the same limits the expiring policy carries and declares the same loss history the insurer own loss run holds: 3 claims and 20,650.00 USD incurred. The declaration says the two must agree, so the pair is a ready-made consistency test. The DOCX twin in the same directory carries the identical text.

File: PDF · Insurance Documents · 1 page
Use case: Data import· Paired fixture

Pine Property Services: Insurance renewal application (DOCX)

Insurance renewal application (DOCX) for Pine Property Services. A renewal application for the 2027 policy year. It asks for the same limits the expiring policy carries and declares the same loss history the insurer own loss run holds: 3 claims and 20,650.00 USD incurred. The declaration says the two must agree, so the pair is a ready-made consistency test. The PDF twin in the same directory carries the identical text.

File: DOCX · Insurance Documents
Use case: Data import· Paired fixture

Pine Property Services: insurance document set README

Document set README for Pine Property Services. 27 files, 2 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Insurance Documents
Use case: Data import

Juniper Workspace Cloud: Articles of incorporation (PDF)

Articles of incorporation (PDF) for Juniper Workspace Cloud. The constitution of Juniper Workspace Cloud Limited: 8 clauses covering authorised capital of 1,000,000 ordinary shares of 0.01 USD, allotment and transfer procedure, meetings, directors and the statutory registers. The subscriber table records the founding allotment of 540,000 shares for 5,400.00 USD, which is the opening row of the register of members. The DOCX twin in the same directory carries the identical text.

File: PDF · Corporate Records · 2 pages
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Articles of incorporation (DOCX)

Articles of incorporation (DOCX) for Juniper Workspace Cloud. The constitution of Juniper Workspace Cloud Limited: 8 clauses covering authorised capital of 1,000,000 ordinary shares of 0.01 USD, allotment and transfer procedure, meetings, directors and the statutory registers. The subscriber table records the founding allotment of 540,000 shares for 5,400.00 USD, which is the opening row of the register of members. The PDF twin in the same directory carries the identical text.

File: DOCX · Corporate Records
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Certificate of incorporation

Certificate of incorporation for Juniper Workspace Cloud. A one-page certificate stating that Juniper Workspace Cloud Limited was incorporated on 14 February 2024 under number FC-00847213. Every other document in this set repeats that number and that date, so it is the anchor a reader can check the rest of the set against.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Share certificate SC-001

Share certificate SC-001 for Juniper Workspace Cloud. A share certificate for Fictional founder A covering 300,000 ordinary shares of 0.01 USD, a nominal value of 3,000.00 USD and 50.0000 percent of the 600,000 shares in issue.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Share certificate SC-004 (PDF)

Share certificate SC-004 (PDF) for Juniper Workspace Cloud. A share certificate for Fictional investor D covering 60,000 ordinary shares of 0.01 USD, a nominal value of 600.00 USD and 10.0000 percent of the 600,000 shares in issue. The DOCX twin in the same directory carries the identical text.

File: PDF · Corporate Records · 1 page
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Share certificate SC-004 (DOCX)

Share certificate SC-004 (DOCX) for Juniper Workspace Cloud. A share certificate for Fictional investor D covering 60,000 ordinary shares of 0.01 USD, a nominal value of 600.00 USD and 10.0000 percent of the 600,000 shares in issue. The PDF twin in the same directory carries the identical text.

File: DOCX · Corporate Records
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Share certificate SC-005

Share certificate SC-005 for Juniper Workspace Cloud. A share certificate for Fictional founder B covering 180,000 ordinary shares of 0.01 USD, a nominal value of 1,800.00 USD and 30.0000 percent of the 600,000 shares in issue. It replaces SC-002, which was cancelled on 2026-07-06 when the 18,000 share transfer was registered.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Share certificate SC-006

Share certificate SC-006 for Juniper Workspace Cloud. A share certificate for Fictional founder C covering 60,000 ordinary shares of 0.01 USD, a nominal value of 600.00 USD and 10.0000 percent of the 600,000 shares in issue. It replaces SC-003, which was cancelled on 2026-07-06 when the 18,000 share transfer was registered.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Register of members workbook

Register of members workbook for Juniper Workspace Cloud. A two-sheet workbook holding the register and the capitalisation table. The register sheet has no total row and the cap table sheet does, so a reader that assumes the last row of a sheet is data on one and a total on the other gets both wrong.

File: XLSX · Corporate Records
Use case: Data import· Conversion set

Juniper Workspace Cloud: Board minutes, allotment meeting (PDF)

Board minutes, allotment meeting (PDF) for Juniper Workspace Cloud. Minutes of the board meeting of 18 May 2026 recording one resignation, one appointment and the allotment of 60,000 shares at 0.25 USD. The allotment table splits the 15,000.00 USD consideration into 600.00 of nominal and 14,400.00 of premium and states 600,000 shares in issue afterwards, which is what the register of members, the allotment return and the annual return all hold. The DOCX twin in the same directory carries the identical text.

File: PDF · Corporate Records · 1 page
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Board minutes, allotment meeting (DOCX)

Board minutes, allotment meeting (DOCX) for Juniper Workspace Cloud. Minutes of the board meeting of 18 May 2026 recording one resignation, one appointment and the allotment of 60,000 shares at 0.25 USD. The allotment table splits the 15,000.00 USD consideration into 600.00 of nominal and 14,400.00 of premium and states 600,000 shares in issue afterwards, which is what the register of members, the allotment return and the annual return all hold. The PDF twin in the same directory carries the identical text.

File: DOCX · Corporate Records
Use case: Data import· Paired fixture

Juniper Workspace Cloud: Board minutes, trading and annual return meeting

Board minutes, trading and annual return meeting for Juniper Workspace Cloud. Minutes of 7 September 2026 reviewing the 12 invoices in the saas-subscriptions ledger. Invoiced 668.00 USD, received 649.00, outstanding 19.00 on INV-10, and active recurring revenue 235.00 USD per month across the five accounts that are still active. Every one of those figures is the model own arithmetic, not a restatement.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Written board resolution approving a share transfer

Written board resolution approving a share transfer for Juniper Workspace Cloud. The resolution that registers the 18,000 share transfer on 6 July 2026, cancels SC-002 and SC-003 and issues SC-005 and SC-006. It states in terms that the transfer leaves the 600,000 shares in issue and the 20,400.00 USD paid up unchanged and only moves 180.00 USD of paid-up capital between two members, which is the trap a reader falls into if it adds the shares column of shareholding-history.csv.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Written resolution of members authorising the allotment

Written resolution of members authorising the allotment for Juniper Workspace Cloud. The members resolution that authorised the 60,000 share allotment, passed on 11 May 2026 by 462,000 of the 540,000 voting shares then in issue, which is 85.5556 percent. The voting table shows the third founder as no response rather than against, so the percentages in favour and against do not sum to 100.

File: PDF · Corporate Records · 1 page
Use case: Data import· Conversion set

Juniper Workspace Cloud: Annual return

Annual return for Juniper Workspace Cloud. A five-part annual return made up to 2026-09-08: 600,000 ordinary shares in issue with 6,000.00 USD of called-up capital and 14,400.00 USD of share premium, 4 members holding 100.0000 percent between them, 4 officers in office, 2 persons with significant control and 2 charges of which 1 is outstanding. Every figure is reproduced by a register in the same directory.

File: PDF · Corporate Records · 2 pages
Use case: Data import· Paired fixture

Juniper Workspace Cloud: corporate document set README

Document set README for Juniper Workspace Cloud. 30 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Corporate Records
Use case: Data import

Fieldnote Supply Shop: Sales tax filing worksheet workbook

Sales tax filing worksheet workbook for Fieldnote Supply Shop. The worksheet as a single 20 column sheet. The permit numbers are text values with embedded hyphens and leading letters, so they survive a spreadsheet import that would otherwise reformat a bare numeric code, and the two empty permit cells stay empty rather than becoming zero.

File: XLSX · Tax Filings · 6 rows
Use case: Data import· Conversion set

Fieldnote Supply Shop: Sales tax return for California

Sales tax return for California for Fieldnote Supply Shop. An eight-line California return for the 2026-08-01 to 2026-08-31 period. Net taxable sales 46.00 USD at 8.750 percent gives 6.12 collected; less 2.10 refunded the net tax due is 4.02, and after a vendor collection allowance of 0.03 the remittance is 3.99 USD. Every line number is the same line the worksheet column carries.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Fieldnote Supply Shop: Sales tax return for New York

Sales tax return for New York for Fieldnote Supply Shop. An eight-line New York return for the 2026-08-01 to 2026-08-31 period. Net taxable sales 80.00 USD at 8.875 percent gives 8.52 collected; less 1.42 refunded the net tax due is 7.10, and after a vendor collection allowance of 0.00 the remittance is 7.10 USD. Every line number is the same line the worksheet column carries.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Harbour Kitchen Group: GST/HST return (PDF)

GST/HST return (PDF) for Harbour Kitchen Group. A six-line Canadian GST/HST return in CAD for Harbour Kitchen Group. Line 101 is 26,214.00 CAD of net sales, line 105 is 13 percent of it at 3,407.82, line 108 claims 255.25 of input tax credits on the 1,963.44 CAD of purchases that fall inside the reporting period, and line 109 is 3,152.57 CAD of net tax. Every figure is computed from the restaurant model rather than restated. The DOCX twin in the same directory carries the identical text.

File: PDF · Tax Filings · 1 page
Use case: Data import· Paired fixture

Harbour Kitchen Group: GST/HST return (DOCX)

GST/HST return (DOCX) for Harbour Kitchen Group. A six-line Canadian GST/HST return in CAD for Harbour Kitchen Group. Line 101 is 26,214.00 CAD of net sales, line 105 is 13 percent of it at 3,407.82, line 108 claims 255.25 of input tax credits on the 1,963.44 CAD of purchases that fall inside the reporting period, and line 109 is 3,152.57 CAD of net tax. Every figure is computed from the restaurant model rather than restated. The PDF twin in the same directory carries the identical text.

File: DOCX · Tax Filings
Use case: Data import· Paired fixture

Tern Client Services: Payee certification, W-9 shaped (PDF)

Payee certification, W-9 shaped (PDF) for Tern Client Services. A W-9 shaped payee certification for Sample specialist 1, engaged under CTR-2026-01 in the contracts set. It certifies United States person status, which is why this payee receives a 1099-NEC shaped slip for 960.00 USD while the payee who files the W-8BEN shaped certificate does not. The DOCX twin in the same directory carries the identical text.

File: PDF · Tax Filings · 1 page
Use case: Data import· Paired fixture

Tern Client Services: Payee certification, W-9 shaped (DOCX)

Payee certification, W-9 shaped (DOCX) for Tern Client Services. A W-9 shaped payee certification for Sample specialist 1, engaged under CTR-2026-01 in the contracts set. It certifies United States person status, which is why this payee receives a 1099-NEC shaped slip for 960.00 USD while the payee who files the W-8BEN shaped certificate does not. The PDF twin in the same directory carries the identical text.

File: DOCX · Tax Filings
Use case: Data import· Paired fixture

W-8BEN shaped owner certification (PDF): Tern Client Services

Beneficial owner certification, W-8BEN shaped (PDF) for Tern Client Services. A W-8BEN shaped certification for Sample specialist 2, a payee outside the United States. It removes 1,440.00 USD of the 4,320.00 USD of contractor payments from the 1099-NEC population, which is why the 1099 recipient list totals 2,880.00 rather than the full ledger. The DOCX twin in the same directory carries the identical text.

File: PDF · Tax Filings · 1 page
Use case: Data import· Paired fixture

W-8BEN shaped owner certification (DOCX): Tern Client Services

Beneficial owner certification, W-8BEN shaped (DOCX) for Tern Client Services. A W-8BEN shaped certification for Sample specialist 2, a payee outside the United States. It removes 1,440.00 USD of the 4,320.00 USD of contractor payments from the 1099-NEC population, which is why the 1099 recipient list totals 2,880.00 rather than the full ledger. The PDF twin in the same directory carries the identical text.

File: DOCX · Tax Filings
Use case: Data import· Paired fixture

Fieldnote Supply Shop: Information slip, 1099-NEC shaped, WRK-01

Information slip, 1099-NEC shaped, WRK-01 for Fieldnote Supply Shop. A 1099-NEC shaped slip reporting 960.00 USD of nonemployee compensation to Sample specialist 1, being 16 recorded hours at 60.00 USD. Box 4 and box 5 are 0.00 because a payee certification is on file, and box 6 is empty rather than zero because there is no state identification number to report.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Fieldnote Supply Shop: Information slip, 1099-NEC shaped, WRK-03

Information slip, 1099-NEC shaped, WRK-03 for Fieldnote Supply Shop. A 1099-NEC shaped slip reporting 1,920.00 USD of nonemployee compensation to Sample specialist 3, being 32 recorded hours at 60.00 USD. Box 4 and box 5 are 0.00 because a payee certification is on file, and box 6 is empty rather than zero because there is no state identification number to report.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Tern Client Services: Information statement, 1042-S shaped

Information statement, 1042-S shaped for Tern Client Services. A 1042-S shaped statement reporting 1,440.00 USD of gross income to the payee who filed the W-8BEN shaped certificate, with a zero rate, exemption code 03 and no withholding because the services were performed outside the United States. It is the file that closes the gap between the 1099-NEC list and the contractor ledger.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Harbour Kitchen Group: Information slip, T4 shaped (PDF)

Information slip, T4 shaped (PDF) for Harbour Kitchen Group. A T4 shaped slip for Fictional colleague 3 covering the 2026-08-20 to 2026-09-02 rostered period. Box 14 is 1,100.00 CAD, which is the base pay the restaurant model records for EMP-03 across 50 hours; boxes 16, 18 and 22 are 5.95, 1.66 and 15 percent of it, giving 65.45, 18.26 and 165.00, and net pay is 851.29 CAD. The DOCX twin in the same directory carries the identical text.

File: PDF · Tax Filings · 1 page
Use case: Data import· Paired fixture

Harbour Kitchen Group: Information slip, T4 shaped (DOCX)

Information slip, T4 shaped (DOCX) for Harbour Kitchen Group. A T4 shaped slip for Fictional colleague 3 covering the 2026-08-20 to 2026-09-02 rostered period. Box 14 is 1,100.00 CAD, which is the base pay the restaurant model records for EMP-03 across 50 hours; boxes 16, 18 and 22 are 5.95, 1.66 and 15 percent of it, giving 65.45, 18.26 and 165.00, and net pay is 851.29 CAD. The PDF twin in the same directory carries the identical text.

File: DOCX · Tax Filings
Use case: Data import· Paired fixture

Harbour Kitchen Group: T4 shaped summary

T4 shaped summary for Harbour Kitchen Group. The employer summary over the 8 slips: 9,190.00 CAD of employment income, 546.82 of employee contributions matched by 546.82 from the employer, 152.56 of employee premiums with 213.58 from the employer at 1.4 times, and 1,378.50 of income tax, giving a remittance of 2,838.28 CAD.

File: PDF · Tax Filings · 1 page
Use case: Data import· Conversion set

Fieldnote Supply Shop: tax document set README

Document set README for Fieldnote Supply Shop. 34 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Tax Filings
Use case: Data import

Pine Assembly Workshop: Term loan agreement (PDF)

Term loan agreement (PDF) for Pine Assembly Workshop. A 48,000.00 USD term loan at 6.90 percent over 36 months. Clause 3.1 states the level instalment of 1,479.91 USD and clause 3.2 states in words why the final instalment is 1,479.81, which is 0.10 less: 36 level instalments would repay 0.10 USD more than is owed. Total interest is 5,276.66 and total repayments 53,276.66 USD. The DOCX twin in the same directory carries the identical text.

File: PDF · Banking Credit · 2 pages
Use case: Data import· Paired fixture

Pine Assembly Workshop: Term loan agreement (DOCX)

Term loan agreement (DOCX) for Pine Assembly Workshop. A 48,000.00 USD term loan at 6.90 percent over 36 months. Clause 3.1 states the level instalment of 1,479.91 USD and clause 3.2 states in words why the final instalment is 1,479.81, which is 0.10 less: 36 level instalments would repay 0.10 USD more than is owed. Total interest is 5,276.66 and total repayments 53,276.66 USD. The PDF twin in the same directory carries the identical text.

File: DOCX · Banking Credit
Use case: Data import· Paired fixture

Pine Assembly Workshop: Loan amortisation workbook

Loan amortisation workbook for Pine Assembly Workshop. A two-sheet workbook: the 36 schedule rows and a summary sheet holding the inputs and the four control totals. The monthly rate is written to eight decimal places as 0.00575000 so the level payment can be reproduced; at the four places a spreadsheet usually shows, the recomputed payment differs.

File: XLSX · Banking Credit · 36 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Covenant compliance certificate

Covenant compliance certificate for Pine Assembly Workshop. The quarterly certificate clause 6.2 of the facility requires. All four covenants pass: cash of 10,236.00 USD against a 5,000.00 minimum, interest cover of 7.48 times against 4.00, operating expenditure of 2,064.00 against a 4,200.00 budget, and receivables outstanding of 800.00 against a 1,000.00 cap. The cash, expenditure and receivables figures are the accounting model own closing numbers.

File: PDF · Banking Credit · 1 page
Use case: Data import· Conversion set

Alder Books Reconciliation: Credit application (PDF)

Credit application (PDF) for Alder Books Reconciliation. An unsecured working capital application for 15,000.00 USD. Every figure in the financial summary names the wave-one accounting file and column it comes from, so the whole table is checkable: closing cash 10,236.00, invoiced 8,100.00, received 7,300.00, outstanding 800.00 and expenditure 2,064.00 USD. The DOCX twin in the same directory carries the identical text.

File: PDF · Banking Credit · 1 page
Use case: Data import· Paired fixture

Alder Books Reconciliation: Credit application (DOCX)

Credit application (DOCX) for Alder Books Reconciliation. An unsecured working capital application for 15,000.00 USD. Every figure in the financial summary names the wave-one accounting file and column it comes from, so the whole table is checkable: closing cash 10,236.00, invoiced 8,100.00, received 7,300.00, outstanding 800.00 and expenditure 2,064.00 USD. The PDF twin in the same directory carries the identical text.

File: DOCX · Banking Credit
Use case: Data import· Paired fixture

Harbour Kitchen Group: Direct debit mandate (PDF)

Direct debit mandate (PDF) for Harbour Kitchen Group. A recurring pre-authorised debit mandate from Harbour Kitchen Group to Alder Wholesale, signed 8 July 2026. The collections it authorises are the 8 weekly supplier invoices the restaurant purchase ledger already holds for that supplier, 4,077.58 CAD in total, each collected 5 days after its invoice date. The DOCX twin in the same directory carries the identical text.

File: PDF · Banking Credit · 1 page
Use case: Data import· Paired fixture

Harbour Kitchen Group: Direct debit mandate (DOCX)

Direct debit mandate (DOCX) for Harbour Kitchen Group. A recurring pre-authorised debit mandate from Harbour Kitchen Group to Alder Wholesale, signed 8 July 2026. The collections it authorises are the 8 weekly supplier invoices the restaurant purchase ledger already holds for that supplier, 4,077.58 CAD in total, each collected 5 days after its invoice date. The PDF twin in the same directory carries the identical text.

File: DOCX · Banking Credit
Use case: Data import· Paired fixture

Fieldnote Supply Shop: Chargeback representment packet

Chargeback representment packet for Fieldnote Supply Shop. A two-page representment packet for CB-2026-0001, the case the wave-one ecommerce chargeback register still shows as open. The transaction table reproduces both order lines of ORD-006, 6 units totalling 135.00 USD captured, 16.20 USD of tax and 151.20 USD charged to the cardholder, and states the seller net exposure as 150.00 USD, being the capture plus a 15.00 USD case fee. The evidence index and the timeline are printed on page 2 and shipped as CSVs alongside.

File: PDF · Banking Credit · 2 pages
Use case: Data import· Conversion set

Alder Books Reconciliation: banking document set README

Document set README for Alder Books Reconciliation. 25 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Banking Credit
Use case: Data import

Juniper Fitness and Clinic Administration: Superbill (PDF)

Superbill (PDF) for Juniper Fitness and Clinic Administration. An itemised superbill for ENC-0006, the encounter with two service lines. Charges are 120.00 and 85.00 USD totalling 205.00, and the document states the full adjudication that follows: 164.00 allowed, 41.00 written off, 131.20 paid and 32.80 left with the patient. The DOCX twin in the same directory carries the identical text.

File: PDF · Healthcare Claims · 1 page
Use case: Data import· Paired fixture

Juniper Fitness and Clinic Administration: Superbill (DOCX)

Superbill (DOCX) for Juniper Fitness and Clinic Administration. An itemised superbill for ENC-0006, the encounter with two service lines. Charges are 120.00 and 85.00 USD totalling 205.00, and the document states the full adjudication that follows: 164.00 allowed, 41.00 written off, 131.20 paid and 32.80 left with the patient. The PDF twin in the same directory carries the identical text.

File: DOCX · Healthcare Claims
Use case: Data import· Paired fixture

Sample Health Plan: Explanation of benefits (PDF)

Explanation of benefits (PDF) for Sample Health Plan. The member facing explanation of CLM-0006, matching the 835 remittance line for line. Charged 205.00 USD, 41.00 not covered under adjustment CO 45, 164.00 allowed, 131.20 paid by the plan and 32.80 owed by the member under adjustment PR 2. The document explains in words that the not covered amount can never be billed to the member. The DOCX twin in the same directory carries the identical text.

File: PDF · Healthcare Claims · 1 page
Use case: Data import· Paired fixture

Sample Health Plan: Explanation of benefits (DOCX)

Explanation of benefits (DOCX) for Sample Health Plan. The member facing explanation of CLM-0006, matching the 835 remittance line for line. Charged 205.00 USD, 41.00 not covered under adjustment CO 45, 164.00 allowed, 131.20 paid by the plan and 32.80 owed by the member under adjustment PR 2. The document explains in words that the not covered amount can never be billed to the member. The PDF twin in the same directory carries the identical text.

File: DOCX · Healthcare Claims
Use case: Data import· Paired fixture

Juniper Fitness and Clinic Administration: Patient statement

Patient statement for Juniper Fitness and Clinic Administration. The bill that follows the explanation of benefits: 6.40 USD due from Sample visitor 3 on claim CLM-0003, being 20 percent of the allowed amount. The statement says in words that the 8.00 USD contractual write-off is not billed and does not appear as due, which is the difference between this document and the explanation of benefits that precedes it.

File: PDF · Healthcare Claims · 1 page
Use case: Data import· Conversion set

Juniper Fitness and Clinic Administration: healthcare document set README

Document set README for Juniper Fitness and Clinic Administration. 27 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Healthcare Claims
Use case: Data import

Pine Property Services: Rent roll workbook

Rent roll workbook for Pine Property Services. A two-sheet workbook holding the rent roll and the area schedule. The two sheets carry the same six areas, so the building area check can be run within the workbook: both sum to 1200.00 sq m.

File: XLSX · Property Leasing · 6 rows
Use case: Data import· Conversion set

Pine Property Services: Commercial lease (PDF)

Commercial lease (PDF) for Pine Property Services. A ten year lease of U-02 from 1 April 2024 to 31 March 2034, with a tenant break at 31 March 2029 and a rent review the day after. Clause 3.1 states the rent as 195.00 sq m at 225.00 USD, which is 43,875.00 a year and 10,968.75 a quarter, and clause 4.1 fixes the service charge proportion at 16.2500 percent, the area of the demise over the lettable area. Clause 4.3 says in words that the common parts are excluded from the denominator, which is why the six proportions add to one hundred percent. The DOCX twin in the same directory carries the identical text.

File: PDF · Property Leasing · 2 pages
Use case: Data import· Paired fixture

Pine Property Services: Commercial lease (DOCX)

Commercial lease (DOCX) for Pine Property Services. A ten year lease of U-02 from 1 April 2024 to 31 March 2034, with a tenant break at 31 March 2029 and a rent review the day after. Clause 3.1 states the rent as 195.00 sq m at 225.00 USD, which is 43,875.00 a year and 10,968.75 a quarter, and clause 4.1 fixes the service charge proportion at 16.2500 percent, the area of the demise over the lettable area. Clause 4.3 says in words that the common parts are excluded from the denominator, which is why the six proportions add to one hundred percent. The PDF twin in the same directory carries the identical text.

File: DOCX · Property Leasing
Use case: Data import· Paired fixture

Pine Property Services: Service charge reconciliation workbook

Service charge reconciliation workbook for Pine Property Services. A three-sheet workbook: the reconciliation, the expenditure against budget by head of charge, and the budget apportionment. The three sheets close on each other, so the 102,476.00 USD total can be reached down two independent routes, by head of charge and by demise.

File: XLSX · Property Leasing
Use case: Data import· Conversion set

Pine Property Services: Service charge reconciliation statement

Service charge reconciliation statement for Pine Property Services. The statement a tenant receives: expenditure by head of charge against budget, then the apportionment by demise. Actual expenditure is 102,476.00 USD against 96,000.00 budgeted, and the 6,476.00 USD overspend is recovered by balancing charges that sum to the same figure. The statement explains in words why the common parts are outside the denominator and why the vacant unit share stays with the landlord.

File: PDF · Property Leasing · 2 pages
Use case: Data import· Conversion set

Pine Property Services: Quarterly rent and service charge demand

Quarterly rent and service charge demand for Pine Property Services. The 2026-Q4 demand across the 5 let demises: 61,368.75 USD of rent and 21,400.00 of service charge on account, 82,768.75 in total. It states in words that the vacant demise is not demanded and that the 6,476.00 USD balancing charge is dealt with separately, which are the two amounts most easily double counted.

File: PDF · Property Leasing · 1 page
Use case: Data import· Conversion set

Pine Property Services: Schedule of dilapidations

Schedule of dilapidations for Pine Property Services. A served dilapidations schedule against U-04: 5 remedial items totalling 22,430.00 USD, preliminaries at 8 percent of that, contract administration at 5 percent of the running total, and 5,653.85 USD of lost rent for a 8 week programme, giving a 31,089.47 USD claim. Each on cost states the base it is charged on, so the compounding order is visible rather than assumed.

File: PDF · Property Leasing · 2 pages
Use case: Data import· Conversion set

Pine Property Services: property document set README

Document set README for Pine Property Services. 26 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Property Leasing
Use case: Data import

Pine Assembly Workshop: Bill of materials workbook

Bill of materials workbook for Pine Assembly Workshop. A three-sheet workbook: the indented structure per finished unit, the explosion for BUILD-1, and the standard cost roll-up. The Indented and Explosion sheets differ by the order quantity of 2 on every extended column, which is the comparison the workbook exists to make easy.

File: XLSX · Manufacturing Quality
Use case: Data import· Conversion set

Pine Assembly Workshop: Work order (PDF)

Work order (PDF) for Pine Assembly Workshop. The shop paperwork for BUILD-1: 2 DESK due 2026-09-10, the 3 materials to issue at 50.40 USD, the 5 routing operations totalling 30 minutes, and a cost build-up that closes at 80.00 USD against a 80.00 USD standard, a zero variance. The DOCX twin in the same directory carries the identical text.

File: PDF · Manufacturing Quality · 2 pages
Use case: Data import· Paired fixture

Pine Assembly Workshop: Work order (DOCX)

Work order (DOCX) for Pine Assembly Workshop. The shop paperwork for BUILD-1: 2 DESK due 2026-09-10, the 3 materials to issue at 50.40 USD, the 5 routing operations totalling 30 minutes, and a cost build-up that closes at 80.00 USD against a 80.00 USD standard, a zero variance. The PDF twin in the same directory carries the identical text.

File: DOCX · Manufacturing Quality
Use case: Data import· Paired fixture

Pine Assembly Workshop: Inspection measurement workbook

Inspection measurement workbook for Pine Assembly Workshop. The readings and the characteristics in one workbook, so the limits used by the result column can be checked without opening a second file. Decimal values are held as text at the number of places the gauge reads to, which keeps the trailing zero on a nominal of 700.0 that a numeric cell would drop.

File: XLSX · Manufacturing Quality · 25 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Inspection report with measured tolerances

Inspection report with measured tolerances for Pine Assembly Workshop. The full report behind the measurement file: 5 characteristics with their limits, all 25 readings with deviation and result, and the 2 failures named with the amount by which each exceeds its limit. The findings paragraph states those overruns in words, so the description, the table and the CSV all carry the same numbers.

File: PDF · Manufacturing Quality · 2 pages
Use case: Data import· Conversion set

Pine Assembly Workshop: Nonconformance report

Nonconformance report for Pine Assembly Workshop. The report for NCR-2026-0001: characteristic CH-3 sample 3 measured 25.41 against a upper 25.300 limit, outside by 0.110, affecting 1 leg worth 3.00 USD. It records that the gauge was inside calibration on the inspection date, which is what makes the reading evidence rather than a suspect measurement.

File: PDF · Manufacturing Quality · 1 page
Use case: Data import· Conversion set

Pine Assembly Workshop: Certificate of conformance (PDF)

Certificate of conformance (PDF) for Pine Assembly Workshop. A certificate covering the 2 units released under BUILD-1 and lot LOT-2026-0912. The evidence table names five supporting records, every one of which is a file in this directory, and the certificate states the 2 nonconformances rather than omitting them, explaining that the affected legs were replaced before assembly so no nonconforming part is in the certified units. The DOCX twin in the same directory carries the identical text.

File: PDF · Manufacturing Quality · 1 page
Use case: Data import· Paired fixture

Pine Assembly Workshop: Certificate of conformance (DOCX)

Certificate of conformance (DOCX) for Pine Assembly Workshop. A certificate covering the 2 units released under BUILD-1 and lot LOT-2026-0912. The evidence table names five supporting records, every one of which is a file in this directory, and the certificate states the 2 nonconformances rather than omitting them, explaining that the affected legs were replaced before assembly so no nonconforming part is in the certified units. The PDF twin in the same directory carries the identical text.

File: DOCX · Manufacturing Quality
Use case: Data import· Paired fixture

Harbour Components: Material certificate

Material certificate for Harbour Components. The supplier certificate behind the leg stock, naming the 4 purchase orders the inventory-manufacturing model records for LEG and the 48 legs and 144.00 USD they cover. The declared properties are invented values in a plausible shape and the certificate says so in its own words, because a fixture that looked like a real mill certificate would be worse than useless.

File: PDF · Manufacturing Quality · 1 page
Use case: Data import· Conversion set

Pine Assembly Workshop: manufacturing document set README

Document set README for Pine Assembly Workshop. 31 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

File: MD · Manufacturing Quality
Use case: Data import

Clean CSV

A clean, well-formed CSV with a header and 20 rows: the baseline case for CSV parser testing.

File: CSV · CSV · 20 rows
Use case: CSV parsingData import

10,000-Row CSV

A CSV with 10,000 data rows, for testing streaming parsers, memory handling, and import performance.

File: CSV · CSV · 10,000 rows
Use case: CSV parsingData import

Flat JSON Array

A flat JSON array of ten simple objects: the baseline case for JSON parsing and mapping.

File: JSON · JSON · 10 records
Use case: JSON parsingData import

JSON Lines (JSONL)

A JSON Lines file with one object per line, for testing streaming/newline-delimited JSON parsers.

File: JSONL · JSON · 10 records
Use case: JSON parsingData import

Sample XML

A well-formed XML catalogue with nested elements and attributes, for testing XML parsers and XPath queries.

File: XML · XML
Use case: Data import

Sample YAML

A YAML configuration file with nested mappings, sequences, inline lists, and comments, for testing YAML parsers.

File: YAML · YAML
Use case: Data import

Sample SQLite Database

A real SQLite database with two related tables (users and orders joined by a foreign key) for testing database importers and SQL tooling.

File: SQLITE · Database
Use case: Data import

Fake Users Dataset (CSV, 500 rows)

A 500-row dataset of fake but realistic users (name, email, address, date of birth), generated with a fixed seed. Paired with a JSON twin.

File: CSV · Fake Datasets · 500 rows
Use case: Data importConversion testing· Conversion set

Fake Users Dataset (JSON, 500 records)

The 500-row users dataset as a JSON array: the format twin of the CSV version, for testing import and conversion.

File: JSON · Fake Datasets · 500 records
Use case: Data importConversion testing· Conversion set

Fake Orders Dataset (CSV, 1000 rows)

A 1000-row orders dataset whose user_id references the users dataset: a relational fixture for testing joins and import flows. Paired with a JSON twin.

File: CSV · Fake Datasets · 1,000 rows
Use case: Data importConversion testing· Conversion set

Fake Orders Dataset (JSON, 1000 records)

The 1000-row orders dataset as JSON: the format twin of the CSV version, relational to the users dataset.

File: JSON · Fake Datasets · 1,000 records
Use case: Data importConversion testing· Conversion set

NDJSON Stream

A newline-delimited JSON (NDJSON) stream of event records, for testing streaming JSON parsers.

File: NDJSON · JSON · 4 records
Use case: JSON parsingData import

E-commerce Products (CSV, 200 rows)

A realistic e-commerce product catalogue (200 rows): part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 200 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Products (JSON, 200 records)

The e-commerce products table as a JSON array: the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 200 records
Use case: Data importConversion testing· Conversion set

E-commerce Customers (CSV, 500 rows)

A realistic e-commerce customer directory (500 rows): part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 500 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Customers (JSON, 500 records)

The e-commerce customers table as a JSON array: the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 500 records
Use case: Data importConversion testing· Conversion set

E-commerce Orders (CSV, 2000 rows)

A realistic e-commerce order lines (customer_id → customers, product_id → products) (2000 rows): part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 2,000 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Orders (JSON, 2000 records)

The e-commerce orders table as a JSON array: the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 2,000 records
Use case: Data importConversion testing· Conversion set

E-commerce Database Schema (SQL)

A relational SQL schema (products, customers, orders with primary and foreign keys) plus sample INSERTs: the DDL twin of the e-commerce dataset, for testing schema import and migrations.

File: SQL · Ecommerce
Use case: Data importConversion testing

Stock OHLCV: Daily Candles (CSV, 252 rows)

A year of daily OHLCV stock candles (open/high/low/close/volume) as a seeded random walk: a realistic finance time-series for testing charting, indicators, and importers. JSON twin included.

File: CSV · Finance · 252 rows
Use case: Data importTime-series data+1· Conversion set

Stock OHLCV: Daily Candles (JSON, 252 records)

The daily OHLCV candles as a JSON array: the format twin of the CSV, for charting and time-series testing.

File: JSON · Finance · 252 records
Use case: Data importTime-series data· Conversion set

IoT Sensor Readings (CSV, 1440 rows)

A day of IoT sensor readings (temperature, humidity, pressure) at one-minute intervals from three sensors, with a realistic daily cycle plus noise, for testing time-series ingestion and downsampling. JSON twin included.

File: CSV · Iot · 1,440 rows
Use case: Data importTime-series data+1· Conversion set

IoT Sensor Readings (JSON, 1440 records)

The IoT sensor readings as a JSON array: the format twin of the CSV, for time-series testing.

File: JSON · Iot · 1,440 records
Use case: Data importTime-series data· Conversion set

FHIR R4 Patient Bundle (JSON)

A sample HL7 FHIR R4 bundle with a Patient plus vital-sign Observations, an Encounter, and a Condition: a realistic healthcare-interoperability fixture for testing FHIR parsers and mappers. Synthetic data, not a real person.

File: JSON · Healthcare
Use case: Data importConversion testing

Product JSON Schema (draft-07)

A JSON Schema (draft-07) describing a product object, with required fields, types, and constraints, paired with a conforming and a deliberately non-conforming instance for testing validators.

File: JSON · Schema
Use case: Schema validationData import· Conversion set

Large Transactions Dataset (CSV, 50k rows)

A 50,000-row transactions dataset: an in-repo 'large' fixture for testing streaming CSV parsers, import performance, and pagination. Deterministic (fixed seed).

File: CSV · Large · 50,000 rows
Use case: Data importPerformance testing+1

Apache Access Log: Common Format (log)

An Apache access log in the Common Log Format (CLF): client, timestamp, request line, status, and byte count. Deterministic, with reserved documentation IPs. Paired with a Combined-format twin for testing log parsers.

File: LOG · Logs
Use case: Log parsingData import+1· Conversion set

Apache Access Log: Combined Format (log)

An Apache access log in the Combined Log Format: the Common fields plus referer and user-agent. A realistic web-server log for testing access-log parsers, analytics, and grok patterns.

File: LOG · Logs
Use case: Log parsingData import+1· Conversion set

CSV with Mixed Null Representations

A CSV where missing values are written seven different ways (empty string, NULL, NA, N/A, null, None, and a dash) across text and numeric columns. A fixture for testing null-detection and coercion in CSV importers.

File: CSV · Edge Cases · 8 rows
Use case: CSV parsingError handling+1

CSV with Mixed-Type Columns

A CSV whose 'value' column mixes integers, floats, scientific notation, dates, hex, thousands separators, and whitespace, and whose 'flag' column mixes a dozen boolean spellings. A torture test for type inference and schema detection.

File: CSV · Edge Cases · 12 rows
Use case: CSV parsingError handling+1

Wide CSV: 1000 Columns

A CSV with 1000 columns and a handful of rows: a stress test for parsers, spreadsheet importers, and databases with column limits or per-row buffering assumptions. Deterministic (fixed seed).

File: CSV · Edge Cases · 5 rows
Use case: CSV parsingPerformance testing+1

CSV with Mixed Timestamp Formats

A CSV listing timestamps in eleven formats: ISO 8601 with Z and numeric offsets, millisecond precision, naive local, date-only, Unix epoch in seconds and milliseconds, US AM/PM, and RFC 1123. A fixture for testing date parsing and timezone normalisation.

File: CSV · Edge Cases · 11 rows
Use case: CSV parsingError handling+1

Star Schema: Date Dimension (CSV)

The date dimension of a star schema: one row per day with a YYYYMMDD surrogate key and calendar attributes (year, quarter, month, weekday). Joins to the sales fact table on date_key.

File: CSV · Star Schema · 31 rows
Use case: Data importData engineering+1· Conversion set

Star Schema: Product Dimension (CSV)

The product dimension of a star schema: surrogate key, SKU, name, category, and unit price. Joins to the sales fact table on product_key.

File: CSV · Star Schema · 20 rows
Use case: Data importData engineering+1· Conversion set

Star Schema: Customer Dimension (CSV)

The customer dimension of a star schema: surrogate key, name, city, country, and segment. Joins to the sales fact table on customer_key. Names are synthetic.

File: CSV · Star Schema · 40 rows
Use case: Data importData engineering+1· Conversion set

Star Schema: Sales Fact Table (CSV, 300 rows)

The sales fact table at the centre of a star schema: 300 sale lines with foreign keys to the date, product, and customer dimensions plus quantity and amount measures. A fixture for testing joins, star-schema imports, and BI tools.

File: CSV · Star Schema · 300 rows
Use case: Data importData engineering+1· Conversion set

Social Network Graph (GraphML)

A small synthetic social network in GraphML: 12 people in two communities with a few bridging ties, carrying node attributes (name, age, community) and weighted edges. Twinned with a GEXF file for testing graph importers and format converters.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Social Network Graph (GEXF)

The same 12-person social network in GEXF 1.3 (Gephi's native format): node attributes and weighted edges. The format twin of the GraphML file, for testing Gephi imports and GraphML↔GEXF conversion.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Service Dependency Graph (GraphML, directed)

A directed service-dependency graph in GraphML: ten microservices (web, api, auth, db, cache, queue, worker, …) with their call/dependency edges. A fixture for testing directed-graph importers, cycle detection, and topological sorting.

File: GRAPHML · Graph
Use case: Graph dataData import

World Cities (40 rows, CSV)

A curated world-cities dataset: 40 major cities with country, latitude, longitude, and population. A realistic geospatial fixture for testing map plots, geocoding, and CSV→GeoJSON conversion. GeoJSON twin included.

File: CSV · Geospatial · 40 rows
Use case: GeospatialData import+1· Conversion set

World Cities (40 points, GeoJSON)

The same 40 world cities as a GeoJSON FeatureCollection of Points (longitude, latitude order per RFC 7946), each with name, country, and population properties. The mapping twin of the CSV, for testing GeoJSON parsers and map renderers.

File: GEOJSON · Geospatial
Use case: GeospatialData import+1· Conversion set

Survey Responses: Likert + NPS (CSV, 60 rows)

A customer-survey response set: 60 respondents rating five statements on a 1–5 Likert scale plus a 0–10 NPS score and a segment. A fixture for testing survey analysis, aggregation, and NPS/CSAT calculations.

File: CSV · Surveys · 60 rows
Use case: Data importConversion testing+1

Recommender Ratings: user/item/rating (CSV, 240 rows)

A MovieLens-style ratings log: 240 user/item/rating events with Unix timestamps across 50 users and 40 items. A fixture for testing recommender pipelines, collaborative-filtering loaders, and sparse-matrix builders.

File: CSV · Recommender · 240 rows
Use case: Data importModel evaluation+1

Bank Transactions (CSV, 60 rows)

A bank-transaction statement: 60 debits and credits across three accounts (masked numbers) with running balances, categories, and merchants. Synthetic data for testing statement parsers, categorisation, and reconciliation.

File: CSV · Banking · 60 rows
Use case: Data importConversion testing· Conversion set

Bank Transactions (JSON, 60 records)

The bank transactions as a JSON array: the format twin of the CSV, for import and reconciliation testing.

File: JSON · Banking · 60 records
Use case: Data importConversion testing· Conversion set

Payment Test Cards (CSV)

A reference list of well-known payment TEST card numbers (Visa, Mastercard, Amex, Discover, JCB, Diners) with sample CVV and expiry. These are published test values that pass the Luhn check but are not real accounts, for testing payment forms and card validators. Never use real card data.

File: CSV · Banking · 8 rows
Use case: Form testingData import

ISO 20022 Credit Transfer: pain.001 (XML)

A sample ISO 20022 customer credit-transfer initiation (pain.001.001.09): a single payment with debtor/creditor parties, IBANs, BICs, amount, and remittance info. IBANs are published documentation examples; a fixture for testing payment-message parsers and bank integrations.

File: XML · Banking
Use case: Data importConversion testing+1

Real-estate Listings (CSV, 30 rows)

A property-listings dataset: 30 homes with address, type, price, beds/baths, size, year built, coordinates, and status. Synthetic data for testing listing importers, map plots, and price analytics.

File: CSV · Real Estate · 30 rows
Use case: Data importGeospatial+1· Conversion set

Real-estate Listings (JSON, 30 records)

The property listings as a JSON array: the format twin of the CSV, for import and mapping tests.

File: JSON · Real Estate · 30 records
Use case: Data importGeospatial+1· Conversion set

Flight Schedule (CSV, 30 rows)

A flight-schedule dataset: 30 flights with airline, origin/destination airports, departure/arrival times, aircraft, gate, and status. Synthetic data for testing travel apps, schedule parsers, and status boards.

File: CSV · Travel · 30 rows
Use case: Data importConversion testing· Conversion set

Flight Schedule (JSON, 30 records)

The flight schedule as a JSON array: the format twin of the CSV, for import and display tests.

File: JSON · Travel · 30 records
Use case: Data importConversion testing· Conversion set

Weather Forecast: 30 days (CSV, 30 rows)

A 30-day daily weather forecast for one city: high/low temperature, condition, precipitation, wind, and humidity. Synthetic (seeded) data for testing weather widgets, chart tools, and time-series import.

File: CSV · Weather · 30 rows
Use case: Data importTime-series data+1· Conversion set

Weather Forecast: 30 days (JSON, 30 records)

The daily forecast as a JSON array: the format twin of the CSV, for import and charting tests.

File: JSON · Weather · 30 records
Use case: Data importTime-series data+1· Conversion set

Sports League Standings (CSV)

A football-style league table: position, played, won/drawn/lost, goals for/against, goal difference, and points for ten teams, derived from a full round of synthetic match results. Paired with the results JSON.

File: CSV · Sports
Use case: Data importConversion testing· Conversion set

Sports Match Results (JSON)

The full round of match results behind the league table: home/away teams, scores, and dates as a JSON array. A fixture for testing sports-data importers and standings calculators.

File: JSON · Sports
Use case: Data importConversion testing· Conversion set

Employee Directory (CSV, 30 rows)

An employee directory: 30 staff with department, title, hire date, salary, and manager reference. Synthetic HR data for testing org-chart builders, directory imports, and payroll pipelines.

File: CSV · Hr · 30 rows
Use case: Data importConversion testing· Conversion set

Employee Directory (JSON, 30 records)

The employee directory as a JSON array: the format twin of the CSV, for HR import testing.

File: JSON · Hr · 30 records
Use case: Data importConversion testing· Conversion set

Payroll Summary (JSON)

A monthly payroll summary derived from the employee directory: headcount, annual and monthly gross totals, and a per-department breakdown. A fixture for testing finance/HR dashboards and JSON aggregation.

File: JSON · Hr
Use case: Data importConversion testing

CSV with Leading-Zero Identifiers

SKU identifiers that start with zeros. Spreadsheet tools often coerce these to numbers and drop the zeros. Keep them as text.

File: CSV · Edge Cases · 3 rows
Use case: CSV parsingData import

CSV DST and Leap-Day Timestamps

Timestamps spanning a US spring-forward DST gap and leap-day dates for timezone and calendar edge-case testing.

File: CSV · Edge Cases · 4 rows
Use case: CSV parsingData import

CSV: UTF-8 with BOM

A CSV prefixed with a UTF-8 BOM (EF BB BF) and accented / CJK cells, for testing BOM-aware importers.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection+1

CSV: Semicolon Delimiter (EU)

European-style CSV using semicolons as delimiters and comma decimals: a common locale edge case.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: Pipe Delimiter

A pipe-delimited (| ) tabular file, for testing non-comma delimiter autodetection.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

Fixed-Width Positions File (TXT)

A classic fixed-width text extract with documented column positions, for COBOL-style / mainframe importer tests.

File: TXT · Encodings · 3 rows
Use case: CSV parsingData import+1

CSV: Hash Comment Lines

A CSV with # comment lines mixed among data: common in scientific exports; tests comment skipping.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: Single Column

A one-column CSV of email addresses: edge case for delimiter sniffers that expect commas in every row.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

SaaS Product Events (CSV)

Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. CSV twin.

File: CSV · Saas · 24 rows
Use case: Data importCSV parsing· Conversion set

SaaS Product Events (JSON)

Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. JSON twin.

File: JSON · Saas · 24 records
Use case: Data importJSON parsing· Conversion set

POS SKU Catalog (CSV)

A point-of-sale SKU catalog with tax codes and active flags: fictional Meridian Supply inventory. CSV twin.

File: CSV · Pos · 8 rows
Use case: Data importCSV parsing· Conversion set

POS SKU Catalog (JSON)

A point-of-sale SKU catalog with tax codes and active flags: fictional Meridian Supply inventory. JSON twin.

File: JSON · Pos · 8 records
Use case: Data importJSON parsing· Conversion set

Lab Measurements (CSV)

Synthetic lab readings (temperature, pressure, pH) with ISO timestamps for scientific ETL tests. CSV twin.

File: CSV · Lab · 16 rows
Use case: Data importCSV parsing· Conversion set

Lab Measurements (JSON)

Synthetic lab readings (temperature, pressure, pH) with ISO timestamps for scientific ETL tests. JSON twin.

File: JSON · Lab · 16 records
Use case: Data importJSON parsing· Conversion set

Marketing Attribution (CSV)

Synthetic multi-touch attribution click rows with UTM fields, for marketing analytics importers. CSV twin.

File: CSV · Marketing · 10 rows
Use case: Data importCSV parsing· Conversion set

Marketing Attribution (JSON)

Synthetic multi-touch attribution click rows with UTM fields, for marketing analytics importers. JSON twin.

File: JSON · Marketing · 10 records
Use case: Data importJSON parsing· Conversion set

FINANCE: Ledger Lines (CSV)

Synthetic finance dataset (ledger-lines) as CSV, for ETL and warehouse loader tests.

File: CSV · Finance · 8 rows
Use case: Data importCSV parsing· Conversion set

FINANCE: Ledger Lines (JSON)

JSON twin of the finance/ledger-lines mini-dataset.

File: JSON · Finance · 8 records
Use case: Data importJSON parsing· Conversion set

SUPPORT: Tickets (CSV)

Synthetic support dataset (tickets) as CSV, for ETL and warehouse loader tests.

File: CSV · Support · 6 rows
Use case: Data importCSV parsing· Conversion set

SUPPORT: Tickets (JSON)

JSON twin of the support/tickets mini-dataset.

File: JSON · Support · 6 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 01 (JSON)

Deterministic synthetic JSON batch 01 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 02 (JSON)

Deterministic synthetic JSON batch 02 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 03 (JSON)

Deterministic synthetic JSON batch 03 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 04 (JSON)

Deterministic synthetic JSON batch 04 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 05 (JSON)

Deterministic synthetic JSON batch 05 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 06 (JSON)

Deterministic synthetic JSON batch 06 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 07 (JSON)

Deterministic synthetic JSON batch 07 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 08 (JSON)

Deterministic synthetic JSON batch 08 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 09 (JSON)

Deterministic synthetic JSON batch 09 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 10 (JSON)

Deterministic synthetic JSON batch 10 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 11 (JSON)

Deterministic synthetic JSON batch 11 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 12 (JSON)

Deterministic synthetic JSON batch 12 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 13 (JSON)

Deterministic synthetic JSON batch 13 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 14 (JSON)

Deterministic synthetic JSON batch 14 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 15 (JSON)

Deterministic synthetic JSON batch 15 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 16 (JSON)

Deterministic synthetic JSON batch 16 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 17 (JSON)

Deterministic synthetic JSON batch 17 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 18 (JSON)

Deterministic synthetic JSON batch 18 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 19 (JSON)

Deterministic synthetic JSON batch 19 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 20 (JSON)

Deterministic synthetic JSON batch 20 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 01 (CSV)

Deterministic synthetic CSV batch 01 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 02 (CSV)

Deterministic synthetic CSV batch 02 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 03 (CSV)

Deterministic synthetic CSV batch 03 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 04 (CSV)

Deterministic synthetic CSV batch 04 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 05 (CSV)

Deterministic synthetic CSV batch 05 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 06 (CSV)

Deterministic synthetic CSV batch 06 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 07 (CSV)

Deterministic synthetic CSV batch 07 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 08 (CSV)

Deterministic synthetic CSV batch 08 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 09 (CSV)

Deterministic synthetic CSV batch 09 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 10 (CSV)

Deterministic synthetic CSV batch 10 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 11 (CSV)

Deterministic synthetic CSV batch 11 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 12 (CSV)

Deterministic synthetic CSV batch 12 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 13 (CSV)

Deterministic synthetic CSV batch 13 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 14 (CSV)

Deterministic synthetic CSV batch 14 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 15 (CSV)

Deterministic synthetic CSV batch 15 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 16 (CSV)

Deterministic synthetic CSV batch 16 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 17 (CSV)

Deterministic synthetic CSV batch 17 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 18 (CSV)

Deterministic synthetic CSV batch 18 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 19 (CSV)

Deterministic synthetic CSV batch 19 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 20 (CSV)

Deterministic synthetic CSV batch 20 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

HR: Employees Mini (CSV)

Synthetic hr dataset (employees-mini) as CSV, for ETL and warehouse loader tests.

File: CSV · Hr · 8 rows
Use case: Data importCSV parsing· Conversion set

HR: Employees Mini (JSON)

JSON twin of the hr/employees-mini mini-dataset.

File: JSON · Hr · 8 records
Use case: Data importJSON parsing· Conversion set

IOT: Sensor Readings Mini (CSV)

Synthetic iot dataset (sensor-readings-mini) as CSV, for ETL and warehouse loader tests.

File: CSV · Iot · 12 rows
Use case: Data importCSV parsing· Conversion set

IOT: Sensor Readings Mini (JSON)

JSON twin of the iot/sensor-readings-mini mini-dataset.

File: JSON · Iot · 12 records
Use case: Data importJSON parsing· Conversion set

Time-series: Irregular Intervals (CSV)

Sensor readings at irregular minute gaps. Tests time-series resampling and gap detection.

File: CSV · Timeseries · 8 rows
Use case: Time-series dataData import+1· Conversion set

Time-series: Irregular Intervals (JSON)

JSON twin of irregular-interval sensor readings for charting library tests.

File: JSON · Timeseries · 8 records
Use case: Time-series dataData import+1· Conversion set

Time-series: DST Spring Forward Gap (CSV)

Hourly load data skipping the 03:00 hour on DST spring-forward day. Tests timezone/DST gap handling.

File: CSV · Timeseries · 4 rows
Use case: Time-series dataData import+1

Time-series: DST Fall Back Duplicate Hour (CSV)

Load readings with a repeated 01:00 local hour on fall-back DST. Tests ambiguous timestamp handling.

File: CSV · Timeseries · 5 rows
Use case: Time-series dataData import+1

Time-series: Duplicate Timestamp Keys (CSV)

Two rows share the same timestamp key. Tests deduplication and last-write-wins policies.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+2· Conversion set

Time-series: Duplicate Timestamp Keys (JSON)

JSON array with duplicate timestamp keys for ingestion pipeline tests.

File: JSON · Timeseries · 3 records
Use case: Time-series dataData import+1· Conversion set

Time-series: Gap Filled

Series with an explicit null value at a missing sample point.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series: Out Of Order

Timestamps out of chronological order. Tests sort-on-ingest behaviour.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series: Mixed Tz

Same nominal instant expressed in Z, -05:00, and +09:00 offsets.

File: JSON · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series: Nan Gaps

CSV with NaN string and empty cells representing missing measurements.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series: Millisecond

Sub-second millisecond timestamps for precision parsing tests.

File: JSON · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series: Business Hours

Hourly order counts weekdays only (09–16 UTC) across three SAMPLE days.

File: CSV · Timeseries · 24 rows
Use case: Time-series dataData import+1

Time-series: Weekly Agg

Pre-aggregated weekly totals JSON for rollup/chart tests.

File: JSON · Timeseries · 1 row
Use case: Time-series dataData import+1

Time-series: Leap Day

Readings spanning Feb 29 leap day: calendar edge case.

File: CSV · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series: Epoch Boundary

Timestamps at Unix epoch and classic 32-bit Y2038 boundary.

File: JSON · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series: Sparse Events (JSONL)

Sparse event log in JSON Lines: two events hours apart for event-stream ingestion tests.

File: JSONL · Timeseries · 2 records
Use case: Time-series dataData import+2

Parquet: Null-heavy Columns

Tiny Parquet table with null name/score/note cells. Tests null handling in columnar readers.

File: PARQUET · Columnar · 3 rows
Use case: Data importConversion testing· Conversion set

Parquet: Dictionary-encoded Column

Parquet with dictionary-encoded string column. Tests dictionary page decoding.

File: PARQUET · Columnar · 5 rows
Use case: Data importConversion testing

Parquet: Nested Struct Column

Parquet with a struct column. Tests nested type round-trips.

File: PARQUET · Columnar
Use case: Data importConversion testing

Parquet: List Column

Parquet with a list-of-string column. Tests repeated-field decoding.

File: PARQUET · Columnar
Use case: Data importConversion testing

Parquet: Empty Table

Empty Parquet file with schema but no rows: edge case for readers.

File: PARQUET · Columnar · 0 rows
Use case: Data importConversion testing

Parquet: Single Row

Single-row Parquet table: minimal columnar fixture.

File: PARQUET · Columnar · 1 row
Use case: Data importConversion testing

Parquet: Duplicate Key Column

Parquet with repeated key values. Tests join/aggregation edge cases.

File: PARQUET · Columnar · 3 rows
Use case: Data importConversion testing

Parquet: Mixed Nullable Types

Parquet with bool/int/string/float columns including a null integer.

File: PARQUET · Columnar
Use case: Data importConversion testing

Healthcare Claim (FHIR SAMPLE JSON)

Synthetic FHIR Claim resource for healthcare billing parser tests, not a real patient.

File: JSON · Healthcare
Use case: Data importJSON parsing

Healthcare ORM HL7 Message (SAMPLE)

Sample HL7 v2 ORM order message with PID and OBR segments: fictional patient and order ids.

File: HL7 · Healthcare
Use case: Data import

Healthcare Patient Demographics (CSV)

Synthetic patient demographics CSV for EHR import and de-identification pipeline tests.

File: CSV · Healthcare · 2 rows
Use case: Data importCSV parsing

Healthcare Procedure Codes (JSON)

SAMPLE procedure code list with fees for medical billing calculator tests.

File: JSON · Healthcare
Use case: Data importJSON parsing

Healthcare Prescription (JSON)

Synthetic e-prescription JSON for pharmacy routing and validation tests.

File: JSON · Healthcare
Use case: Data import

Healthcare Lab Results (CSV)

Synthetic lab result rows for clinical data warehouse import tests.

File: CSV · Healthcare · 2 rows
Use case: Data importCSV parsing

Fintech Double-entry Ledger (JSON)

Balanced double-entry ledger SAMPLE for accounting engine validation tests.

File: JSON · Fintech
Use case: Data importJSON parsing

Fintech Transaction History (CSV)

Synthetic bank transaction history for personal-finance importer tests.

File: CSV · Fintech · 2 rows
Use case: Data importCSV parsing

Fintech Bank Statement Lines (CSV)

Synthetic bank statement line items for reconciliation tooling tests.

File: CSV · Fintech · 2 rows
Use case: Data import

Fintech SAR Compliance Flag (JSON)

Synthetic suspicious-activity flag JSON for AML compliance workflow tests.

File: JSON · Fintech
Use case: Data import

Inventory BOM Multi-level (JSON)

Multi-level bill-of-materials SAMPLE for MRP and assembly planning tests.

File: JSON · Inventory
Use case: Data importJSON parsing

Inventory SKU Catalog (CSV)

Fictional SKU catalog for ERP and POS import tests.

File: CSV · Inventory · 2 rows
Use case: Data importCSV parsing

Inventory Stock Levels (CSV)

Per-warehouse stock quantities for inventory reconciliation tests.

File: CSV · Inventory · 2 rows
Use case: Data import

Inventory Purchase Order (JSON)

Synthetic purchase order JSON for procurement workflow tests.

File: JSON · Inventory
Use case: Data import

Inventory Cycle Count (CSV)

Cycle-count variance SAMPLE for inventory audit reconciliation tests.

File: CSV · Inventory · 1 row
Use case: Data importCSV parsing

Feather: Null-heavy Columns

Feather/Arrow IPC twin of the null-heavy table, grouped with the Parquet nulls fixture.

File: FEATHER · Columnar · 3 rows
Use case: Data importConversion testing· Conversion set

Feather: Dictionary-encoded Column

Feather file with dictionary-encoded strings: Arrow IPC edge-case fixture.

File: FEATHER · Columnar
Use case: Data importConversion testing

Columnar Nulls Schema (JSON)

JSON description of nullable columns in the null-heavy columnar fixtures.

File: JSON · Columnar
Use case: Data importConversion testing+1· Conversion set

Parquet: Decimal as String Column

Amounts stored as strings in Parquet: common ingestion edge case for ETL parsers.

File: PARQUET · Columnar · 2 rows
Use case: Data importConversion testing

CSV Edge: Semicolon Eu

Tiny SAMPLE CSV (semicolon-eu) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Pipe Delimited

Tiny SAMPLE CSV (pipe-delimited) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Hash Commented

Tiny SAMPLE CSV (hash-commented) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Quoted Embedded Comma

Tiny SAMPLE CSV (quoted-embedded-comma) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Quoted Embedded Newline

Tiny SAMPLE CSV (quoted-embedded-newline) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Empty Fields

Tiny SAMPLE CSV (empty-fields) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Trailing Comma

Tiny SAMPLE CSV (trailing-comma) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Header Only

Tiny SAMPLE CSV (header-only) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Single Column

Tiny SAMPLE CSV (single-column) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge: Mixed Quoting

Tiny SAMPLE CSV (mixed-quoting) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

Directed Acyclic Pipeline - GraphML

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Acyclic Pipeline - GEXF 1.3

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Acyclic Pipeline - JSON edge list

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - GraphML

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - GEXF 1.3

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - JSON edge list

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - GraphML

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - GEXF 1.3

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - JSON edge list

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - GraphML

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - GEXF 1.3

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - JSON edge list

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Alder Table Bistro: Linked operating model

Linked operating model for Alder Table Bistro. 369 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=11,652.45 CAD; Net menu sales=15,780.80 CAD; Menu items sold=1,092.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 369 records
Use case: Data import

Alder Table Bistro: Operating model JSON Schema

Operating model JSON Schema for Alder Table Bistro. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Alder Table Bistro: Numeric expected results

Numeric expected results for Alder Table Bistro. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=11,652.45 CAD; Net menu sales=15,780.80 CAD; Menu items sold=1,092.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Alder Table Bistro: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Alder Table Bistro. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Alder Table Bistro: Purchase import CSV

Purchase import CSV for Alder Table Bistro. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Alder Table Bistro: Equivalent purchase import TSV

Equivalent purchase import TSV for Alder Table Bistro. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Alder Table Bistro: Guest review import CSV

Guest review import CSV for Alder Table Bistro. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Alder Table Bistro: Intentionally invalid purchase import

Intentionally invalid purchase import for Alder Table Bistro. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Alder Table Bistro: Intentionally invalid review import

Intentionally invalid review import for Alder Table Bistro. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Juniper Corner Cafe: Linked operating model

Linked operating model for Juniper Corner Cafe. 365 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=8,715.93 CAD; Net menu sales=10,234.74 CAD; Menu items sold=1,204.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 365 records
Use case: Data import

Juniper Corner Cafe: Operating model JSON Schema

Operating model JSON Schema for Juniper Corner Cafe. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Juniper Corner Cafe: Numeric expected results

Numeric expected results for Juniper Corner Cafe. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=8,715.93 CAD; Net menu sales=10,234.74 CAD; Menu items sold=1,204.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Juniper Corner Cafe: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Juniper Corner Cafe. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Juniper Corner Cafe: Purchase import CSV

Purchase import CSV for Juniper Corner Cafe. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Juniper Corner Cafe: Equivalent purchase import TSV

Equivalent purchase import TSV for Juniper Corner Cafe. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Juniper Corner Cafe: Guest review import CSV

Guest review import CSV for Juniper Corner Cafe. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Juniper Corner Cafe: Intentionally invalid purchase import

Intentionally invalid purchase import for Juniper Corner Cafe. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Juniper Corner Cafe: Intentionally invalid review import

Intentionally invalid review import for Juniper Corner Cafe. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Copper Oven Bakery: Linked operating model

Linked operating model for Copper Oven Bakery. 368 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 368 records
Use case: Data import

Copper Oven Bakery: Operating model JSON Schema

Operating model JSON Schema for Copper Oven Bakery. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Copper Oven Bakery: Numeric expected results

Numeric expected results for Copper Oven Bakery. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Copper Oven Bakery: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Copper Oven Bakery. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Copper Oven Bakery: Purchase import CSV

Purchase import CSV for Copper Oven Bakery. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Copper Oven Bakery: Equivalent purchase import TSV

Equivalent purchase import TSV for Copper Oven Bakery. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Copper Oven Bakery: Guest review import CSV

Guest review import CSV for Copper Oven Bakery. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Copper Oven Bakery: Intentionally invalid purchase import

Intentionally invalid purchase import for Copper Oven Bakery. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Copper Oven Bakery: Intentionally invalid review import

Intentionally invalid review import for Copper Oven Bakery. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Ember Lane Pizza: Linked operating model

Linked operating model for Ember Lane Pizza. 375 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=15,061.21 CAD; Net menu sales=25,954.50 CAD; Menu items sold=1,428.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 375 records
Use case: Data import

Ember Lane Pizza: Operating model JSON Schema

Operating model JSON Schema for Ember Lane Pizza. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Ember Lane Pizza: Numeric expected results

Numeric expected results for Ember Lane Pizza. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=15,061.21 CAD; Net menu sales=25,954.50 CAD; Menu items sold=1,428.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Ember Lane Pizza: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Ember Lane Pizza. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Ember Lane Pizza: Purchase import CSV

Purchase import CSV for Ember Lane Pizza. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Ember Lane Pizza: Equivalent purchase import TSV

Equivalent purchase import TSV for Ember Lane Pizza. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Ember Lane Pizza: Guest review import CSV

Guest review import CSV for Ember Lane Pizza. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Ember Lane Pizza: Intentionally invalid purchase import

Intentionally invalid purchase import for Ember Lane Pizza. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Ember Lane Pizza: Intentionally invalid review import

Intentionally invalid review import for Ember Lane Pizza. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Cedar Street Tacos: Linked operating model

Linked operating model for Cedar Street Tacos. 375 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 375 records
Use case: Data import

Cedar Street Tacos: Operating model JSON Schema

Operating model JSON Schema for Cedar Street Tacos. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Cedar Street Tacos: Numeric expected results

Numeric expected results for Cedar Street Tacos. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Cedar Street Tacos: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Cedar Street Tacos. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Cedar Street Tacos: Purchase import CSV

Purchase import CSV for Cedar Street Tacos. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Cedar Street Tacos: Equivalent purchase import TSV

Equivalent purchase import TSV for Cedar Street Tacos. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Cedar Street Tacos: Guest review import CSV

Guest review import CSV for Cedar Street Tacos. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Cedar Street Tacos: Intentionally invalid purchase import

Intentionally invalid purchase import for Cedar Street Tacos. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Cedar Street Tacos: Intentionally invalid review import

Intentionally invalid review import for Cedar Street Tacos. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Willow Event Kitchen: Linked operating model

Linked operating model for Willow Event Kitchen. 376 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=7,900.99 CAD; Net menu sales=28,781.90 CAD; Menu items sold=1,652.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 376 records
Use case: Data import

Willow Event Kitchen: Operating model JSON Schema

Operating model JSON Schema for Willow Event Kitchen. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Willow Event Kitchen: Numeric expected results

Numeric expected results for Willow Event Kitchen. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=7,900.99 CAD; Net menu sales=28,781.90 CAD; Menu items sold=1,652.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Willow Event Kitchen: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Willow Event Kitchen. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Willow Event Kitchen: Purchase import CSV

Purchase import CSV for Willow Event Kitchen. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Willow Event Kitchen: Equivalent purchase import TSV

Equivalent purchase import TSV for Willow Event Kitchen. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Willow Event Kitchen: Guest review import CSV

Guest review import CSV for Willow Event Kitchen. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Willow Event Kitchen: Intentionally invalid purchase import

Intentionally invalid purchase import for Willow Event Kitchen. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Willow Event Kitchen: Intentionally invalid review import

Intentionally invalid review import for Willow Event Kitchen. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Harbour Kitchen Group: Linked operating model

Linked operating model for Harbour Kitchen Group. 369 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=7,897.76 CAD; Net menu sales=26,214.00 CAD; Menu items sold=1,764.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 369 records
Use case: Data import

Harbour Kitchen Group: Operating model JSON Schema

Operating model JSON Schema for Harbour Kitchen Group. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Harbour Kitchen Group: Numeric expected results

Numeric expected results for Harbour Kitchen Group. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=7,897.76 CAD; Net menu sales=26,214.00 CAD; Menu items sold=1,764.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Harbour Kitchen Group: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Harbour Kitchen Group. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Harbour Kitchen Group: Purchase import CSV

Purchase import CSV for Harbour Kitchen Group. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Harbour Kitchen Group: Equivalent purchase import TSV

Equivalent purchase import TSV for Harbour Kitchen Group. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Harbour Kitchen Group: Guest review import CSV

Guest review import CSV for Harbour Kitchen Group. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Harbour Kitchen Group: Intentionally invalid purchase import

Intentionally invalid purchase import for Harbour Kitchen Group. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Harbour Kitchen Group: Intentionally invalid review import

Intentionally invalid review import for Harbour Kitchen Group. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Fieldnote Supply Shop: Linked operating model

Linked operating model for Fieldnote Supply Shop. 86 records across 9 linked tables; no duplicate primary keys or missing references. Gross item sales=942.00 USD; Refunded amount=80.00 USD; Orders=12.00 records.

File: JSON · Business Kits · 86 records
Use case: Data import

Fieldnote Supply Shop: Operating model JSON Schema

Operating model JSON Schema for Fieldnote Supply Shop. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Fieldnote Supply Shop: Numeric expected results

Numeric expected results for Fieldnote Supply Shop. Exact table counts, metric formulas, 12 chart points and three negative-test outcomes. Gross item sales=942.00 USD; Refunded amount=80.00 USD; Orders=12.00 records.

File: JSON · Business Kits
Use case: Data import

Fieldnote Supply Shop: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Fieldnote Supply Shop. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Fieldnote Supply Shop: Generic primary records CSV

Generic primary records CSV for Fieldnote Supply Shop. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 6 rows
Use case: Data import

Tern Client Services: Linked operating model

Linked operating model for Tern Client Services. 98 records across 9 linked tables; no duplicate primary keys or missing references. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.

File: JSON · Business Kits · 98 records
Use case: Data import

Tern Client Services: Operating model JSON Schema

Operating model JSON Schema for Tern Client Services. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Tern Client Services: Numeric expected results

Numeric expected results for Tern Client Services. Exact table counts, metric formulas, 4 chart points and three negative-test outcomes. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.

File: JSON · Business Kits
Use case: Data import

Tern Client Services: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Tern Client Services. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Tern Client Services: Generic primary records CSV

Generic primary records CSV for Tern Client Services. 4 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 4 rows
Use case: Data import

Alder Books Reconciliation: Linked operating model

Linked operating model for Alder Books Reconciliation. 102 records across 6 linked tables; no duplicate primary keys or missing references. Net cash change=5,236.00 USD; Journal debits=9,364.00 USD; Journal credits=9,364.00 USD.

File: JSON · Business Kits · 102 records
Use case: Data import

Alder Books Reconciliation: Operating model JSON Schema

Operating model JSON Schema for Alder Books Reconciliation. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Alder Books Reconciliation: Numeric expected results

Numeric expected results for Alder Books Reconciliation. Exact table counts, metric formulas, 24 chart points and three negative-test outcomes. Net cash change=5,236.00 USD; Journal debits=9,364.00 USD; Journal credits=9,364.00 USD.

File: JSON · Business Kits
Use case: Data import

Alder Books Reconciliation: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Alder Books Reconciliation. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Alder Books Reconciliation: Generic primary records CSV

Generic primary records CSV for Alder Books Reconciliation. 24 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 24 rows
Use case: Data import

Pine Assembly Workshop: Linked operating model

Linked operating model for Pine Assembly Workshop. 89 records across 11 linked tables; no duplicate primary keys or missing references. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

File: JSON · Business Kits · 89 records
Use case: Data import

Pine Assembly Workshop: Operating model JSON Schema

Operating model JSON Schema for Pine Assembly Workshop. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Pine Assembly Workshop: Numeric expected results

Numeric expected results for Pine Assembly Workshop. Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

File: JSON · Business Kits
Use case: Data import

Pine Assembly Workshop: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Pine Assembly Workshop. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Pine Assembly Workshop: Generic primary records CSV

Generic primary records CSV for Pine Assembly Workshop. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 6 rows
Use case: Data import

Cobalt Operations Team: Linked operating model

Linked operating model for Cobalt Operations Team. 102 records across 5 linked tables; no duplicate primary keys or missing references. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

File: JSON · Business Kits · 102 records
Use case: Data import

Cobalt Operations Team: Operating model JSON Schema

Operating model JSON Schema for Cobalt Operations Team. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Cobalt Operations Team: Numeric expected results

Numeric expected results for Cobalt Operations Team. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

File: JSON · Business Kits
Use case: Data import

Cobalt Operations Team: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Cobalt Operations Team. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Cobalt Operations Team: Generic primary records CSV

Generic primary records CSV for Cobalt Operations Team. 8 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 8 rows
Use case: Data import

Juniper Fitness and Clinic Administration: Linked operating model

Linked operating model for Juniper Fitness and Clinic Administration. 66 records across 5 linked tables; no duplicate primary keys or missing references. Available slots=24.00 slots; Occupied slots=16.00 slots; Booking records=18.00 records.

File: JSON · Business Kits · 66 records
Use case: Data import

Juniper Fitness and Clinic Administration: Operating model JSON Schema

Operating model JSON Schema for Juniper Fitness and Clinic Administration. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Juniper Fitness and Clinic Administration: Numeric expected results

Numeric expected results for Juniper Fitness and Clinic Administration. Exact table counts, metric formulas, 3 chart points and three negative-test outcomes. Available slots=24.00 slots; Occupied slots=16.00 slots; Booking records=18.00 records.

File: JSON · Business Kits
Use case: Data import

Juniper Fitness and Clinic Administration: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Juniper Fitness and Clinic Administration. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Juniper Fitness and Clinic Administration: Generic primary records CSV

Generic primary records CSV for Juniper Fitness and Clinic Administration. 3 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 3 rows
Use case: Data import

Harbour House Stay: Linked operating model

Linked operating model for Harbour House Stay. 53 records across 7 linked tables; no duplicate primary keys or missing references. Occupied room nights=48.00 nights; Room revenue=6,840.00 USD; Ancillary revenue=672.00 USD.

File: JSON · Business Kits · 53 records
Use case: Data import

Harbour House Stay: Operating model JSON Schema

Operating model JSON Schema for Harbour House Stay. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Harbour House Stay: Numeric expected results

Numeric expected results for Harbour House Stay. Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Occupied room nights=48.00 nights; Room revenue=6,840.00 USD; Ancillary revenue=672.00 USD.

File: JSON · Business Kits
Use case: Data import

Harbour House Stay: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Harbour House Stay. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Harbour House Stay: Generic primary records CSV

Generic primary records CSV for Harbour House Stay. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 6 rows
Use case: Data import

Fieldnote Learning Centre: Linked operating model

Linked operating model for Fieldnote Learning Centre. 72 records across 5 linked tables; no duplicate primary keys or missing references. Enrollments=18.00 records; Passed completions=9.00 learners; Available course seats=30.00 seats.

File: JSON · Business Kits · 72 records
Use case: Data import

Fieldnote Learning Centre: Operating model JSON Schema

Operating model JSON Schema for Fieldnote Learning Centre. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Fieldnote Learning Centre: Numeric expected results

Numeric expected results for Fieldnote Learning Centre. Exact table counts, metric formulas, 3 chart points and three negative-test outcomes. Enrollments=18.00 records; Passed completions=9.00 learners; Available course seats=30.00 seats.

File: JSON · Business Kits
Use case: Data import

Fieldnote Learning Centre: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Fieldnote Learning Centre. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Fieldnote Learning Centre: Generic primary records CSV

Generic primary records CSV for Fieldnote Learning Centre. 3 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 3 rows
Use case: Data import

Willow Community Fund: Linked operating model

Linked operating model for Willow Community Fund. 58 records across 8 linked tables; no duplicate primary keys or missing references. Pledged support=2,850.00 USD; Received support=1,800.00 USD; Outstanding pledges=1,050.00 USD.

File: JSON · Business Kits · 58 records
Use case: Data import

Willow Community Fund: Operating model JSON Schema

Operating model JSON Schema for Willow Community Fund. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Willow Community Fund: Numeric expected results

Numeric expected results for Willow Community Fund. Exact table counts, metric formulas, 3 chart points and three negative-test outcomes. Pledged support=2,850.00 USD; Received support=1,800.00 USD; Outstanding pledges=1,050.00 USD.

File: JSON · Business Kits
Use case: Data import

Willow Community Fund: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Willow Community Fund. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Willow Community Fund: Generic primary records CSV

Generic primary records CSV for Willow Community Fund. 3 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 3 rows
Use case: Data import

Pine Property Services: Linked operating model

Linked operating model for Pine Property Services. 57 records across 6 linked tables; no duplicate primary keys or missing references. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: JSON · Business Kits · 57 records
Use case: Data import

Pine Property Services: Operating model JSON Schema

Operating model JSON Schema for Pine Property Services. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Pine Property Services: Numeric expected results

Numeric expected results for Pine Property Services. Exact table counts, metric formulas, 12 chart points and three negative-test outcomes. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: JSON · Business Kits
Use case: Data import

Pine Property Services: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Pine Property Services. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Pine Property Services: Generic primary records CSV

Generic primary records CSV for Pine Property Services. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 6 rows
Use case: Data import

Juniper Workspace Cloud: Linked operating model

Linked operating model for Juniper Workspace Cloud. 75 records across 6 linked tables; no duplicate primary keys or missing references. Active monthly recurring revenue=235.00 USD; Paid invoices=649.00 USD; Outstanding invoices=19.00 USD.

File: JSON · Business Kits · 75 records
Use case: Data import

Juniper Workspace Cloud: Operating model JSON Schema

Operating model JSON Schema for Juniper Workspace Cloud. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Juniper Workspace Cloud: Numeric expected results

Numeric expected results for Juniper Workspace Cloud. Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Active monthly recurring revenue=235.00 USD; Paid invoices=649.00 USD; Outstanding invoices=19.00 USD.

File: JSON · Business Kits
Use case: Data import

Juniper Workspace Cloud: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Juniper Workspace Cloud. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Juniper Workspace Cloud: Generic primary records CSV

Generic primary records CSV for Juniper Workspace Cloud. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

File: CSV · Business Kits · 6 rows
Use case: Data import

csv

474 B

Fieldnote Supply Shop: Shopify profile CSV

Shopify profile CSV for Fieldnote Supply Shop. 6 unique records follow the documented Shopify field subset. Strict local specification checks pass; account import and stored results are not verified.

File: CSV · Business Kits · 6 rows
Use case: Data import

json

1.7 KB

Fieldnote Supply Shop: Shopify profile schema

Shopify profile schema for Fieldnote Supply Shop. 6 unique records follow the documented Shopify field subset. Strict local specification checks pass; account import and stored results are not verified.

File: JSON · Business Kits · 6 rows
Use case: Data import

csv

322 B

Fieldnote Supply Shop: Woocommerce profile CSV

Woocommerce profile CSV for Fieldnote Supply Shop. 6 unique records follow the documented Woocommerce field subset. Strict local specification checks pass; account import and stored results are not verified.

File: CSV · Business Kits · 6 rows
Use case: Data import

json

1.5 KB

Fieldnote Supply Shop: Woocommerce profile schema

Woocommerce profile schema for Fieldnote Supply Shop. 6 unique records follow the documented Woocommerce field subset. Strict local specification checks pass; account import and stored results are not verified.

File: JSON · Business Kits · 6 rows
Use case: Data import

csv

295 B

Tern Client Services: Hubspot profile CSV

Hubspot profile CSV for Tern Client Services. 8 unique records follow the documented Hubspot field subset. Strict local specification checks pass; account import and stored results are not verified.

File: CSV · Business Kits · 8 rows
Use case: Data import

json

1 KB

Tern Client Services: Hubspot profile schema

Hubspot profile schema for Tern Client Services. 8 unique records follow the documented Hubspot field subset. Strict local specification checks pass; account import and stored results are not verified.

File: JSON · Business Kits · 8 rows
Use case: Data import

csv

546 B

Fieldnote Supply Shop: Square profile CSV

Square profile CSV for Fieldnote Supply Shop. 6 unique records follow the documented Square field subset. Map these source fields into a current account export; this file is not a native Square import.

File: CSV · Business Kits · 6 rows
Use case: Data import

json

1.3 KB

Fieldnote Supply Shop: Square profile schema

Square profile schema for Fieldnote Supply Shop. 6 unique records follow the documented Square field subset. Map these source fields into a current account export; this file is not a native Square import.

File: JSON · Business Kits · 6 rows
Use case: Data import

Alder Table Bistro: Supplier price list CSV

Supplier price list CSV for Alder Table Bistro. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Alder Table Bistro: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Alder Table Bistro. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Alder Table Bistro: Purchase order lines CSV

Purchase order lines CSV for Alder Table Bistro. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-BST-1002 totals 329.53 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Alder Table Bistro: Goods-received note lines CSV

Goods-received note lines CSV for Alder Table Bistro. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-BST-2002, an item substitution on GRN-BST-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-BST-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Alder Table Bistro: Supplier invoice lines CSV

Supplier invoice lines CSV for Alder Table Bistro. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-BST-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-BST-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Alder Table Bistro: Credit note lines CSV

Credit note lines CSV for Alder Table Bistro. 2 credit lines, one per note. CN-BST-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-BST-7002 credits 5 units where GRN-BST-2004 records only 3 returned, an overstatement of 15.58 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Alder Table Bistro: Statements of account CSV

Statements of account CSV for Alder Table Bistro. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-BST-6001 closes at 1326.11 CAD and its four declared ageing buckets sum to exactly that. STM-BST-6002 closes at 1559.75 CAD while its declared buckets sum to 1566.76 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Alder Table Bistro: Remittance advice lines CSV

Remittance advice lines CSV for Alder Table Bistro. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 1120.68 CAD is settled and 1765.18 CAD is withheld against statement balances of 2885.86 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Alder Table Bistro: Three-way match report CSV

Three-way match report CSV for Alder Table Bistro. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Alder Table Bistro: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Alder Table Bistro. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Alder Table Bistro: Numeric expected results JSON

Numeric expected results JSON for Alder Table Bistro. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 1452.72 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Juniper Corner Cafe: Supplier price list CSV

Supplier price list CSV for Juniper Corner Cafe. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Juniper Corner Cafe. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Juniper Corner Cafe: Purchase order lines CSV

Purchase order lines CSV for Juniper Corner Cafe. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-CAF-1002 totals 348.83 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Goods-received note lines CSV

Goods-received note lines CSV for Juniper Corner Cafe. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-CAF-2002, an item substitution on GRN-CAF-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-CAF-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Supplier invoice lines CSV

Supplier invoice lines CSV for Juniper Corner Cafe. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-CAF-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-CAF-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Credit note lines CSV

Credit note lines CSV for Juniper Corner Cafe. 2 credit lines, one per note. CN-CAF-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-CAF-7002 credits 5 units where GRN-CAF-2004 records only 3 returned, an overstatement of 3.04 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Statements of account CSV

Statements of account CSV for Juniper Corner Cafe. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-CAF-6001 closes at 1726.12 CAD and its four declared ageing buckets sum to exactly that. STM-CAF-6002 closes at 1449.94 CAD while its declared buckets sum to 1460.86 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Remittance advice lines CSV

Remittance advice lines CSV for Juniper Corner Cafe. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 1235.99 CAD is settled and 1940.07 CAD is withheld against statement balances of 3176.06 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Three-way match report CSV

Three-way match report CSV for Juniper Corner Cafe. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Juniper Corner Cafe: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Juniper Corner Cafe. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Juniper Corner Cafe: Numeric expected results JSON

Numeric expected results JSON for Juniper Corner Cafe. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 1062.16 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Copper Oven Bakery: Supplier price list CSV

Supplier price list CSV for Copper Oven Bakery. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Copper Oven Bakery. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Copper Oven Bakery: Purchase order lines CSV

Purchase order lines CSV for Copper Oven Bakery. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-BAK-1002 totals 289.65 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Goods-received note lines CSV

Goods-received note lines CSV for Copper Oven Bakery. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-BAK-2002, an item substitution on GRN-BAK-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-BAK-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Supplier invoice lines CSV

Supplier invoice lines CSV for Copper Oven Bakery. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-BAK-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-BAK-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Credit note lines CSV

Credit note lines CSV for Copper Oven Bakery. 2 credit lines, one per note. CN-BAK-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-BAK-7002 credits 5 units where GRN-BAK-2004 records only 3 returned, an overstatement of 9.88 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Statements of account CSV

Statements of account CSV for Copper Oven Bakery. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-BAK-6001 closes at 740.74 CAD and its four declared ageing buckets sum to exactly that. STM-BAK-6002 closes at 1395.48 CAD while its declared buckets sum to 1396.87 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Remittance advice lines CSV

Remittance advice lines CSV for Copper Oven Bakery. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 946.62 CAD is settled and 1189.60 CAD is withheld against statement balances of 2136.22 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Three-way match report CSV

Three-way match report CSV for Copper Oven Bakery. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Copper Oven Bakery: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Copper Oven Bakery. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Copper Oven Bakery: Numeric expected results JSON

Numeric expected results JSON for Copper Oven Bakery. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 1261.85 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Ember Lane Pizza: Supplier price list CSV

Supplier price list CSV for Ember Lane Pizza. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Ember Lane Pizza. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Ember Lane Pizza: Purchase order lines CSV

Purchase order lines CSV for Ember Lane Pizza. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-PIZ-1002 totals 468.93 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Goods-received note lines CSV

Goods-received note lines CSV for Ember Lane Pizza. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-PIZ-2002, an item substitution on GRN-PIZ-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-PIZ-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Supplier invoice lines CSV

Supplier invoice lines CSV for Ember Lane Pizza. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-PIZ-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-PIZ-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Credit note lines CSV

Credit note lines CSV for Ember Lane Pizza. 2 credit lines, one per note. CN-PIZ-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-PIZ-7002 credits 5 units where GRN-PIZ-2004 records only 3 returned, an overstatement of 1.04 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Statements of account CSV

Statements of account CSV for Ember Lane Pizza. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-PIZ-6001 closes at 1107.20 CAD and its four declared ageing buckets sum to exactly that. STM-PIZ-6002 closes at 2166.98 CAD while its declared buckets sum to 2177.90 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Remittance advice lines CSV

Remittance advice lines CSV for Ember Lane Pizza. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 1450.33 CAD is settled and 1823.85 CAD is withheld against statement balances of 3274.18 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Three-way match report CSV

Three-way match report CSV for Ember Lane Pizza. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Ember Lane Pizza: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Ember Lane Pizza. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Ember Lane Pizza: Numeric expected results JSON

Numeric expected results JSON for Ember Lane Pizza. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 1892.29 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Cedar Street Tacos: Supplier price list CSV

Supplier price list CSV for Cedar Street Tacos. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Cedar Street Tacos. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Cedar Street Tacos: Purchase order lines CSV

Purchase order lines CSV for Cedar Street Tacos. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-TRK-1002 totals 104.33 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Goods-received note lines CSV

Goods-received note lines CSV for Cedar Street Tacos. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-TRK-2002, an item substitution on GRN-TRK-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-TRK-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Supplier invoice lines CSV

Supplier invoice lines CSV for Cedar Street Tacos. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-TRK-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-TRK-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Credit note lines CSV

Credit note lines CSV for Cedar Street Tacos. 2 credit lines, one per note. CN-TRK-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-TRK-7002 credits 5 units where GRN-TRK-2004 records only 3 returned, an overstatement of 0.42 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Statements of account CSV

Statements of account CSV for Cedar Street Tacos. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-TRK-6001 closes at 547.74 CAD and its four declared ageing buckets sum to exactly that. STM-TRK-6002 closes at 472.24 CAD while its declared buckets sum to 481.61 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Remittance advice lines CSV

Remittance advice lines CSV for Cedar Street Tacos. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 635.20 CAD is settled and 384.78 CAD is withheld against statement balances of 1019.98 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Three-way match report CSV

Three-way match report CSV for Cedar Street Tacos. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Cedar Street Tacos: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Cedar Street Tacos. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Cedar Street Tacos: Numeric expected results JSON

Numeric expected results JSON for Cedar Street Tacos. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 488.57 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Willow Event Kitchen: Supplier price list CSV

Supplier price list CSV for Willow Event Kitchen. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Willow Event Kitchen. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Willow Event Kitchen: Purchase order lines CSV

Purchase order lines CSV for Willow Event Kitchen. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-CAT-1002 totals 208.13 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Goods-received note lines CSV

Goods-received note lines CSV for Willow Event Kitchen. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-CAT-2002, an item substitution on GRN-CAT-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-CAT-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Supplier invoice lines CSV

Supplier invoice lines CSV for Willow Event Kitchen. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-CAT-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-CAT-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Credit note lines CSV

Credit note lines CSV for Willow Event Kitchen. 2 credit lines, one per note. CN-CAT-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-CAT-7002 credits 5 units where GRN-CAT-2004 records only 3 returned, an overstatement of 2.28 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Statements of account CSV

Statements of account CSV for Willow Event Kitchen. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-CAT-6001 closes at 1003.36 CAD and its four declared ageing buckets sum to exactly that. STM-CAT-6002 closes at 981.44 CAD while its declared buckets sum to 991.60 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Remittance advice lines CSV

Remittance advice lines CSV for Willow Event Kitchen. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 1088.50 CAD is settled and 896.30 CAD is withheld against statement balances of 1984.80 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Three-way match report CSV

Three-way match report CSV for Willow Event Kitchen. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Willow Event Kitchen: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Willow Event Kitchen. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Willow Event Kitchen: Numeric expected results JSON

Numeric expected results JSON for Willow Event Kitchen. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 952.38 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Harbour Kitchen Group: Supplier price list CSV

Supplier price list CSV for Harbour Kitchen Group. 48 rows covering 2 suppliers, 6 items and 4 effective dates (2026-08-05, 2026-08-12, 2026-08-19, 2026-08-26). Each row carries the list unit price, the case pack quantity, the price per case and a contract tier price that applies only at 250 units. Every purchase order line in this set is priced from the row matching its supplier, item and order date.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Supplier price list CSV, semicolon and decimal comma

Supplier price list CSV, semicolon and decimal comma for Harbour Kitchen Group. The same 48 price rows re-exported the way a European supplier portal writes them: UTF-8 with a byte-order mark (EF BB BF), semicolon field separators, CRLF line endings, and decimal commas in list_unit_price, price_per_case and contract_tier_unit_price. Column names, column order and every value are identical to price-list.csv; only the encoding and the separators differ.

File: CSV · Procure To Pay · 48 rows
Use case: Data importCSV parsing+1

Harbour Kitchen Group: Purchase order lines CSV

Purchase order lines CSV for Harbour Kitchen Group. 12 lines across 4 purchase orders dated 2026-08-05 to 2026-08-26. Each line repeats its order's net, tax and gross totals, so a reader can check that the line values sum to the header without a second file. Order PO-GRP-1002 totals 325.41 CAD including GST.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Goods-received note lines CSV

Goods-received note lines CSV for Harbour Kitchen Group. 12 received lines across 4 goods-received notes. Three lines are exceptions: a short delivery of 4 units on GRN-GRP-2002, an item substitution on GRN-GRP-2003 where the delivered ingredient id differs from the ordered one, and a part return of 3 units on GRN-GRP-2004. accepted_quantity equals delivered_quantity minus returned_quantity on every row.

File: CSV · Procure To Pay · 12 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Supplier invoice lines CSV

Supplier invoice lines CSV for Harbour Kitchen Group. 14 lines across 5 invoice documents that carry only 4 distinct invoice numbers: INV-GRP-5002 appears twice, dated 2026-08-14 and 2026-08-17. invoice_number is therefore not a key; the pair of invoice_number and invoice_date is. invoice_stated_tax_total is the figure printed on the document, which for INV-GRP-5003 is one cent above the sum of its line tax amounts.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Credit note lines CSV

Credit note lines CSV for Harbour Kitchen Group. 2 credit lines, one per note. CN-GRP-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-GRP-7002 credits 5 units where GRN-GRP-2004 records only 3 returned, an overstatement of 3.80 CAD net.

File: CSV · Procure To Pay · 2 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Statements of account CSV

Statements of account CSV for Harbour Kitchen Group. 13 transaction rows across 2 month-end statements dated 2026-08-31. STM-GRP-6001 closes at 1317.12 CAD and its four declared ageing buckets sum to exactly that. STM-GRP-6002 closes at 1333.12 CAD while its declared buckets sum to 1342.11 CAD.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Remittance advice lines CSV

Remittance advice lines CSV for Harbour Kitchen Group. 13 lines, one for every document on both statements, each marked paid or withheld with a reason. 1041.96 CAD is settled and 1608.28 CAD is withheld against statement balances of 2650.24 CAD; the first two figures sum to the third.

File: CSV · Procure To Pay · 13 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Three-way match report CSV

Three-way match report CSV for Harbour Kitchen Group. 14 rows joining every invoice line to its purchase order line and its goods-received line. 9 rows match on item, quantity and price; the remaining 5 carry a match_result of duplicate-invoice-number, item-substituted, matched-credit-expected, quantity-variance and a note giving the exact variance.

File: CSV · Procure To Pay · 14 rows
Use case: Data importCSV parsing+1

Harbour Kitchen Group: Whole procure-to-pay chain JSON

Whole procure-to-pay chain JSON for Harbour Kitchen Group. One object holding the buyer, both suppliers, all 6 items, the 48-row price list, 4 purchase orders, 4 goods-received notes, 5 invoice documents, 2 credit notes, 2 statements, the remittance advice, the 14-row three-way match and the 6 deliberate defects. Every monetary value is a JSON string with exactly two decimal places.

File: JSON · Procure To Pay
Use case: Data importJSON parsing

Harbour Kitchen Group: Numeric expected results JSON

Numeric expected results JSON for Harbour Kitchen Group. The exact numbers a test asserts: document counts, per-order and per-invoice totals, both tax conventions for every invoice, declared and true ageing for both statements, the remittance reconciliation identity, the 5 three-way match outcomes and all 6 deliberate defects with the assertion that detects each one. The correct purchase order net at list price is 977.16 CAD.

File: JSON · Procure To Pay
Use case: Data importJSON parsing+1

Alder Table Bistro: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Alder Table Bistro. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 0 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Alder Table Bistro: Plate costing lines

Plate costing lines for Alder Table Bistro. 12 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 1.01 to 3.07 CAD.

File: CSV · Restaurant Costing · 12 rows
Use case: Data importCSV parsing· Conversion set

Alder Table Bistro: Plate costing document

Plate costing document for Alder Table Bistro. A nested JSON document with 4 dishes and 12 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Alder Table Bistro: Yield test results

Yield test results for Alder Table Bistro. 5 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 5 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing

Alder Table Bistro: Inventory count sheet

Inventory count sheet for Alder Table Bistro. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 0 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Alder Table Bistro: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Alder Table Bistro. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Alder Table Bistro: Cost of goods sold document

Cost of goods sold document for Alder Table Bistro. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1736.91, purchases 2834.82, closing 2996.92, cost of goods sold 1574.81 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Alder Table Bistro: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Alder Table Bistro. Intentionally inconsistent. Row 3 reports a closing count of 22.20 kg for ING-03 (Potatoes), the counted figure with the two decimal digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 22.02 kg. Every derived value follows the wrong count, so the file is internally consistent and its total of 1574.49 CAD differs from the correct 1574.81 CAD by -0.32 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Alder Table Bistro: Waste and spoilage log

Waste and spoilage log for Alder Table Bistro. 15 dated waste entries across 11 columns, totalling 37.87 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Alder Table Bistro: Product mix report

Product mix report for Alder Table Bistro. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 15780.80 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Alder Table Bistro: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Alder Table Bistro. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Roast chicken plate (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Alder Table Bistro: Daily Z-read and cash-up

Daily Z-read and cash-up for Alder Table Bistro. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 896.00 less discounts 89.60 and comps 11.50 gives net sales 794.90; with GST 39.75 and charged tips 95.39 the total due is 930.04 CAD. Cash, card and gift tenders sum to the 917.54 collected after a 12.50 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 24 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Alder Table Bistro: Daily Z-read as structured data

Daily Z-read as structured data for Alder Table Bistro. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Alder Table Bistro: Tip pool distribution

Tip pool distribution for Alder Table Bistro. 4 allocation rows and one total row for 2026-08-28. The declared pool of 138.14 CAD is 95.39 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 138.14 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Alder Table Bistro: Tip pool that is one cent short

Tip pool that is one cent short for Alder Table Bistro. Intentionally inconsistent. The last allocation row (EMP-04) reads 36.25 where the exact largest-remainder share is 36.26. The allocation rows therefore sum to 138.13 CAD while the total row still declares the pool as 138.14 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Alder Table Bistro: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Alder Table Bistro. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Alder Table Bistro: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Alder Table Bistro. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Alder Table Bistro: HACCP temperature log

HACCP temperature log for Alder Table Bistro. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Alder Table Bistro: Cleaning schedule

Cleaning schedule for Alder Table Bistro. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Alder Table Bistro: Allergen matrix

Allergen matrix for Alder Table Bistro. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 2 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Alder Table Bistro: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Alder Table Bistro. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Potato gratin) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: milk: Cream.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Juniper Corner Cafe. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 0 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Juniper Corner Cafe: Plate costing lines

Plate costing lines for Juniper Corner Cafe. 8 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 0.70 to 1.68 CAD.

File: CSV · Restaurant Costing · 8 rows
Use case: Data importCSV parsing· Conversion set

Juniper Corner Cafe: Plate costing document

Plate costing document for Juniper Corner Cafe. A nested JSON document with 4 dishes and 8 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Juniper Corner Cafe: Yield test results

Yield test results for Juniper Corner Cafe. 2 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 2 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 2 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Inventory count sheet

Inventory count sheet for Juniper Corner Cafe. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 1 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Juniper Corner Cafe: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Juniper Corner Cafe. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Juniper Corner Cafe: Cost of goods sold document

Cost of goods sold document for Juniper Corner Cafe. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1543.40, purchases 2159.69, closing 2164.95, cost of goods sold 1538.14 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Juniper Corner Cafe: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Juniper Corner Cafe. Intentionally inconsistent. Row 3 reports a closing count of 60.57 l for ING-03 (Oat Drink), the counted figure with the two decimal digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 60.75 l. Every derived value follows the wrong count, so the file is internally consistent and its total of 1538.64 CAD differs from the correct 1538.14 CAD by 0.50 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Juniper Corner Cafe: Waste and spoilage log

Waste and spoilage log for Juniper Corner Cafe. 15 dated waste entries across 11 columns, totalling 63.66 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Juniper Corner Cafe: Product mix report

Product mix report for Juniper Corner Cafe. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 10234.74 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Corner Cafe: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Juniper Corner Cafe. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Flat white (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Daily Z-read and cash-up

Daily Z-read and cash-up for Juniper Corner Cafe. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 608.75 less discounts 60.88 and comps 5.50 gives net sales 542.37; with GST 27.12 and charged tips 65.08 the total due is 634.57 CAD. Cash, card and gift tenders sum to the 624.07 collected after a 10.50 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 28 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Juniper Corner Cafe: Daily Z-read as structured data

Daily Z-read as structured data for Juniper Corner Cafe. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Juniper Corner Cafe: Tip pool distribution

Tip pool distribution for Juniper Corner Cafe. 4 allocation rows and one total row for 2026-08-28. The declared pool of 107.83 CAD is 65.08 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 107.83 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Corner Cafe: Tip pool that is one cent short

Tip pool that is one cent short for Juniper Corner Cafe. Intentionally inconsistent. The last allocation row (EMP-04) reads 28.29 where the exact largest-remainder share is 28.30. The allocation rows therefore sum to 107.82 CAD while the total row still declares the pool as 107.83 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Juniper Corner Cafe. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Juniper Corner Cafe. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: HACCP temperature log

HACCP temperature log for Juniper Corner Cafe. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Juniper Corner Cafe: Cleaning schedule

Cleaning schedule for Juniper Corner Cafe. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Juniper Corner Cafe: Allergen matrix

Allergen matrix for Juniper Corner Cafe. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 4 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Corner Cafe: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Juniper Corner Cafe. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Breakfast sandwich) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: cereals_gluten: Sourdough Bread; eggs: Eggs.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Copper Oven Bakery. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 0 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Copper Oven Bakery: Plate costing lines

Plate costing lines for Copper Oven Bakery. 11 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 0.36 to 0.86 CAD.

File: CSV · Restaurant Costing · 11 rows
Use case: Data importCSV parsing· Conversion set

Copper Oven Bakery: Plate costing document

Plate costing document for Copper Oven Bakery. A nested JSON document with 4 dishes and 11 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Copper Oven Bakery: Yield test results

Yield test results for Copper Oven Bakery. 2 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 2 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 2 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Inventory count sheet

Inventory count sheet for Copper Oven Bakery. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 1 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Copper Oven Bakery: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Copper Oven Bakery. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Copper Oven Bakery: Cost of goods sold document

Cost of goods sold document for Copper Oven Bakery. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1479.58, purchases 2420.01, closing 3276.15, cost of goods sold 623.44 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Copper Oven Bakery: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Copper Oven Bakery. Intentionally inconsistent. Row 3 reports a closing count of 102.00 each for ING-03 (Eggs), the counted figure with the last two whole digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 120.00 each. Every derived value follows the wrong count, so the file is internally consistent and its total of 629.74 CAD differs from the correct 623.44 CAD by 6.30 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Copper Oven Bakery: Waste and spoilage log

Waste and spoilage log for Copper Oven Bakery. 15 dated waste entries across 11 columns, totalling 30.33 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct. WASTE-001 lands exactly on a half cent, so a reader that rounds half to even reports a cent less on that row than this file, which rounds half up like every other value in the folder.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Copper Oven Bakery: Product mix report

Product mix report for Copper Oven Bakery. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 6651.14 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Copper Oven Bakery: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Copper Oven Bakery. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Yeasted loaf (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Daily Z-read and cash-up

Daily Z-read and cash-up for Copper Oven Bakery. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 396.75 less discounts 39.68 and comps 4.25 gives net sales 352.82; with GST 17.64 and charged tips 42.34 the total due is 412.80 CAD. Cash, card and gift tenders sum to the 408.30 collected after a 4.50 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 31 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Copper Oven Bakery: Daily Z-read as structured data

Daily Z-read as structured data for Copper Oven Bakery. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Copper Oven Bakery: Tip pool distribution

Tip pool distribution for Copper Oven Bakery. 4 allocation rows and one total row for 2026-08-28. The declared pool of 85.09 CAD is 42.34 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 85.09 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Copper Oven Bakery: Tip pool that is one cent short

Tip pool that is one cent short for Copper Oven Bakery. Intentionally inconsistent. The last allocation row (EMP-04) reads 22.32 where the exact largest-remainder share is 22.33. The allocation rows therefore sum to 85.08 CAD while the total row still declares the pool as 85.09 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Copper Oven Bakery. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Copper Oven Bakery. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: HACCP temperature log

HACCP temperature log for Copper Oven Bakery. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Copper Oven Bakery: Cleaning schedule

Cleaning schedule for Copper Oven Bakery. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Copper Oven Bakery: Allergen matrix

Allergen matrix for Copper Oven Bakery. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 4 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Copper Oven Bakery: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Copper Oven Bakery. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Sweet butter roll) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: cereals_gluten: Bread Flour; milk: Butter.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Ember Lane Pizza. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 3 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Ember Lane Pizza: Plate costing lines

Plate costing lines for Ember Lane Pizza. 18 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 2.00 to 2.75 CAD.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing· Conversion set

Ember Lane Pizza: Plate costing document

Plate costing document for Ember Lane Pizza. A nested JSON document with 4 dishes and 18 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Ember Lane Pizza: Yield test results

Yield test results for Ember Lane Pizza. 2 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 2 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 2 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Inventory count sheet

Inventory count sheet for Ember Lane Pizza. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 1 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Ember Lane Pizza: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Ember Lane Pizza. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Ember Lane Pizza: Cost of goods sold document

Cost of goods sold document for Ember Lane Pizza. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 3388.69, purchases 3636.18, closing 3914.44, cost of goods sold 3110.43 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Ember Lane Pizza: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Ember Lane Pizza. Intentionally inconsistent. Row 3 reports a closing count of 23.52 kg for ING-03 (Crushed Tomatoes), the counted figure with the two decimal digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 23.25 kg. Every derived value follows the wrong count, so the file is internally consistent and its total of 3109.68 CAD differs from the correct 3110.43 CAD by -0.75 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Ember Lane Pizza: Waste and spoilage log

Waste and spoilage log for Ember Lane Pizza. 15 dated waste entries across 11 columns, totalling 43.81 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Ember Lane Pizza: Product mix report

Product mix report for Ember Lane Pizza. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 25954.50 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Ember Lane Pizza: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Ember Lane Pizza. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Margherita pizza (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Daily Z-read and cash-up

Daily Z-read and cash-up for Ember Lane Pizza. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1582.50 less discounts 158.25 and comps 20.00 gives net sales 1404.25; with GST 70.21 and charged tips 168.51 the total due is 1642.97 CAD. Cash, card and gift tenders sum to the 1624.97 collected after a 18.00 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 34 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Ember Lane Pizza: Daily Z-read as structured data

Daily Z-read as structured data for Ember Lane Pizza. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Ember Lane Pizza: Tip pool distribution

Tip pool distribution for Ember Lane Pizza. 4 allocation rows and one total row for 2026-08-28. The declared pool of 211.26 CAD is 168.51 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 211.26 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Ember Lane Pizza: Tip pool that is one cent short

Tip pool that is one cent short for Ember Lane Pizza. Intentionally inconsistent. The last allocation row (EMP-04) reads 55.44 where the exact largest-remainder share is 55.45. The allocation rows therefore sum to 211.25 CAD while the total row still declares the pool as 211.26 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Ember Lane Pizza. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Ember Lane Pizza. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: HACCP temperature log

HACCP temperature log for Ember Lane Pizza. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Ember Lane Pizza: Cleaning schedule

Cleaning schedule for Ember Lane Pizza. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Ember Lane Pizza: Allergen matrix

Allergen matrix for Ember Lane Pizza. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 4 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Ember Lane Pizza: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Ember Lane Pizza. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Basil tomato pizza) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: cereals_gluten: Pizza Flour; milk: Mozzarella.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Cedar Street Tacos. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 1 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Cedar Street Tacos: Plate costing lines

Plate costing lines for Cedar Street Tacos. 18 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 1.18 to 2.11 CAD.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing· Conversion set

Cedar Street Tacos: Plate costing document

Plate costing document for Cedar Street Tacos. A nested JSON document with 4 dishes and 18 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Cedar Street Tacos: Yield test results

Yield test results for Cedar Street Tacos. 3 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 3 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Inventory count sheet

Inventory count sheet for Cedar Street Tacos. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 2 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts. Theoretical closing on CNT-03 lands exactly on a half hundredth of a stock unit, so a reader that rounds half to even prints a different figure than this file, which rounds half up throughout.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Cedar Street Tacos: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Cedar Street Tacos. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Cedar Street Tacos: Cost of goods sold document

Cost of goods sold document for Cedar Street Tacos. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1911.28, purchases 972.73, closing 324.44, cost of goods sold 2559.57 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Cedar Street Tacos: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Cedar Street Tacos. Intentionally inconsistent. Row 3 reports a closing count of 21.97 kg for ING-03 (Black Beans), the counted figure with the two decimal digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 21.79 kg. Every derived value follows the wrong count, so the file is internally consistent and its total of 2559.14 CAD differs from the correct 2559.57 CAD by -0.43 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Cedar Street Tacos: Waste and spoilage log

Waste and spoilage log for Cedar Street Tacos. 15 dated waste entries across 11 columns, totalling 14.33 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Cedar Street Tacos: Product mix report

Product mix report for Cedar Street Tacos. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 19374.60 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Cedar Street Tacos: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Cedar Street Tacos. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Chicken taco trio (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Daily Z-read and cash-up

Daily Z-read and cash-up for Cedar Street Tacos. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1197.00 less discounts 119.70 and comps 11.00 gives net sales 1066.30; with GST 53.32 and charged tips 127.96 the total due is 1247.58 CAD. Cash, card and gift tenders sum to the 1235.58 collected after a 12.00 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 37 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Cedar Street Tacos: Daily Z-read as structured data

Daily Z-read as structured data for Cedar Street Tacos. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Cedar Street Tacos: Tip pool distribution

Tip pool distribution for Cedar Street Tacos. 4 allocation rows and one total row for 2026-08-28. The declared pool of 170.71 CAD is 127.96 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 170.71 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Cedar Street Tacos: Tip pool that is one cent short

Tip pool that is one cent short for Cedar Street Tacos. Intentionally inconsistent. The last allocation row (EMP-04) reads 44.80 where the exact largest-remainder share is 44.81. The allocation rows therefore sum to 170.70 CAD while the total row still declares the pool as 170.71 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Cedar Street Tacos. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Cedar Street Tacos. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: HACCP temperature log

HACCP temperature log for Cedar Street Tacos. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Cedar Street Tacos: Cleaning schedule

Cleaning schedule for Cedar Street Tacos. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Cedar Street Tacos: Allergen matrix

Allergen matrix for Cedar Street Tacos. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 0 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Cedar Street Tacos: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Cedar Street Tacos. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Bean bowl) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: none declared from the costed recipe lines.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Willow Event Kitchen. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 1 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Willow Event Kitchen: Plate costing lines

Plate costing lines for Willow Event Kitchen. 19 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 0.72 to 2.19 CAD.

File: CSV · Restaurant Costing · 19 rows
Use case: Data importCSV parsing· Conversion set

Willow Event Kitchen: Plate costing document

Plate costing document for Willow Event Kitchen. A nested JSON document with 4 dishes and 19 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Willow Event Kitchen: Yield test results

Yield test results for Willow Event Kitchen. 2 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 2 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 2 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Inventory count sheet

Inventory count sheet for Willow Event Kitchen. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 1 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Willow Event Kitchen: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Willow Event Kitchen. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Willow Event Kitchen: Cost of goods sold document

Cost of goods sold document for Willow Event Kitchen. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1100.18, purchases 1886.41, closing 879.96, cost of goods sold 2106.63 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Willow Event Kitchen: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Willow Event Kitchen. Intentionally inconsistent. Row 3 reports a closing count of 22.91 kg for ING-03 (Chickpeas), the counted figure with the two decimal digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 22.19 kg. Every derived value follows the wrong count, so the file is internally consistent and its total of 2104.76 CAD differs from the correct 2106.63 CAD by -1.87 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Willow Event Kitchen: Waste and spoilage log

Waste and spoilage log for Willow Event Kitchen. 15 dated waste entries across 11 columns, totalling 25.38 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Willow Event Kitchen: Product mix report

Product mix report for Willow Event Kitchen. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 28781.90 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Willow Event Kitchen: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Willow Event Kitchen. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "Chicken buffet portion (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Daily Z-read and cash-up

Daily Z-read and cash-up for Willow Event Kitchen. A 62-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1795.50 less discounts 179.55 and comps 18.00 gives net sales 1597.95; with GST 79.90 and charged tips 191.75 the total due is 1869.60 CAD. Cash, card and gift tenders sum to the 1854.60 collected after a 15.00 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 40 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Willow Event Kitchen: Daily Z-read as structured data

Daily Z-read as structured data for Willow Event Kitchen. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Willow Event Kitchen: Tip pool distribution

Tip pool distribution for Willow Event Kitchen. 4 allocation rows and one total row for 2026-08-28. The declared pool of 234.50 CAD is 191.75 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 234.50 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing· Paired fixture

Willow Event Kitchen: Tip pool that is one cent short

Tip pool that is one cent short for Willow Event Kitchen. Intentionally inconsistent. The last allocation row (EMP-04) reads 61.55 where the exact largest-remainder share is 61.56. The allocation rows therefore sum to 234.49 CAD while the total row still declares the pool as 234.50 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Willow Event Kitchen. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Willow Event Kitchen. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: HACCP temperature log

HACCP temperature log for Willow Event Kitchen. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Willow Event Kitchen: Cleaning schedule

Cleaning schedule for Willow Event Kitchen. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Willow Event Kitchen: Allergen matrix

Allergen matrix for Willow Event Kitchen. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 3 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Willow Event Kitchen: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Willow Event Kitchen. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Reception plate) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: milk: Yogurt.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: Purchase pack to recipe unit conversions

Purchase pack to recipe unit conversions for Harbour Kitchen Group. 6 ingredients across 16 columns. Each row carries the purchase pack, the pack price, the cost per stock unit to six decimal places, the cost per recipe unit to eight, and the purchase id, date and supplier the price came from. 0 row(s) report a non-zero rounding residual because the pack size is not a whole number of stock units.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Plate costing lines

Plate costing lines for Harbour Kitchen Group. 10 recipe lines across 4 menu items, 17 columns. Recipe quantities are in grams, millilitres or each; the as-purchased quantity divides by the yield, so the line cost is not a naive multiplication. Plate costs run 0.79 to 3.08 CAD.

File: CSV · Restaurant Costing · 10 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Plate costing document

Plate costing document for Harbour Kitchen Group. A nested JSON document with 4 dishes and 10 recipe lines, an ingredient block carrying the pack and reference purchase for every price, and an explicit roundingRules object naming the decimal places used at each step.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Harbour Kitchen Group: Yield test results

Yield test results for Harbour Kitchen Group. 4 yield tests across 17 columns: raw weight, trim waste, trimmed weight, trim yield percent, cooked weight, cooking loss percent and the overall yield factor. All 4 rows report matches_recipe=yes, meaning each measured trim yield equals the yield percent that plate-costs.csv applies to the same ingredient.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Inventory count sheet

Inventory count sheet for Harbour Kitchen Group. 6 ingredients across 17 columns: par level, opening count, receipts, theoretical usage, recorded waste, theoretical closing, counted closing and the variance between them, priced at standard cost. 1 item(s) close below par. These counted closing quantities are the ones cogs-report-inconsistent.csv contradicts.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Inventory count sheet as transcribed

Inventory count sheet as transcribed for Harbour Kitchen Group. The same closing counts as inventory-count-sheet.csv, in the shape a paper count actually arrives in. CRLF line endings, a UTF-8 byte order mark, a semicolon delimiter and a decimal comma. Two blank lines, one section banner that is not a record, one ingredient split across two locations, one counted as whole packs plus a remainder, one superseded mid-shift row at 14:20, trailing whitespace in three fields, a leading-zero bin code, an empty bin code, and one record carrying ten fields where the header declares 9. Every quirk is named in README.md.

File: CSV · Restaurant Costing · UTF-8 with BOM
Use case: Data importCSV parsing+2· Conversion set

Harbour Kitchen Group: Cost of goods sold document

Cost of goods sold document for Harbour Kitchen Group. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 2124.44, purchases 1963.44, closing 846.80, cost of goods sold 3241.08 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Harbour Kitchen Group: Cost of goods sold that contradicts the count sheet

Cost of goods sold that contradicts the count sheet for Harbour Kitchen Group. Intentionally inconsistent. Row 3 reports a closing count of 91.00 each for ING-03 (Beef Patty), the counted figure with the last two whole digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 19.00 each. Every derived value follows the wrong count, so the file is internally consistent and its total of 3075.48 CAD differs from the correct 3241.08 CAD by -165.60 CAD.

File: CSV · Restaurant Costing · 7 rows
Use case: Data importError handling+1· Conversion set

Harbour Kitchen Group: Waste and spoilage log

Waste and spoilage log for Harbour Kitchen Group. 15 dated waste entries across 11 columns, totalling 31.90 CAD at standard cost. The quantities per ingredient are exactly the recorded waste that inventory-variance.xlsx and cogs-report.xlsx deduct.

File: CSV · Restaurant Costing · 15 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Product mix report

Product mix report for Harbour Kitchen Group. 4 menu items across 12 columns for 2026-08-20 to 2026-09-02: quantity sold, mix percent, gross, discount, net, share of net, plate cost, item cost, item margin and item food-cost percent. Quantities and net sales match the shared sales table row for row; total net is 26214.00 CAD.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Harbour Kitchen Group: Product mix carrying items the menu does not have

Product mix carrying items the menu does not have for Harbour Kitchen Group. Intentionally inconsistent. 6 rows where sales-mix-pmix.csv has 4. MENU-90 and MENU-91 are not in the shared menu table, and the first row renames MENU-01 to "House burger (lunch)", which has a doubled space and a suffix the menu does not carry. The remaining rows are correct.

File: CSV · Restaurant Costing · 6 rows
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: Daily Z-read and cash-up

Daily Z-read and cash-up for Harbour Kitchen Group. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1650.00 less discounts 165.00 and comps 19.50 gives net sales 1465.50; with GST 73.28 and charged tips 175.86 the total due is 1714.64 CAD. Cash, card and gift tenders sum to the 1702.64 collected after a 12.00 refund. 2 voids are logged outside gross sales and the drawer records an over/short of -0.35 on 44 covers.

File: TXT · Restaurant Costing · UTF-8
Use case: Data importLog parsing· Paired fixture

Harbour Kitchen Group: Daily Z-read as structured data

Daily Z-read as structured data for Harbour Kitchen Group. The same Z-read as JSON: 4 item lines, a summary block, 3 tender lines that sum to the total collected, 2 voids, one comp, 1 refund traced to its sales id, and a cash drawer block whose expected figure less the counted figure equals the declared over/short of -0.35 CAD.

File: JSON · Restaurant Costing · UTF-8
Use case: Data importJSON parsing· Paired fixture

Harbour Kitchen Group: Tip pool distribution

Tip pool distribution for Harbour Kitchen Group. 4 allocation rows and one total row for 2026-08-28. The declared pool of 218.61 CAD is 175.86 charged to card plus 42.75 declared cash, split 30 percent to back of house, then allocated within each group by hours times a role weight. Whole cents are assigned by largest remainder, so the rows sum to 218.61 CAD, which equals the pool exactly.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Tip pool that is one cent short

Tip pool that is one cent short for Harbour Kitchen Group. Intentionally inconsistent. The last allocation row (EMP-04) reads 57.38 where the exact largest-remainder share is 57.39. The allocation rows therefore sum to 218.60 CAD while the total row still declares the pool as 218.61 CAD, a shortfall of exactly 0.01 CAD.

File: CSV · Restaurant Costing · 5 rows
Use case: Data importError handling+1· Conversion set

Harbour Kitchen Group: Labour schedule with split and overnight shifts

Labour schedule with split and overnight shifts for Harbour Kitchen Group. 74 shift segments across 17 columns for 2026-08-20 to 2026-09-02, totalling 413.00 paid hours and 9634.00 CAD of base pay. 14 shifts are split into two segments with an unpaid gap, and 9 segments end on the following calendar day, including SHIFT-056 which runs 22:30 on 2026-09-02 to 05:30 on 2026-09-03. 4 rows are authored cover shifts; the rest reproduce the shared staffing table hour for hour.

File: CSV · Restaurant Costing · 74 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Overtime computed on the wrong week boundary

Overtime computed on the wrong week boundary for Harbour Kitchen Group. Intentionally inconsistent. The same 74 shift segments are grouped into Sunday-start work weeks where the declared policy, and labour-hours-overtime.xlsx, start each week on Monday. The correct grouping yields 5.00 payable overtime hours and 51.50 CAD of premium; this file yields 3.00 hours and 31.50 CAD. The hours that disappear belong to EMP-01 in the week beginning 2026-08-24, whose 46.00 hours the Sunday grouping splits across two weeks.

File: CSV · Restaurant Costing · 24 rows
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: HACCP temperature log

HACCP temperature log for Harbour Kitchen Group. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.

File: CSV · Restaurant Costing · 84 rows
Use case: Data importCSV parsing+1

Harbour Kitchen Group: Cleaning schedule

Cleaning schedule for Harbour Kitchen Group. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.

File: CSV · Restaurant Costing · 18 rows
Use case: Data importCSV parsing

Harbour Kitchen Group: Allergen matrix

Allergen matrix for Harbour Kitchen Group. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 3 of 4 dishes declare at least one allergen.

File: CSV · Restaurant Costing · 4 rows
Use case: Data importCSV parsing· Paired fixture

Harbour Kitchen Group: Allergen matrix missing a menu item

Allergen matrix missing a menu item for Harbour Kitchen Group. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-03 (Loaded fries) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: milk: Whole Milk.

File: CSV · Restaurant Costing · 3 rows
Use case: Data importError handling+1· Paired fixture

Fieldnote Supply Shop: Order export CSV

Order export CSV for Fieldnote Supply Shop. 12 orders over 2026-08-01 to 2026-08-12 across 6 tax jurisdictions. merchandise_subtotal minus discount_total equals taxable_amount on every row, tax_amount equals taxable_amount times tax_rate rounded half up, and order_total equals taxable_amount plus tax_amount. Column totals: 942.00 merchandise, 20.00 discount, 922.00 taxable, 96.34 tax.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data import· Conversion set

Fieldnote Supply Shop: Order export JSON

Order export JSON for Fieldnote Supply Shop. The same 12 orders as orders-export.csv with an added totals object. totals.taxableAmount is 922.00 and equals the sum of the per-order taxable_amount values.

File: JSON · Ecommerce Documents · 12 rows
Use case: Data import· Conversion set

Fieldnote Supply Shop: Order export in the European CSV dialect

Order export in the European CSV dialect for Fieldnote Supply Shop. The same 12 orders written with a semicolon delimiter, decimal commas, dot thousands separators and dd/mm/yyyy dates. The first data row reads ORD-001;01/08/2026 and its order_total field is 38,06.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Order export with a UTF-8 BOM and US dates

Order export with a UTF-8 BOM and US dates for Fieldnote Supply Shop. Identical order data to orders-export.csv, but the file opens with the three bytes EF BB BF and the dates are mm/dd/yyyy. The first header cell is therefore order_id preceded by the BOM, which a reader that does not strip it reports as '\ufeffor der_id' with the BOM glued to the name.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Order export encoded as ISO-8859-1

Order export encoded as ISO-8859-1 for Fieldnote Supply Shop. The same 12 orders encoded in ISO-8859-1 (Latin-1) rather than UTF-8. Every byte is below 0x80 in this particular export, so it is byte-identical to the UTF-8 form and is the control case for an encoding test: a detector must not claim to have proved UTF-8 from content that is pure ASCII.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Order export with a header and no rows

Order export with a header and no rows for Fieldnote Supply Shop. A well-formed export for a period with no orders: one header line naming all 13 columns and nothing after it. The file is 163 bytes and ends with a single LF.

File: CSV · Ecommerce Documents · 0 rows
Use case: Data import

Fieldnote Supply Shop: Order export with exactly one row

Order export with exactly one row for Fieldnote Supply Shop. One header line and one data row, order ORD-001 for CUS-01 with an order_total of 38.06. The boundary case for readers that infer column types from a sample, which have exactly one observation per column here.

File: CSV · Ecommerce Documents · 1 row
Use case: Data import

Fieldnote Supply Shop: Order export whose row 7 has an extra field

Order export whose row 7 has an extra field for Fieldnote Supply Shop. Byte-for-byte the same as orders-export.csv except that data row 7 (order ORD-007, file line 8) carries 14 fields where the header declares 13. The surplus field holds the literal text gift-wrap.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data importError handling

Fieldnote Supply Shop: Order line export CSV

Order line export CSV for Fieldnote Supply Shop. 24 order lines, two per order, each naming the variant actually sold. quantity times unit_price equals line_total on every row and the line totals sum to 942.00, which is the merchandise_subtotal column of orders-export.csv before discounts.

File: CSV · Ecommerce Documents · 24 rows
Use case: Data import

Fieldnote Supply Shop: Refund and partial-refund export

Refund and partial-refund export for Fieldnote Supply Shop. 4 refunds: 2 return the whole line and 2 return one unit of a multi-unit line. merchandise_refund totals 80.00 and matches the refunded column of the shop payments table; tax_refund totals 7.46 and is charged at the order jurisdiction rate on the merchandise refunded.

File: CSV · Ecommerce Documents · 4 rows
Use case: Data import

Fieldnote Supply Shop: Refund export JSON

Refund export JSON for Fieldnote Supply Shop. The same 4 refunds as refunds.csv plus the stated refund policy: the order-level promotion is not clawed back when a line is refunded. totals.merchandiseRefund is 80.00.

File: JSON · Ecommerce Documents · 4 rows
Use case: Data import

Fieldnote Supply Shop: Refund export that refunds more than was captured

Refund export that refunds more than was captured for Fieldnote Supply Shop. The four valid refunds from refunds.csv plus three rows against order ORD-005, whose captured amount is 78.00. Those three rows refund 36.00, 42.00 and a further 18.00 of merchandise, a total of 96.00, which exceeds the capture by 18.00. RFND-007 also refunds LINE-009 a second time after RFND-005 already returned both units.

File: CSV · Ecommerce Documents · 7 rows
Use case: Data importError handling

Fieldnote Supply Shop: Returns and RMA register

Returns and RMA register for Fieldnote Supply Shop. 4 return authorisations, one per refund in refunds.csv, each with a requested date four days before the received date and a disposition of return to saleable stock. Every row restocks, so the returned quantities are the ones the inventory feed adds back.

File: CSV · Ecommerce Documents · 4 rows
Use case: Data import

Fieldnote Supply Shop: Returns and RMA register XML

Returns and RMA register XML for Fieldnote Supply Shop. The same 4 authorisations as returns-rma.csv as XML. The root element ReturnAuthorisations declares count="4" and contains exactly that many ReturnAuthorisation children, each with 11 child elements.

File: XML · Ecommerce Documents · 4 rows
Use case: Data import

Fieldnote Supply Shop: Shipping manifest

Shipping manifest for Fieldnote Supply Shop. 10 shipments, one for each of the 10 fulfilled orders; the two orders still processing are absent. billable_weight_kg is the sum of the unit weights on the order plus 0.250 kg of packaging, carried to three decimals. The manifest moves 38 units weighing 21.450 kg with a declared value of 709.00.

File: CSV · Ecommerce Documents · 10 rows
Use case: Data import

Fieldnote Supply Shop: Shipping manifest JSON

Shipping manifest JSON for Fieldnote Supply Shop. The same 10 shipments as shipping-manifest.csv with a totals object declaring 38 units and 21.450 kg of billable weight.

File: JSON · Ecommerce Documents · 10 rows
Use case: Data import

Fieldnote Supply Shop: Multi-jurisdiction tax summary

Multi-jurisdiction tax summary for Fieldnote Supply Shop. 6 jurisdictions across 2 countries, each with its own rate from 0.08250 to 0.13000. Taxable sales total 922.00, tax collected 96.34, tax refunded 7.46 and net tax due 88.88. net_tax_due equals tax_collected minus tax_refunded on every row. tax_collected is the sum of the per-order tax amounts, each already rounded to cents on orders-export.csv, so on US-CA and US-WA it is a cent below what rounding the jurisdiction's own taxable base would give.

File: CSV · Ecommerce Documents · 6 rows
Use case: Data import

Fieldnote Supply Shop: Multi-jurisdiction tax summary JSON

Multi-jurisdiction tax summary JSON for Fieldnote Supply Shop. The same 6 jurisdictions as tax-summary.csv, with the marketplace facilitator basis and the rounding basis both stated. totals.netTaxDue is 88.88, and the document records that US-CA and US-WA differ by a cent under the other rounding basis.

File: JSON · Ecommerce Documents · 6 rows
Use case: Data import

Fieldnote Supply Shop: Inventory and price feed with variants

Inventory and price feed with variants for Fieldnote Supply Shop. 12 variant rows over 6 products, two finishes each. Every gtin is a valid 13-digit GS1 number whose final digit is the modulo-10 check digit, and all 12 begin with a zero, so a spreadsheet that types the column as a number destroys the identifier. Quantities sum to 285 units and match the variant stock in the shop model.

File: CSV · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Inventory and price feed XML

Inventory and price feed XML for Fieldnote Supply Shop. The same 12 variants as inventory-feed.csv. Because the gtin values are element text rather than spreadsheet cells, the leading zeros survive here, which makes this file the reference against which the CSV round trip is checked.

File: XML · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Inventory feed as UTF-16 LE tab-separated text

Inventory feed as UTF-16 LE tab-separated text for Fieldnote Supply Shop. The same 12 variants, tab separated and encoded UTF-16 little endian with an FF FE byte order mark. Every ASCII character occupies two bytes, so a reader that opens the file as UTF-8 sees NUL between each letter and usually reports one column.

File: TSV · Ecommerce Documents · 12 rows
Use case: Data import

Fieldnote Supply Shop: Marketplace settlement transaction detail

Marketplace settlement transaction detail for Fieldnote Supply Shop. 41 settlement lines for period 2026-08: 12 order captures totalling 922.00, 12 referral fees totalling -110.64, 12 processing fees totalling -30.36, one monthly fee of -39.99 and 4 refund debits totalling -80.00. The column sums to 661.01, which is the net payable on settlement-payout.csv.

File: CSV · Ecommerce Documents · 41 rows
Use case: Data import· Paired fixture

Fieldnote Supply Shop: Marketplace settlement and payout summary

Marketplace settlement and payout summary for Fieldnote Supply Shop. The reconciliation people get wrong, stated as a key-value sheet: gross sales 922.00 minus total fees 180.99 minus refunds 80.00 equals net payable 661.01 USD, converted once at 0.91250 to a 603.17 EUR deposit. Every fee component equals the matching group of lines in settlement-transactions.csv.

File: CSV · Ecommerce Documents · 16 rows
Use case: Data import· Paired fixture

Fieldnote Supply Shop: Marketplace settlement and payout summary JSON

Marketplace settlement and payout summary JSON for Fieldnote Supply Shop. The same settlement as settlement-payout.csv with the reconciliation rule written out as a string. netPayableUsd is 661.01 and depositAmountEur is 603.17.

File: JSON · Ecommerce Documents · UTF-8
Use case: Data import

Fieldnote Supply Shop: Settlement whose deposit misses by the FX rounding

Settlement whose deposit misses by the FX rounding for Fieldnote Supply Shop. Every USD figure is identical to settlement-payout.csv, but the deposit was produced by converting each of the 41 settlement lines to EUR and rounding before summing. deposit_amount_eur reads 603.19 where the single conversion of net_payable_usd gives 603.17, a difference of 0.02 EUR that no USD column reveals.

File: CSV · Ecommerce Documents · 16 rows
Use case: Data importError handling

Fieldnote Supply Shop: Three-period payout history

Three-period payout history for Fieldnote Supply Shop. Three consecutive monthly settlements, the last of which is the one detailed in settlement-payout.csv. Each row satisfies gross minus fees minus refunds equals net, and net times fx_rate rounded half up equals the EUR deposit, at three different rates (0.92410, 0.91980 and 0.91250).

File: CSV · Ecommerce Documents · 3 rows
Use case: Data import

Fieldnote Supply Shop: Marketplace fee schedule

Marketplace fee schedule for Fieldnote Supply Shop. The four fee codes the settlement uses, with basis, rate and fixed component. REFERRAL at 0.12000 and PROCESSING at 0.02900 plus 0.30 reproduce every fee line in settlement-transactions.csv; REFUND_ADMIN is present at zero because the period waived it, which is why the settlement has no refund fee lines.

File: CSV · Ecommerce Documents · 4 rows
Use case: Data import

Fieldnote Supply Shop: Open and resolved chargebacks

Open and resolved chargebacks for Fieldnote Supply Shop. Two disputes against orders ORD-006 and ORD-009. Neither has been debited yet, which is why the 661.01 settlement contains no chargeback line: CB-2026-0001 is still open and CB-2026-0002 was won. The disputed amounts equal the captures on those orders exactly.

File: CSV · Ecommerce Documents · 2 rows
Use case: Data import

Fieldnote Supply Shop: Sales by product

Sales by product for Fieldnote Supply Shop. 6 products with units sold, gross merchandise before discount, units refunded and net merchandise. gross_merchandise sums to 942.00, which is the merchandise subtotal of orders-export.csv before the four 5.00 promotions, and merchandise_refunded sums to 80.00.

File: CSV · Ecommerce Documents · 6 rows
Use case: Data import

Fieldnote Supply Shop: Customer export with tax jurisdiction

Customer export with tax jurisdiction for Fieldnote Supply Shop. 6 fictional customers at example.test addresses, each with the jurisdiction that set the tax rate on their orders. Every customer placed 2 orders and merchandise_total sums to 922.00.

File: CSV · Ecommerce Documents · 6 rows
Use case: Data import

Fieldnote Supply Shop: Discount code usage

Discount code usage for Fieldnote Supply Shop. One promotion, SAMPLE5, a fixed 5.00 USD reduction used on 4 of the 12 orders for a total of 20.00. Those are exactly the orders whose discount_total column in orders-export.csv is not zero.

File: CSV · Ecommerce Documents · 1 row
Use case: Data import

Fieldnote Supply Shop: Settlement reconciliation assertions

Settlement reconciliation assertions for Fieldnote Supply Shop. The five identities this document set claims, each with the exact figure it must produce: net payable 661.01 USD, deposit 603.17 EUR and net tax due 88.88. It also records the size of the deliberate defect, 0.02 EUR.

File: JSON · Ecommerce Documents · UTF-8
Use case: Data import· Paired fixture

Pine Assembly Workshop: Shipment export CSV

Shipment export CSV for Pine Assembly Workshop. 16 shipments over 4 delivery rounds, 13 delivered and 3 still in transit. Every parcel is one DESK kit at 12.200 kg gross, so gross_weight_kg is always parcels times 12.200. Parcels total 56 and delivered_parcels total 44; the in-transit rows report 0 delivered and an empty delivery_date.

File: CSV · Logistics Shipping · 16 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Shipment export JSON

Shipment export JSON for Pine Assembly Workshop. The same 16 shipments as shipments-export.csv with a totals object. totals.parcels is 56 and totals.grossWeightKg is 683.200, the sum of the per-shipment weights.

File: JSON · Logistics Shipping · 16 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Bill of lading register

Bill of lading register for Pine Assembly Workshop. 4 bills of lading, one per delivery round, covering all 16 shipments and all 56 pieces. The piece counts are 8, 12, 16, 20 and they sum to 56, which is the parcels column of shipments-export.csv. Freight terms are prepaid on every round.

File: CSV · Logistics Shipping · 4 rows
Use case: Data import

Pine Assembly Workshop: Packing list by carton

Packing list by carton for Pine Assembly Workshop. 168 lines describing the contents of all 56 cartons: three part lines per carton, 4 LEG, 1 PANEL and 12 SCREW, which is the leaf level of the DESK bill of materials. The carton count equals the 56 parcels on shipments-export.csv and every carton weighs 12.200 kg gross.

File: CSV · Logistics Shipping · 168 rows
Use case: Data import

Pine Assembly Workshop: Packing list whose carton count is short of the bill of lading

Packing list whose carton count is short of the bill of lading for Pine Assembly Workshop. The same packing list as packing-list.csv with the 12 lines of the fourth carton on each BOL-2026-0003 consignment removed. It now describes 52 cartons where the register declares 56. BOL-2026-0003 accounts for 12 pieces against a declared 16.

File: CSV · Logistics Shipping · 156 rows
Use case: Data importError handling

Pine Assembly Workshop: Carrier rate sheet

Carrier rate sheet for Pine Assembly Workshop. Two delivery zones. Zone A covers ROUTE-1 ROUTE-2 at 18.00 per stop plus 0.85 per kg; zone B covers ROUTE-3 ROUTE-4 at 24.00 per stop plus 1.10 per kg. A fuel surcharge of 0.065 applies to the base plus the weight charge, and every line rounds half up to cents.

File: CSV · Logistics Shipping · 2 rows
Use case: Data import

Pine Assembly Workshop: Carrier rate sheet JSON

Carrier rate sheet JSON for Pine Assembly Workshop. The same two zones as rate-sheet.csv with the rating formula written out as a string, including the fact that the fuel surcharge applies to the base charge as well as the weight charge. That basis is the one most often got wrong.

File: JSON · Logistics Shipping · UTF-8
Use case: Data import

Pine Assembly Workshop: Rated freight charges

Rated freight charges for Pine Assembly Workshop. 16 rated shipments. line_total equals base_charge plus weight_charge plus fuel_surcharge on every row, weight_charge equals gross_weight_kg times rate_per_kg rounded half up, and fuel_surcharge equals 0.065 of the two added together. The 13 billable rows total 861.19 and all 16 rows total 1093.24.

File: CSV · Logistics Shipping · 16 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Carrier invoice whose fuel surcharge uses the wrong basis on one line

Carrier invoice whose fuel surcharge uses the wrong basis on one line for Pine Assembly Workshop. The 13 billable shipments with a TOTAL row. Every line is correct except SHIP-07, whose fuel_surcharge was computed on the weight charge alone: 53.68 times 0.065 gives 3.49 instead of 5.05 on the base plus weight charge. The line is 1.56 light and the TOTAL row reads 859.63 against the correct 861.19.

File: CSV · Logistics Shipping · 14 rows
Use case: Data importError handling

Pine Assembly Workshop: Proof of delivery register

Proof of delivery register for Pine Assembly Workshop. 13 delivery confirmations, one for each delivered shipment and none for the three still in transit. pieces_delivered equals pieces_expected on every row, so the register accounts for all 44 delivered parcels, and the exception_code column is empty throughout because no delivery was short or damaged.

File: CSV · Logistics Shipping · 13 rows
Use case: Data import

Pine Assembly Workshop: HS tariff code reference

HS tariff code reference for Pine Assembly Workshop. Four tariff codes with duty rates and the unit of quantity each is measured in. Only 9403.30 is used on this entry, because the kit is presented complete but unassembled and is classified as the finished article; the three component codes are shipped so a classification test has a wrong-but-plausible alternative to reject.

File: CSV · Logistics Shipping · 4 rows
Use case: Data import

Pine Assembly Workshop: Customs commercial invoice lines

Customs commercial invoice lines for Pine Assembly Workshop. 4 invoice lines covering the 20 kits on BOL-2026-0004, all classified under HS 9403.30 with country of origin CA. amount_usd equals quantity times unit_price_usd on every line and the column sums to 1360.00; net weight sums to 226.880 kg and gross to 244.000 kg, the difference being the packaging.

File: CSV · Logistics Shipping · 4 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Customs entry XML

Customs entry XML for Pine Assembly Workshop. An import entry for the BOL-2026-0004 consignment on a CIF basis. Goods 1360.00 plus freight 388.08 gives a customs value of 1748.08; duty at 0.025 is 43.70 and import tax at 0.050 on the customs value plus duty is 89.59, a total payable of 133.29. The statistical breakdown restates the 226.880 kg across the three component codes.

File: XML · Logistics Shipping · UTF-8
Use case: Data import· Conversion set

Pine Assembly Workshop: Shipment tracking event export

Shipment tracking event export for Pine Assembly Workshop. 74 scan events in chronological order per shipment: five for each of the 13 delivered shipments and three for each of the 3 still in transit, which never reach OUTFORDEL or DELIVERED. The DELIVERED timestamp on each shipment equals the delivered_time recorded for it on proof-of-delivery.csv.

File: CSV · Logistics Shipping · 74 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Shipment tracking events as newline-delimited JSON

Shipment tracking events as newline-delimited JSON for Pine Assembly Workshop. The same 74 scan events as tracking-events.csv, one JSON object per line with no enclosing array and no trailing comma. The file is not valid JSON as a whole and is not meant to be: each line is a complete document, which is what lets a consumer stream it without buffering the whole file.

File: JSONL · Logistics Shipping · 74 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: Tracking events out of order with a duplicated delivery scan

Tracking events out of order with a duplicated delivery scan for Pine Assembly Workshop. The same events as tracking-events.csv written newest first rather than oldest first, with one extra row: the DELIVERED scan for SHIP-02 appears twice under two different scan_id values, SCN-00010 and SCN-00075, with identical shipment_id, event_code, date and time. The file has 75 rows against 74 distinct events.

File: CSV · Logistics Shipping · 75 rows
Use case: Data import· Conversion set

Pine Assembly Workshop: EDI X12 856 advance ship notice

EDI X12 856 advance ship notice for Pine Assembly Workshop. An ANSI X12 004010 transaction set 856 for bill of lading BOL-2026-0004: 35 segments from ISA to IEA, terminated with a tilde and CRLF as the format carries in practice. The hierarchy is one shipment level, 4 order levels and 4 item levels, so CTT declares 9 HL segments and SE declares 31 segments in the transaction set.

File: EDI · Logistics Shipping · ASCII
Use case: Data import

Pine Assembly Workshop: Open delivery exceptions

Open delivery exceptions for Pine Assembly Workshop. 3 open exceptions, one for each shipment that has not been delivered. Between them they hold 12 parcels, which is exactly the difference between the 56 parcels shipped and the 44 delivered. Every resolution_target is two days after the raised_date.

File: CSV · Logistics Shipping · 3 rows
Use case: Data import

Pine Assembly Workshop: Delivery route plan and capacity

Delivery route plan and capacity for Pine Assembly Workshop. 4 rounds with 4 stops each. Parcels per round are 8, 12, 16, 20 against a vehicle capacity of 30 parcels, so capacity_used_percent runs from 26.67 to 66.67 and no round is over capacity. freight_charged_usd counts only delivered shipments and sums to 861.19.

File: CSV · Logistics Shipping · 4 rows
Use case: Data import

Pine Assembly Workshop: Vehicle utilisation report

Vehicle utilisation report for Pine Assembly Workshop. 4 vehicles, one per round. spare_capacity equals capacity_parcels minus parcels_carried on every row and is positive throughout, from 10 to 22 parcels. fuel_litres is the planned consumption for one run of the round and litres_per_parcel divides it by the parcels carried, rounded half up to three decimals.

File: CSV · Logistics Shipping · 4 rows
Use case: Data import

Pine Assembly Workshop: Logistics reconciliation assertions

Logistics reconciliation assertions for Pine Assembly Workshop. The six identities this set claims with the exact figure each must produce: 683.200 kg gross, 56 parcels, 56 cartons, 861.19 of billable freight and 133.29 of customs charges. It also records the size and cause of both deliberate defects.

File: JSON · Logistics Shipping · UTF-8
Use case: Data import

Tern Client Services: Timesheet export CSV

Timesheet export CSV for Tern Client Services. 24 time entries over 2026-08-01 to 2026-08-24 across 3 projects for one client. billable_amount equals hours times hourly_rate on every row and every row is at the 100.00 standard rate. Hours total 72 and billable_amount totals 7200.00, split 1600.00 / 2400.00 / 3200.00 across the three projects.

File: CSV · Professional Services Billing · 24 rows
Use case: Data import· Conversion set

Tern Client Services: Timesheet export JSON

Timesheet export JSON for Tern Client Services. The same 24 entries as timesheet-export.csv with a byProject rollup and a totals object. totals.hours is 72 and totals.billableAmount is 7200.00, and each byProject member names the invoice that billed it.

File: JSON · Professional Services Billing · 24 rows
Use case: Data import· Conversion set

Tern Client Services: Professional fee schedule

Professional fee schedule for Tern Client Services. Five rate codes. STD at 100.00 per hour is the only billing rate any time entry uses, which is why every row of timesheet-export.csv carries 100.00; OOH and TRV are defined but unused in this period and carry used_this_period false. MIL at 0.62 per kilometre is the mileage rate mileage-log.csv applies and COST at 58.00 per hour is the internal rate project-profitability.csv uses.

File: CSV · Professional Services Billing · 5 rows
Use case: Data import

Tern Client Services: Retainer ledger

Retainer ledger for Tern Client Services. A three-line retainer account: a 4000.00 deposit received on 2026-07-28 and two draws of 1600.00 and 2400.00 applied when SVCINV-1 and SVCINV-2 were raised. The running balance closes at 0.00, which is why SVCINV-3 is billed for payment rather than drawn.

File: CSV · Professional Services Billing · 3 rows
Use case: Data import

Tern Client Services: Invoice register with retainer draws

Invoice register with retainer draws for Tern Client Services. 3 invoices totalling 7200.00, which is the whole of the August timesheet. 4000.00 of it was settled by drawing the retainer to nil and 3200.00 is outstanding on SVCINV-3. amount equals retainer_applied plus cash_due on every row, and every invoice is dated 2026-09-30, 22 days after the 2026-09-08 snapshot, so all three sit in the not yet due bucket.

File: CSV · Professional Services Billing · 3 rows
Use case: Data import· Conversion set

Tern Client Services: Invoice register JSON

Invoice register JSON for Tern Client Services. The same 3 invoices as invoice-register.csv with the settlement rule stated: the retainer is drawn while a balance remains and the remainder is billed. totals.outstanding is 3200.00.

File: JSON · Professional Services Billing · 3 rows
Use case: Data import· Conversion set

Tern Client Services: Work in progress at 2026-08-15

Work in progress at 2026-08-15 for Tern Client Services. Unbilled work at the 2026-08-15 cut-off: 15 of the 24 August time entries had been recorded by then, 45 hours worth 4500.00. Nothing had been invoiced at that date, the first invoice being dated 2026-09-01, so wip_at_cutoff equals value_to_cutoff on every row.

File: CSV · Professional Services Billing · 3 rows
Use case: Data import

Tern Client Services: Work in progress roll-forward

Work in progress roll-forward for Tern Client Services. The full-period roll-forward for the 3 projects and a TOTAL row. Opening WIP is 0.00, 7200.00 of time was added, the same 7200.00 was transferred to billed when the September invoices were raised, and closing WIP is 0.00 on every line. Transfers are negative because they leave work in progress.

File: CSV · Professional Services Billing · 4 rows
Use case: Data import

Tern Client Services: Mileage log

Mileage log for Tern Client Services. 3 client trips totalling 236 km. amount equals distance_km times rate_per_km on every row at the 0.62 per kilometre MIL rate from fee-schedule.csv, and the column sums to 146.32. Each trip names the project it was made for, so the mileage allocates cleanly to the three projects.

File: CSV · Professional Services Billing · 3 rows
Use case: Data import· Conversion set

Tern Client Services: Expense claim with mileage

Expense claim with mileage for Tern Client Services. 6 claim lines for August: 3 mileage lines worth 146.32 and 3 receipted lines worth 75.25, 221.57 in total. amount equals quantity times rate on every line, including the mileage lines where quantity is kilometres. Each line carries the project it belongs to and a receipt reference.

File: CSV · Professional Services Billing · 6 rows
Use case: Data import· Conversion set

Tern Client Services: Expense claim whose mileage was paid at a superseded rate

Expense claim whose mileage was paid at a superseded rate for Tern Client Services. The same 6 lines as expense-claim.csv, but the three mileage amounts were computed at the superseded 0.58 per kilometre while the rate column still reads 0.62. The mileage subtotal is 136.88 where 236 km at the stated rate is 146.32, so the claim is 9.44 light and totals 212.13 instead of 221.57.

File: CSV · Professional Services Billing · 6 rows
Use case: Data importError handling

Tern Client Services: Project profitability

Project profitability for Tern Client Services. 3 projects and a TOTAL row. revenue_billed is the invoiced value, labour_cost is hours times the 58.00 internal COST rate, expenses is the claim allocated by project, and gross_margin is revenue minus the two costs. Total revenue 7200.00 less total cost 4397.57 gives 2802.43, a margin of 38.92 percent.

File: CSV · Professional Services Billing · 4 rows
Use case: Data import

Tern Client Services: Specialist utilisation report

Specialist utilisation report for Tern Client Services. 3 specialists against a stated 64 available hours each. Billable hours are 16, 24, 32, so utilisation runs 25.00 to 50.00 percent. Each specialist worked on exactly one project in this period, which is why the projects column is 1 on every row.

File: CSV · Professional Services Billing · 3 rows
Use case: Data import

Tern Client Services: Sales pipeline export

Sales pipeline export for Tern Client Services. 12 deals across 4 companies and four stages. weighted_amount equals amount times probability on every row, amount totals 34500.00 and weighted_amount totals 15825.00. The 3 won deals total 9000.00, which is the sum of the project budgets on project-profitability.csv, and the lost deals carry probability 0.00 and a weighted amount of 0.00.

File: CSV · Professional Services Billing · 12 rows
Use case: Data import· Conversion set

Tern Client Services: Quote export

Quote export for Tern Client Services. 12 quotes, one per deal, each for the deal amount. 3 are accepted and total 9000.00, the same figure as the won deals on pipeline-export.csv; the remaining 9 are open. Every quote expires on 2026-09-30, 30 days after it was issued.

File: CSV · Professional Services Billing · 12 rows
Use case: Data import

Tern Client Services: Sales activity export

Sales activity export for Tern Client Services. 24 logged activities over 2026-08-01 to 2026-08-24 across three types. Minutes total 720, which is 12 hours, and every deal_id resolves in pipeline-export.csv. This is recorded sales effort and is deliberately separate from the billable time in timesheet-export.csv, which none of it appears in.

File: CSV · Professional Services Billing · 24 rows
Use case: Data import

Tern Client Services: Contact export with quoted fields

Contact export with quoted fields for Tern Client Services. 8 contacts in 33 physical lines, because every billing_address is a four-line address held in one quoted field. The addresses also contain commas, the notes contain doubled double-quote characters where a quotation appears, and the tags field holds the comma-separated value "billing,renewals" inside quotes. Every one of those is correctly escaped RFC 4180.

File: CSV · Professional Services Billing · 8 rows
Use case: Data import· Conversion set

Tern Client Services: Contact export in the semicolon dialect

Contact export in the semicolon dialect for Tern Client Services. The same 8 contacts written with a semicolon delimiter. The billing_address field is still quoted because it contains newlines, but the tags field is now bare: "billing,renewals" needs no quotes when the delimiter is a semicolon, so the same value is quoted in contacts-export.csv and unquoted here. The file has 33 physical lines.

File: CSV · Professional Services Billing · 8 rows
Use case: Data import· Conversion set

Tern Client Services: Professional services reconciliation assertions

Professional services reconciliation assertions for Tern Client Services. The six identities this set claims with the figure each must produce: 7200.00 of billable time, the same amount invoiced, a retainer closing at 0.00, a work-in-progress roll-forward closing at 0.00, 221.57 of expenses and 9000.00 of won deals. It also records the 9.44 size of the deliberate defect.

File: JSON · Professional Services Billing · UTF-8
Use case: Data import

Pine Property Services: Schedule of values

Schedule of values for Pine Property Services. 12 contract line items, one per work order, plus a total line. Each scheduled_value is the approved estimate for that item and the column sums to 3858.00, the original contract sum every payment application starts from. labour_allowance plus material_allowance equals scheduled_value on every line, and each allowance sits a fixed margin above the recorded cost: 65.00 on labour and 20.00 on materials, which is where the 85.00 per item of estimate-over-actual comes from.

File: CSV · Construction Billing · 13 rows
Use case: Data import· Conversion set

Pine Property Services: Application for payment continuation sheet

Application for payment continuation sheet for Pine Property Services. 12 contract items, 2 change order lines and a TOTAL row, in the shape of an AIA G703 continuation sheet. Scheduled values total 4113.00; 1490.00 was certified on the previous application, 1618.00 is claimed this period and 140.00 is materials stored but not installed, giving 3248.00 completed and stored. Retainage is 10 percent of each line and totals 324.80.

File: CSV · Construction Billing · 15 rows
Use case: Data import· Conversion set

Pine Property Services: Application for payment summary

Application for payment summary for Pine Property Services. The nine numbered lines of an AIA G702 style application. Contract sum 3858.00 plus 255.00 of change orders gives 4113.00; 3248.00 is completed and stored, retainage of 324.80 splits 310.80 on work and 14.00 on stored material, and after 1341.00 of previous certificates the current payment due is 1582.20.

File: CSV · Construction Billing · 11 rows
Use case: Data import· Conversion set

Pine Property Services: Application for payment whose retainage was withheld at the wrong rate

Application for payment whose retainage was withheld at the wrong rate for Pine Property Services. The same nine lines as application-for-payment-002-summary.csv, but lines 5a and 5b were computed at 5 percent while their own descriptions still read 10 percent. Retainage reads 162.40 instead of 324.80, so the current payment due on line 8 reads 1744.60 against the correct 1582.20, 162.40 too much.

File: CSV · Construction Billing · 11 rows
Use case: Data importError handling

Pine Property Services: Approved change order register

Approved change order register for Pine Property Services. 2 approved change orders: an addition of 420.00 for extra door hardware and a credit of -165.00 for deleted lighting scope, a net 255.00. The running contract sum moves from 3858.00 to 4113.00, which is line 3 of the payment application. A credit change order is a negative amount, not a separate document type.

File: CSV · Construction Billing · 2 rows
Use case: Data import

Pine Property Services: Retainage ledger

Retainage ledger for Pine Property Services. Two payment applications. Application 001 certified 1341.00 and retained 149.00; application 002 adds 1758.00 of completed and stored value, retains a further 175.80 and certifies 1582.20. Cumulative retainage reaches 324.80, which is 10 percent of the 3248.00 completed and stored to date.

File: CSV · Construction Billing · 2 rows
Use case: Data import

Pine Property Services: Lien waiver register

Lien waiver register for Pine Property Services. Two waivers, one per payment application. LW-2026-001 is unconditional for 1341.00 because that payment has been received; LW-2026-002 is conditional for 1582.20 and takes effect only on receipt of the current payment. The two amounts sum to 2923.20, the total earned less retainage, so nothing certified is unwaived and the 324.80 of retainage is covered by neither, which is exactly right.

File: CSV · Construction Billing · 2 rows
Use case: Data import

Pine Property Services: Job cost report, estimate against actual

Job cost report, estimate against actual for Pine Property Services. 12 work orders with estimate and actual side by side. actual_labour_cost equals actual_labour_hours times actual_labour_rate on every row, actual_total is that plus actual_materials, and variance is estimate_total minus actual_total. Estimates total 3858.00 against 2838.00 of recorded cost, a variance of 1020.00, which is a uniform 85.00 per work order because every estimate carries 65.00 of labour margin and 20.00 of material margin.

File: CSV · Construction Billing · 12 rows
Use case: Data import· Conversion set

Pine Property Services: Job cost report JSON

Job cost report JSON for Pine Property Services. The same 12 work orders as job-cost-report.csv with the margin rule stated explicitly. totals.variance is 1020.00, which is 85.00 times the 12 work orders.

File: JSON · Construction Billing · 12 rows
Use case: Data import· Conversion set

Pine Property Services: Cost code budget against actual

Cost code budget against actual for Pine Property Services. Two cost codes and a TOTAL row. Labour is budgeted 3120.00 against 2340.00 actual and materials 738.00 against 498.00, so the total budget 3858.00 is the contract sum and the total actual 2838.00 is the job cost report. The percentages are variance over budget: 25.00 on labour, 32.52 on materials and 26.44 overall.

File: CSV · Construction Billing · 3 rows
Use case: Data import

Pine Property Services: Work order export

Work order export for Pine Property Services. 12 work orders across 6 properties, two per property, raised daily from 2026-08-01. 9 are completed and 3 are still scheduled. total_cost equals labour_cost plus materials on every row and the column sums to 2838.00. Costs are recorded on scheduled work orders as well as completed ones because the materials were bought in advance.

File: CSV · Construction Billing · 12 rows
Use case: Data import· Conversion set

Pine Property Services: Work order export JSON

Work order export JSON for Pine Property Services. The same 12 work orders as work-order-export.csv with a byProperty rollup. Each of the 6 properties carries exactly 2 work orders and the totalCost figures sum to 2838.00.

File: JSON · Construction Billing · 12 rows
Use case: Data import· Conversion set

Pine Property Services: Material purchase register

Material purchase register for Pine Property Services. 12 material purchases, one per work order, alternating between two fictional merchants. The amounts are the materials column of the job cost report and sum to 498.00, which is the 02-200 actual on cost-code-summary.csv. Every purchase is dated the day its work order was raised.

File: CSV · Construction Billing · 12 rows
Use case: Data import

Pine Property Services: Site daily log

Site daily log for Pine Property Services. 9 daily entries, one for each completed work order, recording the crew, the labour hours and the weather. Hours total 27 and equal the labour hours the job cost report records against the same work orders. The four scheduled work orders have no log entry because no crew has attended them.

File: CSV · Construction Billing · 9 rows
Use case: Data import

Pine Property Services: Completion inspection register

Completion inspection register for Pine Property Services. 9 inspections, one for each completed work order. 8 passed and 1 needs a follow-up, INSPECT-6 against WO-06. follow_up_required is derived from result and agrees with it on every row. Every note carries the standing caveat that these are operational checks, not regulated certificates.

File: CSV · Construction Billing · 9 rows
Use case: Data import

Pine Property Services: Property register with job costs

Property register with job costs for Pine Property Services. 6 properties, each with exactly 2 work orders. total_cost equals labour_cost plus materials on every row and the column sums to 2838.00, the whole job cost. Costs per property run from 328.00 to 618.00.

File: CSV · Construction Billing · 6 rows
Use case: Data import

Pine Property Services: Planned maintenance schedule

Planned maintenance schedule for Pine Property Services. 6 planned reviews, one per property, all on the same 92-day cycle: last carried out 2026-06-15 and next due 2026-09-15, which is 7 days after the 2026-09-08 snapshot. interval_days and days_until_next are both derived from the two date columns.

File: CSV · Construction Billing · 6 rows
Use case: Data import

Pine Property Services: Construction reconciliation assertions

Construction reconciliation assertions for Pine Property Services. The eight identities this set claims with the figure each must produce: a 3858.00 contract sum moving to 4113.00, 3248.00 completed and stored, 324.80 retained, 1582.20 due, and a job cost variance of 1020.00. It also records the 162.40 size of the deliberate defect.

File: JSON · Construction Billing · UTF-8
Use case: Data import

Willow Community Fund: Fair market value of donor benefits

Fair market value of donor benefits for Willow Community Fund. The 2 goods and services supporters received in return for a gift, with the fair market value used to reduce the deductible amount on their receipt: Workshop lunch at 18.00 on 6 receipts and Garden tote bag at 7.50 on 3. No de minimis exception is applied: every benefit is deducted, however small.

File: CSV · Nonprofit Giving · 2 rows
Use case: Data import

Willow Community Fund: Donation receipts with benefit split

Donation receipts with benefit split for Willow Community Fund. 9 receipts for the gifts actually received. 3 are pure gifts where deductible_amount equals gross_amount; 6 were made at a fundraising event and carry a benefit, so their deductible_amount is the gross less the fair market value of what the supporter received. Gross totals 1800.00, benefits 130.50 and deductible 1669.50. Getting this split wrong is the single most common error on a charitable receipt.

File: CSV · Nonprofit Giving · 9 rows
Use case: Data import· Conversion set

Willow Community Fund: Donation receipts JSON

Donation receipts JSON for Willow Community Fund. The same 9 receipts as donation-receipts.csv with the receipt rule written out. totals.deductible is 1669.50, which is 1800.00 of gifts less 130.50 of benefits.

File: JSON · Nonprofit Giving · 9 rows
Use case: Data import· Conversion set

Willow Community Fund: Donation receipts that treat a quid pro quo gift as fully deductible

Donation receipts that treat a quid pro quo gift as fully deductible for Willow Community Fund. The same 9 receipts, but on the 6 rows with a benefit the deductible_amount was copied from gross_amount while value_of_benefits and benefit_description were left correct. The deductible column totals 1800.00 against the correct 1669.50, overstating the deductible amount by 130.50, which is precisely the value of benefits the same file reports.

File: CSV · Nonprofit Giving · 9 rows
Use case: Data importError handling

Willow Community Fund: Pledge instalment schedule

Pledge instalment schedule for Willow Community Fund. 18 instalments across 12 pledges. The 9 settled pledges are single paid instalments; the 3 outstanding pledges are split into three monthly instalments due 2026-06-30, 2026-07-31, 2026-08-31. The instalments of a pledge always sum to its pledge_total: 325.00 splits 108.33, 108.33 and 108.34, so the final instalment absorbs the rounding. The schedule totals 2850.00 and the unpaid part is 1050.00.

File: CSV · Nonprofit Giving · 18 rows
Use case: Data import· Conversion set

Willow Community Fund: Pledge aging at 2026-09-08

Pledge aging at 2026-09-08 for Willow Community Fund. The 9 unpaid instalments bucketed by how overdue they are at the 2026-09-08 snapshot. Each of the three outstanding pledges has one instalment in each of the 1-30, 31-60 and 61-90 buckets, so the buckets hold 350.02, 349.99, 349.99 and total 1050.00. The bucket amounts are not round numbers because the instalment rounding put an extra cent in the youngest bucket.

File: CSV · Nonprofit Giving · 5 rows
Use case: Data import

Willow Community Fund: Grant register

Grant register for Willow Community Fund. 3 grant applications, one per campaign. 2 were awarded in full and total 4500.00; the third is still pending and carries an awarded amount of 0.00 with no award date and no report date. Requested totals 7500.00, so 3000.00 of the ask is still undecided.

File: CSV · Nonprofit Giving · 3 rows
Use case: Data import· Conversion set

Willow Community Fund: Grant budget against actual

Grant budget against actual for Willow Community Fund. 10 rows: four budget lines and a Grant total for each of the 2 awarded grants. Each grant's budget lines sum to the amount awarded, 2000.00 and 2500.00, and actual spend of 4395.25 leaves 104.75 unspent. Two lines are overspent and carry a negative variance; the grant totals are still positive, which is how an overspend hides inside a grant that looks fine.

File: CSV · Nonprofit Giving · 10 rows
Use case: Data import· Conversion set

Willow Community Fund: Restricted and unrestricted fund report

Restricted and unrestricted fund report for Willow Community Fund. 4 funds and a TOTAL row. The general fund carries 1200.00 without donor restrictions and moves not at all in the period; the 3 campaign funds are restricted and receive 1800.00 of donations and 4500.00 of grants. Every row satisfies opening + receipts - expenditure = closing, and the funds close at 3104.75, of which 1904.75 is restricted.

File: CSV · Nonprofit Giving · 5 rows
Use case: Data import· Conversion set

Willow Community Fund: Restricted fund report JSON

Restricted fund report JSON for Willow Community Fund. The same 4 funds as restricted-funds-report.csv with the balancing rule stated and the closing balance split by restriction: 1904.75 with donor restrictions and 1200.00 without.

File: JSON · Nonprofit Giving · UTF-8
Use case: Data import· Conversion set

Willow Community Fund: Fund balance roll-forward by restriction class

Fund balance roll-forward by restriction class for Willow Community Fund. The same money as restricted-funds-report.csv collapsed to two restriction classes and a TOTAL row. Nothing was released from restriction in the period, so the unrestricted class does not move: it opens and closes at 1200.00. The restricted class opens at 0.00, receives 6300.00, spends 4395.25 and closes at 1904.75.

File: CSV · Nonprofit Giving · 3 rows
Use case: Data import

Willow Community Fund: Campaign summary against goal

Campaign summary against goal for Willow Community Fund. 3 campaigns and a TOTAL row. total_raised is donations received plus grants awarded and deliberately excludes the 1050.00 of pledges still outstanding, which sit in their own column. Against 12500.00 of goals, 6300.00 has been raised, 50.40 percent, ranging from 16.88 percent on Library corner to 88.57 percent on Workshop supplies.

File: CSV · Nonprofit Giving · 4 rows
Use case: Data import

Willow Community Fund: Donor summary export

Donor summary export for Willow Community Fund. 8 supporters with their year-to-date position. pledged_total equals received_total plus outstanding_total on every row, and received_total less value_of_benefits equals deductible_total. The columns total 2850.00 pledged, 1800.00 received, 130.50 of benefits and 1669.50 deductible.

File: CSV · Nonprofit Giving · 8 rows
Use case: Data import· Conversion set

Willow Community Fund: Donor summary export JSON

Donor summary export JSON for Willow Community Fund. The same 8 supporters as donor-export.csv, with a privacy note recording that the export deliberately carries no contact or payment data. totals.deductible is 1669.50.

File: JSON · Nonprofit Giving · 8 rows
Use case: Data import· Conversion set

Willow Community Fund: Volunteer hours by person

Volunteer hours by person for Willow Community Fund. 8 volunteers with 47 hours across 16 shifts at 4 events. Every volunteer worked exactly 2 shifts. Volunteer time is recorded in hours and is never valued in money anywhere in this set, which is deliberate: donated time is not a cash receipt and must not reach the fund report.

File: CSV · Nonprofit Giving · 8 rows
Use case: Data import

Willow Community Fund: Fundraising event attendance

Fundraising event attendance for Willow Community Fund. 4 events with attendance against a 30-person capacity, the volunteer effort behind each and the gifts received at it. Attendance runs 60.00 to 80.00 percent of capacity, no event is oversubscribed, and the benefits_given column totals 130.50, exactly the value of benefits deducted on the receipts.

File: CSV · Nonprofit Giving · 4 rows
Use case: Data import

Willow Community Fund: In-kind gift register

In-kind gift register for Willow Community Fund. 3 gifts of goods and services valued at 285.00 in total, each with the basis its value was arrived at. counted_as_cash is false on every row and no in-kind gift appears in restricted-funds-report.csv, donation-receipts.csv or campaign-summary.csv. That separation is the point of the file.

File: CSV · Nonprofit Giving · 3 rows
Use case: Data import

Willow Community Fund: Nonprofit reconciliation assertions

Nonprofit reconciliation assertions for Willow Community Fund. The seven identities this set claims with the figure each must produce: 1669.50 of deductible giving, 2850.00 of scheduled pledges, 1050.00 outstanding, 4500.00 of grants, 3104.75 of closing funds, 6300.00 raised and 285.00 of in-kind value that touches no cash total. It also records the 130.50 size of the deliberate defect.

File: JSON · Nonprofit Giving · UTF-8
Use case: Data import

Fieldnote Learning Centre: Course fee schedule

Course fee schedule for Fieldnote Learning Centre. 3 courses with the fee broken into tuition, materials and a flat 25.00 registration charge. The three components add up to total_fee on every row: 300.00, 350.00 and 225.00. Every course runs 2 sessions, seats 10 and passes at 70.

File: CSV · Education Administration · 3 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Enrolment export

Enrolment export for Fieldnote Learning Centre. 18 enrolments over 3 courses and 12 learners, 6 per course. 15 are complete and 9 passed. passed is true only where the enrolment is complete and the score reaches the pass score, which is why 2 rows carry a score at or above 70 and passed false: ENR-17 at 75 and ENR-18 at 82.

File: CSV · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Enrolment export JSON

Enrolment export JSON for Fieldnote Learning Centre. The same 18 enrolments as enrolment-export.csv with the pass rule written out and a byCourse rollup. 9 of the 15 completed enrolments passed, a rate of 60.00 percent of completions.

File: JSON · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Bursary award register

Bursary award register for Fieldnote Learning Centre. 4 awards worth 807.50. Three are a percentage of the fee and apply to every enrolment the learner holds; one is a fixed 120.00 award and applies to that learner's earliest enrolment only, capped at the fee. award_value is a rate for a percentage award and an amount for a fixed one, which is why the column mixes 0.5000 with 120.00.

File: CSV · Education Administration · 4 rows
Use case: Data import

Fieldnote Learning Centre: Invoice register with bursaries

Invoice register with bursaries for Fieldnote Learning Centre. 18 invoices, one per enrolment. tuition plus materials_fee plus registration_fee equals gross_fee, and gross_fee less bursary_amount equals net_payable, on every row. Gross totals 5250.00, bursaries 807.50 and net payable 4442.50. One invoice is reduced to 0.00 by a full bursary and no invoice is negative. payment_plan is true on the 8 invoices whose net exceeds 250.00.

File: CSV · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Invoice register JSON

Invoice register JSON for Fieldnote Learning Centre. The same 18 invoices as invoice-register.csv with the four rules that govern them written out, including the capping rule that keeps net_payable non-negative. totals.netPayable is 4442.50.

File: JSON · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Invoice register where a bursary exceeds the fee it is set against

Invoice register where a bursary exceeds the fee it is set against for Fieldnote Learning Centre. The same 18 invoices, except that the award on ENR-03 was entered as 350.00 against a 225.00 fee. net_payable on that row reads -125.00, a negative amount, and the net column totals 4205.00 instead of 4442.50. The award is 125.00 larger than the fee it can be applied to.

File: CSV · Education Administration · 18 rows
Use case: Data importError handling

Fieldnote Learning Centre: Fee payment plan schedule

Fee payment plan schedule for Fieldnote Learning Centre. 16 instalments across the 8 invoices whose net payable exceeds 250.00. Each is split into two equal instalments due 2026-08-31 and 2026-09-30; the first is paid and the second is still due. The instalments of an invoice always sum to its net_payable and the schedule totals 2600.00, which is the net payable of those 8 invoices and not of all 18.

File: CSV · Education Administration · 16 rows
Use case: Data import

Fieldnote Learning Centre: Gradebook export, one row per result

Gradebook export, one row per result for Fieldnote Learning Centre. 18 results grouped by course, 6 per course. Scores run from 55 to 100 against a maximum of 100 and a pass score of 70. grade_band is derived from score and completion: 6 fail, 3 pass, 2 merit, 4 distinction and 3 incomplete. An incomplete enrolment gets no band even when its score would earn one.

File: CSV · Education Administration · 18 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Gradebook in wide format

Gradebook in wide format for Fieldnote Learning Centre. The same results as gradebook-export.csv pivoted to one row per learner and one column per course. 12 learners, 3 score columns and 18 empty cells where a learner is not enrolled on that course. An empty cell means no enrolment; it does not mean a score of zero, and treating it as zero destroys both best_score and the pass count.

File: CSV · Education Administration · 12 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Gradebook with an impossible score and a missing one

Gradebook with an impossible score and a missing one for Fieldnote Learning Centre. The same 18 results as gradebook-export.csv with two cells changed. ENR-06 carries a score of 104 where the max_score column on the same row declares 100. ENR-12's score cell is empty while its passed column still reads true and its grade_band still reads distinction, so the file asserts a distinction it holds no score for.

File: CSV · Education Administration · 18 rows
Use case: Data importError handling

Fieldnote Learning Centre: Session attendance register

Session attendance register for Fieldnote Learning Centre. 36 attendance records, 2 sessions for each of the 18 enrolments. 30 are present and 6 are absent, an attendance rate of 83.33 percent. Sessions run on 2026-08-10 and 2026-08-11 for every course, so the register has two dates and no others.

File: CSV · Education Administration · 36 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Attendance summary by course

Attendance summary by course for Fieldnote Learning Centre. 3 courses and a TOTAL row. Attendance is uneven: 66.67 percent on Spreadsheet basics, 83.33 on Customer service and 100.00 on Workshop safety orientation, 83.33 overall. session_slots is enrolments times 2 on every row and sessions_attended plus absences equals it.

File: CSV · Education Administration · 4 rows
Use case: Data import· Conversion set

Fieldnote Learning Centre: Course capacity and outcome report

Course capacity and outcome report for Fieldnote Learning Centre. 3 courses, each seating 10 and holding 6 enrolments, so every course is at 60.00 percent with 4 seats free. pass_rate_of_completed divides passes by completions, not by enrolments, which is why COURSE-1 reports 60.00 percent from 3 passes out of 5 completions rather than out of 6 enrolments.

File: CSV · Education Administration · 3 rows
Use case: Data import

Fieldnote Learning Centre: Certificate eligibility with three conditions

Certificate eligibility with three conditions for Fieldnote Learning Centre. All 18 enrolments tested against three conditions: the enrolment is complete, the score reaches the pass mark, and both sessions were attended. 7 are eligible. 9 enrolments passed, so 2 passing learners are still ineligible on attendance alone: ENR-04 and ENR-11, each of whom attended 1 of 2 sessions. Every ineligible row names its reasons.

File: CSV · Education Administration · 18 rows
Use case: Data import

Fieldnote Learning Centre: Learner summary export

Learner summary export for Fieldnote Learning Centre. 12 learners with their enrolments and fee position. Six learners hold 2 enrolments and six hold 1, 18 in total. gross_fees less bursary_total equals net_payable on every row and the columns total 5250.00, 807.50 and 4442.50. certificates_eligible sums to 7, not to the 9 passes.

File: CSV · Education Administration · 12 rows
Use case: Data import

Fieldnote Learning Centre: Course catalogue with materials

Course catalogue with materials for Fieldnote Learning Centre. 3 courses with their fee, capacity, pass score and the exercise material attached to each. material_characters is the exact length of the markdown exercise held against the course in the operating model, from 197 to 253 characters, so a content-length assertion has a real number to check.

File: CSV · Education Administration · 3 rows
Use case: Data import

Fieldnote Learning Centre: Education reconciliation assertions

Education reconciliation assertions for Fieldnote Learning Centre. The six identities this set claims with the figure each must produce: 5250.00 of gross fees, 4442.50 net of bursary, 9 passes, 7 certificates, 18 results in both gradebook shapes and 2600.00 of scheduled instalments. It also records both deliberate defects and their exact size.

File: JSON · Education Administration · UTF-8
Use case: Data import

Cobalt Operations Team: Payroll register

Payroll register for Cobalt Operations Team. 8 employees and a TOTAL row for the 2026-08-10 to 2026-08-15 period paid on 2026-08-21. gross_pay equals hours times hourly_rate, income_tax is 0.18 of gross, pension_employee is 0.05 of gross and health_benefit is a flat 42.00. total_deductions is the three added together and net_pay is gross less deductions, on every row. Gross totals 9072.00, deductions 2422.56 and net 6649.44.

File: CSV · Payroll Hr · 9 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Payroll register JSON

Payroll register JSON for Cobalt Operations Team. The same 8 employees as payroll-register.csv with the rates and the balancing rule written out. totals.net is 6649.44 and equals totals.gross less totals.totalDeductions, 9072.00 less 2422.56.

File: JSON · Payroll Hr · 8 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Payroll register whose deductions do not reconcile to net pay

Payroll register whose deductions do not reconcile to net pay for Cobalt Operations Team. The same 8 employees as payroll-register.csv except that net_pay for EMP-05 was computed before the pension deduction was applied. That row reads gross 1176.00, total_deductions 312.48 and net_pay 922.32, which is 58.80 more than gross less deductions. The TOTAL row was updated to match the column, so it reads 6708.24 against the correct 6649.44, and the file is internally consistent column-wise while being wrong row-wise.

File: CSV · Payroll Hr · 9 rows
Use case: Data importError handling

Cobalt Operations Team: Payslip lines for every employee

Payslip lines for every employee for Cobalt Operations Team. 32 lines, 4 per payslip: one earning and three deductions. Deductions are written as negative amounts rather than as positive amounts in a deduction column, so the amount column sums straight to net pay: 6649.44 across all 8 payslips. Each payslip's lines sum to that employee's net_pay on payroll-register.csv.

File: CSV · Payroll Hr · 32 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Pay element code list

Pay element code list for Cobalt Operations Team. 8 pay elements split into earnings, employee deductions and employer costs, each with the basis it is calculated on, its rate and the general ledger account it posts to. Overtime is defined but carries used_this_period false because no shift in the period exceeded standard hours. The 7 used elements are exactly the lines that appear on the payslips and in the payroll journal.

File: CSV · Payroll Hr · 8 rows
Use case: Data import

Cobalt Operations Team: Benefit plan rate card

Benefit plan rate card for Cobalt Operations Team. Two health plans. STD costs 105.00 a period of which the employer pays 63.00, 60.00 percent, and all 8 employees are on it. ENH is defined at 174.00 with nobody enrolled, so it is the negative case: a plan that exists in the rate card and must never appear in a deduction.

File: CSV · Payroll Hr · 2 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Benefit deduction schedule

Benefit deduction schedule for Cobalt Operations Team. 8 employees and a TOTAL row. Every employee is on the STD plan from 2026-01-01, contributing 42.00 against an employer contribution of 63.00, so employee contributions total 336.00, employer contributions 504.00 and premiums 840.00. Only the employee side reaches the payroll register; the employer side is a cost, not a deduction.

File: CSV · Payroll Hr · 9 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Benefit deduction schedule JSON

Benefit deduction schedule JSON for Cobalt Operations Team. The same 8 enrolments as benefits-deduction-schedule.csv with the rule that separates a deduction from an employer cost stated in words. totalPremiums is 840.00, of which only 336.00 is deducted from pay.

File: JSON · Payroll Hr · 8 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Leave balances

Leave balances for Cobalt Operations Team. 8 employees and a TOTAL row. remaining_hours is entitlement less taken less approved future leave, and deliberately does not subtract pending requests: 16 hours are awaiting approval and are reported in their own column. Across the team 96 hours have been taken, 16 are approved for the future and 1168 of 1280 remain. remaining_days converts at 8 hours a day.

File: CSV · Payroll Hr · 9 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Leave request register

Leave request register for Cobalt Operations Team. 4 requests of 8 hours each, all for dates after the pay period. 2 are approved and count against the balance; 2 are pending and do not. counts_against_balance is derived from status and never disagrees with it.

File: CSV · Payroll Hr · 4 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Paid hours by shift

Paid hours by shift for Cobalt Operations Team. 48 shifts over 2026-08-10 to 2026-08-15, 6 for each of the 8 employees. base_pay equals paid_hours times hourly_rate on every shift, hours total 336 and base pay totals 9072.00, which is the gross_pay column of payroll-register.csv. No shift exceeds standard hours, which is why no overtime element appears anywhere.

File: CSV · Payroll Hr · 48 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Employee directory

Employee directory for Cobalt Operations Team. 8 employees with department, pay basis, rate and start date. The names are the model's own role labels, not people, and the directory carries no address, telephone number, date of birth or national identifier. The bank fields are reserved test values: sort code 000000 and sequential account numbers from 00000001 to 00000008, flagged as such in the last column.

File: CSV · Payroll Hr · 8 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Employee directory JSON

Employee directory JSON for Cobalt Operations Team. The same 8 employees as employee-directory.csv with a department count and a privacy note. The team splits 4 in Operations, 4 in Service.

File: JSON · Payroll Hr · 8 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Bank payment file

Bank payment file for Cobalt Operations Team. 8 payments, one per employee, for the net pay on payroll-register.csv. The amount column totals 6649.44, which is the net_pay total of the register to the cent. Sort code and account numbers are reserved test values and the reference on every line names the employee and the period.

File: CSV · Payroll Hr · 8 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Fixed-width bank payment file

Fixed-width bank payment file for Cobalt Operations Team. 8 records of exactly 105 characters each, the shape a bank credit-transfer file still arrives in. There is no delimiter and no header. Amounts are unsigned cents, zero filled and right justified in an 11-character field, so 604.80 is written as 00000060480. The column map is bank-payment-layout.json.

File: TXT · Payroll Hr · 8 records
Use case: Data import· Conversion set

Cobalt Operations Team: Fixed-width payment file column map

Fixed-width payment file column map for Cobalt Operations Team. The documented column map for bank-payment-fixed-width.txt: 9 fields with 1-based start, length, end and type, tiling the 105-character record with no gap and no overlap. It also carries the control totals a bank file is checked against: 8 records and 664944 cents.

File: JSON · Payroll Hr · 9 fields
Use case: Data import· Conversion set

Cobalt Operations Team: COBOL copybook for the payment file

COBOL copybook for the payment file for Cobalt Operations Team. A COBOL record description for the same 105-character layout, with PIC clauses matching bank-payment-layout.json field for field: X(n) for the alphanumeric fields and 9(9)V99 for the amount, which is where the two implied decimal places are declared. Comment lines carry the column ranges.

File: TXT · Payroll Hr · 9 fields
Use case: Data import· Conversion set

Cobalt Operations Team: Payroll journal batch

Payroll journal batch for Cobalt Operations Team. 9 double-entry lines and a batch total. Debits are the four expense accounts totalling 10542.17; credits are the five payable accounts totalling the same 10542.17, so the batch balances exactly. The net pay payable credit of 6649.44 is the bank payment file, and the pension and health payables carry both the employee deduction and the employer contribution, which is why they exceed the deduction figures on the register.

File: CSV · Payroll Hr · 10 rows
Use case: Data import· Conversion set

Cobalt Operations Team: Payroll journal batch JSON

Payroll journal batch JSON for Cobalt Operations Team. The same 9 lines as payroll-journal.csv with the posting rule stated. totals.debit and totals.credit are both 10542.17 and totals.difference is 0.00.

File: JSON · Payroll Hr · UTF-8
Use case: Data import· Conversion set

Cobalt Operations Team: Employer cost summary

Employer cost summary for Cobalt Operations Team. What the period actually costs the employer: 9072.00 of gross pay plus 272.16 of employer pension, 694.01 of payroll tax and 504.00 of health contribution, 10542.17 in total, which is 116.21 percent of gross and 31.38 per paid hour. None of it is deducted from pay: employees receive 6649.44.

File: CSV · Payroll Hr · 6 rows
Use case: Data import

Cobalt Operations Team: Year to date earnings

Year to date earnings for Cobalt Operations Team. Cumulative earnings over 5 identical periods, this one and 4 earlier ones on the same hours and rates. Every figure is exactly 5 times the corresponding period figure, so ytd_gross totals 45360.00, ytd_deductions 12112.80 and ytd_net 33247.20. The period-level identity survives: gross less deductions equals net on every row.

File: CSV · Payroll Hr · 9 rows
Use case: Data import

Cobalt Operations Team: Payroll reconciliation assertions

Payroll reconciliation assertions for Cobalt Operations Team. The eight identities this set claims with the figure each must produce: 9072.00 of gross from the shifts, 6649.44 of net after deductions, the same figure on the payslips and in the bank file, 664944 cents as the fixed-width control total, a journal balancing at 10542.17, 1470.17 of employer cost that is never a deduction, and 1168 hours of leave remaining. It also records the 58.80 size of the deliberate defect.

File: JSON · Payroll Hr · UTF-8
Use case: Data import

Juniper Workspace Cloud: Subscription invoice register

Subscription invoice register for Juniper Workspace Cloud. 17 invoices over three cycles: 12 monthly invoices for 2026-07 and 2026-08 and 5 for 2026-09. amount minus paid equals outstanding on every row. Billed totals 913.00 and outstanding 38.00, which is the 19.00 August invoice in dunning plus the 19.00 September invoice for the same account.

File: CSV · Saas Billing · 17 rows
Use case: Data import

Juniper Workspace Cloud: September invoice lines with mid-cycle proration

September invoice lines with mid-cycle proration for Juniper Workspace Cloud. 9 lines across 5 invoices. 5 are recurring plan lines summing to 235.00; 2 are proration credits summing to -49.00 for the unused half of a Team plan; 2 are proration charges summing to 59.00. One account upgrades Team to Studio and one downgrades Team to Basic, both effective 2026-09-16 with 15 of 30 days remaining. The lines sum to 245.00.

File: CSV · Saas Billing · 9 rows
Use case: Data import

Juniper Workspace Cloud: September invoices with proration as JSON

September invoices with proration as JSON for Juniper Workspace Cloud. The 5 September invoices nested with their lines, plus the stated proration basis. totals.total is 245.00 and totals.recurring is 235.00, which equals opening monthly recurring revenue.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Juniper Workspace Cloud: Invoice register widened to 40 columns

Invoice register widened to 40 columns for Juniper Workspace Cloud. The same 17 invoices as invoice-register.csv followed by 29 empty custom_field_NN columns, 40 in total. Every custom field is present in the header and empty in every row, which is what a billing platform export looks like when the tenant has defined no custom fields.

File: CSV · Saas Billing · 17 rows
Use case: Data import

Juniper Workspace Cloud: MRR movement report

MRR movement report for Juniper Workspace Cloud. Opening monthly recurring revenue 235.00 on 2026-09-01, expansion 50.00 from the Team to Studio upgrade, contraction -30.00 from the Team to Basic downgrade, churn -19.00 when account ACC-04 is cancelled on 2026-09-30, no new business, closing 236.00. The opening figure equals the recurring-line subtotal of invoice-lines-2026-09.csv exactly.

File: CSV · Saas Billing · 6 rows
Use case: Data import

Juniper Workspace Cloud: Closing MRR by account

Closing MRR by account for Juniper Workspace Cloud. 6 accounts with the plan each one holds at 2026-09-30 and the recurring revenue that plan carries. Two accounts are cancelled and carry 0.00; the remaining four sum to 236.00, the closing figure on mrr-movement.csv.

File: CSV · Saas Billing · 6 rows
Use case: Data import

Juniper Workspace Cloud: MRR movement report JSON

MRR movement report JSON for Juniper Workspace Cloud. The same movement as mrr-movement.csv with the reconciliation rule stated. openingMrr 235.00, closingMrr 236.00.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Juniper Workspace Cloud: MRR movement report that does not reconcile

MRR movement report that does not reconcile for Juniper Workspace Cloud. Identical to mrr-movement.csv except that the contraction row states -20.00 instead of -30.00. The from_plan and to_plan columns still say Team to Basic, a -30.00 drop, so the row contradicts itself as well as the closing total. Opening plus the four movement rows gives 246.00 while the closing row still states 236.00.

File: CSV · Saas Billing · 6 rows
Use case: Data importError handling

Juniper Workspace Cloud: Dunning sequence

Dunning sequence for Juniper Workspace Cloud. The 6 escalation steps against invoice INV-10 for account ACC-04, the one invoice in the model carrying an outstanding balance of 19.00. Steps run 2026-09-01 to 2026-09-30: reminder, two card retries that fail on insufficient_funds, a final notice, a third retry that fails on do_not_honor, then cancellation. Each row's next_action_date equals the attempt_date of the following row, and the last row has none.

File: CSV · Saas Billing · 6 rows
Use case: Data import

Juniper Workspace Cloud: Dunning sequence JSON

Dunning sequence JSON for Juniper Workspace Cloud. The same 6 steps as dunning-sequence.csv with the retry policy and the terminal state named. terminalState is cancelled.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Juniper Workspace Cloud: Failed payment attempt log

Failed payment attempt log for Juniper Workspace Cloud. The 3 card attempts behind the dunning sequence, with UTC timestamps, the gateway status and the decline code. All three are for 19.00 against invoice INV-10 and all three failed, which is why the balance never moves.

File: CSV · Saas Billing · 3 rows
Use case: Data import

Juniper Workspace Cloud: Raw metered usage events

Raw metered usage events for Juniper Workspace Cloud. 18 daily usage records over 2026-08-01 to 2026-08-03 for 6 accounts, carrying an export count and a storage reading in MB. These are the inputs the tiered usage bill is computed from; the exports column sums to 102.

File: CSV · Saas Billing · 18 rows
Use case: Data import

Juniper Workspace Cloud: Tiered usage rate card

Tiered usage rate card for Juniper Workspace Cloud. Two metered dimensions. Exports: the first 10 are included, units 11 to 20 cost 0.4000 each and everything above 20 costs 0.2500. Storage: 250 MB included, then 0.0150 per MB on the peak reading. The open-ended top tier has an empty to_unit.

File: CSV · Saas Billing · 5 rows
Use case: Data import

Juniper Workspace Cloud: Tiered usage bill

Tiered usage bill for Juniper Workspace Cloud. 6 accounts billed on the rate card. The tier columns split each account's exports across the three bands and always sum back to billable_exports. Export charges total 16.65, storage charges 7.89 and the usage bill 24.54. Account ACC-06 is the only one to reach the third tier, with 1 unit above 20.

File: CSV · Saas Billing · 6 rows
Use case: Data import

Juniper Workspace Cloud: Tiered usage bill JSON

Tiered usage bill JSON for Juniper Workspace Cloud. The same 6 accounts as usage-billing-tiered.csv with the rate card embedded as nested tier objects whose open-ended top band has upTo null. totals.usageTotal is 24.54.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Juniper Workspace Cloud: Revenue recognition and deferred revenue schedule

Revenue recognition and deferred revenue schedule for Juniper Workspace Cloud. 15 monthly periods from 2026-07 to 2027-09. Monthly subscriptions are recognised in their own service month, so the deferred balance is 0.00 until the 1069.20 annual contract is billed in 2026-09 for a service period starting 2026-10. That pushes deferred revenue to 1069.20 at 2026-09-30 and releases it at 89.10 a month until it reaches 0.00 at 2027-09. Billings and recognition both total 1963.20.

File: CSV · Saas Billing · 15 rows
Use case: Data import

Juniper Workspace Cloud: Revenue recognition schedule JSON

Revenue recognition schedule JSON for Juniper Workspace Cloud. The same 15 periods as the CSV with the recognition basis stated. totals.billed and totals.recognised are both 1963.20 and peakDeferred is 1069.20.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Juniper Workspace Cloud: Subscription plan catalog

Subscription plan catalog for Juniper Workspace Cloud. The 3 plans the accounts hold, with the monthly rate, the annual rate at a 10 percent discount and the metered allowances. The Studio annual rate 1069.20 is the amount actually billed on the annual contract invoice.

File: CSV · Saas Billing · 3 rows
Use case: Data import

Juniper Workspace Cloud: Subscription lifecycle events

Subscription lifecycle events for Juniper Workspace Cloud. The 4 events that move recurring revenue in September, each with a UTC timestamp and the MRR delta it causes. The deltas sum to 1.00, which is exactly closing MRR 236.00 minus opening MRR 235.00. The annual contract signing carries a 0.00 delta because the plan rate does not change.

File: CSV · Saas Billing · 4 rows
Use case: Data import

Juniper Workspace Cloud: Billing reconciliation assertions

Billing reconciliation assertions for Juniper Workspace Cloud. The six identities this set claims with their exact figures: opening MRR 235.00, closing MRR 236.00, September invoiced 245.00, usage 24.54 and lifetime billings equal to recognition at 1963.20.

File: JSON · Saas Billing · UTF-8
Use case: Data import

Alder Books Reconciliation: Chart of accounts

Chart of accounts for Alder Books Reconciliation. 9 postable accounts covering assets, liabilities, equity, income and expenses, with the normal balance side declared on every row. Codes run 1000 to 5200 and every account code used anywhere in the general ledger export appears here.

File: CSV · Accounting Ledgers · 9 rows
Use case: Data import

Alder Books Reconciliation: Chart of accounts JSON

Chart of accounts JSON for Alder Books Reconciliation. The same 9 accounts as chart-of-accounts.csv as a JSON array under an accounts key, with the reporting currency declared once at the top level.

File: JSON · Accounting Ledgers · 9 rows
Use case: Data import

Alder Books Reconciliation: General ledger export

General ledger export for Alder Books Reconciliation. 66 ledger lines in four journals: GEN carries the opening balance, SAL the 8 sales invoices, CSH the 8 cash receipts and PUR the 16 supplier payments. Debits total 22464.00 and credits the same, and every document_id posts a balanced pair of lines.

File: CSV · Accounting Ledgers · 66 rows
Use case: Data import

Alder Books Reconciliation: General ledger export JSON

General ledger export JSON for Alder Books Reconciliation. The same 66 lines as general-ledger-export.csv with a totals object declaring 22464.00 of debits and the same of credits. The period runs from the earliest invoice date 2026-07-02 to the last bank movement 2026-08-24.

File: JSON · Accounting Ledgers · 66 rows
Use case: Data import

Alder Books Reconciliation: General ledger with parenthesised credits and grouped thousands

General ledger with parenthesised credits and grouped thousands for Alder Books Reconciliation. The same 66 lines collapsed into one signed_amount column in accounting presentation: credits appear as (1,234.50) rather than -1234.50 and thousands carry comma separators. The first credit line reads (5,000.00). Summing the column requires stripping the separators and reading the parentheses as a negative sign.

File: CSV · Accounting Ledgers · 66 rows
Use case: Data import

Alder Books Reconciliation: General ledger in the European CSV dialect

General ledger in the European CSV dialect for Alder Books Reconciliation. The same 66 ledger lines with a semicolon delimiter, decimal commas, dot thousands separators and dd/mm/yyyy posting dates. This is the shape a ledger export from a European accounting package arrives in.

File: CSV · Accounting Ledgers · 66 rows
Use case: Data import

Alder Books Reconciliation: Trial balance that balances

Trial balance that balances for Alder Books Reconciliation. 9 accounts plus a TOTAL row. Debits and credits each come to 13100.00, so the difference is exactly 0.00. Cash carries 10236.00, which is the closing balance of the bank statement; receivables carry 800.00, which is the aged debtors total; and the two accounts with no movement are reported at 0.00 rather than omitted.

File: CSV · Accounting Ledgers · 10 rows
Use case: Data import

Alder Books Reconciliation: Trial balance JSON

Trial balance JSON for Alder Books Reconciliation. The same 9 accounts as trial-balance.csv with the totals lifted into their own object: debit 13100.00, credit 13100.00, difference 0.00. The TOTAL row is not repeated inside the accounts array, so summing the array cannot double count.

File: JSON · Accounting Ledgers · UTF-8
Use case: Data import

Alder Books Reconciliation: Trial balance out by 1250.00

Trial balance out by 1250.00 for Alder Books Reconciliation. Identical to trial-balance.csv except that account 5200 Services expense is stated as 1923.00 instead of 673.00. Debits therefore come to 14350.00 against credits of 13100.00, a difference of exactly 1250.00. The TOTAL row is recalculated and agrees with the account rows, so the file is internally consistent and only the double-entry rule is broken.

File: CSV · Accounting Ledgers · 10 rows
Use case: Data importError handling

Alder Books Reconciliation: Balanced manual journal batch

Balanced manual journal batch for Alder Books Reconciliation. 3 month-end journals of 2 lines each, 6 lines in total: an accrual, a reclassification and a prepayment release. Each batch_id balances on its own and the batch as a whole posts 339.75 of debits and the same of credits.

File: CSV · Accounting Ledgers · 6 rows
Use case: Data import

Alder Books Reconciliation: Journal batch with one entry out by 45.00

Journal batch with one entry out by 45.00 for Alder Books Reconciliation. The same 3 journals as journal-batch.csv except that line 2 of JB-2026-08-02 credits 19.50 where its debit line is 64.50. That one journal is out by 45.00; the other two balance exactly, which is what makes this the realistic case: a batch-level check catches it only because nothing else offsets it.

File: CSV · Accounting Ledgers · 6 rows
Use case: Data importError handling

Alder Books Reconciliation: Bank statement CSV

Bank statement CSV for Alder Books Reconciliation. 24 transactions from 2026-08-01 to 2026-08-24 in separate debit and credit columns, with a running balance. The statement opens at 5000.00 and closes at 10236.00; 8 credits total 7300.00 and 16 debits total 2064.00.

File: CSV · Accounting Ledgers · 24 rows
Use case: Data import

Alder Books Reconciliation: camt.053 bank statement

camt.053 bank statement for Alder Books Reconciliation. An ISO 20022 camt.053.001.02 BankToCustomerStatement carrying the same 24 entries as bank-statement.csv. The OPBD balance is 5000.00 and the CLBD balance 10236.00; TxsSummry declares 8 credit entries totalling 7300.00 and 16 debit entries totalling 2064.00, and Ntry elements are present for all 24.

File: XML · Accounting Ledgers · UTF-8
Use case: Data import

Alder Books Reconciliation: camt.053 whose entry count does not match its entries

camt.053 whose entry count does not match its entries for Alder Books Reconciliation. Well-formed XML with the same header, balances and TxsSummry as bank-statement-camt053.xml, but the final Ntry, TXN-024 for 206.00 on 2026-08-24, has been dropped. NbOfNtries still declares 24 while only 23 Ntry elements are present, and the entries now sum to 10442.00 against a CLBD balance of 10236.00.

File: XML · Accounting Ledgers
Use case: Data importError handling

Alder Books Reconciliation: MT940 bank statement

MT940 bank statement for Alder Books Reconciliation. A SWIFT MT940 customer statement with tags :20:, :25:, :28C:, :60F:, 24 :61:/:86: pairs, :62F: and :64:. Amounts use the MT decimal comma and dates the YYMMDD form, so the opening balance reads C260801USD5000,00 and the closing balance C260824USD10236,00. Line endings are CRLF, as the MT message format requires.

File: TXT · Accounting Ledgers · ASCII
Use case: Data import

Alder Books Reconciliation: MT940 whose :62F: closing balance is out by 100.00

MT940 whose :62F: closing balance is out by 100.00 for Alder Books Reconciliation. Identical to bank-statement-mt940.txt in every tag except :62F: and :64:, which state C260824USD10336,00 where the 24 :61: movements applied to the :60F: opening balance give C260824USD10236,00. The file is out by exactly 100.00 and nothing inside the statement explains the difference.

File: TXT · Accounting Ledgers
Use case: Data importError handling

Alder Books Reconciliation: OFX 1.0.3 bank statement

OFX 1.0.3 bank statement for Alder Books Reconciliation. An OFX 1.0.3 bank download in the SGML form: nine colon-delimited header lines, a blank line, then unclosed tags inside <OFX>. It carries 24 STMTTRN records with DTPOSTED in YYYYMMDD form and TRNAMT signed, plus a LEDGERBAL of 10236.00 dated 20260824. Line endings are CRLF, as OFX 1.x files from banks are.

File: OFX · Accounting Ledgers · ASCII
Use case: Data import

Alder Books Reconciliation: QIF bank statement

QIF bank statement for Alder Books Reconciliation. A Quicken Interchange Format export opening with !Type:Bank and carrying 24 records terminated by a caret on its own line. Dates use the ambiguous mm/dd/yyyy form QIF is notorious for, amounts are signed with no currency, and there is no balance field at all, so the 10236.00 closing figure can only be derived. Line endings are CRLF.

File: QIF · Accounting Ledgers · 24 records
Use case: Data import

Alder Books Reconciliation: Bank reconciliation

Bank reconciliation for Alder Books Reconciliation. All 24 statement transactions matched one for one to a cash-account ledger line, with a difference column that is 0.00 on every row. There are no unpresented items and no deposits in transit, so the book balance 10236.00 equals the statement balance 10236.00 and the reconciling difference is 0.00.

File: CSV · Accounting Ledgers · 24 rows
Use case: Data import

Alder Books Reconciliation: Bank reconciliation JSON

Bank reconciliation JSON for Alder Books Reconciliation. The same 24 matches as bank-reconciliation.csv with the reconciliation summary at the top: statement closing 10236.00, book closing 10236.00, nothing outstanding or unpresented and a reconciling difference of 0.00.

File: JSON · Accounting Ledgers · UTF-8
Use case: Data import

Alder Books Reconciliation: Aged debtors report

Aged debtors report for Alder Books Reconciliation. 8 open receivables aged at 2026-09-08, each with 100.00 outstanding against an invoice of between 750.00 and 1275.00. The ageing buckets hold 0.00 current, 500.00 at 31 to 60 days and 300.00 at 61 to 90 days, summing to 800.00, the receivables line of the trial balance.

File: CSV · Accounting Ledgers · 9 rows
Use case: Data import

Alder Books Reconciliation: Aged creditors summary

Aged creditors summary for Alder Books Reconciliation. The 3 suppliers behind the 16 operating payments, grouped by expense category. The amounts due are 774.00, 617.00, 673.00 and they sum to 2064.00, which is the total of the three actual columns on the budget report.

File: CSV · Accounting Ledgers · 3 rows
Use case: Data import

Alder Books Reconciliation: Budget versus actual

Budget versus actual for Alder Books Reconciliation. 3 expense categories for 2026-08 with budget, actual, variance and variance percent. Budgets total 4200.00 against actuals of 2064.00, leaving 2136.00 unspent. Every actual equals the sum of the ledger postings to that expense account.

File: CSV · Accounting Ledgers · 3 rows
Use case: Data import

Alder Books Reconciliation: ISO 20022 pain.001 payment initiation

ISO 20022 pain.001 payment initiation for Alder Books Reconciliation. A pain.001.001.03 CustomerCreditTransferInitiation paying the 3 suppliers on aged-creditors.csv. GrpHdr declares NbOfTxs 3 and CtrlSum 2064.00; the single PmtInf block repeats those figures and contains 3 CdtTrfTxInf blocks for 774.00, 617.00, 673.00, each with a creditor IBAN and BIC.

File: XML · Accounting Ledgers · UTF-8
Use case: Data import

Alder Books Reconciliation: SAF-T style ledger extract

SAF-T style ledger extract for Alder Books Reconciliation. An audit-file extract structured after the OECD SAF-T 2.0 element names: Header, MasterFiles with 9 GeneralLedgerAccounts and 8 Customers, then GeneralLedgerEntries declaring NumberOfEntries 33, TotalDebit 22464.00 and TotalCredit 22464.00, with one Transaction per document and 66 Line elements in total.

File: XML · Accounting Ledgers · UTF-8
Use case: Data import

Alder Books Reconciliation: Fixed-width general ledger feed

Fixed-width general ledger feed for Alder Books Reconciliation. 66 records of exactly 120 characters each, the shape a legacy banking or ERP feed still arrives in. Amounts are unsigned cents, zero filled and right justified in a 14-character field, so 5000.00 is written as 00000000500000. Text fields are space padded and truncated at their declared width. There is no delimiter and no header row; the column map is gl-feed-layout.json.

File: TXT · Accounting Ledgers · 66 records
Use case: Data import

Alder Books Reconciliation: Fixed-width GL feed column map

Fixed-width GL feed column map for Alder Books Reconciliation. The documented column map for gl-feed-fixed-width.txt: 7 fields with 1-based start position, length, end position and type, adding up to the declared 120-character record. It also states the padding rules and that amounts carry two implied decimal places.

File: JSON · Accounting Ledgers · 7 fields
Use case: Data import

Alder Books Reconciliation: Fixed-width GL feed with one record a byte short

Fixed-width GL feed with one record a byte short for Alder Books Reconciliation. The same 66 records as gl-feed-fixed-width.txt except that record 5 is 119 characters instead of 120: the final character of the 4-character currency field has been lost. Every other record is correct, so a reader that splits on newlines and slices by position reads USD as US on that one record and carries on silently.

File: TXT · Accounting Ledgers · 66 records
Use case: Data importError handling

Alder Books Reconciliation: COBOL copybook for the GL feed

COBOL copybook for the GL feed for Alder Books Reconciliation. A COBOL record description for the same 120-character layout, with PIC clauses matching gl-feed-layout.json field for field: X(n) for the alphanumeric fields and 9(12)V99 for the two amount fields, which is where the two implied decimal places are declared. Comment lines carry the column ranges.

File: TXT · Accounting Ledgers · 7 fields
Use case: Data import

Alder Books Reconciliation: Ledger reconciliation assertions

Ledger reconciliation assertions for Alder Books Reconciliation. The six identities this set claims with their figures: ledger totals 22464.00, trial balance 13100.00 each side, cash 10236.00, receivables 800.00, a 0.00 bank reconciliation and a pain.001 control sum of 2064.00. It also records the exact size and cause of all five deliberate defects in the set.

File: JSON · Accounting Ledgers · UTF-8
Use case: Data import

Alder Table Bistro: Allergen menu as data

Allergen menu as data for Alder Table Bistro. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 2 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Alder Table Bistro: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Alder Table Bistro. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-02 Tomato soup is printed on printed-menu.pdf at 11.50 CAD and declares 1 allergen in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Alder Table Bistro: Drinks list as data

Drinks list as data for Alder Table Bistro. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Alder Table Bistro: Digital menu

Digital menu for Alder Table Bistro. One document holding the whole front of house: 3 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Alder Table Bistro: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Alder Table Bistro. A schema.org Menu document with 7 MenuSection nodes, 5 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Alder Table Bistro: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Alder Table Bistro. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$11.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Alder Table Bistro: Till import

Till import for Alder Table Bistro. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Alder Table Bistro: Till import in the European dialect

Till import in the European dialect for Alder Table Bistro. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "é", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Alder Table Bistro: Till import with a duplicate item code

Till import with a duplicate item code for Alder Table Bistro. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 11.50 CAD and again on line 23 at 12.50 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Allergen menu as data

Allergen menu as data for Juniper Corner Cafe. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 4 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Corner Cafe: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Juniper Corner Cafe. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Flat white is printed on printed-menu.pdf at 4.75 CAD and declares 1 allergen in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Drinks list as data

Drinks list as data for Juniper Corner Cafe. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Juniper Corner Cafe: Digital menu

Digital menu for Juniper Corner Cafe. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Juniper Corner Cafe: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Juniper Corner Cafe. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Juniper Corner Cafe: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Juniper Corner Cafe. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$4.75", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Juniper Corner Cafe: Till import

Till import for Juniper Corner Cafe. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Corner Cafe: Till import in the European dialect

Till import in the European dialect for Juniper Corner Cafe. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "é", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Juniper Corner Cafe: Till import with a duplicate item code

Till import with a duplicate item code for Juniper Corner Cafe. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 5.50 CAD and again on line 23 at 6.50 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Allergen menu as data

Allergen menu as data for Copper Oven Bakery. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 4 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Copper Oven Bakery: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Copper Oven Bakery. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Yeasted loaf is printed on printed-menu.pdf at 7.50 CAD and declares 1 allergen in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Drinks list as data

Drinks list as data for Copper Oven Bakery. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Copper Oven Bakery: Digital menu

Digital menu for Copper Oven Bakery. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Copper Oven Bakery: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Copper Oven Bakery. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 30 MenuItem nodes carrying 30 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Copper Oven Bakery: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Copper Oven Bakery. Intentionally invalid. All 30 Offer nodes carry price as a JSON string with a currency symbol, the first being "$7.50", where menu.jsonld carries the same 30 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Copper Oven Bakery: Till import

Till import for Copper Oven Bakery. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Copper Oven Bakery: Till import in the European dialect

Till import in the European dialect for Copper Oven Bakery. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "à", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Copper Oven Bakery: Till import with a duplicate item code

Till import with a duplicate item code for Copper Oven Bakery. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 4.25 CAD and again on line 23 at 5.25 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Allergen menu as data

Allergen menu as data for Ember Lane Pizza. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 4 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Ember Lane Pizza: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Ember Lane Pizza. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Margherita pizza is printed on printed-menu.pdf at 17.00 CAD and declares 2 allergens in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Drinks list as data

Drinks list as data for Ember Lane Pizza. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Ember Lane Pizza: Digital menu

Digital menu for Ember Lane Pizza. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Ember Lane Pizza: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Ember Lane Pizza. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Ember Lane Pizza: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Ember Lane Pizza. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$17.00", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Ember Lane Pizza: Till import

Till import for Ember Lane Pizza. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Ember Lane Pizza: Till import in the European dialect

Till import in the European dialect for Ember Lane Pizza. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "à", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Ember Lane Pizza: Till import with a duplicate item code

Till import with a duplicate item code for Ember Lane Pizza. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 20.00 CAD and again on line 23 at 21.00 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Allergen menu as data

Allergen menu as data for Cedar Street Tacos. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 0 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Cedar Street Tacos: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Cedar Street Tacos. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Chicken taco trio is printed on printed-menu.pdf at 13.50 CAD and declares 0 allergens in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Drinks list as data

Drinks list as data for Cedar Street Tacos. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Cedar Street Tacos: Digital menu

Digital menu for Cedar Street Tacos. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Cedar Street Tacos: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Cedar Street Tacos. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Cedar Street Tacos: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Cedar Street Tacos. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$13.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Cedar Street Tacos: Till import

Till import for Cedar Street Tacos. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Cedar Street Tacos: Till import in the European dialect

Till import in the European dialect for Cedar Street Tacos. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "ï", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Cedar Street Tacos: Till import with a duplicate item code

Till import with a duplicate item code for Cedar Street Tacos. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 11.00 CAD and again on line 23 at 12.00 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Allergen menu as data

Allergen menu as data for Willow Event Kitchen. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 3 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Willow Event Kitchen: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Willow Event Kitchen. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Chicken buffet portion is printed on printed-menu.pdf at 21.00 CAD and declares 1 allergen in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Drinks list as data

Drinks list as data for Willow Event Kitchen. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Willow Event Kitchen: Digital menu

Digital menu for Willow Event Kitchen. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Willow Event Kitchen: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Willow Event Kitchen. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Willow Event Kitchen: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Willow Event Kitchen. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$21.00", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Willow Event Kitchen: Till import

Till import for Willow Event Kitchen. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Willow Event Kitchen: Till import in the European dialect

Till import in the European dialect for Willow Event Kitchen. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "é", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Willow Event Kitchen: Till import with a duplicate item code

Till import with a duplicate item code for Willow Event Kitchen. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 18.00 CAD and again on line 23 at 19.00 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: Allergen menu as data

Allergen menu as data for Harbour Kitchen Group. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 3 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.

File: CSV · Restaurant Menus · 4 rows
Use case: Data importCSV parsing· Paired fixture

Harbour Kitchen Group: Allergen menu missing a dish on the menu

Allergen menu missing a dish on the menu for Harbour Kitchen Group. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 House burger is printed on printed-menu.pdf at 18.50 CAD and declares 2 allergens in the costing folder, and it has no row here. The remaining rows are correct.

File: CSV · Restaurant Menus · 3 rows
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: Drinks list as data

Drinks list as data for Harbour Kitchen Group. 8 rows and 7 columns pairing every printed drink line with the till item code it imports as, the serve size in millilitres and the basis of its price. The three drinks sold both ways appear twice, once per service.

File: CSV · Restaurant Menus · 8 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Digital menu

Digital menu for Harbour Kitchen Group. One document holding the whole front of house: 2 printed sections with 4 dishes, 8 drink lines, the set menu, the specials and the 14 entry allergen key. Every dish carries its plate cost and the paths of the two costing files it was read from, so the join back to plate-costs.csv can be checked without guessing.

File: JSON · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Conversion set

Harbour Kitchen Group: Menu as schema.org JSON-LD

Menu as schema.org JSON-LD for Harbour Kitchen Group. A schema.org Menu document with 6 MenuSection nodes, 4 of them top level, and 27 MenuItem nodes carrying 27 Offer nodes, each with price as a JSON number and priceCurrency CAD. Modifiers are menuAddOn MenuItems and every declared allergen travels as an additionalProperty PropertyValue. This is the structured data shape a search engine reads, and it is rare as a downloadable fixture.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importJSON parsing+1· Paired fixture

Harbour Kitchen Group: Menu JSON-LD with string prices

Menu JSON-LD with string prices for Harbour Kitchen Group. Intentionally invalid. All 27 Offer nodes carry price as a JSON string with a currency symbol, the first being "$18.50", where menu.jsonld carries the same 27 prices as JSON numbers. Nothing else differs, so a consumer that accepts text prices reports the file as fine and then fails on the arithmetic.

File: JSONLD · Restaurant Menus · UTF-8
Use case: Data importError handling+1· Paired fixture

Harbour Kitchen Group: Till import

Till import for Harbour Kitchen Group. 21 rows and 6 columns in the shape a point of sale ingests: item_code, item_name, category, price, tax_code, modifier_group. 4 dishes, 8 modifier options across 4 groups, 8 drink lines and one stored value line. Item codes are letter prefixed so a spreadsheet cannot eat a leading zero, and two tax codes are present so a mapping has something to map.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing· Paired fixture

Harbour Kitchen Group: Till import in the European dialect

Till import in the European dialect for Harbour Kitchen Group. The same 21 rows as pos-import.csv in the other dialect a till exports: semicolon delimited, decimal comma in the price column, Latin-1 encoded and CRLF terminated. It carries the non-ASCII characters "à", so reading it as UTF-8 raises a decode error instead of silently producing mojibake.

File: CSV · Restaurant Menus · 21 rows
Use case: Data importCSV parsing+1· Conversion set

Harbour Kitchen Group: Till import with a duplicate item code

Till import with a duplicate item code for Harbour Kitchen Group. Intentionally invalid. 22 rows where pos-import.csv has 21. item_code MENU-02 appears on line 3 at 19.50 CAD and again on line 23 at 20.50 CAD, which is the proposed price in the shared menu_price_changes table. It is the only repeated code in the file, so an importer that keeps the last row it reads silently ships the later price.

File: CSV · Restaurant Menus · 22 rows
Use case: Data importError handling+1· Paired fixture

Tern Client Services: Contract register

Contract register for Tern Client Services. 11 agreements across five document types with their effective dates, terms, expiry dates, notice deadlines and values. The three rows whose value_basis is "not to exceed" sum to 9,000.00 USD, the liability cap the master agreement states at clause 10.2. 2 rows carry an empty value because the document has no monetary value, and 2 carry an empty file because no rendering of that contractor agreement ships in this set.

File: CSV · Contracts Agreements · 11 rows
Use case: Data importCSV parsing· Paired fixture

Tern Client Services: Contract register JSON

Contract register JSON for Tern Client Services. The same 11 agreements as an object with a contracts array. Empty CSV cells become empty strings rather than null, so a reader that treats the two as the same thing and one that does not will both produce the same record count.

File: JSON · Contracts Agreements · 11 records
Use case: Data importJSON parsing· Paired fixture

Tern Client Services: Rate card and caps

Rate card and caps for Tern Client Services. 5 priced terms drawn from the agreements in this set: the 100.00 USD client billing rate, the 60.00 USD contractor pay rate, both expense caps with the dates that separate them, and the 9,000.00 USD liability cap. Every row names the clause it comes from.

File: CSV · Contracts Agreements · 5 rows
Use case: Data importCSV parsing

Tern Client Services: Amendment register

Amendment register for Tern Client Services. Two rows, one per varied clause, each carrying the previous value and the new one so a reader can reconstruct the agreement as it stood on any date. Clause 4.1 moves from 250.00 to 400.00 and clause 5.1 from ten to fifteen business days for one statement of work only.

File: CSV · Contracts Agreements · 2 rows
Use case: Data importCSV parsing

Tern Client Services: Statement of work deliverables

Statement of work deliverables for Tern Client Services. 9 deliverables across the three statements of work, each with a due date, an allocation, the not-to-exceed value of its own statement of work and a single testable acceptance criterion. Grouped by sow_id the allocations sum to exactly 2000.00, 3000.00 and 4000.00, matching the sow_not_to_exceed_usd column on every row of the group. Two rows are marked accepted on 2026-08-24 and carry an accepted_date; the other seven have an empty accepted_date.

File: CSV · Contracts Agreements · 9 rows
Use case: Data importCSV parsing· Paired fixture

Tern Client Services: Statement of work deliverables with an allocation that does not add up

Statement of work deliverables with an allocation that does not add up for Tern Client Services. The same 9 rows as sow-deliverables.csv with one number changed: the SOW-2026-03 D2 allocation is 2150.00 instead of 2200.00. The three SOW-2026-03 allocations therefore sum to 3950.00 against the 4000.00 that every row of that group states as sow_not_to_exceed_usd, a shortfall of 50.00 USD. The other two statements of work still balance exactly.

File: CSV · Contracts Agreements · 9 rows
Use case: Data importCSV parsing+1· Paired fixture

Tern Client Services: Clause index

Clause index for Tern Client Services. Every sub-clause of the three agreements in this set as one row: 57 rows across 3 documents, with the clause number, the heading it sits under, the clauses it refers to and its character count. 16 rows carry at least one cross-reference and every one of those resolves to a clause that exists in the same document.

File: CSV · Contracts Agreements · 57 rows
Use case: Data importCSV parsing· Conversion set

Tern Client Services: Obligation register

Obligation register for Tern Client Services. 14 obligations pulled out of the three agreements, each naming the contract, the exact clause it comes from, who owns it, what triggers it and when it falls due. Every clause_ref resolves to a row of contract-clause-index.csv.

File: CSV · Contracts Agreements · 14 rows
Use case: Data importCSV parsing· Conversion set

Tern Client Services: Execution and signature log

Execution and signature log for Tern Client Services. 19 signature rows covering every executed document in this set. 2 rows have an empty signed_date and an empty method because the counterparty has not signed yet, and their status column says so, so a reader that treats an empty date as a parse failure and one that treats it as unsigned reach different conclusions about the same file.

File: CSV · Contracts Agreements · 19 rows
Use case: Data importCSV parsing

Tern Client Services: Renewal and notice diary

Renewal and notice diary for Tern Client Services. 8 dated events in ascending order, each with the number of days from the fixed snapshot of 2026-09-08. The first is 2026-09-18 at 10 days and the last is 2028-11-09 at 793 days. Every date also appears in contract-register.csv, so the diary can be rebuilt from the register and compared.

File: CSV · Contracts Agreements · 8 rows
Use case: Data importCSV parsing

Tern Client Services: Contract reconciliation identities

Contract reconciliation identities for Tern Client Services. 6 named identities with the figures behind each one, including the two places this set deliberately holds different numbers for the same hours: 100.00 USD billed and 60.00 USD paid per hour, and accepted allocation against billed time on PROJECT-1. The deliberate defect and its measured shortfall of 50.00 USD are listed separately.

File: JSON · Contracts Agreements
Use case: Data importJSON parsing

Pine Property Services: Schedule of insured locations

Schedule of insured locations for Pine Property Services. The 6 scheduled properties with their insured values and each one share of the 2,700,000.00 USD total. The share column is apportioned by largest remainder at four decimal places, so the six shares sum to exactly 100.0000 rather than to 100.0002, which is what rounding each share independently produces.

File: CSV · Insurance Documents · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Schedule of insured vehicles

Schedule of insured vehicles for Pine Property Services. The 4 scheduled vehicles with the delivery route each is assigned to and a flat 620.00 USD premium each, which is the 2,480.00 USD commercial auto line on the policy schedule. The vehicle and route identifiers are the ones the inventory-manufacturing model holds.

File: CSV · Insurance Documents · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Coverage limits

Coverage limits for Pine Property Services. 6 coverage lines. Three of them carry an empty premium_usd because they are sub-limits of the general liability premium rather than separately rated, and the four rows that do carry a premium sum to the 7,040.00 USD base premium on the policy schedule.

File: CSV · Insurance Documents · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Endorsement schedule

Endorsement schedule for Pine Property Services. 4 endorsements with their effective dates and premiums. Two attach at inception and two mid-term, and the four premiums sum to 590.00 USD, the endorsement line of the premium breakdown. E01 and E02 are the two a certificate of insurance has to reflect, and the certificate register carries a column for each.

File: CSV · Insurance Documents · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Premium breakdown

Premium breakdown for Pine Property Services. The full premium chain in 11 numbered lines, each stating the basis it is computed from, so every subtotal can be recomputed from the lines above it. Line 1 is 2700000.00 of insured value at 0.85 per 1000, which is 2295.00; line 11 is 8016.08 USD.

File: CSV · Insurance Documents · 11 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Premium instalment schedule

Premium instalment schedule for Pine Property Services. 5 instalments with a running balance that starts at 8,016.08 USD and reaches exactly 0.00 on the last row. The first 4 are 1603.22 and the last is 1603.20, because 8,016.08 divided by 5 does not land on a whole cent and the remainder is taken off the final instalment.

File: CSV · Insurance Documents · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Certificate of insurance register

Certificate of insurance register for Pine Property Services. 6 certificates, one per scheduled property, all issued 2026-09-08 against policy POL-2026-GL-0001 and all expiring 2027-03-31. days_until_expiry is 204 on every row, which is policy_end minus issue_date, and every row is positive because every certificate was issued while its cover was live.

File: CSV · Insurance Documents · 6 rows
Use case: Data importCSV parsing· Paired fixture

Pine Property Services: Certificate register with a certificate that expired before it was issued

Certificate register with a certificate that expired before it was issued for Pine Property Services. The same 6 valid rows with a seventh added: COI-2026-0007 is issued 2026-09-08 against a policy period that ended 2026-03-31, 161 days earlier, and its days_until_expiry cell reads -161. The row is internally consistent, so the arithmetic check passes and only the business rule that a certificate cannot be issued after its cover ends catches it. Its status still says in force.

File: CSV · Insurance Documents · 7 rows
Use case: Data importCSV parsing+1· Paired fixture

Pine Property Services: Certificate holder register

Certificate holder register for Pine Property Services. The 6 parties who require a certificate, each naming the endorsement that makes them an additional insured and the endorsement that waives subrogation. Every holder appears exactly once in certificate-of-insurance-register.csv.

File: CSV · Insurance Documents · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Claim settlement lines

Claim settlement lines for Pine Property Services. The same seven lines as the settlement statement with the sign held in its own column rather than embedded in the amount, so amounts are all positive and a reader has to apply the sign to reproduce the running balance. Applying the signs in order reproduces every running value and ends at 17400.00.

File: CSV · Insurance Documents · 7 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Claim register

Claim register for Pine Property Services. 3 claims against policy POL-2026-GL-0001, each joined to the work order and property the trades-property model holds. incurred_usd is paid_usd plus reserve_usd on every row; the three rows sum to 17,890.00 paid, 2,760.00 reserved and 20,650.00 incurred. One claim closed without payment because it was assessed below the 1,000.00 USD deductible.

File: CSV · Insurance Documents · 3 rows
Use case: Data importCSV parsing· Paired fixture

Pine Property Services: Claim register JSON

Claim register JSON for Pine Property Services. The same 3 claims with the three column totals hoisted into a totals object, so a reader can check its own aggregation against the file rather than only against another file.

File: JSON · Insurance Documents · 3 records
Use case: Data importJSON parsing· Paired fixture

Pine Property Services: Loss run report

Loss run report for Pine Property Services. The policy-year loss run: 3 claims with a total row. Paid 17,890.00, reserved 2,760.00, incurred 20,650.00 USD against an earned premium of 3,344.66 USD at the 2026-09-08 snapshot, a loss ratio of 617.4 percent. Earned premium is the 7,630.00 USD subtotal, excluding fees and tax, for the 160 days of the 365 day policy period that have elapsed.

File: CSV · Insurance Documents · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Broker account statement

Broker account statement for Pine Property Services. The broker side of the same premium: 7,630.00 USD of written premium, 12.5 percent commission of 953.75 USD, and 7,062.33 USD remitted to the insurer out of the 8,016.08 USD collected. Commission is charged on the subtotal only, not on the fees or the tax, which is why line 2 is not a percentage of line 5.

File: CSV · Insurance Documents · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Insurance reconciliation identities

Insurance reconciliation identities for Pine Property Services. 6 named identities covering the premium chain, the instalment remainder, the apportioned insured values, the settlement calculation, the loss run and the broker account, with the figures behind each. The two deliberately invalid files and their measured 161 day gap are listed separately.

File: JSON · Insurance Documents
Use case: Data importJSON parsing

Juniper Workspace Cloud: Register of members

Register of members for Juniper Workspace Cloud. The 4 members with their holdings, certificate numbers and amounts paid. shares_held sums to 600,000, which is the total_issued_shares value every row carries, and percent_of_issued sums to exactly 100.0000. amount_paid_usd sums to 20,400.00 USD, which is the 6,000.00 USD of nominal capital plus the 14,400.00 USD share premium from the 2026-05-18 allotment.

File: CSV · Corporate Records · 4 rows
Use case: Data importCSV parsing· Paired fixture

Juniper Workspace Cloud: Register of members whose holdings do not add up to the issued capital

Register of members whose holdings do not add up to the issued capital for Juniper Workspace Cloud. The same 4 members with one number changed: MEM-03 holds 59,500 shares instead of 60,000. shares_held now sums to 599,500 against the 600,000 that every row still declares as total_issued_shares, a shortfall of 500 shares, 5.00 USD of nominal capital. percent_of_issued and amount_paid_usd are untouched, so three columns of the same row now disagree with each other.

File: CSV · Corporate Records · 4 rows
Use case: Data importCSV parsing+1· Paired fixture

Juniper Workspace Cloud: Register of members JSON

Register of members JSON for Juniper Workspace Cloud. The same 4 members plus the two cancelled certificates the CSV cannot hold, because a cancelled certificate has no current holding and would need a row with an empty share count. A reader that counts certificates from this file gets six; a reader that counts holdings gets four.

File: JSON · Corporate Records · 4 members
Use case: Data importJSON parsing· Conversion set

Juniper Workspace Cloud: Capitalisation table

Capitalisation table for Juniper Workspace Cloud. The 4 holdings split into nominal and premium with a total row. Only MEM-04 carries premium, 14,400.00 USD, because only the 2026-05-18 allotment was priced above nominal, at 0.25 against 0.01. The percentages are apportioned by largest remainder and sum to exactly 100.0000.

File: CSV · Corporate Records · 5 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Share allotment return

Share allotment return for Juniper Workspace Cloud. 4 allotment rows across two returns. On every row consideration is shares times price and also equals nominal plus premium. The three founding rows are priced at nominal so their premium is 0.00; the 2026-05-18 row is priced at 0.25 against a 0.01 nominal, so 15,000.00 USD of consideration splits into 600.00 nominal and 14,400.00 premium.

File: CSV · Corporate Records · 4 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Shareholding movement history

Shareholding movement history for Juniper Workspace Cloud. 5 movements in date order: four allotments that raise the shares in issue to 600,000 and one transfer of 18,000 shares from MEM-03 to MEM-02 that leaves the total unchanged. Replaying the movements from zero reproduces every holding in register-of-members.csv, including the certificate cancellations the transfer caused.

File: CSV · Corporate Records · 5 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Register of directors and secretaries

Register of directors and secretaries for Juniper Workspace Cloud. 5 officers of whom 4 are currently in office. One row has a resigned_on date of 2026-05-18 and currently_in_office false; the other four have an empty resigned_on. The same date is the board meeting that appointed the replacement, so the register and the minutes agree.

File: CSV · Corporate Records · 5 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Register of persons with significant control

Register of persons with significant control for Juniper Workspace Cloud. The two members holding more than 25 percent of the shares, with their holdings and percentages taken from the register of members. MEM-03 and MEM-04 hold 10.0000 percent each and are correctly absent, so a reader that expects every member to appear here will look for two rows that should not exist.

File: CSV · Corporate Records · 2 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Register of charges

Register of charges for Juniper Workspace Cloud. Two charges, one satisfied and one outstanding. The outstanding floating charge secures 48,000.00 USD, which is the same principal as the loan facility in the banking set, so the two sets describe the same borrowing from the lender side and the borrower side.

File: CSV · Corporate Records · 2 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Statutory registers index

Statutory registers index for Juniper Workspace Cloud. 6 registers with the file that holds each one, the article clause that requires it, the number of entries and the date it was last updated. Every file named exists in this directory and every entry count matches the row count of that file.

File: CSV · Corporate Records · 6 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Meeting attendance register

Meeting attendance register for Juniper Workspace Cloud. 8 attendance rows across two board meetings. The attended column carries three values, true, false and in attendance, because the secretary attends without being a director and does not count towards the quorum. Both meetings met the quorum of two directors with two and three directors present.

File: CSV · Corporate Records · 8 rows
Use case: Data importCSV parsing· Conversion set

Juniper Workspace Cloud: Annual return JSON

Annual return JSON for Juniper Workspace Cloud. The same five parts as a nested object with shareCapital, members, officers, personsWithSignificantControl and charges arrays. Numbers that are counts are JSON numbers and numbers that are money are strings with two decimals, so a reader that coerces everything to float loses the trailing zero on 6000.00 and on 14400.00.

File: JSON · Corporate Records · 4 members
Use case: Data importJSON parsing· Paired fixture

Juniper Workspace Cloud: Annual return XML

Annual return XML for Juniper Workspace Cloud. The same return as XML, with counts as attributes on the container elements and the member name as element text rather than an attribute, so a reader has to take values from both places. Each count attribute equals the number of child elements below it.

File: XML · Corporate Records · 4 members
Use case: Data importSchema validation· Conversion set

Juniper Workspace Cloud: Corporate reconciliation identities

Corporate reconciliation identities for Juniper Workspace Cloud. 6 named identities covering the issued and paid capital, the allotment split, the neutrality of the transfer, the resolution threshold and the trading figures the September minutes quote, with the numbers behind each. The deliberate defect and its 500 share shortfall are listed separately.

File: JSON · Corporate Records
Use case: Data importJSON parsing

Fieldnote Supply Shop: Sales tax filing worksheet

Sales tax filing worksheet for Fieldnote Supply Shop. The 6 jurisdictions this shop collected in during 2026-08-01 to 2026-08-31, taken to the point of remittance. Net tax due sums to 88.88 USD, exactly the figure the wave-one tax-summary.csv reaches by a different route; two jurisdictions allow a vendor collection discount, which takes 0.13 off, so 88.75 USD is actually remitted. 2 rows have an empty permit_number because the two Canadian jurisdictions are filed on the GST/HST return instead.

File: CSV · Tax Filings · 6 rows
Use case: Data importCSV parsing· Paired fixture

Fieldnote Supply Shop: Sales tax filing worksheet JSON

Sales tax filing worksheet JSON for Fieldnote Supply Shop. The same 6 jurisdictions with the three control totals hoisted into a totals object. Rates are strings at five and four decimal places rather than floats, so 0.08875 survives; read as a float it is the rate that most often loses its last digit in a round trip.

File: JSON · Tax Filings · 6 records
Use case: Data importJSON parsing· Paired fixture

Fieldnote Supply Shop: Sales tax nexus summary

Sales tax nexus summary for Fieldnote Supply Shop. Why the shop is registered in each of the 6 jurisdictions, with the permit, the filing frequency and the next due date. Due dates range from 2026-09-20 to 2026-10-31, so a reader that assumes one filing calendar across a multi-state seller gets four of the six wrong.

File: CSV · Tax Filings · 6 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Tax rate table

Tax rate table for Fieldnote Supply Shop. The 6 rates as both a decimal and a percentage, so a reader can check one against the other. US-NY at 0.08875 is the one that a float round trip most often damages, and it is carried here to five decimal places and as 8.875 percent.

File: CSV · Tax Filings · 6 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Sales tax payable control account

Sales tax payable control account for Fieldnote Supply Shop. The ledger account behind the filing: opening 0.00, credited 96.34 of tax collected, debited 7.46 of tax refunded, leaving 88.88 USD payable at the end of the period. The 0.13 vendor allowance and the 88.75 remittance then clear it to exactly 0.00 on 2026-09-20. The balance after row 3 is the same number the filing worksheet reaches by summing six jurisdictions.

File: CSV · Tax Filings · 5 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: GST/HST return lines

GST/HST return lines for Harbour Kitchen Group. The six return lines as a three-column CSV keyed by the line number the form uses, so a reader can address a value by its line rather than by its position. Line 109 and line 115 both carry 3152.57 CAD because there are no instalments to deduct.

File: CSV · Tax Filings · 6 rows
Use case: Data importCSV parsing· Paired fixture

Harbour Kitchen Group: GST/HST return JSON

GST/HST return JSON for Harbour Kitchen Group. The same six lines with the registration, province, rate and period as siblings of the lines array, so the rate can be checked against the line arithmetic without another file.

File: JSON · Tax Filings
Use case: Data importJSON parsing· Paired fixture

Harbour Kitchen Group: GST/HST return workings

GST/HST return workings for Harbour Kitchen Group. Every source record behind the return: 56 sales rows tagged to line 105 and 24 purchase rows tagged to line 108, 80 rows in all. Taxing each row and adding gives 3407.94 and 255.23, which are 0.12 and -0.02 away from the 3407.82 and 255.25 on the return, because the return taxes the period total once and this file taxes every row and then adds.

File: CSV · Tax Filings · 80 rows
Use case: Data importCSV parsing· Conversion set

Tern Client Services: Payee register

Payee register for Tern Client Services. All 3 contractor payees with the certificate each has on file and the information return each one gets. Payments sum to 4,320.00 USD, which is every recorded hour at 60.00 USD, but they split 2,880.00 to 1099-NEC shaped slips and 1,440.00 to a 1042-S shaped statement, so no single information return file totals the ledger.

File: CSV · Tax Filings · 3 rows
Use case: Data importCSV parsing· Conversion set

Tern Client Services: 1099-NEC shaped recipient list

1099-NEC shaped recipient list for Tern Client Services. 2 recipients with every box the slips print. box_1 sums to 2880.00 USD, which is the control_total_box_1 value carried on every row, and the box_6 column is empty on both rows because neither payee has a state identification number. The third contractor is absent by design: WRK-02 files a W-8BEN shaped certificate and is reported on the 1042-S shaped statement.

File: CSV · Tax Filings · 2 rows
Use case: Data importCSV parsing· Paired fixture

Tern Client Services: 1099-NEC shaped recipient list JSON

1099-NEC shaped recipient list JSON for Tern Client Services. The same 2 recipients with the control total hoisted out of the rows and into the document, where it belongs, so the same check can be run against a single authoritative value rather than a value repeated on every row.

File: JSON · Tax Filings · 2 records
Use case: Data importJSON parsing· Paired fixture

Tern Client Services: 1099-NEC shaped recipient list whose boxes do not reach the control total

1099-NEC shaped recipient list whose boxes do not reach the control total for Tern Client Services. The same 2 recipients with one number changed: WRK-03 box_1 reads 1820.00 instead of 1920.00. box_1 now sums to 2780.00 against the 2880.00 that both rows still carry as control_total_box_1, a shortfall of 100.00 USD. box_7 was moved with box_1 so the row stays internally consistent and only the control total catches it.

File: CSV · Tax Filings · 2 rows
Use case: Data importCSV parsing+1· Conversion set

Harbour Kitchen Group: T4 shaped slip register

T4 shaped slip register for Harbour Kitchen Group. All 8 slips for the period. Box 14 sums to 9,190.00 CAD, which is the base pay the restaurant model records across every rostered shift, and boxes 16, 18 and 22 sum to 546.82, 152.56 and 1,378.50. Every row net_pay_cad is box 14 less those three, and the eight net figures sum to 7,112.12 CAD.

File: CSV · Tax Filings · 8 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: T4 shaped summary lines

T4 shaped summary lines for Harbour Kitchen Group. The same 8 summary lines as a CSV keyed by the box number, with the slip count on a line whose key is a word rather than a number, so a reader that assumes an integer key on every row has to handle it.

File: CSV · Tax Filings · 8 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Payroll deduction rates used by the T4 shaped slips

Payroll deduction rates used by the T4 shaped slips for Harbour Kitchen Group. The 5 rates behind every T4 box in this set, with the basis each one is applied to and an explicit statement that no maximum, band or personal exemption is applied. Two rows are multipliers of another row rather than percentages of income, so a reader that treats the rate column as one thing gets the employer lines wrong.

File: CSV · Tax Filings · 5 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Tax obligation calendar

Tax obligation calendar for Fieldnote Supply Shop. 10 dated obligations across four regimes and two currencies, in due date order, each with the days from the fixed snapshot and the amount due. The amount column mixes USD and CAD, so it must not be summed without the currency column: doing so gives a meaningless 10399.60.

File: CSV · Tax Filings · 10 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Tax reconciliation, source against source

Tax reconciliation, source against source for Fieldnote Supply Shop. 7 identities stated as a pair of sources and their values, with the difference computed rather than asserted. Every difference is 0.00, and two of the rows reach across into the wave-one ecommerce set and into the crm-services model, so the file is also a cross-set consistency check.

File: CSV · Tax Filings · 7 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Tax reconciliation identities

Tax reconciliation identities for Fieldnote Supply Shop. 5 named identities across three operating models and two currencies, including the rounding-order identity that measures how far a per-row tax calculation drifts from a per-period one. The deliberate defect and its measured 100.00 USD shortfall are listed separately.

File: JSON · Tax Filings
Use case: Data importJSON parsing

Pine Assembly Workshop: Loan amortisation schedule

Loan amortisation schedule for Pine Assembly Workshop. 36 rows with opening balance, payment, interest, capital, closing balance and cumulative interest. Payment equals interest plus capital and closing equals opening less capital on every row. The closing balance on row 36 is exactly 0.00 because the final payment is adjusted to 1479.81, and cumulative interest ends at 5276.66 USD.

File: CSV · Banking Credit · 36 rows
Use case: Data importCSV parsing· Paired fixture

Pine Assembly Workshop: Loan amortisation schedule whose final balance does not reach zero

Loan amortisation schedule whose final balance does not reach zero for Pine Assembly Workshop. The same 36 months with one number changed: the instalment is 1479.00, the correct 1479.91 rounded down to whole dollars. Every row still satisfies payment equals interest plus capital and closing equals opening less capital, but after the last payment the borrower still owes 36.15 USD instead of 0.00. Cumulative interest ends at 5280.15, which is 3.49 more than the correct schedule, because the balance falls more slowly.

File: CSV · Banking Credit · 36 rows
Use case: Data importCSV parsing+1· Paired fixture

Pine Assembly Workshop: Loan summary

Loan summary for Pine Assembly Workshop. The facility terms as a flat object, including the arrangement fee of 480.00 USD with an explicit arrangementFeeIsFinanced flag set to false, so a reader cannot silently add it to the principal. The monthly rate is a string at eight decimal places for the same reason the workbook carries it that way.

File: JSON · Banking Credit
Use case: Data importJSON parsing· Conversion set

Pine Assembly Workshop: Quarterly interest accrual

Quarterly interest accrual for Pine Assembly Workshop. The first 4 quarters of the facility rolled up from the monthly schedule. Each row opening balance is the opening balance of the first month in the quarter and each closing is the closing of the last, so closing equals opening less capital repaid and the quarters chain without a gap.

File: CSV · Banking Credit · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Covenant test schedule

Covenant test schedule for Pine Assembly Workshop. The 4 covenant tests as data, with required, actual and headroom in their own columns and a unit column, because two of the four are money and one is a ratio. Headroom is signed in the direction of compliance, so a minimum covenant and a maximum covenant both show positive headroom when they pass.

File: CSV · Banking Credit · 4 rows
Use case: Data importCSV parsing· Conversion set

Alder Books Reconciliation: Credit application JSON

Credit application JSON for Alder Books Reconciliation. The same application as an object, with each financial summary row keeping the source string that names the file and column it came from. The connected facility is a nested object rather than a string, so a reader can tell that the existing borrowing belongs to a different entity.

File: JSON · Banking Credit
Use case: Data importJSON parsing· Conversion set

Alder Books Reconciliation: Trade credit references

Trade credit references for Alder Books Reconciliation. 3 trade references with credit limits, highest balance reached and average days to pay. Every highest_balance_usd is below its own credit_limit_usd, so a utilisation check passes on all three, and the two supplier names are the suppliers the inventory-manufacturing model actually buys from.

File: CSV · Banking Credit · 3 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: Direct debit collection schedule

Direct debit collection schedule for Harbour Kitchen Group. 8 collections under mandate DDM-2026-0007, each 5 days after its invoice date with advance notice three days before that. The amounts are the supplier invoice totals the restaurant purchase ledger holds and sum to 4,077.58 CAD. The first collection carries sequence type FRST and the other 7 carry RCUR, which is the distinction a scheme rejects a file for getting wrong.

File: CSV · Banking Credit · 8 rows
Use case: Data importCSV parsing· Conversion set

Harbour Kitchen Group: ISO 20022 pain.008 direct debit initiation

ISO 20022 pain.008 direct debit initiation for Harbour Kitchen Group. A customer direct debit initiation message with 8 payment information blocks, one per collection date, because every block carries a single required collection date. The group control sum is 4077.58 CAD and the number of transactions is 8; each block control sum is its own single amount. The service level and local instrument are proprietary domestic and PAD codes rather than SEPA, because the currency is CAD.

File: XML · Banking Credit · UTF-8
Use case: Data importSchema validation· Conversion set

Harbour Kitchen Group: Direct debit mandate register

Direct debit mandate register for Harbour Kitchen Group. Two mandates for the same debtor account, one active and one cancelled. The active mandate has taken 8 of its 8 collections by the 2026-09-08 snapshot, 4,077.58 CAD of the 4,077.58 authorised. The cancelled mandate still shows the three collections it took before it was cancelled, because cancelling a mandate does not reverse what it already collected.

File: CSV · Banking Credit · 2 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Chargeback evidence index

Chargeback evidence index for Fieldnote Supply Shop. 8 evidence items with the file and record each one points at and what it proves. Seven of the eight resolve into the wave-one ecommerce document set by filename and record identifier, so the packet is not a self-contained story but a set of pointers that either resolve or do not.

File: CSV · Banking Credit · 8 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Chargeback timeline

Chargeback timeline for Fieldnote Supply Shop. 7 events in date order from the order on 2026-08-06 to the representment deadline on 2026-09-11. Three rows carry an empty amount because dispatch, evidence submission and a deadline move no money, so a reader that treats the amount column as always numeric has three rows to handle.

File: CSV · Banking Credit · 7 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Chargeback reason code reference

Chargeback reason code reference for Fieldnote Supply Shop. 5 reason codes with the category, the representment window and the evidence each one expects. The two codes the wave-one chargeback register uses, 10.4 and 13.1, are both here, so that register can be joined to this table to find out what evidence each open case needs.

File: CSV · Banking Credit · 5 rows
Use case: Data importCSV parsing· Conversion set

Fieldnote Supply Shop: Chargeback representment submission

Chargeback representment submission for Fieldnote Supply Shop. The whole case as one object: amounts, evidence pointers and timeline. The amounts object separates netExposure of 150.00 from cardholderTotal of 151.20, which differ by the 16.20 USD of tax, so a reader cannot confuse what the seller loses with what the cardholder paid.

File: JSON · Banking Credit
Use case: Data importJSON parsing· Conversion set

Alder Books Reconciliation: Banking reconciliation identities

Banking reconciliation identities for Alder Books Reconciliation. 5 named identities covering the amortisation, the unfinanced arrangement fee, the covenant directions, the direct debit control sum and the two different chargeback totals, with the figures behind each. The deliberate defect and its measured 36.15 USD closing balance are listed separately.

File: JSON · Banking Credit
Use case: Data importJSON parsing

Juniper Fitness and Clinic Administration: Procedure code table

Procedure code table for Juniper Fitness and Clinic Administration. The 4 procedure codes this clinic bills, with the charge, the allowed amount at 80 percent of charge and the contractual adjustment that is the difference. The code_system column says on every row that these are synthetic placeholders in the five-character shape, not values from any real code set.

File: CSV · Healthcare Claims · 4 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Diagnosis code table

Diagnosis code table for Juniper Fitness and Clinic Administration. The 3 diagnosis codes referenced by the claims, all of them administrative rather than clinical: a routine assessment, a follow-up and an equipment familiarisation visit. Every code is a synthetic placeholder and the table says so in its own column.

File: CSV · Healthcare Claims · 3 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Provider roster

Provider roster for Juniper Fitness and Clinic Administration. The 3 providers with ten-digit identifiers in the national provider identifier shape. Each one carries a real modulo-10 check digit computed over the 80840 prefix and the nine-digit body, so a validator that implements the check digit rule accepts all of them, and the roster records that it did.

File: CSV · Healthcare Claims · 3 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Payer roster

Payer roster for Juniper Fitness and Clinic Administration. The 3 payers with their claim counts and money. Claims sum to 16, charges to 1,180.00 USD, allowed to 876.00 and paid to 700.80, which are the same control totals the remittance and the reconciliation carry.

File: CSV · Healthcare Claims · 3 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Claim adjustment reason codes

Claim adjustment reason codes for Juniper Fitness and Clinic Administration. The 5 adjustment codes the remittance uses, each with its group code and whether it is contractual, patient responsibility or another adjustment. The distinction matters: a CO adjustment can never be billed to the patient and a PR adjustment is exactly what is billed, so a reader that ignores the group code bills the wrong party.

File: CSV · Healthcare Claims · 5 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Payer fee schedule

Payer fee schedule for Juniper Fitness and Clinic Administration. 12 rows, every procedure against every payer. All three payers use the same 80 percent allowed rate and the same 20 percent coinsurance, so the schedule is deliberately uniform and any difference a reader finds between payers in the remittance comes from adjudication rather than from pricing.

File: CSV · Healthcare Claims · 12 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Encounter register

Encounter register for Juniper Fitness and Clinic Administration. 16 encounters, one for each confirmed booking in the appointment model. The two cancelled bookings are absent, so the register has 16 rows where the booking table has 18. Charges sum to 1,180.00 USD across 18 service lines, allowed to 876.00, and the payers paid 700.80 leaving 175.20 with patients.

File: CSV · Healthcare Claims · 16 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Service line detail

Service line detail for Juniper Fitness and Clinic Administration. All 18 service lines across the 16 encounters. Charges sum to 1,180.00 USD, which is the charge column of encounter-register.csv added, and grouping by claim_id reproduces every claim total exactly. This is the file the 837 service-line total has to agree with.

File: CSV · Healthcare Claims · 18 rows
Use case: Data importCSV parsing· Conversion set

X12 837 claim batch: Juniper Fitness and Clinic Administration

X12 837 professional claim batch for Juniper Fitness and Clinic Administration. One interchange, one functional group, one transaction set carrying all 16 claims and 18 service lines. The SE segment declares 225 segments from ST to SE inclusive, which is the count a receiver checks first. Every CLM02 equals the SV102 amounts below it, and the CLM02 values sum to 1,180.00 USD. Segments are terminated with a tilde and the file uses CRLF line endings, which is what an X12 interchange carries in practice.

File: EDI · Healthcare Claims
Use case: Data importSchema validation· Conversion set

X12 837 single claim: Juniper Fitness and Clinic Administration

X12 837 professional claim, single claim for Juniper Fitness and Clinic Administration. The same interchange structure carrying one claim, CLM-0006, with 2 service lines of 120.00 and 85.00 USD. CLM02 is 205.00, which is exactly those two SV102 amounts added. SE01 declares 27 segments.

File: EDI · Healthcare Claims
Use case: Data importSchema validation· Paired fixture

Juniper Fitness and Clinic Administration: X12 837 claim whose service lines do not add up to the claim total

X12 837 claim whose service lines do not add up to the claim total for Juniper Fitness and Clinic Administration. The same single-claim interchange with one element changed: CLM02 reads 225.00 instead of 205.00. The two SV102 amounts are untouched at 120.00 and 85.00, so they still sum to 205.00 and disagree with the claim total by 20.00 USD. Segment counts, envelope control numbers and every other element are correct, so a structural validator passes the file and only the balance rule catches it.

File: EDI · Healthcare Claims
Use case: Data importSchema validation+1· Paired fixture

Juniper Fitness and Clinic Administration: X12 837 batch rendered as JSON

X12 837 batch rendered as JSON for Juniper Fitness and Clinic Administration. The same 16 claims as a JSON document, so a test can compare a parser output against an expected structure without reimplementing the X12 grammar. Control totals are hoisted to the document: 16 claims, 18 service lines and 1,180.00 USD.

File: JSON · Healthcare Claims
Use case: Data importJSON parsing· Conversion set

Juniper Fitness and Clinic Administration: X12 envelope and delimiter specification

X12 envelope and delimiter specification for Juniper Fitness and Clinic Administration. The delimiters, envelope values and segment counts for every X12 file in this directory, including the invalid one, so a test harness can be configured from the fixture rather than by guessing. It also records that the usage indicator is T for test and that every patient carries the same synthetic date of birth.

File: JSON · Healthcare Claims
Use case: Data importJSON parsing

Juniper Fitness and Clinic Administration: X12 835 remittance advice

X12 835 remittance advice for Juniper Fitness and Clinic Administration. One interchange carrying 3 transaction sets, one per payer, because each payer sends its own payment. The three BPR02 amounts sum to 700.80 USD, the payer payment total in encounter-register.csv, and each CLP04 equals the SVC payment amounts below it. The denied claim carries CLP02 of 4 with a zero payment and a CO 97 adjustment for the whole charge, where every other claim carries CLP02 of 1 with a CO 45 contractual adjustment and a PR 2 coinsurance.

File: EDI · Healthcare Claims
Use case: Data importSchema validation· Conversion set

Juniper Fitness and Clinic Administration: X12 835 remittance rendered as JSON

X12 835 remittance rendered as JSON for Juniper Fitness and Clinic Administration. The same 3 payments and 16 claims as a JSON document with the adjustments as objects carrying their group and reason codes, so the contractual and patient-responsibility split is explicit rather than something a reader has to infer from a CAS segment position.

File: JSON · Healthcare Claims
Use case: Data importJSON parsing· Conversion set

Juniper Fitness and Clinic Administration: Remittance adjustment lines

Remittance adjustment lines for Juniper Fitness and Clinic Administration. 35 rows, one per adjustment rather than one per service line, because a paid service line carries two adjustments and a denied one carries a single CO 97. Grouping by adjustment group gives 304.00 USD of CO write-offs and 175.20 USD of PR patient responsibility. Summing the charged column instead double counts, because charged repeats on both adjustment rows of a paid line.

File: CSV · Healthcare Claims · 35 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Claim status register

Claim status register for Juniper Fitness and Clinic Administration. All 16 claims with the status code the 835 CLP02 carries, the payer control number and the 17 days between submission and payment. 1 claim is status 4, denied, and the rest are status 1, processed as primary. Every payer control number is unique and appears once in remittance-835.edi.

File: CSV · Healthcare Claims · 16 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Denial register

Denial register for Juniper Fitness and Clinic Administration. The single denied claim, CLM-0011, denied in full for 85.00 USD under CO 97 with a 90 day appeal deadline of 2026-12-24. The group code is CO, so the amount is a contractual write-off and must not be billed to the patient even though nothing was paid, which is exactly the case a reader gets wrong by assuming an unpaid claim becomes a patient balance.

File: CSV · Healthcare Claims · 1 row
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Receivable aging by payer

Receivable aging by payer for Juniper Fitness and Clinic Administration. The 3 payers plus a total row. On every row paid plus patient responsibility plus written off equals charged, and the three aging buckets sum to the outstanding column. Nothing is older than thirty days because every claim was paid 17 days after submission, so the whole 175.20 USD outstanding sits in the first bucket and is owed by patients rather than by payers.

File: CSV · Healthcare Claims · 4 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Patient roster

Patient roster for Juniper Fitness and Clinic Administration. The 16 patients, which are the fictional visitor names the appointment model already carries, joined to their booking, encounter, claim and payer. Every row carries the same synthetic date of birth of 1900-01-01 and a column that says so, because the X12 claim needs a demographic segment and this set will not hold a plausible personal record to fill it.

File: CSV · Healthcare Claims · 16 rows
Use case: Data importCSV parsing· Conversion set

Juniper Fitness and Clinic Administration: Healthcare reconciliation identities

Healthcare reconciliation identities for Juniper Fitness and Clinic Administration. 6 named identities covering the booking to claim mapping, both money splits, the 837 and 835 balance rules and the denial that is deliberately not a patient balance. The invalid 837 and its measured 20.00 USD difference are listed separately, with a flag recording that the file is structurally valid.

File: JSON · Healthcare Claims
Use case: Data importJSON parsing

Pine Property Services: Schedule of unit areas

Schedule of unit areas for Pine Property Services. The 6 demises in PROP-1 with their floor areas and each one share of the 1200.00 sq m lettable area. Areas sum to the lettable area exactly and the shares sum to exactly 100.0000 percent because they are apportioned by largest remainder. The 185.00 sq m of common parts sits outside this table and is never apportioned, which is why no row accounts for it.

File: CSV · Property Leasing · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Rent roll

Rent roll for Pine Property Services. The 6 demises with area, rent, passing rent and estimated rental value. Unit areas sum to 1200.00 sq m, which is the building_area_sq_m value every row carries. Passing rent is 245,475.00 USD and estimated rental value 271,475.00, the difference being the 26000.00 USD that U-06 would produce if it were let. Annual rent is area times rate on every row and quarterly rent is a quarter of passing rent.

File: CSV · Property Leasing · 6 rows
Use case: Data importCSV parsing· Paired fixture

Pine Property Services: Rent roll whose unit areas do not sum to the building area

Rent roll whose unit areas do not sum to the building area for Pine Property Services. The same 6 demises with one number changed: U-03 reads 211.50 sq m instead of 230.00. Unit areas now sum to 1181.50 against the 1200.00 that every row still declares as building_area_sq_m, a shortfall of 18.50 sq m. The rent columns are untouched, so U-03 annual rent no longer equals its area times its rate either, and the two failures are the same mutation seen twice.

File: CSV · Property Leasing · 6 rows
Use case: Data importCSV parsing+1· Conversion set

Pine Property Services: Rent roll JSON

Rent roll JSON for Pine Property Services. The same 6 demises with the building level figures hoisted out of the rows: lettable area, common area, occupied area and occupancy by area. Occupancy is stated as a percentage of lettable area, not of lettable plus common, which is the choice that moves the number.

File: JSON · Property Leasing
Use case: Data importJSON parsing· Paired fixture

Pine Property Services: Lease abstract

Lease abstract for Pine Property Services. The 5 let demises abstracted onto one row each: term, break, review, rent, service charge proportion and deposit. Quarterly rent is a quarter of annual rent and the deposit is two quarters on every row. Only LSE-2026-02 has a break date, so four of the five rows carry an empty break_date and an empty break_notice_by.

File: CSV · Property Leasing · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Lease abstract JSON

Lease abstract JSON for Pine Property Services. The same 5 leases plus a separate vacantUnits array, because a vacant demise has no lease to abstract but still has an area and a rental value. A reader that counts leases gets five; a reader that counts demises has to add the vacant array to get six.

File: JSON · Property Leasing
Use case: Data importJSON parsing· Conversion set

Pine Property Services: Lease register

Lease register for Pine Property Services. The 5 live leases with days to expiry measured from the 2026-09-08 snapshot. The shortest has 935 days to run and the longest 2761. Service charge percentages here are the same apportionment the budget and reconciliation use, so the register can be joined to either.

File: CSV · Property Leasing · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Service charge expenditure against budget

Service charge expenditure against budget for Pine Property Services. 6 heads of charge plus a management fee and a total. Actual expenditure is 102,476.00 USD against a budget of 96,000.00, and the management fee on both sides is 10 percent of the heads above it rather than a fixed amount, so it moves with the expenditure it is charged on.

File: CSV · Property Leasing · 8 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Service charge budget apportionment

Service charge budget apportionment for Pine Property Services. The 96,000.00 USD budget apportioned across all six demises by area, including the vacant one, because a vacant unit share falls on the landlord and not on the other tenants. The six annual amounts sum to the budget exactly and the percentages sum to exactly 100.0000.

File: CSV · Property Leasing · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Service charge year end reconciliation

Service charge year end reconciliation for Pine Property Services. The year end settlement: each demise share of the 102,476.00 USD actually spent against the 96,000.00 USD paid on account, with the difference as a balancing charge. Every row share of actual less on account equals its balancing charge, and the charges sum to 6,476.00 USD, the overspend. No unit is in credit, so the credit column is 0.00 throughout and is kept as a column rather than dropped.

File: CSV · Property Leasing · 7 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Quarterly rent and service charge demands

Quarterly rent and service charge demands for Pine Property Services. 20 demands across four quarters for the five let demises. Each total is rent plus service charge and each outstanding is total less paid. Demanded rent and service charge across the year come to 331,075.00 USD, and 98,781.25 is outstanding: one genuine arrear and 5 demands for a quarter that has not started at the 2026-09-08 snapshot.

File: CSV · Property Leasing · 20 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Arrears report

Arrears report for Pine Property Services. The one genuine arrear: U-05 owes 16012.50 USD for 2026-Q3, due 2026-07-01 and 69 days overdue at the 2026-09-08 snapshot, which puts it in the 61 to 90 day bucket. The 5 fourth-quarter demands are deliberately absent because a demand for a quarter that has not started is not an arrear.

File: CSV · Property Leasing · 1 row
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Deposit register

Deposit register for Pine Property Services. The 5 deposits, each two quarterly instalments of the rent on its own lease, holding 122,737.50 USD in total. Every deposit is released on expiry subject to a dilapidations claim, which is what connects this register to the dilapidations schedule in the same directory.

File: CSV · Property Leasing · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Schedule of dilapidations lines

Schedule of dilapidations lines for Pine Property Services. The same 12 lines as data, with subtotal and total rows carrying an empty item_ref so they can be told apart from costed items. Only the 5 rows with a reference beginning D are remedial works; the rest are on costs, subtotals or the consequential loss.

File: CSV · Property Leasing · 12 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Schedule of condition

Schedule of condition for Pine Property Services. The 6 elements recorded at lease start and again at the exit inspection, with the dilapidations item each defect leads to. Five of the six lead to a costed item and the sixth records no defect and no action, so the schedule proves the claim is complete rather than only that it is arithmetically right.

File: CSV · Property Leasing · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Lease events diary

Lease events diary for Pine Property Services. 12 dated events in ascending order with days measured from the 2026-09-08 snapshot. 1 of them are already in the past and carry a negative number, because a rent review date that has passed is still a fact about the lease and dropping it would hide a review that was never actioned.

File: CSV · Property Leasing · 12 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Building works recharged to the service charge

Building works recharged to the service charge for Pine Property Services. The 2 work orders the trades-property model records against PROP-1, with their labour and material costs, totalling 328.00 USD. All of them are recharged to the repairs and maintenance head, which is budgeted at 32,192.36 USD and spent at 31,240.00, so these rows are a subset of that head rather than the whole of it.

File: CSV · Property Leasing · 2 rows
Use case: Data importCSV parsing· Conversion set

Pine Property Services: Property reconciliation identities

Property reconciliation identities for Pine Property Services. 5 named identities covering the areas, the rent, the service charge apportionment, the demands and the dilapidations build-up, with the figures behind each. The deliberate defect and its measured 18.50 sq m shortfall are listed separately.

File: JSON · Property Leasing
Use case: Data importJSON parsing

Pine Assembly Workshop: Indented bill of materials

Indented bill of materials for Pine Assembly Workshop. The DESK structure exploded to 2 levels in 6 rows, with an indent column so the tree is readable and an is_assembly flag so leaves can be told from sub-assemblies. Per finished unit the leaves are 4 LEG, 1 PANEL and 12 SCREW, which cost 25.20 USD. The 35.00 USD of sub-assembly rows is the same material counted again at a higher level and must not be added to it.

File: CSV · Manufacturing Quality · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Bill of materials exploded for a production order

Bill of materials exploded for a production order for Pine Assembly Workshop. The same structure exploded for BUILD-1, an order for 2 DESK. Extended quantity is quantity per parent times parent quantity on every row, and the leaf totals of 8 LEG, 2 PANEL and 24 SCREW equal the material requirements the inventory-manufacturing model already holds for that order, which the model_requirement column repeats on each leaf row for comparison.

File: CSV · Manufacturing Quality · 6 rows
Use case: Data importCSV parsing· Paired fixture

Pine Assembly Workshop: Exploded bill of materials whose sub-assembly quantities do not roll up

Exploded bill of materials whose sub-assembly quantities do not roll up for Pine Assembly Workshop. The same 6 rows with one number changed: the SCREW line under BASE carries an extended quantity of 12 instead of 16. That row now says 8 per parent times 2 parents is 12, which is arithmetically false, and the SCREW leaf total falls to 20 against the 24 the model_requirement_component_total column on the same rows still declares. The shortfall is 4 screws, 0.40 USD of material, and it is enough to leave one BASE sub-assembly short at build time.

File: CSV · Manufacturing Quality · 6 rows
Use case: Data importCSV parsing+1· Paired fixture

Pine Assembly Workshop: Bill of materials JSON

Bill of materials JSON for Pine Assembly Workshop. The DESK structure as a flat array with level, parent and both quantities, plus the cost identity at the top: 25.20 USD of leaf material plus 14.80 USD of added value is the 40.00 USD standard cost the parts table holds. A reader can rebuild the tree from parent and component without needing the indent string the CSV carries.

File: JSON · Manufacturing Quality
Use case: Data importJSON parsing· Conversion set

Pine Assembly Workshop: Bill of materials XML

Bill of materials XML for Pine Assembly Workshop. The same structure as genuinely nested XML rather than a flat list with a level column, so a reader has to walk the tree and multiply quantities down the path to reach a leaf requirement. SCREW appears in two different branches with different quantities per parent, 8 under BASE and 4 under TOP.

File: XML · Manufacturing Quality · UTF-8
Use case: Data importSchema validation· Conversion set

Pine Assembly Workshop: Standard cost roll-up

Standard cost roll-up for Pine Assembly Workshop. Every part with its material cost from the level below, the added value on top and the standard cost the parts table holds. On every row material plus added value equals standard cost. The DESK row takes its material from the two sub-assemblies at their standard costs, 35.00 USD, not from the leaves; the leaves come to 25.20 USD, and the difference is the added value already absorbed into the sub-assemblies.

File: CSV · Manufacturing Quality · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Work order routing

Work order routing for Pine Assembly Workshop. The 5 operations for BUILD-1, each with a setup time charged once per order and a run time charged per unit. At an order quantity of 2 the total is 10 setup minutes plus 20 run minutes, 30 in all, which at 37.00 USD an hour is 18.50 USD of labour. Treating setup as a per-unit time instead would give 40 minutes and 24.67 USD.

File: CSV · Manufacturing Quality · 6 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Work order cost build-up

Work order cost build-up for Pine Assembly Workshop. The seven line cost of BUILD-1: 50.40 USD of material, 18.50 of labour and 11.10 of absorbed overhead, giving 80.00 USD against a standard cost of 80.00 USD for the output and a variance of 0.00. The order closes exactly to standard, which is deliberate: it makes any variance a reader computes a defect in their arithmetic rather than a property of the fixture.

File: CSV · Manufacturing Quality · 7 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Work order register

Work order register for Pine Assembly Workshop. The 4 production orders the model holds, all for 2 DESK each, costed through the same routing. Every order closes to standard with a zero variance because setup is the same and the quantity is the same on all four; a different order quantity would produce a variance, which is why the batch size is a column rather than an assumption.

File: CSV · Manufacturing Quality · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Material issue list

Material issue list for Pine Assembly Workshop. The 3 leaf components issued to BUILD-1, at the quantities the explosion reaches and the model requires. Issued value is 50.40 USD, which is exactly line 1 of work-order-cost.csv, so the issue list and the cost build-up close on each other. No sub-assembly appears, because BASE and TOP are made on this order rather than issued to it.

File: CSV · Manufacturing Quality · 3 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Inspection characteristics and tolerances

Inspection characteristics and tolerances for Pine Assembly Workshop. The 5 characteristics taken from DRW-LEG-002 revision C, with the nominal, both tolerances and the resulting limits. Four are bilateral and one, surface roughness, is unilateral with a lower tolerance of zero, so its lower limit equals its nominal and a reader that assumes symmetry computes a limit that does not exist.

File: CSV · Manufacturing Quality · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Inspection measurements with tolerances

Inspection measurements with tolerances for Pine Assembly Workshop. 25 readings, 5 samples across 5 characteristics of the LEG part. Deviation is measured less nominal and carries an explicit sign, and result is pass only when the reading lies between both limits inclusive. 2 readings fail: CH-3 sample 3 measured 25.41, above the upper limit of 25.300 by 0.110; CH-5 sample 5 measured 1.58, below the lower limit of 1.600 by 0.020.

File: CSV · Manufacturing Quality · 25 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Inspection summary

Inspection summary for Pine Assembly Workshop. One row per characteristic with the pass count, the observed minimum and maximum and the range. 3 characteristics pass every sample and 2 do not. The range column is observed spread and not tolerance, so a characteristic can have a small range and still fail if the whole sample sits off nominal.

File: CSV · Manufacturing Quality · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Nonconformance register

Nonconformance register for Pine Assembly Workshop. 2 nonconformances, one per failing reading, each naming the characteristic, the limit breached and the amount by which it is breached. Both are single legs, 6.00 USD of material in total, so the 80.00 USD work order is not materially affected and the closed_on column is empty because neither is closed at the snapshot.

File: CSV · Manufacturing Quality · 2 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Gauge calibration register

Gauge calibration register for Pine Assembly Workshop. The 5 gauges used on this inspection, each with its calibration certificate, the date it was calibrated and the date it falls due. All 5 were inside calibration on 2026-09-10, the inspection date, and the used_for column names the characteristics each one measured, so every characteristic can be traced to a gauge and every gauge to a certificate.

File: CSV · Manufacturing Quality · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Attribute sampling plan

Attribute sampling plan for Pine Assembly Workshop. The sampling table the inspection used. The lot of 16 legs, being the quantity issued to BUILD-1 and BUILD-2 together, falls in the 16 to 25 band, which calls for a sample of 5 and an accept number of 0, and 5 is exactly the number of samples inspection-measurements.csv holds for each characteristic. With an accept number of 0 and 2 nonconforming readings, the lot is rejected on the plan and dealt with by nonconformance rather than by acceptance.

File: CSV · Manufacturing Quality · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Certificate of conformance register

Certificate of conformance register for Pine Assembly Workshop. Two certificates against the same lot and the same inspection report, one per production order. The first discloses 2 nonconformances and the second none, because the nonconforming legs were consumed by the replacement on the first order and the second order drew clean stock from the same lot.

File: CSV · Manufacturing Quality · 2 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Lot genealogy

Lot genealogy for Pine Assembly Workshop. The chain from purchase to certificate for lot LOT-2026-0912 in 7 records, each naming its parent record and the file that evidences it. Every evidence value that names a file names one that exists in this directory, so the genealogy is walkable rather than decorative.

File: CSV · Manufacturing Quality · 7 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: First article inspection

First article inspection for Pine Assembly Workshop. The first article record for LEG against DRW-LEG-002 revision C: all 5 characteristics measured and passed before the run started. The readings are the fourth sample from the production inspection, which is deliberate: the first article passes on every characteristic while the production lot later fails on two, so the pair shows that a clean first article does not guarantee a clean run.

File: CSV · Manufacturing Quality · 5 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Yield and scrap

Yield and scrap for Pine Assembly Workshop. Yield by production order. Every order yields 2 good units for 2 ordered, so finished-goods yield is 100.00 percent on all four, while BUILD-1 scrapped 2 legs worth 6.00 USD at component level. The two measures are in separate columns on purpose: component scrap that is replaced before assembly does not reduce finished-goods yield, and reporting one as the other is the mistake this file exists to catch.

File: CSV · Manufacturing Quality · 4 rows
Use case: Data importCSV parsing· Conversion set

Pine Assembly Workshop: Manufacturing and quality reconciliation identities

Manufacturing and quality reconciliation identities for Pine Assembly Workshop. 6 named identities covering the explosion, the cost roll-up, the work order that closes to standard, the routing, the inspection rule including the unilateral tolerance, and the difference between component scrap and finished-goods yield. The deliberate defect and its 4 unit, 0.40 USD shortfall are listed separately.

File: JSON · Manufacturing Quality
Use case: Data importJSON parsing

Alder Table Bistro: Editable operating workbook

Editable operating workbook for Alder Table Bistro. Native sheets preserve 369 source records, 4 calculated headline metrics and one editable chart. Supplier spend=11,652.45 CAD; Net menu sales=15,780.80 CAD; Menu items sold=1,092.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Alder Table Bistro: Blank input table templates

Blank input table templates for Alder Table Bistro. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Juniper Corner Cafe: Editable operating workbook

Editable operating workbook for Juniper Corner Cafe. Native sheets preserve 365 source records, 4 calculated headline metrics and one editable chart. Supplier spend=8,715.93 CAD; Net menu sales=10,234.74 CAD; Menu items sold=1,204.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Juniper Corner Cafe: Blank input table templates

Blank input table templates for Juniper Corner Cafe. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Copper Oven Bakery: Editable operating workbook

Editable operating workbook for Copper Oven Bakery. Native sheets preserve 368 source records, 4 calculated headline metrics and one editable chart. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Copper Oven Bakery: Blank input table templates

Blank input table templates for Copper Oven Bakery. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Ember Lane Pizza: Editable operating workbook

Editable operating workbook for Ember Lane Pizza. Native sheets preserve 375 source records, 4 calculated headline metrics and one editable chart. Supplier spend=15,061.21 CAD; Net menu sales=25,954.50 CAD; Menu items sold=1,428.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Ember Lane Pizza: Blank input table templates

Blank input table templates for Ember Lane Pizza. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Cedar Street Tacos: Editable operating workbook

Editable operating workbook for Cedar Street Tacos. Native sheets preserve 375 source records, 4 calculated headline metrics and one editable chart. Supplier spend=4,122.61 CAD; Net menu sales=19,374.60 CAD; Menu items sold=1,540.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Cedar Street Tacos: Blank input table templates

Blank input table templates for Cedar Street Tacos. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Willow Event Kitchen: Editable operating workbook

Editable operating workbook for Willow Event Kitchen. Native sheets preserve 376 source records, 4 calculated headline metrics and one editable chart. Supplier spend=7,900.99 CAD; Net menu sales=28,781.90 CAD; Menu items sold=1,652.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Willow Event Kitchen: Blank input table templates

Blank input table templates for Willow Event Kitchen. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Harbour Kitchen Group: Editable operating workbook

Editable operating workbook for Harbour Kitchen Group. Native sheets preserve 369 source records, 4 calculated headline metrics and one editable chart. Supplier spend=7,897.76 CAD; Net menu sales=26,214.00 CAD; Menu items sold=1,764.00 items; Guest reviews=18.00 records. The first worksheet holds 96 compatible purchase rows.

File: XLSX · Business Kits
Use case: Data import

Harbour Kitchen Group: Blank input table templates

Blank input table templates for Harbour Kitchen Group. 18 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Fieldnote Supply Shop: Editable operating workbook

Editable operating workbook for Fieldnote Supply Shop. Native sheets preserve 86 source records, 3 calculated headline metrics and one editable chart. Gross item sales=942.00 USD; Refunded amount=80.00 USD; Orders=12.00 records.

File: XLSX · Business Kits
Use case: Data import

Fieldnote Supply Shop: Blank input table templates

Blank input table templates for Fieldnote Supply Shop. 9 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Tern Client Services: Editable operating workbook

Editable operating workbook for Tern Client Services. Native sheets preserve 98 source records, 3 calculated headline metrics and one editable chart. Total deal value=34,500.00 USD; Weighted deal value=15,825.00 USD; Recorded activity time=720.00 minutes.

File: XLSX · Business Kits
Use case: Data import

Tern Client Services: Blank input table templates

Blank input table templates for Tern Client Services. 9 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Alder Books Reconciliation: Editable operating workbook

Editable operating workbook for Alder Books Reconciliation. Native sheets preserve 102 source records, 3 calculated headline metrics and one editable chart. Net cash change=5,236.00 USD; Journal debits=9,364.00 USD; Journal credits=9,364.00 USD.

File: XLSX · Business Kits
Use case: Data import

Alder Books Reconciliation: Blank input table templates

Blank input table templates for Alder Books Reconciliation. 6 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Pine Assembly Workshop: Editable operating workbook

Editable operating workbook for Pine Assembly Workshop. Native sheets preserve 89 source records, 3 calculated headline metrics and one editable chart. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

File: XLSX · Business Kits
Use case: Data import

Pine Assembly Workshop: Blank input table templates

Blank input table templates for Pine Assembly Workshop. 11 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Cobalt Operations Team: Editable operating workbook

Editable operating workbook for Cobalt Operations Team. Native sheets preserve 102 source records, 3 calculated headline metrics and one editable chart. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

File: XLSX · Business Kits
Use case: Data import

Cobalt Operations Team: Blank input table templates

Blank input table templates for Cobalt Operations Team. 5 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Juniper Fitness and Clinic Administration: Editable operating workbook

Editable operating workbook for Juniper Fitness and Clinic Administration. Native sheets preserve 66 source records, 3 calculated headline metrics and one editable chart. Available slots=24.00 slots; Occupied slots=16.00 slots; Booking records=18.00 records.

File: XLSX · Business Kits
Use case: Data import

Juniper Fitness and Clinic Administration: Blank input table templates

Blank input table templates for Juniper Fitness and Clinic Administration. 5 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Harbour House Stay: Editable operating workbook

Editable operating workbook for Harbour House Stay. Native sheets preserve 53 source records, 3 calculated headline metrics and one editable chart. Occupied room nights=48.00 nights; Room revenue=6,840.00 USD; Ancillary revenue=672.00 USD.

File: XLSX · Business Kits
Use case: Data import

Harbour House Stay: Blank input table templates

Blank input table templates for Harbour House Stay. 7 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Fieldnote Learning Centre: Editable operating workbook

Editable operating workbook for Fieldnote Learning Centre. Native sheets preserve 72 source records, 3 calculated headline metrics and one editable chart. Enrollments=18.00 records; Passed completions=9.00 learners; Available course seats=30.00 seats.

File: XLSX · Business Kits
Use case: Data import

Fieldnote Learning Centre: Blank input table templates

Blank input table templates for Fieldnote Learning Centre. 5 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Willow Community Fund: Editable operating workbook

Editable operating workbook for Willow Community Fund. Native sheets preserve 58 source records, 3 calculated headline metrics and one editable chart. Pledged support=2,850.00 USD; Received support=1,800.00 USD; Outstanding pledges=1,050.00 USD.

File: XLSX · Business Kits
Use case: Data import

Willow Community Fund: Blank input table templates

Blank input table templates for Willow Community Fund. 8 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Pine Property Services: Editable operating workbook

Editable operating workbook for Pine Property Services. Native sheets preserve 57 source records, 3 calculated headline metrics and one editable chart. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: XLSX · Business Kits
Use case: Data import

Pine Property Services: Blank input table templates

Blank input table templates for Pine Property Services. 6 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Juniper Workspace Cloud: Editable operating workbook

Editable operating workbook for Juniper Workspace Cloud. Native sheets preserve 75 source records, 3 calculated headline metrics and one editable chart. Active monthly recurring revenue=235.00 USD; Paid invoices=649.00 USD; Outstanding invoices=19.00 USD.

File: XLSX · Business Kits
Use case: Data import

Juniper Workspace Cloud: Blank input table templates

Blank input table templates for Juniper Workspace Cloud. 6 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Alder Table Bistro: Procure-to-pay workbook

Procure-to-pay workbook for Alder Table Bistro. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Juniper Corner Cafe: Procure-to-pay workbook

Procure-to-pay workbook for Juniper Corner Cafe. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Copper Oven Bakery: Procure-to-pay workbook

Procure-to-pay workbook for Copper Oven Bakery. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Ember Lane Pizza: Procure-to-pay workbook

Procure-to-pay workbook for Ember Lane Pizza. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Cedar Street Tacos: Procure-to-pay workbook

Procure-to-pay workbook for Cedar Street Tacos. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Willow Event Kitchen: Procure-to-pay workbook

Procure-to-pay workbook for Willow Event Kitchen. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Harbour Kitchen Group: Procure-to-pay workbook

Procure-to-pay workbook for Harbour Kitchen Group. 9 worksheets holding the same rows as the CSV exports plus a 'Deliberate defects' sheet naming all 6: Price list 48 rows; Purchase orders 12 rows; Goods received 12 rows; Invoice lines 14 rows; Credit notes 2 rows; Statement 13 rows; Remittance 13 rows; Three-way match 14 rows; Deliberate defects 6 rows. Money cells are numbers formatted 0.00 rather than text, so a spreadsheet reader can sum a column without parsing strings.

File: XLSX · Procure To Pay · 134 rows
Use case: Data importSpreadsheet testing

Alder Table Bistro: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Alder Table Bistro. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 12 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 73 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Alder Table Bistro: Yield test workbook with live formulas

Yield test workbook with live formulas for Alder Table Bistro. 5 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 5 rows
Use case: Spreadsheet testingData import

Alder Table Bistro: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Alder Table Bistro. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Alder Table Bistro: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Alder Table Bistro. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 1574.81 CAD against 15780.80 CAD of net menu sales, a food cost of 9.98 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Alder Table Bistro: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Alder Table Bistro. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Alder Table Bistro: Recipe costing as an OpenDocument spreadsheet

Recipe costing as an OpenDocument spreadsheet for Alder Table Bistro. Three tables. PlateCosts holds 12 recipe lines with the as-purchased quantity and line cost as live ODF formulas; Summary rolls each dish up with SUMIF and computes margin and food-cost percent. The same figures in value form are in plate-costs.csv.

File: ODS · Restaurant Costing
Use case: Spreadsheet testingData import· Conversion set

Juniper Corner Cafe: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Juniper Corner Cafe. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 8 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 61 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Juniper Corner Cafe: Yield test workbook with live formulas

Yield test workbook with live formulas for Juniper Corner Cafe. 2 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 2 rows
Use case: Spreadsheet testingData import

Juniper Corner Cafe: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Juniper Corner Cafe. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Juniper Corner Cafe: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Juniper Corner Cafe. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 1538.14 CAD against 10234.74 CAD of net menu sales, a food cost of 15.03 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Juniper Corner Cafe: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Juniper Corner Cafe. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Copper Oven Bakery: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Copper Oven Bakery. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 11 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 70 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Copper Oven Bakery: Yield test workbook with live formulas

Yield test workbook with live formulas for Copper Oven Bakery. 2 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 2 rows
Use case: Spreadsheet testingData import

Copper Oven Bakery: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Copper Oven Bakery. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Copper Oven Bakery: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Copper Oven Bakery. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 623.44 CAD against 6651.14 CAD of net menu sales, a food cost of 9.37 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Copper Oven Bakery: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Copper Oven Bakery. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Ember Lane Pizza: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Ember Lane Pizza. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 18 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 91 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Ember Lane Pizza: Yield test workbook with live formulas

Yield test workbook with live formulas for Ember Lane Pizza. 2 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 2 rows
Use case: Spreadsheet testingData import

Ember Lane Pizza: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Ember Lane Pizza. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Ember Lane Pizza: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Ember Lane Pizza. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 3110.43 CAD against 25954.50 CAD of net menu sales, a food cost of 11.98 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Ember Lane Pizza: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Ember Lane Pizza. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Ember Lane Pizza: Inventory variance as an OpenDocument spreadsheet

Inventory variance as an OpenDocument spreadsheet for Ember Lane Pizza. Two tables. Theoretical closing, the variance quantity, the variance at standard cost and the total are live ODF formulas over 6 ingredients. The same figures in value form are in inventory-count-sheet.csv.

File: ODS · Restaurant Costing
Use case: Spreadsheet testingData import· Conversion set

Cedar Street Tacos: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Cedar Street Tacos. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 18 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 91 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Cedar Street Tacos: Yield test workbook with live formulas

Yield test workbook with live formulas for Cedar Street Tacos. 3 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 3 rows
Use case: Spreadsheet testingData import

Cedar Street Tacos: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Cedar Street Tacos. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Cedar Street Tacos: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Cedar Street Tacos. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 2559.57 CAD against 19374.60 CAD of net menu sales, a food cost of 13.21 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Cedar Street Tacos: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Cedar Street Tacos. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Willow Event Kitchen: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Willow Event Kitchen. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 19 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 94 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Willow Event Kitchen: Yield test workbook with live formulas

Yield test workbook with live formulas for Willow Event Kitchen. 2 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 2 rows
Use case: Spreadsheet testingData import

Willow Event Kitchen: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Willow Event Kitchen. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Willow Event Kitchen: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Willow Event Kitchen. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 2106.63 CAD against 28781.90 CAD of net menu sales, a food cost of 7.32 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Willow Event Kitchen: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Willow Event Kitchen. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Harbour Kitchen Group: Recipe costing workbook with live formulas

Recipe costing workbook with live formulas for Harbour Kitchen Group. Four sheets. Ingredients converts 6 purchase packs to a cost per recipe unit; PlateCosts holds 10 recipe lines; Summary uses SUMIF to roll each dish up and computes margin and food-cost percent; Notes records the provenance. Exactly 67 cells are live formulas with no cached value, so a values-only reader sees them empty and a recalculating reader reproduces plate-costs.csv exactly.

File: XLSX · Restaurant Costing
Use case: Spreadsheet testingData import

Harbour Kitchen Group: Yield test workbook with live formulas

Yield test workbook with live formulas for Harbour Kitchen Group. 4 tests over two sheets. Trimmed weight, trim yield, cooking loss and the yield factor are formulas; the last column is an IF that compares the measured trim yield against the yield the recipe applies and writes yes or no.

File: XLSX · Restaurant Costing · 4 rows
Use case: Spreadsheet testingData import

Harbour Kitchen Group: Inventory variance workbook with live formulas

Inventory variance workbook with live formulas for Harbour Kitchen Group. 6 ingredients over two sheets. Theoretical closing, the variance quantity, the variance priced at standard cost, the below-par flag and the total are formulas. Theoretical usage is built from the sales table multiplied by the yield-adjusted recipe quantities, so it already carries the yield adjustment.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import· Conversion set

Harbour Kitchen Group: Cost of goods sold workbook with live formulas

Cost of goods sold workbook with live formulas for Harbour Kitchen Group. Four sheets. COGS computes opening plus purchases less closing for 6 ingredients; Reconciliation proves the identity usage and waste at standard, plus the purchase price variance, less the count variance, equals the reported figure; Summary lands on 3241.08 CAD against 26214.00 CAD of net menu sales, a food cost of 12.36 percent. The purchases line is the sum of the 24 shared purchase rows dated inside 2026-08-20 to 2026-09-02.

File: XLSX · Restaurant Costing · 6 rows
Use case: Spreadsheet testingData import

Harbour Kitchen Group: Scheduled hours and overtime workbook

Scheduled hours and overtime workbook for Harbour Kitchen Group. Three sheets. WeeklyHours carries 24 employee-weeks over 3 Monday-start work weeks, with weekly overtime above 44 hours, payable overtime as the greater of the daily and weekly figures, and the premium at half the base rate. DailyHours breaks the same segments down into 59 employee-days with a daily overtime formula above 8 hours. The period carries 5.00 payable overtime hours and 51.50 CAD of premium.

File: XLSX · Restaurant Costing · 24 rows
Use case: Spreadsheet testingData import· Paired fixture

Harbour Kitchen Group: Tip pool as an OpenDocument spreadsheet

Tip pool as an OpenDocument spreadsheet for Harbour Kitchen Group. Two tables. Points and the allocation total are live ODF formulas; the allocated amounts are the whole-cent largest-remainder shares that sum to the declared pool of 218.61 CAD.

File: ODS · Restaurant Costing
Use case: Spreadsheet testingData import· Conversion set

GDPR Sample Data Export (ZIP)

A small ZIP shaped like a GDPR subject-access export: profile JSON, activity CSV, consents JSON, and a README. All PII is fictional SAMPLE data.

File: ZIP · Exports · 4 members
Use case: Data importConversion testing+1

GDPR Export: JSON Only (ZIP, SAMPLE)

SAMPLE subject-access ZIP with JSON profile/preferences only: fictional PII.

File: ZIP · Exports · 3 members
Use case: Privacy export testingData import+1

GDPR Export: CSV Heavy (ZIP, SAMPLE)

SAMPLE GDPR-style ZIP dominated by activity/devices/sessions CSVs: fictional PII.

File: ZIP · Exports · 4 members
Use case: Privacy export testingCSV parsing+1

GDPR Export: Nested Paths (ZIP, SAMPLE)

SAMPLE nested-folder GDPR export with JSON + JSONL members: fictional PII.

File: ZIP · Exports · 4 members
Use case: Privacy export testingData import+1

GDPR Messages Export (JSON, SAMPLE)

Standalone SAMPLE messages JSON fragment for privacy-export parsers.

File: JSON · Exports
Use case: Privacy export testingData import

GDPR Activity Log (JSONL, SAMPLE)

SAMPLE activity JSONL for subject-access export pipelines.

File: JSONL · Exports
Use case: Privacy export testingData import

Closed STEP stock block: 40 × 30 × 20 mm

One closed faceted BREP with six planar faces. Triangulation yields 12 triangles, eight unique geometric positions, bounds 0,0,0 to 40,30,20 mm, surface area 5,200 mm² and volume 24,000 mm³. Hard-normal vertices may be duplicated.

File: STEP · Business Cad · 12 triangles
Use case: Data import

Stock block geometry: expected results and reader evidence

One closed faceted BREP with six planar faces. Triangulation yields 12 triangles, eight unique geometric positions, bounds 0,0,0 to 40,30,20 mm, surface area 5,200 mm² and volume 24,000 mm³. Hard-normal vertices may be duplicated.

File: JSON · Business Cad · 12 triangles
Use case: Data import

Sentiment Classification Dataset (JSONL)

A labelled sentiment-classification dataset in JSON Lines: 24 short product-review-style sentences balanced across positive, negative, and neutral. Fully synthetic; a fixture for testing text-classification loaders, tokenizers, and JSONL parsers.

File: JSONL · Nlp · 24 records
Use case: ML training dataNLP datasets+2

Model Benchmark Results (JSON)

A model-evaluation summary in JSON, per-task scores for a fictional model across sentiment, NER, summarization, translation, and QA, each with its metric and sample size. A fixture for testing eval dashboards and leaderboard importers.

File: JSON · Eval
Use case: Model evaluationJSON parsing+1

Coverage: Per-File Table (CSV)

The same coverage as a flat table with a TOTAL row, for spreadsheets, trend charts and diffing two runs without an XML parser. The TOTAL row is the arithmetic sum of the four file rows, so it doubles as a checksum on any tool that regenerates it. Every file in this group describes the same four-file source tree and reports 127/140 lines, 17/24 branch outcomes and 18/20 functions, so a converter can be diffed against a known answer.

File: CSV · Coverage · 5 rows
Use case: CSV parsingConversion testing+1· Conversion set

Test Case Matrix: Twelve Documented Cases (CSV)

Twelve test cases with level, priority, the requirement each covers, preconditions, steps and expected result: the table a test-management import expects. Eleven of the twelve are automated, and the requirement column joins this file to the traceability matrix next to it.

File: CSV · Plans · 12 rows
Use case: CSV parsingData import+1· Conversion set

Requirements Traceability Matrix with One Gap (CSV)

Thirteen requirements mapped to the test cases that cover them, and one, REQ-PAY-02, deliberately covered by nothing. A coverage-gap report that does not surface that row is not working, which makes this the answer key for exactly that check.

File: CSV · Plans · 13 rows
Use case: CSV parsingData import+1· Conversion set

SBOM Component Inventory (CSV)

The same fictional component tree flattened to a spreadsheet-friendly CSV (name, version, licence, depth, purl and a SHA-256 prefix) for testing the export path SBOM tools offer alongside JSON. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Sbom · 10 rows
Use case: CSV parsingData import+1· Conversion set

Lockfile Pin Summary (CSV)

Declared range against resolved version for every fictional package pinned by the lockfiles in this category: the table a review needs to see which pins drifted from their manifest ranges. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Lockfiles · 9 rows
Use case: CSV parsingData import+1· Conversion set

OSV Vulnerability Records (JSON Lines)

All four SAMPLE advisories as newline-delimited OSV records: the bulk shape an advisory database is loaded from, where each line must parse independently. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

File: JSONL · Vulnerability · 4 records
Use case: JSON parsingData import+1· Conversion set

Vulnerability Summary (CSV)

The four SAMPLE advisories flattened to one row each: the export a security review circulates, and the reference answer for any converter run against the Trivy, Grype or OSV reports here. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

File: CSV · Vulnerability · 4 rows
Use case: CSV parsingData import+1· Conversion set

Severity Scoring and SLA Matrix (CSV)

A severity-band table mapping CVSS ranges to remediation SLAs and gate actions, with the finding count each band has in this fixture set, so a policy engine can be tested end to end. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

File: CSV · Vulnerability · 5 rows
Use case: CSV parsingConfig testing+1· Conversion set

SLSA Build Level Matrix (CSV)

How the nine fictional dependencies distribute across SLSA build levels, with the policy outcome for each band: the table that turns the VSA's dependencyLevels object into something reviewable. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Provenance · 4 rows
Use case: CSV parsingData import+1· Conversion set

Dependency Graph (GraphML)

The dependency graph in GraphML, with typed attribute keys for node version, licence and depth and for edge range: the interchange format graph databases and analysis tools import. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: GRAPHML · Graphs
Use case: Graph dataConversion testing+1· Conversion set

Transitive Dependency Closure (CSV)

Every edge in the fictional dependency graph as one row (parent, child, declared range, resolved version, depth and whether the edge is direct), the form a spreadsheet or SQL import can aggregate. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Graphs · 10 rows
Use case: CSV parsingGraph data+1· Conversion set

Kestrel Bay Territory: OpenStreetMap XML Twin

The towns and roads in OSM XML: tagged nodes, three highway ways sharing the junction node at Kestrel Bay, and a route relation over them. All object IDs are negative (the convention for objects that have never been uploaded), so nothing here can be mistaken for real OSM data.

File: OSM · Territory · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

GPX: Route (rte) Rather Than a Track

A `rte` element: an ordered list of waypoints describing a planned route, with no timestamps because it has not been travelled yet. Many importers only look for `trk` and report this perfectly valid file as empty.

File: GPX · Gpx · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

GPX: Standalone Waypoints Only

Five `wpt` elements for the towns of the territory, with names, symbols and descriptions but no track or route. It is the GPX equivalent of a point layer, and the third of the three top-level GPX content types.

File: GPX · Gpx · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

NMEA 0183: Mixed GGA/RMC/GSA/GSV/VTG Log

A twelve-fix receiver log with the five sentence types a GPS unit normally interleaves, including three-part GSV satellite-in-view sets. Every checksum is correct, so a parser that verifies them should accept the whole file.

File: NMEA · Nmea · ASCII
Use case: GeospatialTime-series data+1· Conversion set

NMEA 0183: GGA Sentences Only

The same twelve fixes reduced to GGA alone. GGA carries time-of-day but no date and no speed, so a parser that only reads GGA cannot place the track on a calendar: a real limitation that this file makes obvious rather than leaving to be discovered later.

File: NMEA · Nmea · ASCII
Use case: GeospatialTime-series data+1· Conversion set

NMEA 0183: Receiver With No Fix

Six cycles of a receiver that has power but no satellite lock: GGA fix quality 0, RMC status V, and empty coordinate fields throughout. Parsers that split on commas and index positionally read these empty fields as zeros and plot the track at Null Island.

File: NMEA · Nmea · ASCII
Use case: GeospatialError handling+1· Conversion set

NMEA 0183: Bad Checksum and Truncated Sentence

A log with one sentence whose checksum has been altered and a final sentence truncated mid-transmission with no checksum at all: the two ways a serial GPS feed actually degrades. A correct parser drops both and keeps everything else.

File: NMEA · Nmea · ASCII
Use case: GeospatialError handling+1· Conversion set

KML: Point Placemarks With Descriptions

Five town Placemarks with plain-text descriptions and no styling: the smallest useful KML and the baseline for the rest of this subcategory. Coordinates match the master territory, so a KML-to-GeoJSON conversion can be diffed against a known answer.

File: KML · Kml · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

KML: LineString Placemarks With tessellate

The three roads as LineString Placemarks with `tessellate` set, which tells a globe renderer to drape the line over terrain rather than drawing it as a straight chord. Converters that drop the flag produce lines that tunnel through hills.

File: KML · Kml · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

KMZ: Single doc.kml, No Resources

The minimal KMZ: a ZIP holding exactly one `doc.kml` at the archive root and nothing else. Readers are supposed to open the first .kml they find, and most look for the conventional name: this file satisfies both rules.

File: KMZ · Kml · 1 member
Use case: GeospatialConversion testing+1· Conversion set

kmz

658 B

KMZ: Bundled Icon Referenced by a Relative Path

A KMZ whose style points at `files/markers/town.png` inside the same archive. Resolving that relative href against the archive rather than the filesystem is the whole job of a KMZ reader, and it is where extract-then-parse implementations break.

File: KMZ · Kml · 2 members
Use case: GeospatialConversion testing+1· Conversion set

Shapefile: Towns Attributes (.dbf, dBase III)

The attribute table as a dBase III file: fixed-width, space-padded, ASCII numerics. Field names are capped at ten characters and there is no type for dates-with-time or for nested values, which is why shapefile export loses so much of a modern schema.

File: DBF · Shapefile · 5 records
Use case: GeospatialData import+1· Conversion set

Shapefile: Roads Attributes (.dbf with a decimal field)

The road attribute table, including a numeric field declared with two decimal places. DBF stores numbers as right-justified ASCII, so the declared width and decimal count are the only thing that says 9.40 is not 940.

File: DBF · Shapefile · 3 records
Use case: GeospatialData import+1· Conversion set

Shapefile: Parcels Attributes (.dbf)

The parcel attribute table, joined to the .shp purely by record order: there is no key and no explicit link. Deleting a geometry without deleting its row shifts every subsequent attribute onto the wrong shape, silently.

File: DBF · Shapefile · 3 records
Use case: GeospatialData import+1· Conversion set

Shapefile Bundle: Kestrel Bay Towns (zipped component set)

A zipped shapefile containing the full five-file point set: .shp, .shx, .dbf, .prj and .cpg. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.

File: ZIP · Shapefile · 5 members
Use case: GeospatialConversion testing+1· Conversion set

Shapefile Bundle: Kestrel Bay Parcels (zipped component set)

A zipped shapefile containing a three-file polygon set with no .cpg, so the DBF encoding is undeclared. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.

File: ZIP · Shapefile · 4 members
Use case: GeospatialConversion testing+1· Conversion set

Shapefile DBF: Accented Attributes in UTF-8

The same four accented attribute rows written in UTF-8. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.

File: DBF · Shapefile · 4 records
Use case: GeospatialEncoding detection+1· Conversion set

Shapefile DBF: Accented Attributes in CP1252

The same four accented attribute rows written in CP1252. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.

File: DBF · Shapefile · 4 records
Use case: GeospatialEncoding detection+1· Conversion set

GeoPackage: Three Feature Layers in One SQLite Container

The territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.

File: GPKG · Geopackage
Use case: GeospatialConversion testing+1· Conversion set

GeoPackage: Aspatial Attributes Table (no geometry column)

A GeoPackage holding an `attributes` table with no geometry at all: the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.

File: GPKG · Geopackage · 10 rows
Use case: GeospatialData import+1· Conversion set

MBTiles: Raster Tile Pyramid, Zoom 4 to 8

A small raster tile pyramid covering the invented territory, one flat colour per zoom level so a wrongly addressed tile is obvious on sight. The row axis follows the TMS convention, which is flipped relative to the XYZ scheme web maps use: the single most common reason an MBTiles layer renders upside down.

File: MBTILES · Geopackage
Use case: GeospatialData import+1· Conversion set

MBTiles: Structurally Valid Tileset With No Tiles

Every required MBTiles table and metadata key, and not one tile row. This is what a failed or interrupted tile build actually produces, and it is the fixture that finds code which reports success because the file opened and the schema validated.

File: MBTILES · Geopackage
Use case: GeospatialError handling+1· Conversion set

OSM XML: Multipolygon Relation With Outer and Inner Ways

Wither Lake and its island as an OSM multipolygon relation: two closed ways tagged separately and joined by a relation whose members carry outer and inner roles. OSM has no polygon primitive at all, so reconstructing the hole means reading the relation rather than the ways.

File: OSM · Gml Osm · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

OSM XML, Intentionally Invalid: Way and Relation With Dangling References

Intentionally invalid: a way referencing node -9 and a relation referencing way -999, neither of which is in the file. This is the normal state of a bounding-box extract, where objects are clipped at the boundary, so a reader has to decide between rejecting the file and building partial geometry, and must say which.

File: OSM · Gml Osm · UTF-8
Use case: GeospatialError handling+1· Conversion set

FITS BINTABLE: Typed Columns with TUNIT (.fits)

A FITS binary table with four typed columns, big-endian numerics packed with no inter-field padding and TUNIT declaring milli-jansky on the two flux columns. It is the fixture for a table reader that has to build a row struct from TFORM codes rather than guess widths.

File: FITS · Fits · 12 rows
Use case: Scientific dataSerialization testing+1· Conversion set

HDF5 Compound Record dtype: Mixed Field Types (.h5)

A compound-dtype dataset mixing an integer key, two float measurements, a fixed-width byte string and a boolean flag in a single record. It is the fixture for readers that must map an HDF5 record type onto a native struct without reordering or repadding the fields.

File: H5 · Hdf5 · 10 records
Use case: Scientific dataSerialization testing+1· Conversion set

NumPy .npy: Structured Record Array with Units in Field Names (.npy)

A 16-record structured array carrying a value, its uncertainty and a quality flag, with the physical unit encoded in the field-name suffix because .npy has nowhere else to put it. The header descriptor is a list of field tuples rather than a single type string, which is the parsing branch this file exercises.

File: NPY · Arrays · 16 records
Use case: Scientific dataSerialization testing+1· Conversion set

Units on a Second Header Row: Not Data (.csv)

The same instrument export with units on a second header row instead of inside the column names, which is how a great many laboratory instruments write CSV. An importer that treats row two as data types every measurement column as text and then quietly refuses to plot anything.

File: CSV · Measurements
Use case: Scientific dataCSV parsing+2· Conversion set

Gravimetric Mass: TSV With Bracketed Units and Spaces in Headers (.tsv)

Ten weighings as tab-separated values with headers that contain spaces, brackets and parentheses, 'u(mass) [g]', the way balance software actually writes them. Column names like these break naive slug-based header handling long before the numbers become a problem.

File: TSV · Measurements · 10 rows
Use case: Scientific dataEditor testing+1· Conversion set

Three-Molecule SDfile Library: Multi-Record (.sdf)

Three molecules of different sizes in one SDfile, each with its own connection table and four data fields, separated by the $$$$ terminator. It is the fixture for streaming SDfile readers that have to split on the terminator rather than load the whole file.

File: SDF · Chemistry · 3 records
Use case: Scientific dataEditor testing+1· Conversion set

SMILES Library: Ten Structures Including Aromatics and Salts (.smi)

Ten tab-delimited SMILES covering the notation features that trip parsers: lowercase aromatic atoms, ring-closure digits, branch parentheses, explicit charges in brackets and a dot-disconnected salt. Every structure is small enough to verify by hand.

File: SMI · Chemistry · 10 records
Use case: Scientific dataEditor testing+1· Conversion set