Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
The promise of e-invoicing was a single source of truth: an IRN generated at the IRP propagates to the supplier’s GSTR-1 and the buyer’s GSTR-2B without manual data entry. The reality for finance teams managing e-invoice reconciliation in India is more complicated. Auto-population does not mean auto-reconciliation, and the introduction of 6 private IRP portals alongside the government IRP has created a multi-source IRN environment that requires its own tracking layer.
How E-Invoice Data Flows in India
When a supplier generates an e-invoice, the process is:
- Invoice JSON uploaded to an IRP (government portal or one of 6 private IRPs: Cygnet, Clear, IRIS, EY, Deloitte, or Masters India).
- IRP validates the data, generates a unique IRN (64-character hash), and embeds a QR code.
- The validated invoice is pushed to the GST portal at https://www.gst.gov.in, which auto-populates the supplier’s GSTR-1 and the buyer’s GSTR-2B.
- GSTR-2B is generated on the 14th of each month as a static, locked document reflecting all e-invoices and manual GSTR-1 entries filed by the supplier’s cut-off date.
For buyers, the GSTR-2B reconciliation guide explains how to use GSTR-2B as the basis for ITC claims under Rule 36(4). E-invoice data feeds directly into this document — making IRN-level reconciliation a prerequisite for ITC accuracy.
E-Invoice Reconciliation Checkpoints
| Checkpoint | Data Source | Match Key | Common Error |
|---|---|---|---|
| IRN generation vs ERP invoice | IRP API / ERP | Invoice number + supplier GSTIN | ERP invoice raised but IRN not generated (system failure) |
| GSTR-1 auto-population vs IRN | Supplier GSTR-1 + IRP records | IRN + invoice date | Cancelled IRN still showing in GSTR-1 after 24-hour window lapse |
| GSTR-2B vs purchase register | GSTR-2B + accounts payable | Supplier GSTIN + invoice number | Invoice received but supplier filed late; appears in next month’s GSTR-2B |
| Credit/debit note vs original IRN | ERP + GSTR-2B | Original IRN reference | Credit note raised but not linked to original IRN in supplier’s GSTR-1 |
| Multi-IRP consolidation | All IRP portals used | IRN (unique across all IRPs) | Same invoice processed on two IRPs due to ERP integration error; duplicate IRN not possible but reconciliation gaps occur |
New Mismatch Types Introduced by E-Invoicing
Cancelled IRNs in GSTR-2B. An IRN can be cancelled within 24 hours through the IRP. After that window, cancellation requires a credit note. When the credit note is processed in a later month, the buyer’s GSTR-2B for the original month still shows the original invoice. Finance teams must track open IRN cancellations separately and ensure the corresponding credit note appears in GSTR-2B before claiming net ITC.
Multi-IRP environments. Companies using Tally, SAP, or Zoho integrations may route invoices through different private IRPs. Each IRP generates a valid IRN. A buyer receiving invoices from suppliers using multiple IRPs must consolidate IRN data from all portals during GSTR-1 vs GSTR-3B reconciliation checks, since the GST portal aggregates all IRNs regardless of originating IRP.
B2C and exempted supplies. E-invoicing does not cover B2C transactions (consumers), exempt supplies, or supplies from composition taxpayers. These still require manual reconciliation. A company with mixed B2B and B2C supply chains must maintain two parallel reconciliation tracks.
Amendment handling. Since an e-invoice cannot be amended post-IRN, all corrections flow through credit or debit notes. If a supplier amends an invoice value after e-invoice generation, the original GSTR-2B entry persists and a new credit/debit note entry appears in the subsequent GSTR-2B. For buyers, this creates a multi-row reconciliation for a single underlying transaction.
Structured reconciliation software India handles IRN-level matching by treating each IRN as a unique transaction identifier, flagging cancelled IRNs without corresponding credit notes, and aggregating multi-IRP sources into a single matching workspace.
GSTR-9 Implications for E-Invoice Data
E-invoice data flows into the GSTR-9 annual return reconciliation through the aggregated GSTR-1 and GSTR-2B figures. Any IRN-level mismatches not resolved during the monthly cycle carry forward into the annual return as unexplained differences in Table 4 (outward supplies) or Table 6/7 (ITC claimed vs available).
For the annual reconciliation to close cleanly, every cancelled IRN must have a corresponding credit note in GSTR-2B, and every debit note must reference a valid original IRN. Finance teams using purpose-built GST reconciliation software can flag open IRN exceptions as a month-close checklist item rather than discovering them during GSTR-9 preparation in December.
Practical Steps for E-Invoice Reconciliation
Each month, the e-invoice reconciliation workstream should cover:
- Pull IRN register from all IRP portals used by your suppliers.
- Match IRNs against your purchase register on invoice number, date, and GSTIN.
- Identify IRNs marked cancelled at IRP — verify corresponding credit notes in GSTR-2B.
- Confirm GSTR-2B entries for the month reconcile to the IRN register net of cancellations.
- Flag invoices in the purchase register with no corresponding IRN (supplier may have missed e-invoice generation — a compliance risk for the supplier that can affect ITC eligibility).