Panels and management control
Collections and reconciliation
AI-assisted payment matching, with human confirmation and cross-checking against your management system.
Who it's for Administration teams receiving loose transfers and receipts and having to guess who each one belongs to.
The problem
Transfers arrive with a blank reference, receipts come through WhatsApp, and payments carry the account holder's name, which isn't the customer's name. Someone has to look at each one and decide who to credit.
Whatever can't be identified ends up in limbo: an unanswered email, a folder, someone's memory. And that money still shows as debt for a customer who already paid.
How I solve it
01Receipt first
The flow starts where it starts in real life: you upload the receipt. The system doesn't require knowing whose it is up front, because that's precisely what needs figuring out.
02The AI proposes, the person decides
A model reads the receipt and proposes the matching customer, along with what led it there. The person confirms or corrects. No blind automatic posting: in collections, being wrong is worse than not deciding.
03Unidentified stays visible
Whatever couldn't be resolved goes to an "unmatched" tray with its amount and date. It's money that exists and has to be worked, not a fact lost in an inbox.
04Cross-checked against your management system
The customer master syncs from your ERP, and postings are cross-checked against issued invoices. Discrepancies surface on their own.
05Bad data, made visible
This work always uncovers deeper problems in the customer master. In one case, measuring showed only a third of customers had a tax ID on file. That stops being a suspicion and becomes a list of things to fix.
What I've already built
- Collections module built for an importer's administration team, with 10,055 customers synced from its ERP.
- The system proposes the match with a language model and a person confirms; unidentified payments stay in a tray instead of disappearing.
- The assessment found only 31% of the customer master had a tax ID on file, and that automatic validation of certain invoice types wasn't available, so that case is handled conservatively rather than emitting a false record.