GSTR-2B vs Purchase Register: Why Enterprises Lose ITC Every Month (and How to Stop It)

Every month before filing the GSTR-3B, the finance team matches the purchase register with GSTR-2B. The main concern of every business has always been claiming Input Tax Credit on time; despite adopting multiple software solutions, most of them fail to avail it, but the actual reason is still hidden.

For an enterprise processing thousands of vendor invoices a month, even a 3% to 5% gap adds up to a serious annual loss.

This blog entirely focuses on the reason why enterprises lose ITC every month.

What is an input tax credit on GST?

It is the process in GST where a registered business reduces the tax amount it owes on sales using the credits it has already paid during purchases.

A simple overview of how ITC is claimed:

There are three companies: Company X, Company Y, and Company Z.

1. Company X bought raw materials for its IT team for ₹1,000 from Company Y. After applying 18% GST, it paid ₹1,180.
   
   [Product cost: ₹1,000 + 18% GST (₹180)  = ₹1,180 ]
   
   The ₹180 GST paid by Company X will be its Input Tax Credit (ITC), in the applicable conditions.
   
   
2. Company Y reported this sale in its GSTR-1. The invoice details can then be reflected in Company X’s GSTR-2B, showing ₹180 as eligible ITC, subject to the applicable conditions.
   
   
3. Company X modified the purchased goods and then sold the finished goods to Company Z for ₹5,000. After applying 18% GST, it sold them for ₹5,900.
   
   [Product cost: ₹5,000 + 18% (₹900) = ₹5,900]

Company X has now collected ₹900  GST from Company Z.

1. Company X has paid ₹180 GST on its purchase from Company Y and has ₹180 of eligible ITC. It has collected ₹900 GST on its sale to Company Z.

So:

Output GST collected = ₹900
Less: Eligible ITC = ₹180
Net GST payable = ₹900 - ₹180 = ₹720

Therefore, Company X uses its ₹180 ITC to reduce its output GST liability of ₹900 and pays the remaining ₹720 GST to the government.

Why the Two Records Are Difficult to Match

Now, to claim the ITC, companies face multiple challenges, and one of them is matching the records of your purchase register with GSTR-2B

The two documents are built differently.

• Purchase register:
  Your purchase register contains a record of what you received and booked. It reflects your accounting entries, your data quality, and your timing.
• GSTR-2B: a static, system-generated statement, produced on the 14th of the following month. It reflects what your suppliers filed and when they filed it.

To keep the numbers accurate, you compare your data with your vendors' data, filtered through GSTN rules.

A mismatch does not always mean an error. It can be a wrong GSTIN, duplicate claims, a blocked credit, or an invoice that was never reported.

The Real Causes of ITC Leakage

Most of these errors arise because of the  process failures that can be fixed with proper actions taken on time.

The Rules That Turn a Mismatch into a Loss

Four provisions decide whether a gap becomes a permanent cost.

1. Section 16(2)(aa): ITC needs the invoice to appear in GSTR-2B. No appearance, no claim for that period.
2. Section 16(4): the claim deadline is 30 November following the end of the financial year, or the date of filing the annual return, whichever is earlier. An invoice chased after that date cannot be claimed.
3. Rule 37: If you have not paid the supplier within 180 days of the invoice date, you must reverse the ITC (with interest) and can re-claim it once you pay.
4. Section 50(3): ITC wrongly availed and utilised attracts interest at 24% per annum.

The Invoice Management System Changes the Workflow

Since the Invoice Management System (IMS) was introduced in October 2024, the GSTR-2B is no longer entirely a function of what suppliers filed. You can now show your involvement there by accepting, rejecting, or keeping the invoices pending.

Invoices you take no action on are treated as accepted when 2B is generated.

This is useful, but it creates new risks:

• A rejected invoice drops out of your ITC, even if the purchase is genuine.
• Invoices parked as pending cannot stay there indefinitely.
• Credit notes need a deliberate decision, because accepting one reduces your ITC.

An IMS action is now a financial decision, and it needs a reviewer, a deadline, and a reason, just like a payment approval.

A Reconciliation Framework That Works at Enterprise Scale

Reconciliation done only in the filing week will always be rushed. A better step looks like this.

1. Reconcile continuously, not monthly. Pull supplier-wise data from the GST portal as it updates and then compare it with purchases throughout the month. By the 14th, most differences should already be known.

2. Match in layers, not in one pass. Strict matching on GSTIN + invoice number + date + value will miss real invoices because of wrong formatting. Use progressive matching:

3. Classify every exception with an owner. Mismatch is not a status. Each open item should carry a cause (supplier, data entry, timing, ineligible), an owner (procurement, AP, tax, vendor), and a due date.

4. Make vendor follow-up systematic. Send supplier-wise lists of missing invoices before the supplier's GSTR-1 due date, not after your 3B deadline.

5. Carry forward differences deliberately. An invoice missing this month often appears next month. Without a carry-forward ledger, it is claimed twice, claimed late, or forgotten.

6. Align payments with Rule 37. Maintain an ageing report of invoices approaching 180 days unpaid, so reversals and re-claims are planned rather than discovered during audit.

The Metrics Worth Tracking

If you only track the total mismatch value, you will miss where the problem sits. Track these monthly: 

A small group of vendors typically causes a large share of the exceptions, and a focused escalation on those vendors usually delivers more than any internal process change.

Where Software Fits In

Spreadsheets can manage a few hundred invoices. Beyond that, VLOOKUP-based reconciliation starts to fail, with slow files, inconsistent matching rules, and no audit trail.

This is the problem Webtel's GST filing software is built to handle. It brings portal data and purchase registers into a single view, applies layered matching rules, flags supplier non-filers, and keeps exception ownership visible. 

Using Web-GST, businesses can:

• Set up GST masters: Create GSTINs, appoint masters, map data, and view HSN, SAC, and tax-rate-wise details.
• Manage purchase data: Import data and validate or rectify invoices against the accounts books.
• Reconcile ITC: Reconcile purchase data with GSTR-2A and GSTR-2B to identify mismatches and potential ITC gaps.
• File GSTR-1: Prepare and file GSTR-1 directly from the system.
• Compute and file GSTR-3B: Calculate tax liability and file GSTR-3B directly.
• Track and compare ITC: Compare ITC across GSTR-2A and GSTR-2B and perform annual reconciliation.
• Manage exceptions: Identify mismatches, supplier non-filers, and other exceptions so they can be addressed before they impact ITC.

ITC is often lost not because the rules are unclear, but because reconciliation happens too late, matching is too rigid, and exceptions have no clear ownership.

Treating GSTR-2B as a continuous control rather than a month-end report helps businesses identify and resolve issues before they affect their ITC.