Core concepts
Countries, entities and jurisdiction
Which rules apply to whom, and why it follows the work rather than the employer.
Rules are resolved from where the work is done, not from where the legal entity is registered. A Wyoming company employing somebody in California owes California's rules, and the product will apply them.
Most specific wins
A rule can be scoped to an entity and region, an entity, a country and region, a country, or the whole tenant. The most specific match applies. A rule scoped to somewhere else is never used as a fallback — it either matches or it does not exist for that person.
| Scope | Example |
|---|---|
| Entity + region | This subsidiary's Californian staff |
| Entity | This subsidiary |
| Country + region | Anybody working in California |
| Country | Anybody working in the United States |
| Tenant default | Everybody, absent anything better |
Holiday calendars are the exception
Calendars compose instead of competing. Somebody in the United States observes federal days and state days and their company's own days, unioned and de-duplicated by date.
Jurisdiction differences are data, not code
Adding a country means adding rows: a leave policy, an overtime rule, a holiday calendar. There is no branch anywhere on a country code, which is why a country nobody has shipped a preset for still works — it simply starts generic.