Skip to content
Novus Examples
json718 B

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.

json

application/json

718 B
Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Net Usd
661.01

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

Specifications

Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Net Usd
661.01
Deposit Eur
603.17
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Evaluate the reconciliation string against the numeric fields in the same document.
Expected result
grossSalesUsd 922.00 minus fees.totalUsd 180.99 minus refundsUsd 80.00 equals netPayableUsd 661.01, and the single conversion of that at 0.91250 equals depositAmountEur 603.17.

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

“Fieldnote Supply Shop: Marketplace settlement and payout summary JSON” 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("settlement-payout.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.