Skip to content
Novus Examples
xml2.4 KB

Alder Books Reconciliation: ISO 20022 pain.001 payment initiation

ISO 20022 pain.001 payment initiation for Alder Books Reconciliation. A pain.001.001.03 CustomerCreditTransferInitiation paying the 3 suppliers on aged-creditors.csv. GrpHdr declares NbOfTxs 3 and CtrlSum 2064.00; the single PmtInf block repeats those figures and contains 3 CdtTrfTxInf blocks for 774.00, 617.00, 673.00, each with a creditor IBAN and BIC.

xml

application/xml

2.4 KB
Document Set
accounting
Industry
finance
Source Kit
accounting-reconciliation
Synthetic
true
As Of
2026-09-08
Message Type
pain.001.001.03

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
pain.001.001.03
Transactions
3
Control Sum
2064.00
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Parse the payment file and validate the control sum against the transactions.
Expected result
NbOfTxs is 3 at both group and payment-information level and exactly that many CdtTrfTxInf elements are present; their InstdAmt values sum to 2064.00, equal to both CtrlSum fields, and every Ccy attribute is USD.

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: ISO 20022 pain.001 payment initiation” 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: 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 xml.etree.ElementTree as ET

tree = ET.parse("supplier-payments-pain001.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.