Cobalt Operations Team: COBOL copybook for the payment file
COBOL 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.
txt
text/plain
- Document Set
- payroll
- Industry
- people-operations
- Source Kit
- people-operations
- Synthetic
- true
- As Of
- 2026-09-08
- Fields
- 9
Binary txt: 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
- Fields
- 9
- Record Length
- 105
- Line Endings
- LF
- Encoding
- ASCII
Testing contract
Reference control- Scenario
- Compare the copybook PIC clauses with the JSON column map.
- Expected result
- The 9 PIC clauses total 105 characters and each one's width matches the length of the field with the same name in bank-payment-layout.json. The single 9(9)V99 clause is the field the JSON map declares with amountScale 2.
What is a .txt file?
TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.
How to use this file
Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.
How to use this file for testing
“Cobalt Operations Team: COBOL copybook for the payment file” 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: 9 fields · ASCII · LF. 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.
Related files
- 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.
- 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.
Generated by generation/industry_documents.py. Free for any use, no attribution required, license.