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.
json
application/json
- Kit
- restaurant-pizzeria
- Schema Version
- 1
- Synthetic
- true
- As Of
- 2026-09-08
- Currency
- CAD
- Tax Name
- GST
Binary json: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Kit
- restaurant-pizzeria
- Schema Version
- 1
- Synthetic
- true
- As Of
- 2026-09-08
- Currency
- CAD
- Tax Name
- GST
- Tax Rate
- 0.05
- Purchase Orders
- 4
- Invoice Documents
- 5
- Distinct Invoice Numbers
- 4
- Credit Notes
- 2
- Statements
- 2
- Deliberate Defects
- 6
- Money Encoding
- two-place decimal string
Testing contract
Expected to pass- Scenario
- Read whole procure-to-pay chain json into a procure-to-pay import, three-way match and reconciliation workflow for Ember Lane Pizza.
- Expected result
- 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.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Ember Lane Pizza: Whole procure-to-pay chain JSON” is a deterministic Novus Examples fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: JSON · 76,725 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("procure-to-pay.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonAlder Table Bistro: Numeric expected results JSONNumeric 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.
- jsonAlder Table Bistro: Whole procure-to-pay chain JSONWhole 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.
- jsonCedar Street Tacos: Numeric expected results JSONNumeric 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.
- jsonCedar Street Tacos: Whole procure-to-pay chain JSONWhole 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.
- jsonCopper Oven Bakery: Numeric expected results JSONNumeric 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.
- jsonCopper Oven Bakery: Whole procure-to-pay chain JSONWhole 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.
Generated by generation/restaurant_procurement.py. Free for any use, no attribution required, license.