Features
The rest of it
Timesheets, attendance, GST invoicing, payroll and an API — built on the same honest numbers.
01
Time that survives a bad connection
The agent keeps up to three days of work on the laptop and sends it when the network returns. Chunks carry their own identity, so a retry after two hours offline is recognised rather than counted twice.
02
Timesheets, approvals and reports
Weekly timesheets with an approval that locks the week — payroll and invoices are built from approved weeks, so a late chunk cannot silently change what was signed off. Manual entries are separate rows with a required reason, never edits to what the agent recorded.
03
Attendance and leave
A register built from tracked time rather than punches, with work schedules, a holiday calendar, leave types and balances. Present, absent and on-leave are three different things, and payroll reads them that way.
04
Indian invoicing and payroll
GST invoices with CGST/SGST or IGST decided by place of supply, TDS on taxable value, Rule 46 numbering, and a financial year that runs April to March. Money is integer paise end to end — no floats anywhere in billing.
05
Alerts that do not cry wolf
One alert per condition, not one per evaluation. Idle streaks, missing agents, a machine that lost a permission — raised once, muted or resolved by a person.
06
An API and webhooks
A read API with per-organization keys, and signed webhooks for the events that matter. Payloads carry a timestamp inside the signature, so a captured request cannot be replayed later.
Built for how an Indian team actually bills
GST, TDS and an April-to-March year are not a localisation layer here. They are how the money code works.
Talk to us