Why the GST Invoice Management System (IMS) Changed Everything for AP Teams

The Invoice Management System went live on the GSTN portal in October 2025 with no announcement that most mid-market finance teams noticed. The GSTR-3B filing for April 2026 was the first return where the ITC hard block applied — meaning ITC could only be claimed on invoices reflected in GSTR-2B, with no manual overrides. Finance teams that had not understood IMS by March 2026 discovered the consequence when their April GSTR-3B was smaller than expected.

Here is how IMS works and what it changes in your monthly AP workflow.

How IMS Works

When a supplier uploads an invoice to the IRP — either through the e-invoicing portal or through their GSTR-1 filing — it appears in the recipient's IMS dashboard. The IMS is a running list of all inward supply invoices from GST-registered suppliers, organized by filing period.

For each invoice in the IMS, you have three actions: Accept (you confirm the invoice is correct and you want to claim ITC), Reject (you dispute the invoice — this sends a signal back to the supplier), or Pending (you are deferring the decision). If you do nothing, the system automatically treats the invoice as Accepted after a defined period.

The critical connection: only invoices you Accept in IMS, and that are reflected in your GSTR-2B, are eligible for ITC claim in GSTR-3B. This is the hard block. An invoice you received, paid, and entered in your purchase register but that is not in GSTR-2B because the supplier filed late — you cannot claim that ITC until it appears.

What Changes in the Monthly Workflow

Earlier GSTR-2B monitoring. Under the old workflow, many teams downloaded GSTR-2B on the 13th or 14th and reconciled before filing. Under IMS, the 13th is too late. Invoices that appear late in the filing period may not have enough time for correction cycles with suppliers. The first IMS and GSTR-2B check should happen by the 5th — after most suppliers have filed their GSTR-1 — to identify gaps early.

Active Reject decisions. Before IMS, rejecting a supplier invoice was an informal process — you disputed it by email or phone. Now, rejecting in IMS is a formal action with consequences: it notifies the supplier, removes the invoice from your GSTR-2B, and requires a reprocessing cycle. Rejecting the wrong invoice — for example, an invoice you legitimately received but have a minor amount dispute with — creates a correction process that takes time. Be specific about what Reject means in your team's workflow versus Pending.

Managing the auto-Accept risk. The default behavior — inaction equals Accepted — is designed to reduce friction for most invoices. But it creates a risk for invoices you have not yet received goods for, invoices under dispute, or invoices from suppliers whose GSTR-1 has errors. A team that does not monitor IMS actively will end up Accepting invoices they should have held.

IMS volume management. A company processing 500 invoices per month has 500 potential IMS entries to review. In practice, most of these should be routine Accepts — invoices that match your purchase register, have valid IRNs, and have corresponding GRN confirmations. The IMS workflow is manageable if routine invoices are processed first and exceptions are isolated. A backlog of 200 unreviewed IMS entries on the 12th of the month is an AP process failure, not an IMS design problem.

The finance teams managing IMS effectively treat it as the final check in the monthly AP cycle, not as an additional administrative task. The ITC amounts that flow through the IMS — and the interest cost of losing them to avoidable blocks — make it one of the highest-value activities in the AP calendar.