One workspace

One company, three countries, three payrolls

Add a legal entity per country. Everybody belongs to one, is paid in its currency and is run under its rules, and you still see the whole headcount on one screen.

app.offichr.com/settings/entities
India · Greater Noida184 people
₹ INRPF · ESI · PT · TDS
UAE · Dubai26 people
AEDGratuity · WPS
United Kingdom · London11 people
£ GBPPAYE · NI · pension
Saudi Arabia · Riyadh7 people
SARGOSI

One company, four payrolls. Each person is paid in the currency of the entity they belong to, under that country’s rules — and sees only the forms it has.

Illustrative interface — figures are examples, not a customer’s data.

Benefits

What changes when a country is a setting, not a deployment

Each person paid in their own currency

Rupees, dirhams, pounds, riyals. The payslip remembers the currency it was issued in, so last year’s slip does not quietly re-read in this year’s money.

The statutory rules of the place

PF, ESI, professional tax and TDS in India. Gratuity and WPS in the UAE. PAYE, National Insurance and pension in the UK. GOSI in Saudi Arabia. Each entity runs its own.

Nobody sees forms their country has not got

An Indian investment declaration and Form 16 are simply absent for an employee in Doha. They are not shown and then refused. The menu is built from the country, in the browser, the app and the admin screens alike.

The papers people actually have

PAN and Aadhaar in India, Emirates ID in the UAE, a National Insurance number in the UK. Each is asked for where it exists and nowhere else.

On the phone too

The same country rules reach the employee's pocket

The app is built from the same country pack as the browser. Somebody in Dubai opens it and finds gratuity where an Indian colleague finds Form 16. Not a greyed-out menu item with an explanation attached.

In 09:04 · Out —

Working

Leave
Payslip
Claim
Casual leave6.5
April payslipPDF
Claim EXP-0418₹14,280
AndroidYour logo, your colour

Everything in the app — nothing opens a browser

Illustrative interface — figures are examples, not a customer’s data.

How it works

    01

    Add the entity

    Country, registered name, currency, time zone. The statutory rules come with the country.

    02

    Put people in it

    Each employee belongs to one entity, which settles their currency, their forms and their payroll rules.

    03

    Run payroll per entity

    Separate runs, separate approvals and separate bank files, with one set of reports across the lot.

    04

    Report on the whole company

    Headcount, cost and attrition across entities, each figure in its own currency and totalled where that makes sense.

Capability

Where it runs today

Five countries with their own rulebook

India, the United Arab Emirates, the United Kingdom, Saudi Arabia and Qatar, each with its own statutory engine, identity fields, bank fields and leave conventions.

Anywhere else, on the general pack

A country without its own rulebook runs on a generic one: your currency, your leave policy, your working week, with no statutory deductions invented for it.

  • Any ISO country and currency
  • Nothing deducted that the country does not levy

Multiple entities in one country

Two Indian companies under one group each keep their own PF code, ESI sub-code, GSTIN and approver chain.

The working week is local

Sunday to Thursday in the Gulf, Monday to Saturday in a plant, Monday to Friday in an office. Attendance, leave and payroll all read the same setting.

Questions people ask

Read next

Add a second country in the trial

Create an entity, move one employee into it, and watch the forms and the currency change with them.