Invoice Management System (IMS) in GST
How IMS rebuilds GSTR-2B from supplier invoices you accept, reject or keep pending, what each action does to your input tax credit, and the deadlines.
The Invoice Management System changed where input tax credit gets decided. It used to be decided in a spreadsheet, after the fact, by whoever reconciled the purchase register against GSTR-2A. It is now decided on a portal screen, before GSTR-2B exists, by whoever clicks Accept, Reject or Pending — or by nobody, which is its own decision with its own consequences. This post is about running that screen: what arrives on it, what each button does downstream, and the monthly routine that keeps an AP team ahead of it. For the statutory background and the GSTR-2B mechanics, read GSTR-2B and the Invoice Management System alongside this.
What IMS is, and the problem it was built for
IMS went live on the GST portal in October 2024. It is one dashboard per GSTIN, listing every inward B2B document your suppliers have reported against you — invoices, debit notes, credit notes and the amendments to each.
The problem it solves is one every AP team recognises. Before IMS, supplier data flowed into your GSTR-2B untouched. A duplicated invoice, a supply that never left the vendor's warehouse, a bill raised against the wrong GSTIN of yours — each still landed in your GSTR-2B as available credit. You found it at reconciliation, if you found it at all, and cleaning it up meant a reversal and an interest exposure.
IMS moves the review upstream. The recipient now gets a say before the statement is drawn, which means bad records can be stopped rather than unwound. That is the upside. The corresponding obligation is that somebody has to look.
How a supplier invoice lands on your dashboard
A record reaches your IMS in two stages, and the distinction matters more than it first appears.
Saved. When a supplier saves an invoice in their GSTR-1, the Invoice Furnishing Facility or GSTR-1A, the record generally becomes visible on your dashboard straight away, before they have filed anything. A supplier who is still editing can change or delete it, and what you see reflects the latest saved version.
Filed. Only once the supplier files does the record become eligible to flow into your GSTR-2B. Until then it is a preview, not a credit. This is why a document can sit on your dashboard all month and still be absent from the statement on the 14th — the supplier saved it and never filed. The filing timetable behind that is in the GSTR-1 filing guide, and the calendar view is in GST return due dates.
You can act on a saved record. It is rarely worth it. Act on filed records, and read saved ones as an early warning of what is coming.
Three actions, and a fourth outcome nobody chooses
Accept. You agree the document is yours and the credit belongs in this period. It flows into GSTR-2B as available ITC.
Reject. The document is not yours, is a duplicate, or is wrong in a way that makes the credit indefensible. It is excluded from GSTR-2B entirely and appears in the rejected section of the statement, so your supplier can see the outcome and re-report correctly.
Pending. You are not ready to decide. The record is excluded from this period's GSTR-2B and carried forward on the dashboard until you act on it, at which point the credit lands in the GSTR-2B of the period in which you accepted it. Pending is the right answer for an invoice whose goods have not arrived, since the credit is not yours until receipt anyway — see the input tax credit conditions. It is not a permanent parking space: the Section 16(4) deadline keeps running while the record sits there, and the arithmetic of that deadline is in the ITC time limit under Section 16.
No action. This is the fourth outcome, and it is the default for everything your team does not reach. A record left untouched is deemed accepted and enters GSTR-2B exactly as though you had clicked Accept. Nothing warns you. The credit simply appears, and you have claimed it.
Not every document can be parked. Some record types must be accepted or rejected in the period they appear, with original credit notes the clearest long-standing example. GSTN has relaxed parts of this in phases since the facility launched, and the boundary has moved more than once, so confirm the current position for your record type on gst.gov.in rather than trusting a rule you learned in 2024.
What each action does downstream
Every action has three consequences: one in your GSTR-2B, one in your GSTR-3B, and one on the other side of the transaction. The third is the one teams forget.
| Action | Effect on GSTR-2B | Effect on GSTR-3B | Effect on the supplier |
|---|---|---|---|
| Accept | Included as available ITC for the period | Auto-populated into the ITC table; claimable subject to the usual eligibility tests | None. Their reported liability stands |
| Reject | Excluded; shown in the rejected section of the statement | No credit flows through; nothing to claim | Invoice or debit note: they must re-report or amend it. Credit note: the tax is added back to their liability |
| Pending | Excluded from this period, carried forward on the dashboard | Nothing this period; the credit arrives in the period you later accept it | None. The document stays filed on their side |
| No action | Deemed accepted and included, identically to Accept | Auto-populated and claimed, whether or not you reviewed it | None |
The GSTR-3B column is where the discipline pays off, because the ITC table there is auto-populated from GSTR-2B. GSTN has stated its intention to restrict how far that table can be edited at filing time, and the timing of that restriction has shifted more than once — treat it as unsettled and confirm the current position on gst.gov.in before you assume you can still override a figure. The safe assumption is that the number you fix in IMS is the number you file. The filing mechanics themselves are in the GSTR-3B filing guide.
When GSTR-2B is drafted, and when it is redrawn
A draft GSTR-2B is generated on the 14th of the month following the tax period, built from supplier filings and filtered through your IMS actions as they stand at that moment. Under the QRMP scheme the statement is quarterly rather than monthly.
The 14th is not a lock. IMS remains open afterwards, and if you change an action the portal lets you recompute GSTR-2B for that period so the statement reflects the new decision. What closes the window is filing GSTR-3B for the period: once that return is in, the statement is settled and any later change to a record affects a subsequent period instead.
When a supplier changes the record after you acted
Suppliers revise documents, and the revision interacts with whatever you already decided.
If the supplier edits or deletes a record before filing, the dashboard follows them. An edited record replaces what you saw, and the action you took against the old version does not carry over — the document comes back needing a fresh decision. A deleted record disappears along with your action. This is the practical argument for not spending time on saved records.
If the supplier amends after filing, through GSTR-1A or an amendment in a later GSTR-1, the amended document arrives as its own line on your dashboard and needs its own action. The original and the amendment are separate records with separate fates, and the amendment generally flows into the GSTR-2B of the period in which the supplier filed it, not the period of the original invoice. Expect a timing difference between your books and the statement, and expect it to be legitimate.
An IMS action is a decision about one version of a document, not about the document forever. Re-check anything you actioned early in the month before you sign off.
Credit notes, and the cost of rejecting one
Credit notes run in the opposite direction to everything else on the dashboard, and that inversion is where teams do real damage.
When a supplier issues a credit note — a return, a discount, a price correction — they reduce their output tax liability by it, and you reduce your credit by the same amount. Accepting one in IMS therefore reduces your ITC, which feels wrong to click, which is why teams working fast reject it.
Rejecting a credit note is not a neutral decline. It tells the portal the reduction was not valid, and the tax the supplier had removed from their liability is added back to it. Your supplier pays tax on a discount they already gave you, and they will ask why. If the credit note is genuine — the goods did go back, the discount was agreed — accepting it is simply correct, and your books should already reflect the reduction. Reject one only when the underlying credit is not yours, and be prepared to explain it. The document rules sit in debit notes and credit notes under GST.
A monthly routine an AP team can actually run
The routine that works is early, ordered by value, and finished before the 14th.
- Days 1–11: watch, do not act. Use the view to chase suppliers who have not reported invoices you are holding, rather than to click buttons on drafts.
- Day 12: pull and match. Export the dashboard, match it against the purchase register and goods-receipt records, and split the result into matched, unmatched, and matched but not yet received.
- Day 12–13: act, highest value first. Accept the matched. Mark the received-but-unverified as pending. Reject only what you can defend in a sentence. Route every credit note past whoever owns the supplier relationship before it is rejected.
- Day 14: read the draft. Compare the generated GSTR-2B against your expected ITC figure. A gap means a supplier did not file, an amendment landed, or an action did not save.
- Before filing GSTR-3B: recompute if anything moved. Then file, knowing the period is about to close.
- After filing: chase the pendings. Every carried-forward record is credit you have not claimed yet and a clock you are running down.
The full AP-side version of this, including onboarding checks, is in vendor GST verification for accounts payable.
The gap IMS cannot close
IMS answers one question precisely: did this supplier report this document against my GSTIN. It does not answer the one that decides whether the credit survives — is this supplier still a live, filing registration.
A vendor whose GSTIN was cancelled in August still has July invoices on your dashboard. A vendor who has stopped filing GSTR-3B while still filing GSTR-1 keeps populating your IMS with documents you can happily accept, right up until the tax they never paid becomes your reversal under Rule 37A. A retrospective cancellation reaches backwards into periods you already closed, which is its own problem — see what happens when a supplier's GST is cancelled retrospectively.
None of that is visible on the IMS screen. It lives in the registration record and filing history behind the GSTIN — a separate lookup, and above a few dozen vendors a programmatic one. Checking supplier return filing status on a schedule turns a reconciliation surprise into an early warning; the setup is described in automated daily vendor GSTIN monitoring.
That is the check our API is built for: one call returns registration details and GSTR filing history together, at ₹0.50 per verification and ₹0.40 once a single credit purchase crosses 2,500 credits, with purchased credits that do not expire. Verifying your email releases 20 free credits, valid for 30 days, which is enough to run your top vendors before deciding anything — see pricing and the API docs, or create an account. For one-off checks there are five free lookups a day at GST number search with no signup.
Frequently asked questions
A note on accuracy. GST rules change often. This article reflects our understanding as of 21 September 2026 and is general information, not tax or legal advice. For the authoritative position, check gst.gov.in and cbic-gst.gov.in, or speak to a qualified tax professional about your specific situation.
Check a GSTIN right now, free
Five lookups a day, no account required. Status, filing history, e-invoicing and jurisdiction.
Free GST search toolBuild it into your product
One REST call, JSON back. Get an API key and 20 free verification credits in under a minute.
Start freeMore on gst rules & compliance
Browse every guide in the GST API blog.