Reconciliation & exception review
Workflow concept · fictional records · no live connections
Bring ledger and bank exports into one reviewable exception workflow, with every result linked to its source.
For accounting outsourcing, cfo and advisory teams.
Open the working fictional-data demo
A useful first scope
One entity, one reporting period and two agreed export formats, with an accountant-defined acceptance dataset.
What goes in
- An agreed ledger export and bank export, for one entity and currency.
- A mapping for reference, date, amount and source ID.
- Matching rules and tolerances approved by the accounting reviewer.
What comes out
- Matched records with source IDs and match reason.
- Amount differences, duplicate candidates and unmatched records.
- Reviewer notes and decisions, without silently changing the books.
How a reviewer would use it
- Overview: source file names, raw counts/totals, matched totals and unresolved exceptions.
- Records: filter by matched, amount difference, unmatched or duplicate candidate; search by reference.
- Review: show the full ledger/bank evidence, rule explanation and reviewer note; recording a review does not resolve the financial difference.
- Export: download results, exceptions and review history separately. Reset restores the original fictional records.
Inspect the fictional records and expected results
This is a design brief for a fuller demonstration, not an upload form or a working third-party connector.
ledger.csv id,reference,amount L001,INV-1042,12000 L002,INV-1043,8500 L003,INV-1044,6400 L004,INV-1045,3200 L005,INV-1046,5000 L006,INV-1047,2400 L007,INV-1048,1800 L008,INV-1049,3600 bank.csv id,reference,amount B001,INV-1042,12000 B002,INV-1043,8000 B003,INV-1045,3200 B004,INV-1046,5000 B005,INV-1046,5000 B006,INV-1047,1200 B007,INV-1047,1200 B008,INV-1049,3600 B009,UNALLOCATED,700
Rules and assumptions
- Use INR and integer paise internally. In this fixture amounts are whole rupees. All records are within an approved fictional reporting period.
- Match on reference and exact amount. B004/B005 are a deliberately duplicated transaction pair: flag B005 as a duplicate candidate and exclude it from suggested matches; do not silently delete it.
- Allow the explicit split settlement B006+B007 for INV-1047; show both sources and their sum. Do not implement arbitrary subset matching.
- INV-1043 is an amount difference of ₹500. INV-1044 and INV-1048 have no bank match. B009 has no ledger match.
- A human can mark an item reviewed, request evidence or leave it open. Review status and accounting reconciliation status are distinct.
What should be checkable
- Ledger: 8 records, raw total ₹42,900. Bank: 9 records, raw total ₹39,900. Preserve both original totals.
- Five ledger references match, with total ₹26,200: INV-1042, 1045, 1046, 1047 and 1049. Six bank source records support those matches.
- Five exception records/groups remain: one amount difference, two unmatched ledger records, one duplicate bank candidate, one unallocated bank record.
- All 17 input records appear in a match group or an exception; no missing or double-counted source row.
- Changing a review status never changes source amounts or marks an amount discrepancy financially resolved.
Agree the boundary
Do not offer automatic bookkeeping entries or real bank connectivity in this demonstration. Dates, tolerance and foreign-currency handling are explicitly out of scope.
The professional reviewer owns accounting treatment and business rules. DataHarmoni scopes the technical preparation, validation and output with your team.
Discuss a similar workflowA short anonymized description is enough to start.