GST · e-Invoice

Voucher To IRN, Without Re-Typing

The invoice you raised is the invoice that goes for registration. HSN was captured at the item, the counterparty was validated at entry — nothing is assembled a second time.

✓One Entry One IRN

✓HSN Captured At The Item

✓QR & Ack Stored On The Invoice

See It On Your Books › Watch The 90-Second Tour

e-Invoice, On Screen

Raise The Invoice

A normal sales voucher — nothing special asked of the person typing it.

Validation

GSTIN, HSN and mandatory fields checked before anything is sent.

Registration

The invoice goes for IRN generation as recorded.

QR & Acknowledgement

IRN, acknowledgement number and QR stored against the voucher.

Print & Share

The compliant invoice, with QR, out to the customer.

Cancellation

Within the window, cancelled and tracked — never silently deleted.

See It In Action ›

Autobooks Assembles. You Confirm.

Registration is irreversible after the window closes, so it is never automatic.

At EntryPreparedYour Call

Item With HSN

Counterparty GSTIN

Place Of Supply

Tax Split

Payload Assembled

Mandatory Fields Checked

Errors Surfaced First

Confirm Registration

Store IRN & QR

Cancel If Needed

Automated — Autobooks does it Your call — nothing without you

What Travels With The Invoice

	From The Item	From The Party	From The Voucher	Back From IRP
Captured	HSN Code UQC Unit Rate	GSTIN Place Of Supply B2B Flag	Number & Date Taxable Value Tax Split	IRN Ack No & Date QR Code
Where It Lives	Item master	Ledger master	Voucher line	Stored on the voucher

Nothing is entered twice, so nothing can disagree with itself

WHY IT NEVER NEEDS A SECOND SCREEN

The Invoice Is The Payload. Not A Copy Of It.

e-Invoicing fails when the registration data is assembled separately from the accounting entry. Here they are the same record — so an IRN cannot describe an invoice your books do not have.

Who Built This ›

Fits The Stack You Already Have

IRPGSTNQR PrintPDF TemplatesExcel Export

Turnover thresholds change; the page follows the notification, not the other way round.

Questions A CA Asks First

Who has to generate an IRN?

Businesses above the notified turnover threshold, for B2B supplies, exports and credit or debit notes against them. B2C is outside e-invoicing, though QR requirements may still apply.

Does my team have to do anything different?

No. They raise a sales invoice the way they always did. The registration payload is assembled from that entry.

What happens if a mandatory field is missing?

It surfaces before anything is sent — HSN, unit, counterparty GSTIN, place of supply — with the invoice open so it can be fixed at source.

Where is the IRN stored?

Against the voucher, along with the acknowledgement number, date and QR code, so the compliance artefact and the accounting record never drift apart.

Can an e-invoice be cancelled?

Within the window allowed by the portal, and it is tracked. Outside the window the correction is a credit note — which is the accounting answer anyway.

Does this cover e-way bills?

e-Invoicing and e-way bills are separate obligations. What is captured here — HSN, value, place of supply — is the same data an e-way bill needs.

What if the portal is down?

The invoice is recorded in your books regardless; registration is retried. Your accounting never waits on somebody else's uptime.

See It On Your Books ›