India GST ITC Reconciliation: GSTR-2B, IMS & Rule 37

India GST ITC reconciliation is the monthly process of matching your purchase register with supplier-reported GST records so you claim input tax credit only on eligible invoices. In practice, that means checking whether the invoices in your books appear correctly in the GST system, deciding what to do with those records in IMS, and then using GSTR-2B as the fixed monthly basis for the claim that ultimately flows into GSTR-3B. It also means keeping one eye on payment status, because if an invoice stays unpaid beyond 180 days, Rule 37 requires proportionate ITC reversal with interest, even though that credit can be reclaimed once payment is made.

That is why India GST ITC reconciliation is not just a portal exercise. It is an invoice-level control process. You are testing whether the supplier invoice in your purchase register, the supplier's filing behavior, the IMS status, and your own payment position all support the claim you want to make.

For most teams, the monthly control point is GSTR-2B, not GSTR-2A. GSTR-2A is useful for visibility because it changes as suppliers file or amend records. GSTR-2B is the static statement used for claim review in a given cycle. IMS now sits inside that workflow because recipients can accept, reject, or pend records, and those actions affect what should move into the claim process. As Taxmann's summary of GSTN's IMS rollout notes, the system was introduced to help taxpayers verify supplier invoices for accurate ITC claims, and no mandatory action is required for GSTR-2B generation.

That official rule matters because it shifts the work away from a vague "match the portal" mindset. Finance teams need invoice-level evidence that the supplier GSTIN is right, the invoice number is captured consistently, the tax values agree with the source document, and unpaid invoices approaching the 180-day ITC reversal threshold are visible before filing day. When those controls fail, the issue often shows up later as a GSTR-2B exception, but the root cause usually began in invoice capture, record standardization, supplier follow-up, or payment monitoring.

The rest of the workflow follows that logic. First, you need to understand how IMS, GSTR-2A, GSTR-2B, and GSTR-3B fit together. Then you need a match-ready purchase register, a clear mismatch taxonomy, a monthly review cadence, and a Rule 37 control for invoices that remain unpaid. Once those pieces are in place, reconciliation becomes less about reacting to portal surprises and more about running a controlled monthly process.

How IMS, GSTR-2A, GSTR-2B, and GSTR-3B Fit Together

The easiest way to understand the workflow is to think of each layer as doing a different job.

• GSTR-1 is where supplier-side invoice data enters the GST system.
• IMS is where the recipient reviews relevant records and decides whether to accept, reject, or keep them pending.
• GSTR-2A is the dynamic visibility layer, so it changes as supplier filings and amendments change.
• GSTR-2B is the static monthly statement that finance teams use as the claim baseline.
• GSTR-3B is where the ITC claim is finally reported.

In policy terms, the GST Council shapes the rule direction, CBIC drives the administration and interpretation layer, and GSTN runs the operating system that finance teams actually work inside each month.

This is where many guides blur together. The GSTR-2A vs GSTR-2B difference is not a small technical distinction. GSTR-2A tells you what is appearing in a live, moving view. GSTR-2B tells you what is locked for the cycle you are about to work on. If your team uses GSTR-2A as the control document, the reconciliation will keep shifting underneath you. If your team uses GSTR-2B as the static basis but ignores IMS actions and late supplier changes, you can still miss issues that need review before filing.

The GST invoice management system IMS adds an action layer that did not exist in older portal-only explanations. When you accept a record, you are confirming that it should feed the claim process. When you reject it, the record does not simply disappear; it becomes a supplier-side issue that usually needs correction or follow-up. When you keep it pending, you are deliberately postponing the decision because the supporting evidence or commercial reality is not settled yet. Finance teams also need to understand the more recent process updates properly. The October 2025 changes did not mean GSTR-2B stopped generating automatically or that GSTR-3B stopped receiving auto-populated ITC values. The real change was around expanded IMS handling, recomputation controls, Bill of Entry visibility in IMS, and tighter treatment of pending records.

That sequence matters upstream as well. If you already understand how India's IRN and IRP e-invoicing workflow feeds GST return data upstream, it becomes easier to see why supplier reporting quality affects what reaches IMS and later GSTR-2B. By the time the claim reaches GSTR-3B, most of the control work should already be done. Filing is the last step. Reconciliation discipline has to happen earlier, when you can still identify whether the issue is a supplier behavior problem, an invoice-data problem, or a genuine eligibility problem.

---

Why Purchase Register Quality Decides Whether ITC Matches

If your purchase register is inconsistent, the rest of the reconciliation process becomes noisy. Teams often describe this as a GST portal problem, but many exceptions are created before anyone opens IMS or downloads GSTR-2B.

A match-ready register should contain the fields that actually drive the comparison: supplier name, GSTIN, invoice number, invoice date, taxable value, tax amounts by component where relevant, credit note treatment, and current document status. It should also reflect the same document logic that your team will use during review. If one analyst enters a supplier invoice number with slashes, another removes the slashes, and a third trims leading zeros, the same invoice can look unmatched even when the supplier filed correctly. The same thing happens when GSTINs are mistyped, tax amounts are rounded inconsistently, or credit notes are parked in a separate tracker that never feeds the main reconciliation file.

That is why good GST purchase register reconciliation starts with standardization rules, not just a portal download. You need confidence that the row in your register actually represents the source invoice. When a mismatch appears, your team should be able to answer basic questions immediately: Is the invoice missing from the register, missing from the supplier filing, present with a different number format, mapped to the wrong GSTIN, or affected by a later credit note?

Consider a common case. The supplier uploads invoice number 00458/24-25 in GSTR-1. Your AP team keyed the same document as 4582425 in the purchase register after removing separators and compressing the year marker. The supplier did file, GSTR-2B does show the invoice, but the record fails to match because the internal register transformed the identifier beyond recognition. That is not a portal failure. It is a data-governance failure.

The control objective is not perfection in every field. It is enough consistency to separate true tax issues from preventable formatting issues. Many of the same invoice matching controls that help standardize records before month-end review apply here, but GST reconciliation adds higher stakes because bad structure can delay or block ITC. The same purchase-register discipline also shows up in Indonesia's input VAT reconciliation workflow under Coretax, where supplier tax invoices and monthly credit timing have to line up before input VAT can be used confidently.

This is one place where an upstream extraction tool can add measurable value. Invoice Data Extraction can pull supplier names, GSTINs, invoice numbers, invoice dates, taxable values, tax amounts, and line items from PDF or image invoices into structured Excel, CSV, or JSON outputs. That does not replace IMS review or GST filing, but it helps teams start from a cleaner register instead of re-keying fields from mixed supplier formats every month.

The Most Common GST ITC Mismatches and How to Investigate Them

Not every exception belongs in the same queue. A better GSTR-2B reconciliation guide separates mismatches by root cause so the reviewer knows what to verify first.

1. Supplier filing gaps or delays
The invoice exists in your books, but the supplier has not filed it in GSTR-1 yet, filed late, or amended it after your review window. This is a supplier follow-up issue first. Confirm the source invoice, confirm the expected filing period, and then follow up with the supplier using specifics instead of a generic "not reflecting" message.

2. GSTIN and master-data errors
If the supplier GSTIN on the invoice does not match the GSTIN captured in your register, the record may appear as missing or mismatched even though the supplier filed. Check the source document, vendor master, and any manual edits made during AP booking.

3. Invoice-number inconsistencies
This is one of the most common internal causes of failed ITC matching GST reviews. Differences in slashes, hyphens, prefixes, spaces, leading zeros, or credit-note numbering conventions can create false exceptions. Compare the portal record to the invoice image, not just to the spreadsheet cell.

4. Tax-value variances
Sometimes the record matches at invoice level, but taxable value, IGST, CGST, or SGST amounts do not line up. These are usually caused by data-entry errors, supplier mistakes, rounding differences, or partial credit-note activity. Review the original invoice and any subsequent adjustments before deciding whether the mismatch is material.

5. Credit note timing and amendment issues
Credit notes often distort reconciliation because they appear in a different period from the original invoice or are captured in the register after the main review is already underway. Treat them as their own category. If you mix them into general unmatched invoices, the team loses sight of whether the problem is timing, value adjustment, or document linkage.

6. Period cut-off and duplicate-entry issues
An invoice booked in one month but filed in another, or entered twice internally, can look like a GST visibility issue when it is really a process-timing issue. Cross-period checks matter, especially around month-end and year-end closes.

The practical lesson is that ITC mismatch GST reasons should be classified before anyone starts supplier outreach or tax adjustments. Once you label the exception correctly, invoice mismatch resolution gets faster because each bucket has a different next step: supplier chase, data correction, amendment review, credit-note mapping, or timing review.

A Monthly GST Reconciliation Workflow From Invoice Capture to GSTR-3B

Teams that treat reconciliation as a once-a-month download usually end up doing emergency cleanup near the filing deadline. A better operating model runs through the month and turns GSTR-3B into the output of a controlled process.

1. Capture and standardize invoice data early.
   As invoices arrive, make sure the purchase register is updated with standardized identifiers, tax values, supplier GSTINs, and document status. If you wait until the portal review window, you create avoidable noise.

2. Review supplier-side visibility and IMS status.
   Once records begin appearing through the GST workflow, compare them against your register and identify which invoices can be accepted, which require investigation, and which should remain pending briefly because the supporting facts are incomplete.

3. Work the exception list by cause, not by chronology.
   Separate supplier non-filing, GSTIN errors, invoice-number inconsistencies, value mismatches, and credit-note issues. This avoids wasting time on issues your team cannot solve internally.

4. Resolve what you control before supplier escalation.
   Fix internal data errors, attach invoice evidence, confirm whether a document was booked in the correct period, and make sure the same invoice is not duplicated under different identifiers. Many teams discover that a meaningful share of exceptions can be cleared without leaving the finance team.

5. Use IMS actions as part of the workflow, not as an afterthought.
   Accepted records should move cleanly toward the claim process. Rejected records should trigger supplier correction or clarification. Pending records need a tracked reason and a follow-up date, especially now that pending treatment has tighter operating limits.

6. Finalize GSTR-2B review before filing GSTR-3B.
   By this point, your finance team should have a documented position on what is claimable, what remains blocked, and what must be reversed or deferred. That is the stage where the GSTR-3B ITC auto-population becomes useful, because it is being checked against a prepared dataset rather than against raw exceptions.

7. Preserve the audit trail.
   Keep a trace from source invoice to purchase-register row to portal record to final claim logic. If you need a broader control model, a broader invoice reconciliation framework for tracing discrepancy root causes can help structure ownership and exception handling beyond GST.

This monthly cadence is what turns India GST ITC reconciliation from a reactive compliance task into a repeatable finance control. The forms matter, but the sequence matters more.

---

Rule 37 Turns Unpaid Invoices Into a Reconciliation Risk

Many teams treat unpaid-invoice tracking as an AP follow-up issue and GST review as a tax issue. Rule 37 makes that split dangerous.

Under Rule 37 read with Section 16(2), if the recipient does not pay the supplier within 180 days from the invoice date, the input tax credit already claimed must be reversed in proportion to the unpaid amount. Interest is calculated at 18% per annum from the date the ITC was availed until the date of reversal. The credit can be reclaimed once payment is eventually made, and this rule does not apply to reverse charge supplies.

That means a clean GSTR-2B match is not the end of the story. An invoice can be fully reflected, accepted, and claimed, but still create compliance exposure later if payment aging is not monitored. This is why the Rule 37 180 day ITC reversal control belongs inside the reconciliation process. The tax team needs visibility into payment status, and the AP team needs visibility into which invoices carry claimed credit that may need reversal.

Take a simple example. Suppose you claimed ITC on an invoice for INR 100,000 plus GST, but by day 180 you have paid only half the amount. The reversal is proportionate to the unpaid share, not necessarily the whole credit. If your team does not connect the payment ledger to the claimed invoice, the reversal can be missed, and the later re-claim can be missed as well when the balance is finally settled.

The operational control is straightforward in concept even if the data work is tedious. Your register needs aging fields, payment-status fields, and a way to flag invoices nearing the 180-day threshold. It also needs a process for documenting reversals, interest exposure, and later re-availment. When teams separate those records from the main reconciliation workflow, they often protect the monthly claim but lose control of the later correction cycle. GST ITC reconciliation India therefore includes not only matching and eligibility review, but also ongoing monitoring of whether the commercial payment condition continues to support the claim.

Where Automation Helps Without Becoming a GST Filing Tool

Once you look at reconciliation as an invoice-data workflow, the best automation opportunities become clearer. Most finance teams do not need another promise about filing. They need less manual cleanup before they review IMS, GSTR-2B, and GSTR-3B.

Automation helps most in five places:

• Invoice capture into a structured purchase register so supplier names, GSTINs, invoice numbers, dates, taxable values, tax amounts, and line items are not being re-keyed from every PDF.
• Field standardization so invoice-number formats, tax fields, and document types are more consistent before matching starts.
• Exception preparation so missing fields, suspicious values, and inconsistent identifiers are visible before the tax review window tightens.
• Aging and payment monitoring so invoices approaching the Rule 37 threshold are easier to spot.
• Operational visibility so the team spends less time on spreadsheet cleanup and more time on genuine mismatch resolution and supplier follow-up.

That is the practical role of invoice data extraction for GST reconciliation workflows. A tool like Invoice Data Extraction can take PDF or image invoices, follow user instructions about what fields to extract, and return structured XLSX, CSV, or JSON outputs for review. Teams can use it to prepare cleaner purchase-register data, especially when invoices arrive in mixed formats or when one reviewer's spreadsheet conventions do not match another's. It supports reconciliation readiness, but it is not a GST return filing tool, an IMS submission layer, or a substitute for the legal judgment behind claim eligibility.

If you are deciding whether automation is justified, look for signals that the current process has outgrown manual handling:

• your exception list is driven by formatting differences rather than genuine tax issues
• month-end review depends on large amounts of spreadsheet cleanup
• the same supplier data has to be corrected repeatedly
• unpaid-invoice tracking is too weak to support 180-day reversal monitoring
• supplier follow-up starts too late because the team is still cleaning the register

When those patterns are present, GST reconciliation automation is not about removing professional judgment. It is about reducing the manual friction that keeps your team from applying that judgment where it matters.