Skip to content
Novus Examples
json2.5 KB

Cobalt Operations Team: Payroll reconciliation assertions

Payroll reconciliation assertions for Cobalt Operations Team. The eight identities this set claims with the figure each must produce: 9072.00 of gross from the shifts, 6649.44 of net after deductions, the same figure on the payslips and in the bank file, 664944 cents as the fixed-width control total, a journal balancing at 10542.17, 1470.17 of employer cost that is never a deduction, and 1168 hours of leave remaining. It also records the 58.80 size of the deliberate defect.

json

application/json

2.5 KB
Document Set
payroll
Industry
people-operations
Source Kit
people-operations
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
payroll
Industry
people-operations
Source Kit
people-operations
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. The knownDefect block predicts payroll-register-deductions-mismatch.csv: EMP-05 stating 922.32 where gross less deductions is 863.52, 58.80 out, which is that row's own pension deduction.

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

“Cobalt Operations Team: Payroll 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("payroll-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.