Why mismatches happen in the first place
SAP (or whatever ERP the company runs) has its own version of what was billed. The distributor has their own records -- sometimes also SAP, sometimes Tally, sometimes a notebook. The two rarely match perfectly, and not because anyone's being dishonest: invoices get entered on different dates, a scheme discount gets applied on one side and missed on the other, a credit note gets issued but not reflected everywhere, or a duplicate entry slips in during a busy month-end.
None of this is unusual. The problem isn't that mismatches exist -- it's that without a regular reconciliation process, they compound silently for months before anyone notices the outstanding figure looks wrong.
The manual reconciliation process
Done by hand, this typically looks like:
- Export invoices from SAP for the period, as Excel.
- Get the distributor's own billing records for the same period -- by email, WhatsApp, or however they send it.
- Match invoice-by-invoice, usually on invoice number first, falling back to date + amount when numbers don't line up.
- List what doesn't match: missing on one side, duplicated, or a different amount.
- Chase each mismatch individually to find out why, then correct it on whichever side is wrong.
This works, but it's slow, and it has to be repeated every cycle -- there's no running memory of what was already resolved last time unless someone keeps a very disciplined log.
Why ageing matters, not just totals
A single outstanding total hides more than it shows. ₹10 lakh outstanding could mean a healthy mix of recent, expected dues -- or it could mean ₹8 lakh of it is 90+ days overdue and quietly becoming uncollectible. Ageing the outstanding into bands (0-30, 31-60, 61-90, 90+ days) turns one vague number into something you can actually act on: chase the old stuff first, and watch which distributors consistently drift into the older bands.
Credit notes and debit notes
Credit notes (money owed back to the distributor -- a scheme claim, a return, a price correction) and debit notes (the reverse) are where reconciliation most often goes wrong, because they're easy to track as a separate, disconnected list instead of against the specific invoice they relate to. A credit note that isn't linked back to its invoice is very easy to apply twice, or to lose track of entirely.
Where manual reconciliation breaks down
It scales badly. Reconciling one distributor by hand each month is manageable. Reconciling fifty, each on their own schedule, each sending data in a slightly different format, each with their own history of unresolved mismatches, turns into a full-time job that still falls behind. The telltale sign: a finance team that can tell you the total outstanding, but not confidently explain why it changed from last month.
What's worth automating
The matching itself -- invoice number, amount, date -- is mechanical and exactly the kind of thing worth automating first. What shouldn't be automated away is the judgement call on genuinely ambiguous mismatches; those still need a human to look at the specific invoice and decide what actually happened.
In WorklikeGenie, invoices come in by SAP export, API, or Excel/CSV, and billing reconciliation runs against distributor and retailer records automatically, with ageing bands and credit/debit notes linked to the invoices they relate to -- see the full billing reconciliation checklist for the steps this is built around, whether or not you're using WorklikeGenie to do it.