Cobalt Operations Team: Payroll journal batch JSON
Payroll journal batch JSON for Cobalt Operations Team. The same 9 lines as payroll-journal.csv with the posting rule stated. totals.debit and totals.credit are both 10542.17 and totals.difference is 0.00.
json
application/json
- Document Set
- payroll
- Industry
- people-operations
- Source Kit
- people-operations
- Synthetic
- true
- As Of
- 2026-09-08
- Lines
- 9
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
- Lines
- 9
- Balances
- true
- Encoding
- UTF-8
Testing contract
Expected to pass- Scenario
- Parse the batch, total both sides and check the stated difference.
- Expected result
- The 9 lines sum to 10542.17 on each side and the difference is 0.00 as declared. Every line has a value on exactly one side, so a reader that sums a single amount column with signs would need to negate the credits to reach the same answer.
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 journal batch 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("payroll-journal.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.
- csvCobalt Operations Team: Benefit deduction scheduleBenefit deduction schedule for Cobalt Operations Team. 8 employees and a TOTAL row. Every employee is on the STD plan from 2026-01-01, contributing 42.00 against an employer contribution of 63.00, so employee contributions total 336.00, employer contributions 504.00 and premiums 840.00. Only the employee side reaches the payroll register; the employer side is a cost, not a deduction.
- jsonCobalt Operations Team: Benefit deduction schedule JSONBenefit 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.
- csvCobalt Operations Team: Benefit plan rate cardBenefit plan rate card for Cobalt Operations Team. Two health plans. STD costs 105.00 a period of which the employer pays 63.00, 60.00 percent, and all 8 employees are on it. ENH is defined at 174.00 with nobody enrolled, so it is the negative case: a plan that exists in the rate card and must never appear in a deduction.
- 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.
Generated by generation/industry_documents.py. Free for any use, no attribution required, license.