Module
Statutory Returns
GSTR-1 and GSTR-3B built from the invoices, checked against the ledger, filed by you.
Watch demo
The return was filed. The books say something else, and nobody knows which is right.
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
- GSTR-1 as the form groups it — B2B, B2C large, B2C small, credit notes, exports and the HSN summary
- GSTR-3B taking its outward numbers from those same tables rather than computing them a second way
- The difference between the return and the ledger, reported and never absorbed, with both numbers
- Every table exported as CSV, and every export recorded with what it said at the time
A worked example
From the demonstration tenant, on one of the ledger's own periods
the tables and the ledger are the same documents read two ways, so they agree
where they do not, the gap is a finding — before a notice rather than after one
and nothing is filed: SIAARU holds no digital signature, here or anywhere
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A return is queried line by line, so a number that cannot be traced to the invoice behind it is a number somebody has to rebuild under pressure. The place-of-supply engine already stamps every charge with its head and the section that decided it, which is the part most systems cannot show. What is missing is the rest of a company's ledger, which SIAARU does not keep. Filing is not planned at any point: SIAARU holds no digital signature and files nothing with any authority, and that is a decision rather than a gap.
Opened by the finance director and the owner — 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.
Prepared, never filed. SIAARU holds no digital signature and files nothing with any authority — the same boundary as DutyGuard and e-Invoice, and it does not move for a return. Scope is stated narrowly on purpose: outward supplies and the summary. Annual returns, reconciliation against GSTR-2B, reverse charge, advances and amendment tables are out of it. And the tables export as CSV rather than as the portal's own JSON: the offline utility's schema could not be reached when this was built, and a file claiming to be that format written from recollection would be worse than none.
Where this sits
One of 36 modules, on one engine.
Statutory Returns 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.