Fintech Bank Statement Lines (CSV)
Synthetic bank statement line items for reconciliation tooling tests.
line,date,description,amount
1,2026-01-01,Opening balance,1000.0
2,2026-01-15,Sample purchase,-42.5
Specifications
- Rows
- 2
- Domain
- fintech
Testing contract
Expected to pass- Scenario
- Exercise Fintech Bank Statement Lines (CSV) in its fintech workflow. Synthetic bank statement line items for reconciliation tooling tests.
- Expected result
- 2 data records using ',' delimiters and UTF-8; header fields are line, date, description, amount; data-record widths (columns:count) are {"4":2}. Declared feature checks: domain=fintech.
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
“Fintech Bank Statement Lines (CSV)” 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: 2 rows. 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("statement-lines.csv")
print(df.head())
print(df.dtypes)Related files
- jsonFintech Double-entry Ledger (JSON)Balanced double-entry ledger SAMPLE for accounting engine validation tests.
- jsonFintech SAR Compliance Flag (JSON)Synthetic suspicious-activity flag JSON for AML compliance workflow tests.
- csvFintech Transaction History (CSV)Synthetic bank transaction history for personal-finance importer tests.
- csv10,000-Row CSVA CSV with 10,000 data rows — for testing streaming parsers, memory handling, and import performance.
- csvAlder Books Reconciliation — Generic primary records CSVGeneric primary records CSV for Alder Books Reconciliation. 24 generic records with stable primary keys. Map the documented fields before importing into another platform.
- jsonAlder Books Reconciliation — Intentionally invalid semantic test recordsIntentionally invalid semantic test records for Alder Books Reconciliation. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.
Generated by generation/data_wave_f.py. Free for any use, no attribution required, license.