HRMS · Compliance

The rule is
configuration.

A payroll engine that hard-codes provident fund can only ever run one country, and every rate change becomes a release. Here a country’s rules are a versioned pack, validated before it is allowed anywhere near a payslip.

Why the same engine runs several countries. Not because it was written four times, but because the part that differs is data.

Country packs

Rules that arrive as configuration.

Versioned per countryA pack you upload, versioned, so a rate change is an edit with a history rather than a deployment.
Validated before useChecked against a schema before it can affect a payslip, because a malformed rule discovered at run time is discovered on somebody’s salary.
Deductions derive from itPF, ESI, professional tax and the rest come out of the pack and sync into the payroll components, rather than being maintained twice.
Where the rule applies

Tax that changes by location.

Location tax rulesProfessional tax and its equivalents differ by state and city. The rules are held per location and applied from the employee’s office.
Establishment registrationsThe registration numbers a filing needs, kept as records against the establishment they belong to rather than in somebody’s folder.
Statutory artifactsThe documents a compliance step produces, generated and retained rather than recreated each time an inspector asks.
Why it matters

The half of payroll that is not arithmetic.

Rates moveAnd when they do, the fix is a new pack version rather than a code change, a release and a regression risk on everybody’s pay.
Countries differIndia, the UAE, the UK and the US do not share a deduction model. Treating the rules as data is what makes one engine honest across all of them.
Nearby

Related capabilities.

Payroll · Employee records · HR reports

Compliance that survives a rate change.

Upload the new pack. The next run uses it, and the old payslips still explain themselves against the old one.

Get started → See pricing