Skip to content
Novus Examples
csv5.4 KB

Alder Books Reconciliation: General ledger in the European CSV dialect

General ledger in the European CSV dialect for Alder Books Reconciliation. The same 66 ledger lines with a semicolon delimiter, decimal commas, dot thousands separators and dd/mm/yyyy posting dates. This is the shape a ledger export from a European accounting package arrives in.

csv

text/csv

5.4 KB
Document Set
accounting
Industry
finance
Source Kit
accounting-reconciliation
Synthetic
true
As Of
2026-09-08
Rows
66

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
accounting
Industry
finance
Source Kit
accounting-reconciliation
Synthetic
true
As Of
2026-09-08
Rows
66
Delimiter
semicolon
Decimal Mark
comma
Date Format
dd/mm/yyyy
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Import the ledger with the European dialect configured and check that it still balances.
Expected result
Read with a semicolon delimiter and a comma decimal mark, the 66 lines give debits and credits of 22464.00 each, the same totals as general-ledger-export.csv.

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

“Alder Books Reconciliation: General ledger in the European CSV dialect” 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: 66 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("general-ledger-eu-dialect.csv")
print(df.head())
print(df.dtypes)

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