Skip to content
Novus Examples
json2.3 KB

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.

json

application/json

2.3 KB
Document Set
construction
Industry
trades-property
Source Kit
trades-property
Synthetic
true
As Of
2026-09-08
Identities
8

Binary json: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
construction
Industry
trades-property
Source Kit
trades-property
Synthetic
true
As Of
2026-09-08
Identities
8
Documented Defects
1
Encoding
UTF-8

Testing contract

Reference control
Scenario
Drive a reconciliation test from this file against the other documents in the set.
Expected result
All eight identities hold against the shipped files, including the one that trips people up: summary line 9 exceeds the continuation sheet's balance_to_finish by exactly the 324.80 of retainage. The knownDefect block predicts application-for-payment-002-retainage-rate.csv overstating the payment due by 162.40.

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

“Pine Property Services: Construction reconciliation assertions” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: UTF-8. 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("construction-reconciliation.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.