E-Invoicing and the IRN, Explained
Author : purchase pro | Published On : 30 Sep 2026
E-invoicing is often misunderstood as a new way of creating invoices.
It is not.
You continue creating invoices through your existing ERP or billing software. The additional step is reporting the invoice to the government's Invoice Registration Portal (IRP), where it is validated and assigned an Invoice Reference Number (IRN) along with a QR code and digital signature.
For finance and procurement teams, however, e-invoicing is not only a supplier-side compliance requirement.
Your supplier's e-invoice compliance can directly affect your input tax credit.
If an applicable supplier sends an invoice without a valid IRN, the buyer can face ITC consequences.
This guide explains how e-invoicing works, who must comply, the 30-day reporting requirement, and the buyer-side controls finance teams should build into their AP workflow.
What Is E-Invoicing?
E-invoicing does not mean creating your invoice directly on the GST portal.
Your business can continue creating invoices in its own ERP, accounting system or billing software.
The difference is that applicable invoices need to be reported to the Invoice Registration Portal.
The IRP validates the invoice and returns:
-
Invoice Reference Number (IRN)
-
QR code
-
Digital signature
The invoice then has the required e-invoice validation under the process described in the article.
Simple e-invoice workflow
Create Invoice in ERP
↓
Report Invoice to IRP
↓
IRP Validates Data
↓
IRN Generated
↓
QR Code + Digital Signature
↓
Invoice Becomes Valid Under the E-Invoice Process
What Is an IRN?
An IRN, or Invoice Reference Number, is a unique identifier generated for an applicable invoice through the Invoice Registration Portal.
According to the source article, the IRN is a 64-character hash generated using four inputs:
-
Supplier GSTIN
-
Financial year
-
Document type
-
Document number
This makes the invoice uniquely identifiable within the GST system.
The validated invoice data is also pushed to relevant downstream systems, including the seller's GSTR-1 and the e-way bill portal where applicable.
Why Is an IRN Important?
An invoice issued without a valid IRN is not treated as a valid tax invoice under the rule described in the source.
The source article states that such an invoice:
-
Cannot be relied on for ITC
-
Can create issues when goods are in transit
-
Exposes the customer as well as the supplier
This makes IRN verification relevant not only for the seller but also for the buyer receiving the invoice.
For AP teams, the practical control is simple:
Check the IRN and QR code before booking the invoice.
Who Must Comply With E-Invoicing?
The source article describes the FY 2025-26 applicability based on Aggregate Annual Turnover (AATO).
|
AATO |
Applicability |
|
More than ₹5 crore in any FY since 2017-18 |
E-invoicing applies to B2B, exports, supplies to government, credit notes and debit notes |
|
₹10 crore or more |
Above requirements plus the 30-day reporting window |
|
₹5 crore or below |
Not currently required according to the source; voluntary enablement possible |
Important AATO Detail
The turnover test is based on the PAN level, not individual GSTINs.
That means branches and GST registrations under the same PAN are aggregated for the applicability test described in the article.
Another important point is that the test considers any financial year since 2017-18.
The source states that once the ₹5 crore threshold is crossed in any applicable year, the obligation continues even if turnover later falls below that level.
Who Is Exempt From E-Invoicing?
The source lists certain sectors that remain exempt regardless of turnover, including:
-
Banks
-
NBFCs
-
Insurers
-
Goods Transport Agencies
-
Passenger transport
-
Multiplex/cinema admissions
-
SEZ Units
The article recommends checking the applicable exemption position and using the e-invoice exemption declaration on the GST portal where relevant.
Important:
Don't assume your business is or isn't enabled.
The source recommends using the “Check Enablement Status” facility on the IRP portal by entering the GSTIN.
The 30-Day E-Invoice Reporting Rule
One of the most important changes highlighted in the article is the 30-day reporting requirement.
From 1 April 2025, businesses with AATO of ₹10 crore or more must report applicable invoices, credit notes and debit notes to the IRP within 30 days from the document date, according to the supplied source.
If an applicable document is uploaded after the 30-day window:
IRP rejects the document.
No IRN is generated.
And the invoice is treated as invalid under the GST process described in the article.
What Happens If the 30-Day Window Is Missed?
The source identifies two major consequences.
1. The Original Invoice Cannot Simply Be Backdated
The article states that the supplier cannot simply report the old invoice after the deadline.
The stated fix is to issue a fresh invoice with:
-
A new document number
-
Current date
-
Reporting within the applicable window
2. The Customer Cannot Claim ITC Against the Original
From the buyer's perspective, the original invoice does not provide the required basis for the ITC claim described in the article.
This is why the 30-day rule is not only a seller-side compliance issue.
It can become a customer-side finance issue too.
The 24-Hour Cancellation Window
There is another important timing rule.
Once an IRN has been generated, the source states that the cancellation window is 24 hours.
After that, cancellation needs to be handled through a credit note.
This means invoice creation and validation need to be handled carefully.
A finance team shouldn't assume that an invoice can simply be cancelled whenever an error is discovered.
Why E-Invoicing Matters to Buyers
Most e-invoicing explanations focus on the supplier.
But buyers have a direct financial interest in the supplier getting it right.
If an applicable supplier sends an invoice without a valid IRN, the source identifies three buyer-side consequences:
-
The invoice cannot support ITC.
-
It does not flow into GSTR-2B as expected.
-
Late reporting can delay the credit or require reissue if the reporting window is missed.
So the relationship is:
Supplier E-Invoice Compliance
↓
Valid IRN
↓
Valid Invoice
↓
GSTR-2B Visibility
↓
ITC Control
This makes e-invoice verification an important part of the AP process.
3 Buyer-Side Controls Finance Teams Should Implement
1. Verify IRN and QR Before Booking
The source recommends checking the IRN and QR code on the invoice PDF before booking it.
This allows the AP team to identify the problem at invoice receipt rather than during an audit or later reconciliation.
Recommended workflow:
Invoice Received
→
Check IRN
→
Check QR
→
Validate Supplier
→
Book Invoice
2. Monitor GSTR-2B Before Finalising ITC
The article recommends controlling payment and ITC around the invoice's reflection in GSTR-2B, while also considering applicable payment timelines.
This creates a stronger connection between:
Invoice Verification → GSTR-2B → ITC Control
3. Capture E-Invoice Applicability During Vendor Onboarding
Don't wait until the first invoice arrives.
The source recommends tagging suppliers as:
-
E-invoicing in-scope
-
E-invoicing out-of-scope
during vendor onboarding.
Then every invoice from an in-scope supplier can automatically go through the IRN verification workflow.
Common E-Invoicing Mistakes
Mistake 1: Looking Only at Current-Year Turnover
The applicability test described in the source looks at any financial year since 2017-18, not simply the current year's turnover.
Mistake 2: Checking GSTIN-Level Turnover
AATO is calculated at the PAN level.
For example, multiple GST registrations under the same PAN need to be considered together for the applicability test.
Mistake 3: Accepting an Invoice Without an IRN
An applicable supplier's invoice without a valid IRN can create an immediate ITC problem for the buyer.
The article recommends catching this at invoice receipt rather than waiting for quarter-end.
Mistake 4: Missing the 30-Day Reporting Window
For businesses covered by the 30-day requirement, late reporting can result in IRP rejection and require the invoice to be reissued according to the process described in the article.
Mistake 5: Trying to Cancel After 24 Hours
The source states that after the 24-hour cancellation window, the correction needs to flow through a credit note.
Mistake 6: Applying E-Invoicing to B2C
The source states that B2C invoices are not e-invoiced and identifies B2B, exports, supplies to government, credit notes and debit notes as the relevant categories described in the article.
E-Invoice Compliance Checklist
The source's checklist provides a useful AP control framework.
|
Control |
What Good Looks Like |
|
Own applicability |
Check enablement status on the IRP portal |
|
30-day flag |
Applicable outbound documents flagged for reporting within 30 days |
|
Vendor master flag |
Suppliers tagged as in-scope/out-of-scope |
|
IRN verification |
Inbound invoices checked for IRN and QR |
|
Hold on missing IRN |
Booking/payment workflow flags missing IRN |
|
24-hour cancellation watch |
Corrections caught within the cancellation window |
|
Document type coverage |
Invoices, credit notes and debit notes covered |
|
Exempt-supply tagging |
B2C and exempt categories correctly identified |
The later pages of the source expand these controls, including vendor-master tagging, IRN verification on receipt, missing-IRN holds and 24-hour cancellation monitoring.
How to Build E-Invoice Verification Into AP
A practical workflow can look like this:
Step 1: Identify Supplier Applicability
Check whether the supplier is subject to e-invoicing.
Step 2: Receive the Invoice
Capture the invoice in the AP workflow.
Step 3: Verify IRN
Check the IRN and QR code.
Step 4: Validate Invoice Details
Ensure the invoice information matches the transaction and supplier details.
Step 5: Book the Invoice
Only proceed once the applicable checks are complete.
Step 6: Monitor GSTR-2B
Check whether the invoice flows into the buyer's GST records as expected.
Step 7: Resolve Exceptions
If IRN, invoice or GSTR-2B information is missing or incorrect, notify the supplier and resolve it before the issue reaches the audit stage.
E-Invoicing Software: Why Automation Matters
For businesses processing large numbers of supplier invoices, manually checking every IRN and QR can become difficult.
An e-invoicing software workflow can help bring these controls into the AP process.
The objective is not simply to generate invoices.
A mature workflow should help teams manage:
-
Supplier applicability
-
IRN verification
-
QR verification
-
Invoice booking controls
-
Missing-IRN exceptions
-
GSTR-2B visibility
-
Vendor onboarding
-
30-day reporting alerts
-
24-hour cancellation monitoring
-
Credit-note workflows
This turns e-invoice compliance from a periodic audit exercise into an every-invoice control.
How PurchasePro Fits Into the AP Compliance Workflow
For PurchasePro's positioning, this article should connect e-invoicing with the broader procurement → AP → GST compliance workflow rather than presenting e-invoicing as an isolated feature.
The core workflow can be presented as:
Vendor Onboarding
↓
E-Invoice Applicability
↓
Invoice Received
↓
IRN + QR Verification
↓
Invoice Booking
↓
↓
ITC Control
This fits the article's central buyer-side message: supplier compliance can directly affect the buyer's ITC position.
Suggested PurchasePro CTA
Bring e-invoice checks into your AP workflow.
Book a PurchasePro Demo
Internal link: PurchasePro GST / AP compliance page — verify the live URL before publishing.
Why E-Invoice Controls Should Start at Vendor Onboarding
Vendor onboarding is often treated as a master-data exercise.
But the article suggests using it as an e-invoice compliance control point.
Each supplier can be tagged according to whether e-invoicing applies to them.
Then the AP workflow can automatically determine whether an incoming invoice needs IRN verification.
This creates a simple control:
Supplier Master → E-Invoice Flag → Invoice Receipt → IRN Verification
Instead of discovering supplier compliance issues after an invoice has already entered the books.
E-Invoice Compliance Checklist for Finance Teams
Before closing the AP cycle, check:
-
Is our own e-invoice applicability confirmed?
-
Is the GSTIN's enablement status checked?
-
Are applicable suppliers tagged?
-
Is IRN verified on incoming invoices?
-
Is the QR code checked?
-
Are invoices without valid IRNs flagged?
-
Are applicable outbound invoices monitored for the 30-day deadline?
-
Is the 24-hour cancellation window monitored?
-
Are credit notes and debit notes covered?
-
Are B2C and exempt transactions correctly identified?
-
Is GSTR-2B monitored for relevant ITC?
-
Are supplier exceptions followed up?
Closing Thoughts
E-invoicing started as a seller-side reporting requirement.
But for finance and procurement teams, its impact extends into the buyer's AP and ITC workflow.
The source article's central message is that supplier e-invoice discipline can determine whether the buyer's ITC stands up to scrutiny. This makes vendor onboarding and inbound invoice verification important finance controls.
The practical approach is:
Check applicability.
Verify the IRN.
Check the QR.
Monitor the reporting window.
Track GSTR-2B.
Resolve exceptions early.
As the source notes, e-invoicing thresholds have been reduced progressively, while reporting windows have also become shorter.
For AP teams, building these controls into everyday invoice processing is more sustainable than trying to identify problems during an audit.
FAQs
1. What is e-invoicing?
E-invoicing is the process of reporting applicable invoices to the Invoice Registration Portal so that they can be validated and assigned an Invoice Reference Number, QR code and digital signature. It does not mean creating the invoice directly on the GST portal.
2. What is an IRN?
IRN stands for Invoice Reference Number. The source describes it as a 64-character hash generated using the supplier GSTIN, financial year, document type and document number.
3. Why is an IRN important?
The source states that an invoice issued without a valid IRN cannot be relied on for ITC and can create consequences for goods in transit and the buyer.
4. Who must generate an e-invoice?
The supplied article describes e-invoicing applicability for businesses crossing the applicable AATO threshold, with the article's FY 2025-26 table identifying more than ₹5 crore in any FY since 2017-18 as the relevant threshold described there.
5. What is the 30-day e-invoice rule?
According to the source, from 1 April 2025, businesses with AATO of ₹10 crore or more must report applicable invoices, credit notes and debit notes to the IRP within 30 days of the document date.
