Cobalt Operations Team: Benefit deduction schedule JSON
Benefit deduction schedule JSON for Cobalt Operations Team. The same 8 enrolments as benefits-deduction-schedule.csv with the rule that separates a deduction from an employer cost stated in words. totalPremiums is 840.00, of which only 336.00 is deducted from pay.
json
application/json
- Document Set
- payroll
- Industry
- people-operations
- Source Kit
- people-operations
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 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
- Rows
- 8
- Encoding
- UTF-8
Testing contract
Expected to pass- Scenario
- Apply the stated rule and check which side of it each figure falls on.
- Expected result
- Summing employee_contribution across the 8 enrolments gives 336.00, which appears in the deduction total of payroll-register.csv; summing employer_contribution gives 504.00, which appears only in employer-cost-summary.csv and in no deduction anywhere.
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: Benefit deduction schedule 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: 8 rows · 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("benefits-deduction-schedule.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- csvCobalt Operations Team: Bank payment fileBank payment file for Cobalt Operations Team. 8 payments, one per employee, for the net pay on payroll-register.csv. The amount column totals 6649.44, which is the net_pay total of the register to the cent. Sort code and account numbers are reserved test values and the reference on every line names the employee and the period.
- txtCobalt Operations Team: COBOL copybook for the payment fileCOBOL copybook for the payment file for Cobalt Operations Team. A COBOL record description for the same 105-character layout, with PIC clauses matching bank-payment-layout.json field for field: X(n) for the alphanumeric fields and 9(9)V99 for the amount, which is where the two implied decimal places are declared. Comment lines carry the column ranges.
- csvCobalt Operations Team: Employee directoryEmployee directory for Cobalt Operations Team. 8 employees with department, pay basis, rate and start date. The names are the model's own role labels, not people, and the directory carries no address, telephone number, date of birth or national identifier. The bank fields are reserved test values: sort code 000000 and sequential account numbers from 00000001 to 00000008, flagged as such in the last column.
- jsonCobalt Operations Team: Employee directory JSONEmployee directory JSON for Cobalt Operations Team. The same 8 employees as employee-directory.csv with a department count and a privacy note. The team splits 4 in Operations, 4 in Service.
- csvCobalt Operations Team: Employer cost summaryEmployer cost summary for Cobalt Operations Team. What the period actually costs the employer: 9072.00 of gross pay plus 272.16 of employer pension, 694.01 of payroll tax and 504.00 of health contribution, 10542.17 in total, which is 116.21 percent of gross and 31.38 per paid hour. None of it is deducted from pay: employees receive 6649.44.
- txtCobalt Operations Team: Fixed-width bank payment fileFixed-width bank payment file for Cobalt Operations Team. 8 records of exactly 105 characters each, the shape a bank credit-transfer file still arrives in. There is no delimiter and no header. Amounts are unsigned cents, zero filled and right justified in an 11-character field, so 604.80 is written as 00000060480. The column map is bank-payment-layout.json.
Generated by generation/industry_documents.py. Free for any use, no attribution required, license.