Reconcile the books against the return, invoice by invoice

What it matches

Pick a mode and a period, upload one file per side — or a register and a return for every month in the year — and the tool pairs the documents.

Sales against GSTR-1

Your sale register against the outward-supply return you filed. Every invoice is paired, and what does not pair is listed on the side it sits on: booked but never declared, or declared but never booked.

Purchase against GSTR-2A

The purchase register against the supplier-declared ledger, with per-supplier netting so a credit note does not read as a missing invoice, and with the ITC gap stated per supplier. Credit and debit notes are reconciled rather than dropped.

Pairing, then differences

Documents are paired on identity first and value second, not the other way round. Keying purely on exact value is what turns an ordinary rounding difference of a few paise into a "gap" — and a genuinely different invoice into a match with a number that happens to agree.

Two ways to read the same exceptions

The unmatched population is offered dealer-wise — one row per party with the difference it accounts for, expandable to the invoices behind it — and invoice-wise, one flat row per document with the party named on every line. Dealer-wise answers who do I ring. Invoice-wise answers which bills.

Parties that could not be placed

A separate panel lists the rows that neither rule could place: no document number in the books names a supplier in the return, and no tax total identifies one. Nothing in that panel is a suggestion — it is the party’s own rows. Without it, a register with a couple of thousand unplaceable rows shows an empty proposals table and reads as finished.