Skip to content
Novus Examples
txt1.7 KB

Alder Books Reconciliation: MT940 bank statement

MT940 bank statement for Alder Books Reconciliation. A SWIFT MT940 customer statement with tags :20:, :25:, :28C:, :60F:, 24 :61:/:86: pairs, :62F: and :64:. Amounts use the MT decimal comma and dates the YYMMDD form, so the opening balance reads C260801USD5000,00 and the closing balance C260824USD10236,00. Line endings are CRLF, as the MT message format requires.

txt

text/plain

1.7 KB
Document Set
accounting
Industry
finance
Source Kit
accounting-reconciliation
Synthetic
true
As Of
2026-09-08
Message Type
MT940

Binary txt: 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
Message Type
MT940
Statement Lines
24
Line Endings
CRLF
Decimal Mark
comma
Closing Balance
10236.00
Encoding
ASCII

Testing contract

Expected to pass
Scenario
Parse the MT940 and check the closing balance against the statement lines.
Expected result
The :60F: opening balance 5000,00 plus the 24 :61: movements gives 10236,00, which is exactly the :62F: closing balance and the :64: available balance. Every line ends CRLF and every amount uses a comma decimal separator.

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

“Alder Books Reconciliation: MT940 bank statement” 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: ASCII · CRLF. 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.