Skip to content
Testaroo
md6.3 KB

Alder Books Reconciliation: banking document set README

Document set README for Alder Books Reconciliation. 25 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

Preview, first 50 linesmd
# Alder Books Reconciliation: loan amortisation, credit application, direct-debit mandate and chargeback documents

The lending and payments paperwork that sits between a business and its bank: a term loan with a full amortisation schedule that closes on zero, a covenant certificate tested against the accounting ledger, a credit application whose every figure names the file it came from, a recurring direct debit mandate with its ISO 20022 pain.008 message, and a complete chargeback representment packet whose evidence index points back into the wave-one order and settlement exports.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Records are derived from the shared operating model `accounting-reconciliation`, so identifiers join across this set, across the other commercial document sets, and across every fixture built on the same model.

## Reconciliation identities this set asserts

- On every schedule row payment equals interest plus capital and closing equals opening less capital; capital sums to 48,000.00 USD and the final balance is exactly 0.00.
- The level instalment of 1,479.91 USD is the annuity formula on 48,000.00 at 0.57500 percent for 36 months, and the final instalment of 1,479.81 clears the 0.10 USD that 36 level instalments would overcollect.
- The four quarterly accrual rows chain without a gap and each interest figure is the three monthly amounts added.
- Every covenant figure is the accounting model own closing number, and headroom is positive on all four because it is signed in the direction of compliance.
- The 8 direct debit collections are the supplier invoices in the purchase ledger, each collected 5 days later, and they sum to 4,077.58 CAD, the control sum in the pain.008 message.
- Seller exposure on the chargeback is 150.00 USD and the cardholder total is 151.20 USD. Both are built from the same 135.00 USD capture and neither equals the other.
- All seven wave-one evidence references in the dispute packet resolve to a file and a record that exist.

## Parameters this set introduces

These are properties of the document class, not of the operating model. They are declared once and every file in the set agrees with them.

- The facility: LN-2026-0001, 48,000.00 USD at 6.90 percent over 36 months from 2026-07-01, with a 480.00 USD arrangement fee that is not financed.
- The four covenant levels and the interest cover definition, which is a fixture definition printed on the certificate rather than a standard accounting measure.
- The mandate: DDM-2026-0007, signed 2026-07-08, with a 5 day collection lead and three days of advance notice.
- Bank identifiers: sort code 00-00-00 and account numbers from the reserved test range, and a creditor scheme identifier in the same shape.
- The 15.00 USD chargeback case fee and the dispatch record date, which is the wave-one shipping manifest value rather than a new one.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `loan-agreement-LN-2026-0001.pdf` | pdf | valid | Term loan agreement (PDF) |
| `loan-agreement-LN-2026-0001.docx` | docx | valid | Term loan agreement (DOCX) |
| `loan-amortisation-schedule.csv` | csv | valid | Loan amortisation schedule |
| `loan-amortisation-schedule-final-balance-nonzero.csv` | csv | invalid | Loan amortisation schedule whose final balance does not reach zero |
| `loan-amortisation-schedule.xlsx` | xlsx | valid | Loan amortisation workbook |
| `loan-summary.json` | json | valid | Loan summary |
| `interest-accrual.csv` | csv | valid | Quarterly interest accrual |
| `covenant-compliance-certificate.pdf` | pdf | valid | Covenant compliance certificate |
| `covenant-tests.csv` | csv | valid | Covenant test schedule |
| `credit-application.pdf` | pdf | valid | Credit application (PDF) |
| `credit-application.docx` | docx | valid | Credit application (DOCX) |
| `credit-application.json` | json | valid | Credit application JSON |
| `credit-references.csv` | csv | valid | Trade credit references |
| `direct-debit-mandate.pdf` | pdf | valid | Direct debit mandate (PDF) |
| `direct-debit-mandate.docx` | docx | valid | Direct debit mandate (DOCX) |
| `direct-debit-collection-schedule.csv` | csv | valid | Direct debit collection schedule |
| `direct-debit-pain008.xml` | xml | valid | ISO 20022 pain.008 direct debit initiation |
| `direct-debit-mandate-register.csv` | csv | valid | Direct debit mandate register |
| `chargeback-evidence-index.csv` | csv | valid | Chargeback evidence index |
| `chargeback-timeline.csv` | csv | valid | Chargeback timeline |
… 70 lines total: download for the full file.

Specifications

Document Set
banking
Industry
finance
Source Kit
accounting-reconciliation
Entity
Alder Books Reconciliation
Synthetic
true
As Of
2026-09-08
Documented Files
25
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 25 entries including this README, and the deliberate-defect section names 1 file(s) with the measured size of each discrepancy.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Alder Books Reconciliation: banking document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 6,501 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

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