e-Invoicing under GST is not a PDF format — it is a registration step. For businesses above the notified turnover threshold, every B2B invoice, credit note and debit note must be reported to a government Invoice Registration Portal (IRP), which validates it, assigns an Invoice Reference Number (IRN) and returns a digitally signed QR code. Until that happens, the document is not a valid tax invoice. The practical consequence: e-invoicing cannot be a month-end activity. It has to happen at the moment of invoicing, wherever invoicing happens — the billing desk, the warehouse, or the back of a van.
What the mandate actually requires
- Who. Registered businesses whose aggregate annual turnover crosses the notified threshold (₹5 crore since August 2023) must register B2B invoices, credit/debit notes and export invoices on an IRP. B2C invoices are outside the mandate.
- What. The invoice is reported as a structured JSON in the notified schema — line items, HSN codes, GSTINs, tax breakup — not as a document image. Validation failures are rejected at the portal, which means data quality problems surface one invoice at a time.
- What comes back. The IRP returns the IRN (a hash that makes the invoice unique nationwide) and a signed QR code that must appear on the printed or shared invoice.
- Timelines. Larger taxpayers must report invoices to the IRP within a limited window of the invoice date, so late batch uploads are not a safe habit for anyone.
- Cancellation. An e-invoice can be cancelled on the IRP only within 24 hours, and only in full. After that, the correction route is a credit note — which itself must be registered.
- Downstream. IRN-registered invoices auto-populate GSTR-1, so what you report to the IRP is what the return will say. Divergence between the two is exactly what notices are made of.
Why bolted-on e-invoicing keeps breaking
Most e-invoicing failures are not portal failures — they are process failures. Invoicing happens in one system, e-invoice registration in another (a portal screen, a spreadsheet upload, a standalone utility), and the gap between them is bridged by a person. Invoices go out before the IRN exists. Cancellations happen in the billing system but never reach the IRP, or on the IRP but never reach the books. A field sale is written up hours after the goods changed hands. Each gap is invisible on the day and expensive in the return.
How xMatix runs e-invoicing
In xMatix, e-invoicing is a property of the invoice itself, not a separate job. The finance core and order-to-cash flow produce GST-correct invoices — GSTIN-validated parties, HSN-coded lines, place-of-supply logic — and registration with the IRP happens as part of the invoicing flow. The IRN and signed QR code land back on the invoice record, print on the document, and stay attached for audit.
Credit and debit notes follow the same path, so the cancellation-window problem becomes a workflow rather than a memory test: within the window, cancel on the IRP and in the books together; outside it, the system routes the correction through a registered credit note.
Because invoices auto-populate GSTR-1 from the same ledger that registered them, the filing grids reconcile against what the IRP already knows — the return is a checklist, not an investigation.
e-Invoicing where there is no desk
The hardest e-invoices are the ones raised in the field. In van sales, the invoice is created at the outlet — often offline. xMatix captures the invoice on the offline-first mobile app, queues it durably, and completes IRP registration when connectivity returns, within the reporting window. The engineering behind that is described honestly in e-Invoice from a moving van.
Common questions
Who is required to generate e-invoices under GST?
Registered businesses whose aggregate annual turnover has crossed the notified threshold — ₹5 crore since August 2023 — must register their B2B invoices, credit/debit notes and export invoices on an Invoice Registration Portal. Once the threshold is crossed, the obligation applies from the notified date onward and does not lapse if turnover later falls.
What is an IRN and why does it matter?
The Invoice Reference Number is a unique hash assigned by the Invoice Registration Portal when it accepts an invoice. For a mandated business, a B2B invoice without an IRN is not a valid tax invoice — the buyer's input tax credit and your own GSTR-1 both depend on it. The IRP also returns a signed QR code that must appear on the invoice document.
Can an e-invoice be cancelled or corrected?
Cancellation on the IRP is allowed only within 24 hours, and only for the whole invoice. After the window closes, corrections travel through a credit or debit note, which must itself be registered. xMatix treats both paths as one workflow, so the books, the IRP and the printed documents stay in agreement.
How does xMatix handle e-invoicing for van sales and field billing?
Invoices raised at the outlet are captured on the offline-first mobile app and queued durably on the device. When connectivity returns, the platform completes IRP registration and attaches the IRN and QR code to the invoice record — the field team sells where the network is weakest without the business falling out of compliance.
Does e-invoicing change how GSTR-1 is filed?
Yes, in your favour — IRP-registered invoices auto-populate GSTR-1. Because xMatix registers invoices from the same ledger the returns are prepared from, the GSTR-1 grid reconciles against what the portal already holds instead of being rebuilt from spreadsheets at month-end.