E-invoicing under the GST framework requires every registered business with aggregate annual turnover exceeding ₹5 crores to generate invoices through the Invoice Registration Portal obtaining an Invoice Reference Number and QR code for every B2B transaction, export supply, and government supply before the document is issued to the recipient. An invoice generated outside this process is not a valid tax invoice under the GST Act meaning the recipient cannot claim ITC on the purchase, the supplier is exposed to penalty proceedings, and the transaction creates a compliance gap in both parties’ records that the department’s reconciliation system identifies automatically.
E-way bill compliance adds a parallel logistics tracking obligation requiring a valid e-way bill for every movement of goods valued above ₹50,000, with validity periods tied to the distance of transportation and automatic integration with e-invoices for compliant businesses. At RVG India, e-invoicing and e-way bill engagements are structured around system integration, process automation, and compliance monitoring ensuring IRN generation, QR code embedding, and e-way bill creation are built into the business’s existing invoicing workflow rather than managed as separate manual processes that create volume related errors at scale.
The 30 day invoice reporting deadline applicable to businesses with turnover exceeding ₹10 crores adds a time sensitive dimension to the e-invoicing obligation that high-volume businesses frequently underestimate. Invoices not reported to the IRP within 30 days of the invoice date cannot be uploaded beyond that window meaning the IRN is permanently unavailable, the document remains non compliant, and the recipient’s ITC claim on that transaction is at risk. For businesses processing hundreds of B2B invoices monthly, the gap between a functioning IRP integration and a manual or partially automated process is measured not in administrative inconvenience but in the cumulative penalty and ITC denial exposure that accrues across every non-compliant invoice.
Where the API connection between the business's invoicing system and the Invoice Registration Portal fails due to configuration errors, credential issues, or system incompatibility IRN generation stops entirely. Every invoice raised during the outage is a non compliant document. High volume businesses processing dozens of invoices daily accumulate significant penalty exposure within hours of an undetected integration failure.
Businesses with turnover exceeding ₹10 crores cannot upload invoices to the IRP beyond 30 days from the invoice date. Invoices missed within this window cannot be retrospectively validated the IRN is permanently unavailable, the document remains non compliant, and the recipient's ITC claim is at risk. A batch processing failure or manual oversight affecting even one invoice period creates an irreversible compliance gap.
Where e-way bill details vehicle number, transporter ID, or goods value do not align with the corresponding e-invoice data, the e-way bill is technically defective. Goods intercepted in transit with a defective e-way bill are liable to detention, seizure, and penalty proceedings regardless of whether the underlying supply was fully compliant in every other respect.
Bulk invoice uploads to the IRP are rejected where individual invoices contain data errors incorrect GSTIN formats, invalid HSN codes, value mismatches, or duplicate invoice numbers. In high volume environments, rejection of a batch does not identify the specific error invoice requiring manual identification and correction across the entire upload before resubmission within the available reporting window.
Every B2B invoice issued without a valid IRN carries a penalty of ₹10,000 under Section 122 of the CGST Act. Beyond the direct penalty, the recipient cannot claim ITC on a non compliant invoice creating a downstream compliance impact on the buyer's tax position that affects the commercial relationship and, in B2B environments, the supplier's own credibility as a compliant trading partner.
E-invoicing is mandatory for registered businesses with aggregate annual turnover exceeding ₹5 crores in any financial year since 2017-18. The threshold is evaluated on a cumulative basis across all GSTINs under the same PAN meaning businesses that crossed ₹5 crores in any prior year remain within the e-invoicing obligation even if current year turnover is lower. Certain categories are exempt regardless of turnover including SEZ units, banks, insurance companies, and businesses making only B2C supplies.
E-invoicing applies to B2B supplies, exports, and supplies to government entities where the supplier is above the prescribed turnover threshold. It does not apply to B2C transactions, supplies by SEZ units, financial institutions, or certain notified categories. Within applicable transactions, every tax invoice, credit note, and debit note issued to a registered recipient requires IRN generation before the document is issued not after the transaction is completed.
Businesses with aggregate annual turnover exceeding ₹10 crores are required to report invoices to the IRP within 30 days of the invoice date. Invoices not reported within this window cannot be uploaded to the IRP after the deadline the IRN is permanently unavailable, the document remains non compliant, and the recipient cannot claim ITC on that transaction. Businesses between ₹5 crores and ₹10 crores currently have no prescribed reporting deadline but are expected to generate IRNs at the time of invoice issuance.
An invoice issued without a valid IRN is not a valid tax invoice under the GST framework for businesses above the e-invoicing threshold. The recipient cannot claim ITC on the transaction. The supplier is liable to a penalty of ₹10,000 per non compliant invoice under Section 122 of the CGST Act. Where the volume of non compliant invoices is significant, the aggregate penalty exposure and ITC denial impact on recipients can constitute a material compliance failure affecting both parties' tax positions.
Where an e-invoice is generated for a transaction involving goods movement above ₹50,000, the IRP auto populates Part A of the e-way bill from the authenticated invoice data. The transporter is then required to update Part B with vehicle details before the goods movement commences. This integration eliminates data entry duplication between the invoice and e-way bill but only functions correctly where the e-invoice data is complete and accurately reflects the goods value, HSN classification, and recipient details without errors that prevent auto population.
We assess the business's existing invoicing infrastructure ERP system, accounting software, transaction volume, and GSTIN structure and implement the IRP API integration within the existing workflow. For Tally, Zoho, SAP, and other standard platforms, integration is configured to generate IRNs and embed QR codes automatically at the point of invoice creation. For businesses using custom or legacy systems, we evaluate the most appropriate integration approach direct API, GSP connectivity, or bulk upload framework based on the system's technical capability and the business's transaction volume.