Reconciliation exceptions engine: bank against ledger
Matches bank receipts to the sales ledger by reference, amount and date, split and partial payments, and ranks every exception by money at risk.
The problem it solves
Most reconciliations are done by eye in a spreadsheet, so the 90% that match take all the time and the 10% that matter get a quick look at month end. The engine reverses that: the matches are automatic and the exceptions are the deliverable.
What it does
- Reads the bank statement and the sales ledger exports, copes with messy headers and number formats.
- Four matching passes: invoice reference, amount plus date plus name, split payments (one receipt for two or three invoices), partial payments.
- Duplicates are held out and reported, never allocated.
- Writes an Excel workbook: headline summary, exceptions ranked by money at risk with a reason code and an action each, matches with the rule that made them, open invoices with days overdue.
How it was tested
- A planted defect manifest of 15 cases (duplicates, splits, partials, wrong references) recovered 15 of 15.
Screens
Who it is for
Any business with more than 200 bank lines a month.
See it running on a call → hamza.jamal@finamatik.com Source code on GitHub →
Built and tested on sample data before any live credential is connected. Every system Finamatik ships is adapted to the client's own tools and owned by the client outright.