GSTR-2B vs Books Reconciliation Checklist

Pull both files at the same cutoff

Half the mismatches teams chase are not mismatches. They are timing differences because Purchase Register was pulled on the 5th and GSTR-2B was downloaded on the 8th, after three more vendors filed. Pull both on the same day, every time, or your baseline is already wrong.

Normalize before you compare

GSTINs get typed with stray spaces. Invoice numbers get prefixed inconsistently between your ERP and what the vendor actually filed. Round off IGST to two decimals on both sides before matching, not after. If your process compares raw strings, you are manufacturing false mismatches.

Match tax components separately

A total that matches can still hide a wrong split between CGST and SGST, or IGST claimed on what should have been an intra-state supply. Compare each tax head on its own. Totals-only matching is the fastest way to file a return that is wrong in a way nobody notices until an audit.

Set two tolerance tiers, not one

Exact match is the goal, but rupee-level rounding differences are not errors worth escalating. A tight tolerance (say, one rupee) for auto-clear, and a wider one (say, twenty rupees) for flagged-but-not-urgent, keeps your review queue focused on the mismatches that are actually mismatches.

Bucket what is left, then work the buckets in order

Only-in-books usually means a vendor has not filed yet. Only-in-2B usually means you missed booking an invoice. Amount mismatches usually mean a credit note was applied on one side and not the other. Work only-in-2B first, it is the bucket most likely to cost you input tax credit if ignored.

Close with a number, not a feeling

"Reconciliation looks fine" is not a close. "1,842 of 1,861 invoices matched exact or within tolerance, 19 flagged, all 19 have an assigned owner and a target date" is a close.

If your last reconciliation ended with a feeling instead of a number, when was it actually closed?