Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Supplier-side GSTR-1 amendments under Type 9 and Type 9A surface in the buyer's IMS as new actionable entries with references to original invoices. Buyers who accepted the original must re-act on the amendment, and buyers who rejected the original face the ghost-invoice risk where the amendment can deemed-Accept past 30 days. Without a structured amendment workflow, ITC integrity breaks at scale.
An amendment-aware workflow tracks original-amendment pairs by reference, presents both versions to the buyer with the action delta clearly marked, applies the same purchase-register match logic to the amended version, and inherits or rolls back the original action based on buyer decision. Section 16(4) time limit alerts surface for prior-period amendments approaching the deadline.
Amendment-pair tracking on supplier GSTIN plus original invoice number plus amendment reference, action-delta presentation, inheritance rules from original to amendment, Section 16(4) deadline alerts per invoice, and re-action SLA aligned to the 30-day deemed-Accept clock.
Amendment-cycle decision log with original-versus-amended action history, post-amendment GSTR-2B reflecting the buyer's latest decisions, Section 16(4) time-limit dashboard for pending amendment items, and audit trail capturing both original and amended decision timestamps.
A supplier discovers in June that an invoice they filed in April had a wrong tax rate. They file a Type 9A amendment in their June GSTR-1, correcting the prior-period entry. The buyer had Accepted the original April invoice and claimed ITC on it. The amendment now appears in the buyer’s June IMS as an amended entry. The buyer must re-act: Accept the amendment (rolling back the original Accept and applying the corrected amount), Reject the amendment (keeping the original), or mark Pending. This is the amendment cycle reconciliation problem — and without a structured workflow, finance teams accumulate ghost invoices, orphaned ITC, and Section 16(4) time-limit exposures.
Two Amendment Types Under GSTR-1
The GST portal supports two B2B amendment types in GSTR-1:
Type 9 — Current Period Amendment. Supplier corrects an invoice within the same monthly cycle. Used when the supplier discovers an error before filing the current GSTR-1, or when amending an already-filed current-period invoice. Typically same-month corrections.
Type 9A — Prior Period Amendment. Supplier corrects an invoice from an earlier tax period. Used when a discrepancy is discovered after the original GSTR-1 was filed and the next period has begun. Subject to the Section 16(4) time limit — generally amendments are allowed until November 30 of the following financial year or the annual return filing, whichever is earlier.
Both types flow into the buyer’s current-period IMS dashboard as amended entries with a reference to the original invoice.
How Amendments Surface in the Buyer’s IMS
When a supplier files a Type 9 or Type 9A amendment, the GST portal:
- Creates a new entry in the supplier’s GSTR-1 for the current period.
- Marks the entry as an amendment with a reference to the original invoice’s GSTIN plus invoice number plus original period.
- Populates this as a new actionable line in the buyer’s IMS dashboard.
- Leaves the buyer’s prior IMS action on the original invoice intact for that period’s GSTR-2B.
The buyer now has both versions in view: the original (already actioned, contributing to a prior GSTR-2B) and the amendment (newly actionable, contributing to the current GSTR-2B once decided).
The Four Amendment Scenarios
| Original Action | Amendment Action | Net Effect on GSTR-2B |
|---|---|---|
| Accept | Accept amendment | Original supersededby amendment; ITC adjusts to amended amount |
| Accept | Reject amendment | Original Accept stands; amendment ignored |
| Accept | Pending amendment | Original Accept stands until amendment is decided or deemed-Accepted at day 31 |
| Reject | Accept amendment | Original Reject overridden by amended Accept; ITC available on amended amount |
| Reject | Reject amendment | Original Reject stands; amendment also Rejected |
| Reject | Pending amendment | Ghost invoice risk — amendment can deemed-Accept past 30 days against buyer’s original Reject intent |
The Reject-then-Pending case is the principal source of ghost invoices. A buyer who Rejected an original invoice and then ignores the amendment can find the amended invoice deemed-Accepted into GSTR-2B 30 days later — flowing ITC the buyer never intended to claim.
The Time-Lag Mechanic
Amendments surface in the buyer’s IMS within 24 hours of supplier filing. The 30-day deemed-Accept clock starts at IMS surfacing, not at supplier filing. This means:
- A Type 9 amendment filed on June 5 surfaces in IMS by June 6 and has its deemed-Accept threshold on July 6.
- A Type 9A amendment for an April invoice, filed in June, surfaces in IMS in June and has the same June-based 30-day clock.
The amendment’s IMS clock is independent of the original invoice’s tax period. This is consistent with how GSTR-2B incorporates amendments — they flow into the GSTR-2B of the period in which the amendment is filed, not the original period.
Credit Notes Versus Amendments
Credit notes under Section 34 of the CGST Act are a different mechanism. A credit note is a separate document the supplier issues to reduce the tax liability of a previously-filed invoice. It is filed in the supplier’s GSTR-1 as a credit-note entry, not as an amendment.
Credit notes also surface in the buyer’s IMS for action. The buyer Accept on a credit note triggers an ITC reversal under Rule 53 of the CGST Rules — the ITC originally claimed is reversed by the credit note amount.
| Mechanism | Use Case | IMS Treatment |
|---|---|---|
| Type 9 / 9A amendment | Correct invoice details (amount, GSTIN, period) | Replaces or modifies the original |
| Credit note (Section 34) | Reduce the invoice amount (sales returns, discounts, errors) | Separate IMS entry; Accept triggers ITC reversal |
| Debit note (Section 34) | Increase the invoice amount (additional charges, tax differences) | Separate IMS entry; Accept triggers additional ITC |
For the credit-note specifics, see credit note reconciliation under GST. The amendment cycle workflow runs in parallel with the credit-note workflow — the same IMS dashboard surfaces both.
The Ghost Invoice Problem in Detail
A ghost invoice is an amendment that flows into GSTR-2B without explicit buyer action, against the buyer’s stated intent on the original.
The mechanic:
- Supplier files original invoice in April.
- Buyer Rejects the original in April IMS (e.g., wrong GSTIN, fictitious goods).
- Supplier files Type 9A amendment in May, correcting the “error” the buyer flagged.
- Amendment surfaces in buyer’s May IMS.
- Buyer’s AP team, focused on May invoices, doesn’t notice the amendment is for a previously-Rejected April invoice.
- Amendment sits in May IMS with no action. Day 31 hits, deemed-Accept fires.
- ITC on the amended invoice flows into June’s GSTR-2B and becomes available for ITC claim.
The buyer has now claimed ITC against an invoice they originally Rejected. The audit trail will show Reject in April and Accept-by-default in May — a contradiction the buyer cannot easily explain.
Disciplined amendment-cycle workflows surface amendments against previously-Rejected originals as high-priority queue items with day-15 alerts, not day-25.
Worked Example: Manufacturer With 1,800 Invoices and 90 Amendments
A manufacturer running 1,800 monthly inward invoices typically sees 90 to 120 amendment entries per month — roughly 5 to 7 percent of volume. Distribution:
- 65 Type 9 same-period amendments (mostly amount corrections, GSTIN typos).
- 45 Type 9A prior-period amendments (issues discovered in audit or reconciliation).
- 18 of the 110 amendments reference previously-Rejected originals (the high-priority subset).
Decision distribution after re-action:
- 78 amendments Accepted (corrections were valid and buyer agrees).
- 22 amendments Rejected (buyer disputes the amendment or amended values still incorrect).
- 10 amendments Pending (vendor follow-up needed).
The 18 amendments against previously-Rejected originals require explicit buyer review — none should default to deemed-Accept. Of these, the typical pattern is 4 to 6 Accept (vendor corrected the original error), 10 to 12 Reject (vendor’s correction is itself wrong), and 1 to 3 Pending for further investigation.
Section 16(4) Time Limit Interaction
Section 16(4) of the CGST Act sets the deadline for ITC claim: generally November 30 of the following financial year or the annual return filing date, whichever is earlier. Amendments do not extend this deadline.
A Type 9A amendment for a FY 2024-25 invoice can be filed by the supplier as late as their FY 2025-26 cut-off. But the buyer’s ITC claim must still fit within FY 2024-25’s Section 16(4) window. If the amendment surfaces in October 2026 for a FY 2024-25 invoice, the November 30, 2025 deadline has already passed — the resulting ITC is unclaimable regardless of the amendment.
Amendment-aware workflows expose Section 16(4) deadlines per invoice. Items approaching the deadline flag for priority review.
Recurring Review Discipline
Amendment-cycle reconciliation is not a one-off event. It is a recurring monthly discipline overlaid on the regular IMS workflow. Each monthly IMS pull should:
- Separate fresh invoices from amendment entries.
- Map each amendment to its original (by supplier GSTIN plus original invoice number plus original period).
- Surface the four-scenario matrix per amendment with clear action delta.
- Apply Section 16(4) deadline alerts on prior-period amendments.
- Capture re-action timestamps in the audit trail alongside the original action timestamps.
A purpose-built GST reconciliation software handles this as a native capability. Manual workflows on spreadsheets typically lose track of original-amendment pairings within two to three monthly cycles. For multi-process integration, where amendment-cycle reconciliation sits alongside TDS, bank, and platform-settlement processes, a unified reconciliation software India maintains the audit trail across processes that share supplier master data.
For the foundational IMS workflow that the amendment cycle layers on top of, see IMS vs GSTR-2B reconciliation and the GSTR-2B reconciliation guide.