GST compliance in a restaurant used to mean printing a bill with the right tax lines and filing GSTR returns on time. E-invoicing adds a step: for the invoices it covers, you must register each one with the government’s Invoice Registration Portal (IRP) and print the returned reference number and QR code on the invoice. Miss it, and the invoice is not valid for input-tax credit on the buyer’s side — and you are exposed to penalties.
This guide walks through when e-invoicing applies to a restaurant, how it works mechanically, and a checklist you can hand to your accountant. It is general information, not tax advice; thresholds and rules change, so confirm the current position with your CA or the GST portal.
Does e-invoicing apply to my restaurant?
E-invoicing has been phased in by aggregate annual turnover, with the threshold coming down over successive notifications. It applies to B2B supplies — invoices issued to another registered business — and to exports. It does not apply to B2C bills issued to walk-in diners, which remain ordinary tax invoices (though larger businesses must print a dynamic QR code on B2C invoices too).
For a restaurant this means the invoices that typically need an IRN are corporate catering, banquet and event billing, bulk orders for offices, and any sale where the customer gives you a GSTIN. If your PAN-level turnover crosses the threshold in any financial year since GST began, e-invoicing applies from the next year onward.
How IRN generation works
- Your billing system builds the invoice in the prescribed JSON schema (supplier and buyer GSTIN, line items, HSN/SAC codes, tax breakup).
- The JSON is sent to the IRP, directly or through a GSP.
- The IRP validates it, generates a unique 64-character Invoice Reference Number (IRN), digitally signs the invoice, and returns a signed QR code.
- Your system prints the IRN and QR code on the invoice. The invoice data flows automatically into your GSTR-1 and, where applicable, the e-way bill system.
The IRN itself is a hash of your GSTIN, the financial year, the document type and the invoice number — which is why it can be computed offline by NIC’s published algorithm and why the invoice number must never be reused within a year.
Where restaurants get it wrong
- Cancelling after 24 hours. An IRN can only be cancelled within 24 hours of generation. After that you must issue a credit note.
- Editing a registered invoice. Once an IRN exists the invoice is frozen. Amend with debit or credit notes, not by editing.
- Wrong HSN/SAC. Restaurant services generally fall under SAC 9963; packaged goods sold alongside carry their own HSN. Mixing them up misstates tax.
- Duplicate invoice numbers across outlets. Each GSTIN needs a unique series; chains with one GSTIN and many outlets must coordinate numbering.
- Generating IRNs by hand on the portal. It works for five invoices a month; it does not work for a banquet business.
E-way bills: when a restaurant needs one
An e-way bill is required for the movement of goods above a value threshold. Restaurants meet it when moving stock between a central kitchen and outlets, delivering large catering orders, or transferring equipment. If your e-invoicing system is integrated, the e-way bill can be generated from the same data with the vehicle details added.
Compliance checklist
| Area | Check |
|---|---|
| Registration | GSTIN per state, e-invoice enablement on the portal, API credentials or GSP set up |
| Master data | Buyer GSTINs validated, SAC/HSN on every menu item and product, tax rates per item |
| Numbering | Unique, sequential invoice series per GSTIN and financial year |
| Generation | IRN and QR on every B2B invoice before it is handed over; cancellation only within 24 hours |
| Corrections | Credit/debit notes for changes; no editing of registered invoices |
| Returns | GSTR-1 auto-populated from IRP data reconciled with your books; GSTR-3B liability matched to actual collections |
| Aggregators | Swiggy/Zomato payouts reconciled against your sales so TCS and commission are accounted correctly |
| Records | Signed invoice JSON and QR retained for the statutory period; encrypted backups |
What good software does for you
The ideal is that none of this is a separate task. The bill you print at the counter is the tax invoice; if the customer is a business, the system generates the IRN in the background and prints the QR; the invoice lands in the books with the right ledger entries; GSTR-1 reconciles against the IRP data with one click; and aggregator payouts are matched against sales so your GSTR-3B does not overstate liability.
Restro Sarthi builds this in: GST tax invoices at the counter, IRN and e-way bill generation with the NIC offline signing algorithm (so B2B billing survives an outage), GSTR reconciliation, Schedule III statements and online-payout reconciliation — all inside the same platform that runs your POS. See the finance suite or book a demo with your accountant on the call.
