Skip to content
Novus Examples
xml14.7 KB

Alder Books Reconciliation: camt.053 whose entry count does not match its entries

camt.053 whose entry count does not match its entries for Alder Books Reconciliation. Well-formed XML with the same header, balances and TxsSummry as bank-statement-camt053.xml, but the final Ntry, TXN-024 for 206.00 on 2026-08-24, has been dropped. NbOfNtries still declares 24 while only 23 Ntry elements are present, and the entries now sum to 10442.00 against a CLBD balance of 10236.00.

xml

application/xml

14.7 KB
Document Set
accounting
Industry
finance
Source Kit
accounting-reconciliation
Synthetic
true
As Of
2026-09-08
Message Type
camt.053.001.02

Binary xml: 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
camt.053.001.02
Declared Entries
24
Actual Entries
23
Missing Entry
TXN-024
Intentionally Invalid
true

Testing contract

Expected to fail
Scenario
Parse the statement and check the declared entry count and closing balance against the entries present.
Expected result
NbOfNtries declares 24 but only 23 Ntry elements exist, and replaying them from the OPBD 5000.00 reaches 10442.00, which is 206.00 short of the declared CLBD 10236.00. A parser that trusts the header without counting reports a clean import.

What is a .xml file?

XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.

How to use this file

Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.

How to use this file for testing

“Alder Books Reconciliation: camt.053 whose entry count does not match its entries” is a deterministic Novus Examples fixture for Data import, Error handling. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: XML · 15,074 bytes. 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 xml.etree.ElementTree as ET

tree = ET.parse("bank-statement-camt053-entry-count-mismatch.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])

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