Skip to content
Novus Examples
txt848 B

Cobalt Operations Team: Fixed-width bank payment file

Fixed-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.

txt

text/plain

848 B
Document Set
payroll
Industry
people-operations
Source Kit
people-operations
Synthetic
true
As Of
2026-09-08
Records
8

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
Records
8
Record Length
105
Fields
9
Amount Encoding
unsigned cents, zero filled
Line Endings
LF
Encoding
ASCII

Testing contract

Expected to pass
Scenario
Parse the file by column position using bank-payment-layout.json and total the amount field.
Expected result
Every one of the 8 lines is exactly 105 characters before the newline. Reading columns 68 to 78 as unsigned cents and dividing by 100 gives 6649.44, matching bank-payment-file.csv and the net_pay total of the payroll register.

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: Fixed-width bank 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: 8 records · 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.

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.