Module
Statutory Returns
GSTR and TDS assembled from what was decided, rather than reconstructed at month end.
What it produces
- GSTR-1 and GSTR-3B working papers built from invoices already stamped with their tax head
- Input credit matched against GSTR-2B, with the mismatches named supplier by supplier
- TDS deducted at the section that applies, with the certificate and the challan tracked
- Every figure tracing to the invoice line it came from, because a return is queried line by line
A worked example
Illustrative only — nothing is filed and nothing is computed
the place-of-supply engine already stamps each charge with its head and the section that decided it
what is missing is the aggregation into a return, and the reconciliation against 2B
filing is not planned at any point — SIAARU holds no signature and files nothing
Illustrative figures. 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 figure that cannot be traced to the invoice behind it is a figure 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 figure 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.
Not built, and further off than it looks. The tax head on each line exists, which is the foundation, but a return also needs the rest of a company's ledger — the entries SIAARU does not keep. Filing is not planned at all: SIAARU holds no digital signature and files nothing with any authority, here or in DutyGuard, and that does not change for a return.
Where this sits
One of 32 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 31 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.