e-Invoice software for GST (IRN & QR)
Generate GST e-invoices with IRN and QR — offline JSON out of the box, and live IRN through your GST Suvidha Provider — on a real billing app.
Live product UI — sample data.
IRN & QR ready
Every eligible invoice is prepared for IRN and QR in the government schema.
Offline JSON, live optional
e-invoice JSON is generated offline; connect your GSP for live IRN generation.
On real billing
e-invoicing sits on a full GST billing app with returns and a posted ledger.
What this actually means in practice
An e-invoice is not a different invoice; it is your invoice registered. You raise it as usual, LekhaPro maps it to the NIC schema, and the JSON goes to the Invoice Registration Portal. The IRP returns an Invoice Reference Number — a hash computed from your GSTIN, the financial year, the document type and the document number. Because those four fields are the input, one document number can never be registered twice within a year.
What comes back matters as much as what goes out. LekhaPro stores the IRN, the acknowledgement number and date, and the signed QR code against the invoice, so the printed copy carries a QR that a field officer can scan and verify against the government's own signature. An invoice without that QR is not an e-invoice, however correct its arithmetic — which is why registration belongs inside billing rather than in a separate upload chore.
Correction is where most people trip. A registered IRN can only be cancelled within the window the portal allows, and cancellation is whole-document — you cannot edit a line. After that window the only route is a credit or debit note, which registers as its own e-invoice. LekhaPro reflects exactly this: cancel with a reason code while it is permitted, raise a note afterwards, and let both flow into GSTR-1, which the IRP auto-populates from what was registered.
| What the IRP returns | What LekhaPro does with it |
|---|---|
| IRN — a hash of GSTIN, financial year, document type and document number | Stored on the invoice; the same number cannot be registered again that year |
| Acknowledgement number and acknowledgement date | Kept against the invoice as the registration receipt for your records |
| Signed QR code | Printed on the invoice so the copy can be scanned and verified |
| Signed invoice payload | Held as the registered version; the books are never re-keyed from it |
| Cancellation confirmation | Marks the IRN cancelled with its reason code and stops further reprints |
| Error code on rejection | Surfaced against the invoice so the fault is corrected and re-sent |
What’s included
- IRN & QR e-invoice schema
- Offline e-invoice JSON
- Live IRN via your GSP
- e-way bill JSON too
- GSTR-1/3B
- Credit/debit notes
- Offline-first
What it does not do
- · LekhaPro does not push invoices to the Invoice Registration Portal on its own. Live IRN generation and cancellation run on your own GST Suvidha Provider credentials, entered in Configuration → GST Portal API; without them the same schema-correct JSON exports for upload.
- · Applicability is not policed for you — whether e-invoicing applies to your business at all depends on the turnover criteria as notified, and that is a decision to confirm with your CA rather than a switch in the software.
- · No payroll or HR module; staff salaries are recorded as journal entries or expenses in the ledger.
Frequently asked
Can it generate IRN and QR?
Yes — invoices are prepared in the e-invoice schema for IRN and QR; JSON is generated offline and live IRN works through your GST Suvidha Provider.
Do I need a GSP?
Only for live IRN generation. Without one, the same e-invoice JSON is produced offline for upload.
Does it also do e-way bills?
Yes — e-way bill JSON is generated the same way.
Can the same invoice number be registered twice?
No. The IRN is computed from your GSTIN, the financial year, the document type and the document number, so re-sending the same combination returns the existing IRN rather than a fresh one. That is why a duplicate series across two branches, or a numbering run that resets mid-year, causes rejections — the portal is enforcing uniqueness, not the software.
I registered an invoice with the wrong value. What now?
If you are still inside the cancellation window the portal allows, cancel the IRN with a reason code and register a corrected invoice. Once that window has passed there is no edit available: issue a credit note for the excess or a debit note for the shortfall, register that note as its own e-invoice, and let both documents flow into GSTR-1.
What exactly is included in e-Invoice · IRN?
IRN & QR e-invoice schema, offline e-invoice JSON, live IRN via your GSP, e-way bill JSON too, GSTR-1/3B and credit/debit notes, and 1 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is e-invoice · irn handled differently here?
It rests on IRN & QR ready, offline JSON, live optional and on real billing. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does e-Invoice · IRN work offline?
On the Desktop edition, yes — completely. IRN & QR e-invoice schema and offline e-invoice JSON run against a local database on your own machine, so the screens behave the same with the network unplugged as with it connected. AI and billing are the only two things that reach out. On the Cloud edition e-invoice · irn runs in the browser and needs a connection.
Does e-Invoice · IRN post to the real books?
Yes, and that is the whole reason it lives in this product rather than beside it. What IRN & QR ready records lands in the same posted double-entry ledger the Trial Balance, P&L and GST returns are built from — so there is no second set of e-invoice · irn numbers to reconcile against the first.
How does e-Invoice · IRN affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever e-invoice · irn produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.