Module

SIAARU Payroll

Salary, statutory deductions and Form 16 Part B — every rate stated with its source, and nothing filed on your behalf.

In build — not switched on₹25,000 / month
See pricing

What it produces

  • An org structure that is a structure: departments, reporting lines, grades, and a job description each role is measured against
  • Promotion history — what changed, when, from what to what, and who approved it
  • A salary structure per employee, effective-dated, as named components rather than one CTC figure
  • Payslips computed from that structure and the period's own events, each printing its arithmetic
  • EPF, ESIC, professional tax and TDS, every rate and slab carrying the source and effective date it came from
  • Form 16 Part B prepared from the year's own payslips
  • Contribution files as CSV with the working — not a portal format written from recollection

A worked example

September — 42 employees, ₹18,44,120 gross
EPF ₹1,42,560 at 12% of basic, ceiling ₹15,000 — source: EPF Act, stated 01 Apr 2026
professional tax ₹8,400 on the Gujarat slab — stated 01 Apr 2026
1 employee unassessed: no professional tax slab stated for Karnataka
→ the return is prepared. Your accountant files it.

Illustrative figures. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

Payroll is the one system where being confidently wrong is discovered by the employee, in public, on the tenth — which is why every rate, slab and ceiling here is stated by you and carries the source it came from, rather than being built in. The EPF wage ceiling, the two ESIC contribution rates, the professional tax slab for each state you employ in, and the income tax slabs for the regime each employee elected all move, and they move on different dates. Where one has not been stated the payslip refuses that deduction by name instead of quietly applying last year's. Form 16 has two parts and only one of them can honestly be produced by software that files nothing: Part B is the salary breakdown and the tax computed, prepared here from the year's own payslips, while Part A comes from TRACES and carries the quarterly returns actually filed.

Opened by the administrator and the finance director — 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.

Being built, and two of its three parts are done. The org structure is built: departments, reporting lines that refuse a loop by name, grades, job descriptions, and a promotion history that records what changed from what to what. Salary and payslips are built: an effective-dated structure per employee as named components, a payslip that prints the arithmetic behind every line, and — once a named person approves the run — that payslip mailed to the employee it belongs to, one recipient per message, with an address shared by two people holding both. The statutory layer is what remains, and until it lands this module stays here rather than in your hands: a payslip with no provident fund, no professional tax and no TDS on it is exactly the confidently wrong document this module exists to avoid. The boundary is fixed, and it is the one DutyGuard, e‑Invoice and Statutory Returns already hold: SIAARU prepares and records, and a named person files. Two parts of that are worth stating plainly. Every rate, slab and ceiling is yours to state, carrying its source and the date it took effect — the EPF wage ceiling, the two ESIC contribution rates, the professional tax slab for each state you employ in, and the income tax slabs for the regime each employee elected. Where one is not stated the payslip refuses that deduction by name rather than quietly applying last year’s, because a payroll that is confidently wrong is discovered by the employee, in public, on the tenth. And Form 16 has two parts: Part B is the salary breakdown and the tax computed, prepared here from the year’s own payslips; Part A comes from TRACES and carries the quarterly returns actually filed. SIAARU holds no TAN credential and files nothing, so it prepares Part B and says so.

Where this sits

One of 33 modules, on one engine.

SIAARU Payroll 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 32 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.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.