IRN + QR on the receipt, every B2B settle | HelloBooks POS B2B sales above the e-invoicing threshold fire the canonical e-invoice pipeline at settle. The IRN, the QR, and the acknowledgement number print on the receipt — no manual portal hop, no end-of-day batch.
IRN + QR on the receipt, every B2B settle
B2B sales above the e-invoicing threshold fire the canonical e-invoice pipeline at settle. The IRN, the QR, and the acknowledgement number print on the receipt — no manual portal hop, no end-of-day batch.
Part of HelloBooks POS · Compliance & tax (India)
For most retailers, e-invoicing is the heaviest GST burden — payload generation, IRP authentication, signing, QR rendering. HelloBooks moves all of this to the engine and away from the till. The cashier presses Settle; the IRN comes back in seconds; the QR is on the printed receipt.
Every detail, dialled in
Built for the till, validated against the canonical accounting engine — so every POS sale closes the books cleanly.
Threshold-aware auto-fire
Outlets above the GST e-invoicing threshold (or B2B-only stores) auto-fire the e-invoice on every B2B settle. Counter sales below the threshold or to unregistered customers skip the call cleanly.
- Threshold check at settle
- B2B-only outlet toggle
- GSTIN-based opt-in
- Per-outlet override
IRN + signed QR on the receipt
The till waits for the IRP response (typically 1-2 seconds), bakes the signed QR into the receipt template, and prints. The customer sees IRN, acknowledgement, and canonical QR.
- IRN printed on every B2B receipt
- Signed QR rendered to printer
- Acknowledgement number visible
- Falls back to retry on transient IRP errors
Canonical pipeline reused
The same e-invoice client used by the back office handles POS too — Fynamics GSP for IRN generation and cancellation. So GSTR-1 reflects POS sales correctly and a cancelled bill cancels the IRN.
- Fynamics GSP under the hood
- GSTR-1 reflects POS bills
- Cancelled bill → cancelled IRN
- No POS-specific compliance logic
Why teams move off legacy tills
- Cashier types into the IRP portal
- Receipt printed before the IRN
- GSTR-1 misses POS bills
- Cancellations re-typed manually
- Engine fires the IRP automatically
- Receipt prints with IRN baked in
- GSTR-1 reflects POS bills
- Cancel triggers IRN cancellation
Questions, answered
What if the IRP is down at the moment of settle?
The settle still completes; the bill is queued for IRN generation and the receipt prints with a placeholder note. We retry until the IRN is received and re-print on demand.
Does B2C also fire an e-invoice?
No — by design. B2C bills follow the simplified GST tax-invoice flow. Only B2B (recipient with GSTIN) fires the canonical e-invoice pipeline.
How does this connect to GSTR-1?
Every POS B2B bill that gets an IRN flows into GSTR-1 like any back-office invoice. No separate POS reconciliation.
What happens on bill cancellation?
The IRN is cancelled through the canonical pipeline within the IRP cancellation window. The audit trail records the cancel reason.
Related POS features
Ready to automate your books?
Join 2,000+ businesses saving 20+ hours per month. Get started free — no credit card required.