A fictional package you can inspect
From invoice to ledger to a supported answer.
Three invoices. Two receipts. One unresolved adjustment. Follow the records, check the reconciliation, and see what the evidence can and cannot establish.
Entirely fictional. Every company, identifier, figure and record in this example was constructed for this demonstration. It contains no acquired or redacted customer records. The missing support is intentional.
What preparation connects
A record chain you can follow.
The prepared output retains source references, calculations and open questions. It does not silently turn a ledger description into supporting evidence.
01 / Source excerpts
Link the payment to the invoice.
The constructed receipt records explicitly reference the invoices they settle. Open balances are calculated from those links, not matched by amount alone.
| Invoice | Issued | Matched receipts | Open |
|---|---|---|---|
| INV-001 | 12,000 | 10,000 | 2,000 |
| INV-002 | 8,000 | 8,000 | 0 |
| INV-003 | 5,000 | 0 | 5,000 |
| Total | 25,000 | 18,000 | 7,000 |
02 / Organize
Keep the ledger's meaning and its references.
The account map identifies cash, accounts receivable, revenue and other income. The journal records both sides of each posting and retains the invoice or receipt reference.
A separate $500 manual entry debits receivables and credits other income. Its posting appears in the ledger. No supporting invoice or approval is included, so it remains separate from the $7,000 linked to open invoices.
03 / Reconcile
Explain the whole balance.
All opening balances are zero in this deliberately small example. The $7,500 closing AR agrees with the trial balance, including the $500 entry that still needs support.
A numerical tie checks consistency between files. It does not prove the adjustment is valid, the balance is collectible, or the records are complete.
| Opening balance | 0 |
|---|---|
| Invoices issued | +25,000 |
| Matched receipts | −18,000 |
| Manual entry needing support | +500 |
| Closing ledger / trial balance | 7,500 |
| Unexplained arithmetic difference | 0 |
04 / Prepared output
Separate the calculation from the judgment.
The downloadable JSON preserves the linked records, reconciliation and evidence status. A buyer can inspect the preparation without assuming every posted amount is substantiated.
Supported within this example
$7,000 remains on linked invoices.
Three invoice records total $25,000. Two explicitly matched receipts total $18,000. The arithmetic and source references are inspectable.
No inference recorded
The entry stays as posted.
A ledger description or numerical tie does not establish the entry's purpose, validity or appropriate accounting treatment. No missing evidence is filled in by assumption.
Unresolved
The $500 needs supporting evidence.
Request the underlying document, rationale and approval before concluding whether the adjustment should remain or be reversed. Missing support does not establish an error.
Package contents
Check the files behind the page.
One constructed company, one month, one receivables workflow. The package includes five CSV files, prepared JSON, a manifest and a reading guide with field definitions, relationships, transformations, checks and limitations.
This public demonstration is not a private evaluation holdout, an available acquired-data lot, or evidence of model performance. Commercial packages and permitted uses are agreed separately.
Another working example
Cash Review.
Match a fictional bank statement to a cash ledger, inspect unresolved items and download the workpaper.
Start with your workflow
What would a useful sample let you check?
Tell us the financial workflow, the output you need, and the records or context missing from your current approach. Acquired records, custom datasets and optional tasks are scoped to that requirement.