An India-first payroll engine, with global architecture.
Currency, locale, statutory rules and pay calendars are configuration rather than assumptions, so adding a country is a rule set — not a rewrite. Being honest about where that stands matters more than a map full of flags.
- Countries
- Rule sets
- Payroll
- Workforce cost
- Consolidated view
What makes this industry's payroll different
Where this actually stands
India statutory payroll is implemented and tested. Other countries currently use a generic earnings-only rule set: real arithmetic, but not local statutory rules. We will not pretend otherwise.
Nothing is hard-coded to one country
No component assumes a currency symbol, a date format or a tax regime. That is what makes expansion tractable.
Multi-country payroll and EOR
On the roadmap, and labelled as such everywhere it appears.
How your structure is modelled
- Company
- Region
- Location
- Department
- Employee
One dimension model serves every industry. This pack calls its main unit a entity; the payroll engine beneath is identical everywhere.
Questions this industry asks
- “What does our workforce cost across locations?”
- “Which locations are growing fastest?”
- “How is payroll structured for a new country?”