Step-by-Step Guide to Generating IRN and QR Codes via Invoice Registration Portals

1. Executive Summary & Legal Framework

Under the Indian Goods and Services Tax (GST) framework, e-Invoicing has transformed statutory compliance from traditional retrospective reporting into real-time transaction authentication. Managed by the Goods and Services Tax Network (GSTN) and executed through official Invoice Registration Portals (IRPs)—operated by the National Informatics Centre (NIC) and designated private GSPs (GST Suvidha Providers)—e-invoicing mandates that B2B and export invoices receive a unique legal identity prior to issuance.

This unique identity consists of two critical elements:

1. Invoice Reference Number (IRN): A 64-character cryptographic hash generated via the SHA-256 algorithm.

2. Digitally Signed QR Code: A machine-readable, high-density matrix containing core invoice parameters and a digital signature from the IRP, ensuring off-line verification and tampering prevention.

• Eliminating Tax Evasion: Eradicating duplicate invoices, ghost billings, and fraudulent Input Tax Credit (ITC) claims.

• Interoperability: Ensuring invoices generated on one accounting software (e.g., Tally, Zoho, SAP, Oracle) can be read natively by any other system.

• Automated GST Returns: Seamlessly populating GSTR-1 for suppliers and GSTR-2B for recipients directly from IRP data streams.

2. Applicability & Mandate Thresholds

The applicability of e-invoicing is governed by Notification No. 13/2020–Central Tax (and subsequent amendments), which systematically brought taxpayers under the IRP mandate based on Aggregate Annual Turnover (AATO).

Statutory Exemptions

Regardless of AATO turnover, specific sectors are explicitly exempted from generating IRN and QR codes under GST Rule 48(4):

• Insurers, Banking Companies, or Financial Institutions (including NBFCs).

• Goods Transport Agencies (GTA) supplying services in relation to transportation of goods by road.

• Suppliers of Passenger Transportation Services.

• Suppliers of services by way of admission to exhibition of cinematograph films in multiplex screens.

• Special Economic Zone (SEZ) Units (Note: SEZ Developers are NOT exempt and must generate IRNs).

• Government Departments and Local Authorities.

3. Anatomical Breakdown: What is an IRN and QR Code?

Understanding the Invoice Reference Number (IRN)

The IRN is a unique, 64-character hash value produced by applying the SHA-256 cryptographic algorithm to three specific transaction values:

Example IRN Output:

3a8f9c12b7d4e5f60a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f

Because the hash is calculated from these exact variables, any attempt to issue a second invoice with the same combination results in a duplicate error code (2190: Duplicate IRN) from the IRP system.

Anatomical Structure of the Signed QR Code

The Quick Response (QR) Code embedded on an e-invoice is not a standard web link; it is a high-density, Base64-encoded binary string signed digitally with the IRP’s private key. The QR code contains 10 mandatory data parameters:

Before attempting to generate an IRN, ensure the following prerequisites are complete:

1. Active GSTIN: The supplier and buyer GSTINs must be active on the GST Portal.

2. Enablement on e-Invoice Portal: Check enablement status on einvoice1.gst.gov.in. If your business crossed the ₹5 Cr threshold recently and remains un-enabled, manually request enablement via the portal by submitting financial proofs.

3. IRP Registration Credentials: Create dedicated user credentials on the e-Invoice Portal (separate from primary GST Portal credentials).

4. Mandatory Multi-Factor Authentication (MFA): MFA is required across all IRP and E-Way bill login processes.

5. Compliant ERP/Accounting System: ERP systems (SAP, Tally Prime, Zoho Books, Microsoft Dynamics) must support the official e-Invoice Schema (INV-01) format.

5. Step-by-Step Guide to Generating IRNs and QR Codes

6. Technical Architecture & Integration Methods

Businesses choose integration protocols based on transaction volume, operational complexity, and infrastructure capabilities.

7. Common Errors, Validation Rules & Remediation

When IRP systems reject a JSON payload during validation, specific error codes are returned. The table below lists common error codes, root causes, and resolution steps.

8. Post-Generation Workflows: Cancellation, Amendment & Reconciliation

Cancellation Protocol Rules

If an invoice is cancelled or contains incorrect data after IRN generation, strict statutory timeframes apply:

• No Direct Modifications on IRP: You cannot edit an IRN once generated. You must cancel it (within 24 hours) or issue a Credit/Debit note.

• GSTR-1 Integration: The IRP automatically pushes verified IRN details into the supplier’s GSTR-1 (Table 4 for B2B supplies) at midnight daily.

• GSTR-2B Auto-Reflections: The recipient views auto-populated credit data inside their GSTR-2A/2B for simplified ITC reconciliation.

9. Business Impact & Best Practices for Compliance

Implementing automated e-invoicing offers key strategic benefits:

1. Automate API Integration: Avoid manual bulk Excel generation if monthly invoice volume exceeds 100 transactions to eliminate human error.

2. Implement Sandbox Testing: Test all custom ERP schema modifications inside the official IRP Sandbox environment (sandbox.einvoice1.gst.gov.in) before pushing to production.

3. Automate Multi-Factor Authentication (MFA): Set up automated MFA key rotation or GSP API authentication to ensure uninterrupted batch processing.

4. Enforce Real-Time Validation: Use ERP validation scripts to check HSN length, PIN-state matching, and GSTIN status before making the payload call to IRP.