Module
e-Invoice & e-Way
The IRN and the e-way bill raised from the invoice that already exists, not typed twice.
Watch demo
The portal refused it. The lorry is at the gate and nobody can see the payload.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- Every check the portal makes, made here first — against the record that caused it, not a four-digit code four hours later
- The INV-01 document assembled from the invoice, its lines and their classification, readable before it is sent
- IRN, acknowledgement, signed QR and e-way bill recorded against the invoice, with the payload kept as it was sent
- Cancellation inside the twenty-four hours the portal allows, refused after it with the credit note named as the remedy
A worked example
From the demonstration tenant, on invoices it raised
8 invoices ready to register, 32 held here with the field and the line named
no rate derived by dividing tax by net, no classification taken from a similar item
and no registration made until a named person presses the button against your own credential
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
An invoice is typed once into the billing system and again into the portal, and the second typing is where the mismatch enters. SIAARU already computes the invoice, its lines and the tax head on each of them, which is most of what a registration needs — but registering an invoice is an act with a legal consequence, and it will not be made against a schema somebody guessed. It waits on the real specification and on a tenant registering their own credential, because the credential belongs to the company whose invoice it is.
Opened by the finance director and the logistics manager — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
SIAARU holds no digital signature, asks for no GST portal password and registers nothing on its own: a registration is made under your company's own credential, by a named person, and this module records what was sent and what came back. Two limits are worth stating. The document is built to the INV-01 schema as published, and the field names were taken from working payloads rather than from GSTN's own schema file, which could not be reached from the build environment — so it must be checked against that file before a first live registration. And the adapter is proven against a fixture portal, not a live one, because proving it live needs a tenant's credential.
Where this sits
One of 36 modules, on one engine.
e-Invoice & e-Way reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.