Skip to content
Novus Examples
csv875 B

Cobalt Operations Team: Bank payment file

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

csv

text/csv

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

Binary csv: 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
Total Usd
6649.44
Synthetic Bank Details
true
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Total the payment file and compare it with the net pay total on the register.
Expected result
8 payments sum to 6649.44, equal to the net_pay column of payroll-register.csv. Every employee_id appears exactly once, and paying from payroll-register-deductions-mismatch.csv instead would send 58.80 too much.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Cobalt Operations Team: 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 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 pandas as pd

df = pd.read_csv("bank-payment-file.csv")
print(df.head())
print(df.dtypes)

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