An organisation model, not an industry template.
Define the structure your organisation actually has — departments, sites, roles, permissions — then activate the modules that run on it. Manufacturing, services, healthcare, education, distributed field teams: the model is the same, the configuration is yours. Everything below is specific and checkable.
Interface illustration. Sample figures, not a customer's data.
What is different underneath
Every platform in this category lists the same modules. The difference is the model they sit on, and what the system does when it is asked for something it cannot be certain of.
The organisation is modelled, not assumed
Departments, sites, designations, roles and per-action permissions are yours to define, and every module reads that one structure. No vertical edition to buy into, and no rebuild when the organisation changes shape.
Statutory maths that refuses to guess
EPF wage ceilings, ESI including overtime, professional tax by state. Where the system does not hold a state's slab it says so and stops, instead of deducting zero. A spreadsheet deducts zero silently, and the shortfall surfaces at assessment.
A finalised month cannot quietly change
Once a month is finalised it is a record. Restating it takes a person, and the system shows what will move before it moves. Most payroll sheets can be edited afterwards by anyone who can open the file.
One company, several sites, different rules
Each location keeps its own state, its own statutory settings, its own timezone and its own salary day basis. Running four sites across two states is the ordinary case here, not an enterprise upgrade.
The reconciliation check
One action compares what payroll says against attendance, against the slips, and against the statutory position — and lists every disagreement. This is the check that does not exist in a spreadsheet, because a spreadsheet has nothing to disagree with.
What is actually running
The figures below come from a deployment we run ourselves, on our own operations, as at 30 August 2026. No logos and no certifications appear on this page, because we hold neither — and borrowed credibility does not survive a buyer who checks.
The screens the figures on the left are counted from. Interface illustration; sample figures, not a customer's data.
The company that builds this software runs its own operation on it — attendance, payroll, a work order, a billing abstract and the invoice that came out of it. That is a weaker proof than a named customer and a stronger one than a testimonial we wrote ourselves. When a customer is willing to be named, they will appear here instead.
What you get today
This list is generated from the same source the product reads. Nothing on the roadmap appears on it, so it cannot describe a module you are unable to switch on.
People
Finance & Payroll
Payroll
Salary structures, deductions, payslips and review workflow.
EPF splits reconciled line-by-line with a company's own filed EPFO return
Statutory & Tax Workflows
Calculation support and the records your filings are built from — you stay in control of filing.
EPFO and ESIC return files generated straight from finalised payroll
Business Operations
What a person still does
Every one of these is a control we chose to keep, not a gap we have not got to. Software that moves money on its own is a liability, not a feature.
- The platform prepares the bank file. A person reviews it and makes the payment. No money moves without a human.
- Statutory figures are calculated, not filed. Your CA confirms them before anything is submitted.
- Returns are exported for upload. The upload to the EPFO and ESIC portals is done by you, on the portal.
- AI drafts. A person approves. Nothing is sent to a client or an employee on the assistant's own authority.