Skip to content
Novus Examples
json1.1 KB

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.

json

application/json

1.1 KB
Document Set
tax
Industry
retail
Source Kit
retail-commerce
Entity
Tern Client Services
Synthetic
true
As Of
2026-09-08

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

Specifications

Document Set
tax
Industry
retail
Source Kit
retail-commerce
Entity
Tern Client Services
Synthetic
true
As Of
2026-09-08
Records
2
Control Total
2880.00
Empty Strings Not Null
true

Testing contract

Expected to pass
Scenario
Sum box_1 across the recipients array and compare with controlTotalBox1.
Expected result
The sum is 2880.00 and controlTotalBox1 is 2880.00. The empty state identification numbers are empty strings, not nulls, so a reader that distinguishes the two sees a present but empty field.

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

“Tern Client Services: 1099-NEC shaped recipient list 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: 2 records. 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("form-1099-nec-recipients.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.