One platform. Every country you operate in.
Day.io is used in 50 countries. Each country keeps its own overtime, break and rest rules inside one account, with one set of admins.
The rules change at every border. The platform doesn't.
Each market sets its own working-time rules and its own payroll close.
Four things that change per country. All four are already set.
Most global tools localise the interface and stop there. The part that decides whether a rota is workable is everything underneath it.
Working-time rules
Overtime, breaks, rest periods and shift premiums are configured per market, so one policy engine applies each country's own rules instead of a single global default.
Their own language
Employees use the app in their own language. Day.io supports dozens of languages.
How people clock in
Every clock-in method is optional. Where a regulator treats biometric data as sensitive, teams run on mobile, kiosk or badge instead — same rules engine, same reports.
What payroll receives
Approved hours go to payroll as an export file, or straight into ADP, SAP or Workday.
Add a country without starting a new project
Opening a market shouldn't mean a second system, a second admin team and a second set of reports that never quite reconcile.
- ✓ One account and one set of admins, with every country inside it
- ✓ Country policies that inherit a global default and override it where local rules differ
- ✓ Reporting across markets for head office, and per-market reporting for whoever files it
- ✓ A new country goes live with its language and rules already set up