The ITC you booked isn't the ITC you can claim
A founder is about to claim ₹14 lakh of input tax credit. Riya asks how much is actually in their GSTR-2B. The gap is ₹2.8 lakh — and the fix is a phone call, not a write-off.

“The credit you booked isn't the credit you can claim.”
Transcript›
You're claiming ₹14 lakh. How much of it is actually in your 2B?
You can only claim the ITC the portal can see. Your books don't decide that — your vendors do.

“₹2.8 lakh of credit — booked, but not in 2B. Six vendors haven't filed.”
Transcript›
Claim it now and it's a notice next quarter. Drop it and you've gifted ₹2.8 lakh away. Neither is the answer.
An invoice missing from 2B isn't lost yet. It's a vendor who's late — and a call you haven't made.

“Reconcile before you file. The credit you keep is the credit you proved.”
Transcript›
Four vendors filed after the nudge — claim the ₹2.1 lakh now. Two are chronic; their ₹0.7 lakh moves to next month's 2B, not the bin. File a 3B that ties out.
The chase-list is the product. Matching is easy — knowing exactly who to call is the win.
The longer take
A founder once told me, the week before a GSTR-3B deadline, that his input tax credit for the month was ₹14 lakh. I asked how he knew. He opened his accounting software and pointed at the purchase ITC total. That number is real — it's the GST he actually paid his suppliers. But it answers a different question from the one that matters at filing time, which is: how much of that credit has the portal actually made available to you?
Those two numbers are not the same, and the difference is the whole game. Under Rule 36(4) and Section 16(2)(aa), you can claim ITC on an invoice only if it appears in your GSTR-2B — and your 2B is built from what your suppliers filed in their GSTR-1, not from what you booked. So the credit you can legally claim is bounded by your vendors' filing discipline, not your own. The gap between 'ITC in my books' and 'ITC in my 2B' is, quite literally, money whose fate is in someone else's hands.
There are two ways to get that gap wrong, and both cost real money. Claim the full booked amount and the portion that isn't in 2B becomes over-claimed credit — recoverable later by the department with interest and penalty, which is the notice nobody wants. Quietly drop the gap to be safe and you've written off credit you were genuinely entitled to — cash gifted away because a vendor was a week late. The discipline that avoids both is the same one every month: reconcile the purchase register against 2B, isolate exactly what's booked but not yet in 2B, and decide each line on evidence rather than on the deadline clock.
And here's the part people miss: the value isn't in the matching. Pairing invoice numbers across two files is the easy bit a machine should do. The value is in what falls out of it — the per-vendor chase-list. A reconciliation that ends with 'these six suppliers, totalling ₹2.8 lakh, haven't filed' turns an abstract gap into six phone calls. Most of those vendors file within the week once nudged; you claim that credit in the same period. The chronic late-filers' invoices don't get written off either — they're deferred, expected to land in a subsequent 2B, and tracked so they're claimed when they do. Nothing is guessed and nothing is gifted away.
At twenty invoices a month you can do all of this in a spreadsheet. At a few thousand it breaks — not on the matching logic but on the variations that look like differences and aren't: invoice numbers with stray leading zeros, second-decimal rounding on tax, credit notes that should reduce credit, amendments that supersede the original, the same invoice landing in next month's 2B. A tool earns its place by absorbing all of that so the human spends their time on the chase-list and the judgment calls, not on row-by-row matching against a deadline. The honest framing: GSTR-2B reconciliation isn't optional and it isn't hard — it's just relentless, every month, and that's exactly the kind of work worth handing to something that doesn't get tired in week two of the close.