json2.1 KB

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.

Data import JSON parsing

Preview, first 50 linesjson

{
  "schemaVersion": 1,
  "generatedAt": "2026-09-08",
  "sourceKit": "trades-property",
  "propertyId": "PROP-1",
  "currency": "USD",
  "areaUnit": "sq m",
  "identities": [
    {
      "id": "areas",
      "statement": "Unit areas sum to the lettable area, and the apportionment shares sum to exactly one hundred percent.",
      "lettableArea": "1200.00",
      "commonArea": "185.00",
      "byUnit": {
        "U-01": "260.00",
        "U-02": "195.00",
        "U-03": "230.00",
        "U-04": "175.00",
        "U-05": "210.00",
        "U-06": "130.00"
      },
      "shareTotal": "100.0000"
    },
    {
      "id": "rent",
      "statement": "Annual rent is area times rate on every demise; passing rent excludes the vacant unit and estimated rental value includes it.",
      "passingRent": "245475.00",
      "estimatedRentalValue": "271475.00",
      "vacantUnitValue": "26000.00"
    },
    {
      "id": "service-charge",
      "statement": "Budget and actual both apportion by area across all six demises, and the balancing charges are the difference.",
      "budget": "96000.00",
      "actual": "102476.00",
      "balancingTotal": "6476.00",
      "vacantUnitShareBorneByLandlord": "11101.57"
    },
    {
      "id": "demands",
      "statement": "Every demand is rent plus service charge; outstanding splits into one arrear and demands that are not yet due.",
      "demanded": "331075.00",
      "outstanding": "98781.25",
      "trueArrears": "16012.50",
      "notYetDue": 5
    },
    {
      "id": "dilapidations",
      "statement": "The two on costs compound in the order the schedule states, and loss of rent is weeks over fifty-two of the annual rent.",
      "worksSubtotal": "22430.00",

… 67 lines total: download for the full file.

Specifications

Document Set: property
Industry: trades-property
Source Kit: trades-property
Entity: Pine Property Services
Synthetic: true
As Of: 2026-09-08
Identities: 5
Defects Listed: 1

Testing contract

Reference control

Scenario: Use this file as the expected-value table when testing a reader against the rest of the set.
Expected result: Every figure here is reproduced by at least two other files in the directory, and the deliberateDefects array names the single invalid file and the exact size of the area shortfall.

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: Property reconciliation identities” is a deterministic Testaroo 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 · 2,140 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("property-reconciliation.json") as f:
    data = json.load(f)
print(type(data), len(data))

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