GST IMS Dashboard Actions Step-by-Step: Accept, Reject, Pending for Indian Businesses

The GST Invoice Management System (IMS) dashboard is now the single chokepoint between your supplier’s GSTR-1 filing and your own GSTR-2B. Every invoice your suppliers upload lands here first, waiting for one of three actions: Accept, Reject, or Pending. Miss the window and the system decides for you — and the default is not in your favour for disputed invoices.

This walkthrough is for finance, indirect-tax, and accounts-payable teams running monthly IMS cycles in India. It assumes you already know the basics of GSTR-2B and Section 16(2)(aa); the focus here is dashboard mechanics, deadline timing, and multi-GSTIN orchestration with a worked ₹85 Cr manufacturer example.

Quick reference: the three IMS actions

The “No action equals Accept” default is the rule most teams underestimate. If your AP clerk goes on leave during cut-off week and 60 invoices sit untouched, those 60 invoices enter your 2B and trigger ITC claims you may not be entitled to under Section 16(2)(aa) if the supplier later fails to pay tax.

What does the IMS dashboard actually show?

When you log into the GST portal and open IMS, the dashboard lists every B2B invoice, credit note, and debit note your suppliers have reported via GSTR-1, GSTR-1A, or IFF for the current return period. Each row carries the supplier’s GSTIN, invoice number, date, taxable value, tax heads (CGST/SGST/IGST/Cess), and the current action status.

Filters let you slice by supplier, document type, value band, and action taken. The bulk-action option, where available, lets you act on multiple invoices at once — essential for any business with more than a few hundred monthly records.

The dashboard refreshes as suppliers file or amend. An invoice you accepted on the 5th may be amended by the supplier on the 12th; the amended version reappears in your queue and your earlier action lapses. This is why a single end-of-month review is not enough — IMS is a rolling workflow.

When are the actual deadlines?

Three dates matter every month:

1. 11th of the following month — supplier GSTR-1 filing due. Most invoices for the period are visible in IMS by this date.
2. 13th of the following month — supplier GSTR-1A and IFF amendments close. The IMS queue stabilises.
3. 14th of the following month — GSTR-2B is generated. Whatever action state exists at this moment is locked into 2B.

Anything not actioned by the 14th defaults to Accept. The practical operating model for most India teams is: triage daily from the 1st, intensive review on the 11th–13th, sign-off and final push by end of day on the 13th.

How do you Accept an invoice on the IMS dashboard?

The Accept flow is the simplest. From the IMS list view:

1. Open the invoice row to inspect supplier GSTIN, invoice number, date, taxable value, and tax breakup.
2. Match against your purchase order and goods receipt note. For services, match against the engagement record or work-order completion certificate.
3. Confirm the supplier has filed GSTR-1 for the period — IMS shows this status flag.
4. Click “Accept”. The row status changes and a confirmation appears.
5. For bulk Accept, select the rows and use the bulk action menu.

Accept is the right action when the invoice matches your records, the supplier has filed, and you intend to claim the ITC. Once 2B is generated, the ITC sits in your eligible bucket for the GSTR-3B period.

When should you Reject an invoice?

Reject is the right action in four scenarios:

• The invoice is not yours — wrong recipient GSTIN entered by the supplier.
• The invoice is a duplicate of one already reported.
• The taxable value, tax rate, or HSN is materially wrong and the supplier needs to issue a credit note plus a fresh invoice.
• You disown the transaction entirely — for example, a fraudulent supply you never received.

To reject:

1. Open the invoice row and document the reason (your internal note, not visible to the supplier).
2. Click “Reject”.
3. Confirm the action. The supplier sees the rejection in their outward IMS view and can issue a corrected invoice in the next period.

Rejected invoices are excluded from your GSTR-2B for the current period. The ITC does not arise. If the supplier re-files a corrected invoice in a later month, it reappears in IMS and you act on it again.

When is Pending the right action?

Pending is the most under-used action and the most useful in three situations:

• Goods in transit at month-end. The supplier has filed GSTR-1 but the consignment has not reached your warehouse. Section 16(2)(b) requires receipt of goods before ITC. Pending defers the invoice until the month you actually receive it.
• Documentation gaps. Lorry receipt, e-way bill, or quality certificate is awaited. Pending buys time without forcing a Reject you will have to reverse.
• Supplier dispute under negotiation. A pricing or quantity dispute is open; you do not want to Accept and claim ITC you may have to reverse, nor Reject and burn the supplier relationship before talks conclude.

Pending invoices roll forward to the next IMS cycle. You can change the action — Accept, Reject, or hold again — when the next 2B is generated. There is no statutory cap on how long an invoice can stay Pending, but auditors will ask questions about anything held for more than two or three cycles.

Worked example: a ₹85 Cr manufacturer, single month

Consider a mid-size auto-component manufacturer in Pune, ₹85 Cr annual turnover, single GSTIN, roughly 480 inward B2B invoices per month across 140 suppliers. Here is how a clean IMS month looks on the dashboard.

Reading the table: 370 invoices worth ₹5.60 Cr accepted, 18 invoices worth ₹36.8 lakh rejected, and 92 invoices worth ₹1.37 Cr held as Pending. The ITC entering GSTR-2B for this period is the tax component on the ₹5.60 Cr accepted base — roughly ₹1.01 crore at the blended 18% rate.

The day-25 alert volume — internal reminders for items still un-actioned — for this manufacturer typically runs at 35 to 50 records by the morning of the 13th, mostly the “supplier not filed” bucket plus late documentation cases. The AP lead clears these by close of business on the 13th, ensuring nothing slips into deemed-Accept on the 14th.

Want to estimate the ITC at risk in your own monthly cycle? Run the numbers in our ITC Leakage Calculator to see how much value sits in mis-actioned IMS records across a typical year.

How does multi-GSTIN orchestration work?

A group with 8 GSTINs across states will see 8 separate IMS dashboards. Each is governed by its own login and its own GSTR-2B cycle. The risks of decentralised IMS action are real:

• Two GSTINs of the same group taking different actions on invoices from the same supplier.
• Inconsistent Pending policies — one GSTIN holds aggressively, another auto-accepts.
• No single audit trail for tax-head reporting at group level.

The operating pattern that works is a daily pull of IMS records from every GSTIN into a single workbench, classification against a shared ruleset (PO match, GRN match, supplier filing status, value band), and a bulk push of actions back to the portal where the API supports it. Group-level dashboards show un-actioned counts by entity, day-by-day, with escalation triggered as the 13th approaches.

For mid-market and enterprise groups, the difference between disciplined orchestration and entity-by-entity workflow is usually one or two crore rupees of ITC visibility per quarter — most of it from the Pending bucket being managed rather than defaulting.

How does IMS change Rule 36(4) and 88C/88D exposure?

Rule 36(4) — the 5% provisional ITC restriction — was structurally absorbed by IMS for invoices flowing through the dashboard. Only accepted invoices count for ITC; there is no provisional buffer. This is cleaner but unforgiving: if you fail to Accept, you do not claim, full stop.

Rule 88C and 88D mismatch notices continue to operate downstream. If your GSTR-3B claim exceeds the ITC visible in 2B by more than the prescribed thresholds, you receive a DRC-01C (Rule 88C) or DRC-01D (Rule 88D) intimation. Disciplined IMS action — and disciplined Pending hygiene — keeps the 2B figure honest and reduces the trigger surface.

Section 16(2)(aa) — supplier must have furnished details and tax must have been paid — still bites. IMS Accept on an invoice whose supplier later defaults on GSTR-3B still creates reversal exposure. The dashboard does not absolve you of supplier-payment risk; it only structures the invoice-acceptance layer.

What should your monthly IMS calendar look like?

A workable rhythm for an Indian finance team:

• Days 1–10: daily IMS pull, classify clean matches, Accept where rules pass.
• Day 11: intensive review of supplier filing status; chase non-filers.
• Day 12: Reject decisions finalised with internal notes; Pending decisions documented with reason codes.
• Day 13: final sweep, bulk action push, sign-off by the indirect-tax lead.
• Day 14: GSTR-2B generated; reconcile against the action register.
• Day 15 onwards: Pending items roll into the next cycle; supplier follow-ups begin for rejected invoices.

The teams that get this right treat IMS as a continuous workflow, not a month-end task. The dashboard rewards daily attention and punishes neglect through the deemed-Accept default.

Where to go next

If you are scoping tooling to take IMS action off spreadsheets, start with our GST reconciliation software overview — it covers the dashboard automation, ERP match logic, and multi-GSTIN orchestration patterns referenced above. For broader coverage of reconciliation infrastructure across TDS, GST, NACH, and bank, see reconciliation software India.

The IMS dashboard is not difficult. It is unforgiving. Three actions, one default, one deadline a month — get those four facts right and the rest is operational discipline.