E-invoicing that generates the IRN before you print

Under the GST e-invoicing mandate, a B2B invoice above the turnover threshold is only valid once it carries an Invoice Reference Number (IRN) and the digitally signed QR from the NIC portal — and the buyer’s input-tax credit depends on it. E-invoicing software should make that an invisible background step, not a second system.

HelloBooks generates the IRN and signed QR the moment you save the invoice, embeds them on the printed document, and carries the same record forward into the e-way bill and GSTR-1.

Save a B2B invoice and HelloBooks builds the NIC JSON payload, submits it, and writes the IRN and signed QR back onto the invoice — so the document you print or share is already compliant.

• IRN and signed QR generated when the invoice is saved
• Both embedded on the printed and shared PDF automatically
• Applied above the ₹5 crore e-invoicing threshold
• Cancellations within the NIC window handled from the same screen

NIC rejects payloads for real reasons — duplicate IRN, schema mismatch, GSTIN-not-found, a cancelled counterparty registration. HelloBooks shows that error on the invoice itself with the NIC error code, so your accounts team fixes and retries immediately instead of finding a gap when the GSTR-1 does not tie out.

The e-invoice record carries forward: the e-way bill is created from the same invoice with the IRN already attached, and the supply flows into GSTR-1 — so your e-invoice log, EWB register and GST return reconcile by construction instead of by spreadsheet.

Each registration generates its own e-invoices, and place of supply is derived from the buyer’s GSTIN so the tax heads on the IRN payload are correct — CGST + SGST intra-state, IGST inter-state — across a multi-GSTIN group filing from one workspace.