HR records leave and attendance in Zoho People; payroll calculates salaries, WPS files and gratuity. We connect the two, and post the result to Zoho Books, so the monthly pay run stops depending on spreadsheets.
Zoho People holds employee records, leave, attendance and overtime, and passes approved data at the payroll cut-off to Zoho Payroll, whose UAE edition is designed to support WPS salary files and end-of-service gratuity. The salary journal then posts to Zoho Books by cost centre. UAE employers avoid spreadsheet handovers, missed unpaid leave and WPS file rejections.
A Zoho People payroll integration in the UAE connects the HR system where employee records, leave, attendance and shifts are kept with the payroll engine that calculates monthly salaries. For most UAE employers that engine is Zoho Payroll, which Zoho offers with a UAE edition built around local requirements such as WPS salary files and end-of-service gratuity; confirm current features for your plan. The salary journal then flows to Zoho Books for the accounts.
The typical pain we see is the monthly handover. HR exports a leave report from Zoho People, someone adds overtime from a site timesheet, finance adjusts for unpaid leave and new joiners in a spreadsheet, and the WPS Salary Information File is built by hand for the bank portal. Every manual step is a chance to underpay or overpay, and WPS rejections delay salaries for the whole company.
This page is about connecting Zoho People with payroll inside the Zoho stack. For the general picture of linking payroll with any ERP, see payroll integration in the UAE, and for the payroll product itself, Zoho Payroll in the UAE.

The products we configure, integrate and support on projects like this one.
Product names and logos are trademarks of their respective owners and are shown only to identify the software we implement.
Payroll errors in the UAE are expensive in two ways: unhappy staff and WPS non-compliance. These are the common causes.
An employee takes five days of unpaid leave approved in Zoho People, but the deduction never reaches the payroll spreadsheet. The overpayment is noticed months later, if at all.
Site supervisors send overtime hours on paper or WhatsApp photos. Payroll staff retype them, and disputes are settled by whoever shouts loudest.
A new hire is onboarded in HR but not added to payroll, or a resigned employee is still paid. Pro-rata calculations for mid-month changes are done by hand.
A wrong labour card number, routing code or IBAN in the Salary Information File causes rejection. Salaries are delayed and the employer risks MOHRE follow-up.
Finance books a rough end-of-service provision each month because nobody trusts the joining dates, unpaid leave and basic salary history in the spreadsheet.
Salaries hit the ledger as a single bank payment, so cost by department, project or cost centre is missing from management accounts.
A typical cycle once the integration is in place, with HR and finance approvals kept as explicit steps.
One shared database: every step updates stock, finance and reports in real time.
We set one master for each data set and avoid editing the same field in two apps.
| Data | Direction | Trigger / frequency | Notes |
|---|---|---|---|
| Employee profile and joining date | People to Payroll | On creation or change | Joining date drives gratuity and pro-rata; lock it after payroll starts |
| Department, designation, cost centre | People to Payroll | On change | Needed to split salary cost in the journal |
| Leave taken and loss of pay days | People to Payroll | At payroll cut-off | Only approved leave; pending requests flagged before lock |
| Attendance and overtime hours | People to Payroll | At payroll cut-off | Overtime rules per UAE Labour Law and company policy |
| Salary structure and allowances | Maintained in Payroll | On revision | Basic, housing, transport and other allowances as separate components |
| Bank IBAN, labour card and personal ID numbers | Maintained in Payroll (or People, by decision) | On change | Required for the WPS Salary Information File |
| Exits and final settlement | People to Payroll | On resignation or termination | Last working day, leave encashment and gratuity calculation |
| Salary journal | Payroll to Zoho Books | After pay run approval | Expense, accrual and bank lines by cost centre |
Field coverage of the native integration differs by plan; we confirm which items sync natively and which need a custom step.
Within the Zoho stack the native links handle most of the flow. Custom work fills gaps such as site timesheets or a bank's specific file format.
We plan payroll go-live so that at least one cycle runs in parallel with the old method.
We reconcile the employee list in Zoho People against the last payroll and WPS file: names, joining dates, labour card numbers, IBANs and salary components.
Leave types, unpaid leave rules, overtime rates, shift patterns and attendance cut-off dates are set in Zoho People to match your contracts and policy.
Salary components, WPS employer details and gratuity rules are configured. The statutory basis is 21 days' basic wage per year for the first five years and 30 days per year after, capped at two years' wage; see our gratuity software page.
Each salary component is mapped to a ledger account and cost centre in Zoho Books so management accounts show cost by department or project, as covered in payroll accounting integration.
We run one or two months alongside the existing payroll, compare employee by employee, and only then submit the WPS file from the new process.
Payroll touches labour law, WPS and personal data. Confirm specific treatments with your HR legal advisor or accountant.
Mainland employers registered with MOHRE pay salaries through approved banks, exchange houses or agents using a Salary Information File. Employee identifiers and bank details must be correct for the file to be accepted; read more on WPS payroll.
Under Federal Decree-Law 33 of 2021, gratuity depends on basic wage and continuous service. Accurate joining dates and unpaid leave from Zoho People are what make the payroll calculation trustworthy.
Passport, Emirates ID, salary and bank data are sensitive. Restrict access by role in both apps and align retention with the UAE Personal Data Protection Law.
Payroll records and journals support salary expense deductions for corporate tax; keep them with supporting documents for at least five years.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
The main gain is a payroll cycle that runs on approved data instead of reconstructed data.
Leave, attendance and overtime arrive already approved, so payroll staff review exceptions instead of rebuilding inputs.
Bank and ID details are maintained once and validated before the file is generated.
Monthly end-of-service accruals are based on actual service and basic salary, not estimates.
Journals in Zoho Books split cost by department or project, which management accounts and project costing need.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertZoho People is an HR application for records, leave, attendance and performance. Salary calculation is done in a payroll application, typically Zoho Payroll, which receives the HR data through the integration.
Zoho Payroll's UAE edition is designed to support WPS salary file generation. File formats can vary by bank or agent, so we test the output with your bank before go-live and confirm the current feature set for your plan.
Yes. Leave and attendance can be exported or pushed by API to another payroll system. The integration is more custom, and you lose some native links such as the shared employee record.
Many free zone employers are not on MOHRE WPS but have their own salary rules. We configure separate pay groups so free zone and mainland staff follow the correct process.
Zoho People can import attendance from supported biometric devices or through its API. Overtime and late deductions are then calculated from approved attendance and passed to payroll.
For a single entity with clean employee data, a rollout including one parallel run often takes six to ten weeks. Multiple entities, sites or shift patterns extend that.
Related Solutions
Related Industries
Related ERP Platforms
Tell us your headcount, entities and current payroll process, and we will plan a Zoho People payroll integration with a safe parallel run.
Dubai, United Arab Emirates