GST and input tax credit
What Is GST IMS? Invoice Actions and ITC Workflow
Direct answer
The GST Invoice Management System, or IMS, is a portal workflow where recipients review specified supplier documents and mark them accepted, rejected or pending. No action is treated as deemed acceptance at GSTR-2B generation. IMS outcomes shape downstream statement data, but recipients must still verify documents, receipt, business use and every legal condition for input tax credit.
Acronym: IMS. Also known as: GST IMS, recipient invoice action system.
Key takeaways
- Accept, reject, pending and no action have different effects on GSTR-2B and GSTR-3B.
- An action can be changed before the corresponding GSTR-3B is filed; the latest saved action governs.
- Supplier edits can reset a recipient action, so exception queues need repeat monitoring.
- Use rejection for genuinely incorrect documents, not as a substitute for internal ineligibility accounting.
The four IMS action states
| State | Portal treatment | Finance interpretation |
|---|---|---|
| Accepted | The eligible record is considered for GSTR-2B and downstream GSTR-3B population. | The document appears commercially correct, but statutory ITC checks still apply. |
| Rejected | The record is excluded from the recipient’s eligible flow and the supplier can see the recipient action. | Use when the document itself is not yours or is materially wrong; preserve reason and supplier follow-up. |
| Pending | The record does not become part of GSTR-2B or GSTR-3B and remains on IMS until action or the applicable statutory limit. | Use for a real unresolved fact, with an owner and review date. |
| No action | The system treats the record as deemed accepted when GSTR-2B is generated. | Silence has an outcome; do not confuse an untouched queue with reviewed eligibility. |
GSTN guidance also distinguishes records that are not routed through IMS in the ordinary way. Teams should follow the current portal advisory for reverse-charge and system-ineligible records rather than forcing them into an accept/reject process.
IMS action lifecycle from supplier save to filing
- Supplier prepares a record. Specified invoices, debit notes, credit notes and amendments can flow to the recipient view according to their save or file status.
- Recipient reviews the record. AP or tax users compare GSTIN, document identity, values and tax to commercial evidence.
- Recipient saves an action. Actions may be changed multiple times before filing the corresponding GSTR-3B; the latest action overwrites the earlier one.
- Supplier filing confirms the record. Filed and accepted, rejected or deemed-accepted records are considered at the GSTR-2B cut-off under portal rules.
- Draft GSTR-2B is generated. If the recipient changes an action after generation, the revised advisory requires recomputation.
- GSTR-3B is filed. Filing freezes the action for that return workflow. The legal claim remains the taxpayer’s responsibility.
When a supplier edits a saved record before filing, GSTN says the edited version replaces it in IMS and the previous recipient action resets. Therefore, a daily “action completed” metric can overstate closure unless the process also detects reset records.
How IMS affects GSTR-2B and GSTR-3B
| Event | GSTR-2B effect | Control response |
|---|---|---|
| Accept filed invoice | Included in the relevant eligible population, subject to system rules. | Complete section 16 and section 17 review before claim. |
| Reject filed invoice | Excluded from eligible ITC treatment. | Tell supplier why; verify whether amendment or credit note is appropriate. |
| Mark invoice pending | Held outside GSTR-2B and GSTR-3B until resolved. | Record evidence gap, owner and deadline. |
| Take no action | Deemed accepted at generation. | Do not allow unattended records to bypass policy review. |
| Change action after draft | Draft becomes stale until recomputed. | Recompute and archive the version used for filing. |
| Supplier amends record | Original and amendment treatment depends on return periods and workflow. | Review the sequence; do not act on an amendment out of order when the portal prevents it. |
IMS is a data-governance layer, not a complete ITC engine. Internal books can still contain goods-receipt, blocked-credit, duplicate and business-purpose facts that the portal does not know.
A controlled IMS review workflow
- Assign portal access by role, keep maker and reviewer responsibilities separate, and retain action logs.
- Load the IMS population into a controlled work queue keyed by supplier GSTIN, document type, number, date and tax amount.
- Auto-recommend only high-confidence exact matches; require people to decide ambiguous, high-value or exception records.
- Accept only after the document belongs to the GSTIN and agrees with core commercial evidence. Acceptance is not the final legal-eligibility sign-off.
- Reject wrong-recipient, duplicate or materially incorrect documents with a precise reason that a supplier can act on.
- Use pending sparingly for unresolved receipt, disputed supply or missing evidence, and set an escalation date well before section 16(4) becomes relevant.
- Monitor supplier edits and action resets; re-open records automatically when the source changes.
- After the fourteenth-day draft, process late action changes, recompute GSTR-2B, and lock the exact statement used for GSTR-3B review.
Track queue ageing by reason, supplier and value. A large “pending” balance without owners merely moves risk out of the current statement. Review credit notes promptly because rejecting a valid reduction can create an overstated ITC position.
Exception states that deserve special attention
An upward amendment can require action only after the supplier files it. If original and amended records fall in different GSTR-2B periods, GSTN may require the recipient to act on the original and file its GSTR-3B before acting on the amendment. Preserve the sequence so the economic net amount is not counted twice.
Credit notes are another sensitive class. IMS does not necessarily know which original invoice a delinked credit note economically relates to. Before rejection, compare contracts, return records and supplier correspondence. The additional GSTN FAQ advises correction through invoice amendment when that is the correct mechanism rather than trying to repair a wrong invoice with an unrelated credit note.
Some records can be system-ineligible because of the section 16(4) time limit or place-of-supply logic and may flow directly to the relevant unavailable area instead of ordinary IMS action. Reverse-charge supplies also have distinct treatment. Design the work queue around documented portal categories, and never invent a manual action solely to make dashboard counts reconcile.
Agree the dashboard summary to the downloaded detail before approval. A count mismatch, stale recomputation or reset action can otherwise go unnoticed when reviewers look only at value totals. Preserve user, timestamp, previous state and new state for manual overrides so the team can reconstruct why a record changed.
Example: reviewing a mixed IMS queue
A consumer brand receives 160 IMS records before its August close. Exact matching clears 132 invoices. Of those, 124 pass the internal eligibility screen and are accepted. Eight are commercially valid but relate to blocked or apportioned use; the team records the correct GSTR-3B treatment rather than rejecting accurate supplier invoices.
Twelve records belong to another GSTIN and are rejected with supplier-specific correction requests. Six invoices are pending because warehouse receipt is disputed. Four credit notes match product returns and are accepted after AP posts them. The remaining six have no book record: two are duplicates, three were sent to the wrong legal entity, and one relates to a service received but not accrued.
After the draft GSTR-2B is generated, the warehouse resolves four pending invoices. The recipient changes those actions to accepted and uses the IMS recompute function. It retains the first draft, the changed-action report, the recomputed statement and reviewer approval. This sequence produces a traceable GSTR-2B population while keeping legal eligibility, blocked-credit and accounting decisions explicit.
Frequently asked questions
What happens if I take no action in IMS?
GSTN says a no-action record is deemed accepted at GSTR-2B generation. That is a portal outcome, not evidence that your team reviewed every eligibility condition.
Can an IMS action be changed?
Yes. The official FAQ says actions can be changed multiple times before the corresponding GSTR-3B is filed, with the latest action replacing the previous one.
What does pending do?
A pending record stays outside GSTR-2B and GSTR-3B until it is accepted or rejected, or until the applicable statutory timeline prevents further treatment. Give every pending item an owner.
When must GSTR-2B be recomputed?
The revised advisory says recomputation is mandatory when an action is changed or first taken after the draft GSTR-2B generation point. Follow the current portal prompt and archive the recomputed version.
Does rejecting an invoice automatically correct the supplier return?
No. Rejection communicates downstream treatment and becomes visible in the workflow, but the supplier may need to amend its source filing. Maintain follow-up until the actual record is corrected.
Are reverse-charge invoices handled like ordinary IMS invoices?
No. GSTN guidance identifies reverse-charge records as a special category rather than an ordinary recipient-action population. Determine liability, cash payment and credit separately under the law.
Does accepting a record mean ITC is legally eligible?
No. Acceptance confirms the recipient’s portal treatment of the supplier document. The business must still test receipt, business purpose, documentation, section 16 conditions, section 17 restrictions and return reporting.
Sources and further reading
- Goods and Services Tax Network: Revised Advisory on Invoice Management SystemVerified Jul 25, 2026
- Goods and Services Tax Network: FAQs on Invoice Management SystemVerified Jul 25, 2026
- Goods and Services Tax Network: Additional FAQ on IMS dated 17 October 2024Verified Jul 25, 2026
- India Code: CGST Act section 16: eligibility and conditions for ITCVerified Jul 25, 2026
- India Code: CGST Act section 17: apportionment and blocked creditsVerified Jul 25, 2026
Educational disclaimer: This material is general information, not legal, tax, or accounting advice. Check current official guidance and your facts with a qualified professional.
From definition to workflow
Apply this concept with connected finance operations
Finnoto connects source records, approvals, reconciliation evidence, and exception ownership so teams can move from knowing the rule to operating the control.
Explore GSTR-2B reconciliation