Reconciliation is deceptively simple with one entity, one bank account and one ledger. The trouble starts when a business grows into several legal entities, each with its own books, tax registrations, banking relationships and intercompany flows. The same process that worked in a spreadsheet quietly stops scaling.
Where it actually breaks
In our experience, breakages cluster in a few predictable places:
- Intercompany mismatches. Entity A books a payable that Entity B never recognises as a receivable — or books it in a different period. Without a single matching engine across entities, these drift for months.
- Tax-head reconciliation. GST and TDS introduce their own sub-ledgers that must tie back to both the books and the statutory returns. Manual tie-outs are slow and error-prone.
- Volume in bank and marketplace data. Once transaction counts run into the tens of thousands per month, eyeballing a statement is no longer a control — it is a hope.
The controls that hold
The teams that keep clean books at scale tend to share the same habits:
- A rules-based matching engine that auto-clears the obvious matches so humans only touch genuine exceptions.
- Standardised intercompany identifiers so a transaction can be matched across entities, not just within one.
- A persistent audit trail on every match, write-off and adjustment — who, what, when and why.
What good looks like
Done well, month-end stops being a fire drill. Exceptions are surfaced early, the audit trail answers questions before they are asked, and finance spends its time investigating the handful of items that matter rather than re-keying the thousands that do not.
This is exactly the problem RecoLens was built to solve — reconciliation across AP/AR, TDS, GST, bank, marketplace, GL and intercompany, with a full audit trail.