E-invoicing without typing it twice
The e-invoice payload is a lossless function of the invoice you already recorded. Acronix treats it that way: build from the voucher, validate first, import the response back.
- IRP-schema payload
- Pre-submit validation
- Response import
- Role-gated cancel
Where this usually goes wrong
Duplicate entry into the IRP
Re-keying an invoice into a portal is both slow and a fresh opportunity to diverge from your own books.
Rejections found at the portal
Discovering a missing GSTIN or a bad HSN at submission time is the most expensive moment to discover it.
The IRN never making it back
An IRN that lives only in a portal download is not on your invoice, and not in your records.
How it works in the app you can download
Every capability below ships in the current build.
Payloads built from the voucher
The IRP JSON is generated from the sale you already recorded — same party, same lines, same tax.
Validation before submission
A dedicated GST validation panel surfaces the problems — missing GSTIN, HSN, place of supply — while you can still fix them cheaply.
Response imported back
The signed IRP response is parsed and attached to the invoice, so the IRN lives on the voucher rather than in a download folder.
Cancellation handled
Cancel flows are supported and gated behind the Accountant role.
Moving from older accounting software?
Where Acronix is genuinely different — and where the tool you have already does the job. No invented weaknesses.
- Data at restAES-256 encrypted file — unreadable if the disk is copiedUsually a plain local data folder
- Switching machinesSign in on the new device and your books sync downSurrender the licence, copy a backup, restore by hand
- Working offlineFully offline-first — no internet needed to runOffline too, but cloud backup is bolt-on
- Keyboard-first entryEvery action has a shortcut; hands never leave the keysKeyboard-driven — the one thing they got right
- The interfaceA modern, high-density UI built this decadeFunctional, but a 1990s screen
- GST suiteGSTR-1, 3B, e-invoice, e-way bill from the same vouchersPresent, often as paid add-ons
Questions
E-Invoice (IRN) — questions, answered
Straight answers on what's in the current build and what it does not do.
Do I have to re-type the invoice into the IRP portal?
No. The IRP-schema payload is generated from the sale you already recorded — same party, same lines, same tax — so the e-invoice is built from your books rather than keyed a second time into a government site.
Can I catch problems before I submit to the portal?
Yes. A dedicated GST validation panel surfaces missing or inconsistent fields — GSTIN, HSN, place of supply — while they are still cheap to fix, instead of letting you discover them at submission, which is the most expensive moment to find them.
Where does the IRN end up after it is generated?
The signed IRP response is parsed and attached back onto the invoice, so the IRN lives on the voucher itself rather than in a portal download folder that nobody keeps. Your record and the portal record match.
Can I prepare the e-invoice offline and push it when connected?
The app runs on a local encrypted database, so the payload is built and validated on your machine. You do the assembly and the checking without waiting on the line, and the push happens against the portal when you are connected.
Can I cancel an e-invoice?
Yes. Cancellation is supported and gated behind the Accountant role, so the ability to reverse an IRN sits with the people who should hold it rather than with anyone at a billing counter.
What data does the payload actually use?
It is a lossless function of the sale voucher — the party, the lines, the HSN and the tax that produced the invoice. Because it is derived from the same voucher, the e-invoice cannot diverge from the books it came from.
Try it on your own books
14 days, every feature unlocked, no credit card. Your data stays encrypted on your own machine.