Book a callFree trial

HR automation: one source for your people data

HR automation means having recurring HR tasks carried out by software instead of people. Onboarding, leave, absence, appraisals, document management, expense claims and reporting all follow fixed rules, with one place where your people data lives.

Book a consultationGet to know us

Where your HR time really goes

Ask an HR adviser what their week goes on and you rarely hear "strategic HR policy". You hear: drafting contracts and sending them to four places, retyping leave requests, passing on absence reports, phoning changes through to payroll, chasing expired certificates, and cobbling together a monthly report nobody is quite sure is correct.

HR automation solves that. Not because technology is fun, but because you can only steer on staff turnover, absence and capacity when your figures are reliable.

And that last point is the one that often gets skipped: automation is not the goal but the precondition for HR analytics. As long as your absence figures are spread across three different files, every dashboard is a guess in nice colours.

The four building blocks of a working HR environment

  • HR administration and processes

    Zoho People is the heart of it: one digital file per employee with contracts, personal details, job history and documents. Around it run the processes: leave requests routed to the right approver, absence registration, time tracking, expense claims, appraisal cycles and onboarding checklists that start themselves as soon as a contract is signed. Employees handle their own requests through self-service, so HR no longer acts as a go-between.

  • Recruitment and selection

    Recruitment belongs at the start of the same chain, not in a separate tool with its own database. Zoho Recruit manages vacancies, applicants, the pipeline and communication, and turns a hired candidate into an employee in Zoho People in a single step. Everything you already asked for during the application (address, qualifications, availability) does not need to be typed in again. That saves not only time but also the typing errors that later turn up in your payroll tax return.

  • Training and knowledge management

    Zoho Learn is the layer missing from most HR environments: a knowledge base and learning platform in one. You record your handbooks, work instructions and procedures in it, build onboarding courses and mandatory training, and track who has completed what. For organisations with certification requirements (healthcare, engineering, transport, financial services) that is the difference between "we think everyone is up to date" and an export file you can show an auditor.

  • AI agents that actually do the work

    With Zoho Zia Agents you deploy AI agents that carry out HR tasks independently within the boundaries and permissions you set. In practice that means things like: answering employee questions about leave balances, policies or the collective labour agreement from your own knowledge base, starting and monitoring onboarding tasks, pre-sorting applications on hard criteria, flagging that absence in a team is rising, and preparing periodic reports with an explanation.

    One important point: an HR agent works with particularly sensitive data. Because Zia Agents run inside the platform, they inherit the roles and permissions model you have already set up. An agent sees no more than the user it acts for, and every action can be traced. That is a fundamentally different story from a standalone chatbot into which someone pastes personnel data.

Why you should not put payroll in your HR system

You have just put everything in one place, and now payroll processing should stay outside it? Yet in the Netherlands that is almost always the wisest choice. Five reasons.

  • Dutch payroll legislation is a specialism

    Payroll taxes, sector premiums, the work-related costs scheme, the 30% ruling, pension returns to the right fund, the payroll tax return to the Dutch Tax Administration, sickness and recovery reports to the UWV, and on top of that collective labour agreements that differ per sector and change every year. An international HR suite does not keep up with all that for a market of seventeen million people. Dutch payroll providers do nothing else.

  • Payslip errors cost more than leave balance errors

    A wrong leave balance is corrected with a conversation. A wrong payroll tax return means correction messages, possibly additional assessments and fines, and a lot of explaining. That work belongs with a party that takes responsibility for it and has set up a professional administration for it.

  • Separation of duties is an advantage, not an obstacle

    Salary data is the most sensitive personnel data you have. By keeping it in a separate system with its own authorisation structure, you automatically limit who can access it. An HR employee handling leave requests does not need to see everyone's gross salary. That helps your GDPR accountability and the working atmosphere.

  • Your accountant already works in that system

    In many organisations an external payroll bureau or the accountant processes salaries, and they work in Loket.nl, Nmbrs or a similar package. Moving away from that means switching supplier, overhauling a way of working and convincing a partner, for a problem you did not have.

  • You keep your freedom of movement

    An HR suite and a payroll package have different life cycles. Keeping them separate lets you replace your HR environment without touching your payroll, and vice versa. Cramming everything into one system sounds efficient, but turns every future change into a project.

Connecting Zoho to Loket.nl, Nmbrs and similar packages

So the right question is not "how do I get payroll into my HR system", but "how do I make sure both systems see the same truth without anyone retyping anything".

This is where it gets concrete. The common Dutch payroll packages (Loket.nl, Nmbrs, Visma, Exact Salaris, AFAS and similar) all offer an API or an import route. With that you build an integration in which HR is the source and payroll the processor.

Who owns which data

Agreeing on this before you build prevents ninety per cent of the trouble later on.

Data Source Direction
Personal details, address, bank account Zoho People HR → payroll
Start date, contract type, hours, job title Zoho People HR → payroll
Contract changes and salary changes Zoho People (recording), payroll package (processing) HR → payroll
Leave requests and balances Zoho People HR → payroll (when paid out or deducted)
Sickness and recovery reports Zoho People HR → payroll → UWV
Hours worked and overtime Zoho People HR → payroll
Expense claims and allowances Zoho People HR → payroll
Payslip and annual statement Payroll package Payroll → employee portal
Journal entries Payroll package Payroll → accounting
Leaving the company Zoho People HR → payroll

The rule of thumb: everything to do with the employee starts in HR, everything to do with money and tax returns ends in the payroll package. Payslips flow back, so employees find them in their own portal rather than through a separate login.

How to build such an integration in practice

There is no ready-made standard connector between Zoho and the Dutch payroll packages. In practice it is done through one of these three routes, depending on what your supplier offers:

  • API integration

    The clean solution when the payroll package has a usable REST API. Changes are passed on directly and in a controlled way, with error handling and logging.

  • File exchange

    Many payroll packages work with a periodic changes file. Less elegant, but robust and often quicker to set up.

  • RPA as a safety net

    If there is no API and no import route, a software bot can carry out the actions in the portal the way an employee would. Not pretty, but effective with older packages.

The change process you want to have

A well-designed chain looks like this: a manager submits a contract change in Zoho People, the right person approves it, the change is recorded in the employee file and passed on to the payroll package, payroll checks and processes it, and the payslip comes back in the employee's self-service portal. Nobody emails an Excel file. Nobody calls to ask whether it has been processed yet.

The biggest gain is in the monthly round of changes. Organisations that do this by hand lose hours on it every payroll run, with the added risk of typing errors you only discover when an employee calls.

Scenario 1: your HR runs on Excel and folders on a server

This is more familiar than many organisations admit. A staff list in Excel, contracts in a folder per employee, leave in a second sheet, absence in a third, and a handful of people who know which version is the right one.

Signs you are ready to switch:

  • You have more than roughly twenty employees and the list is kept by more than one person
  • Nobody can say how many leave hours are outstanding without digging
  • Contracts and copies of ID documents are stored in folders without a retention period, which is a GDPR risk in itself
  • An expired certificate or a contract that was not terminated in time has already slipped through the net
  • The monthly report for the management team takes a day and leads to arguments about the figures instead of the conclusions
  • There are several versions of the same file with names like "staff_final_v3_new"

How such a switch works

Take an organisation with thirty-five employees, an HR adviser who spends two days a week on it, and an external payroll bureau working in Nmbrs. Realistic lead time for an organisation of that size: a few weeks, most of which goes into steps 1 and 2. The approach:

  1. Clean up first

    The existing Excel file becomes the basis, but not until duplicate rows, outdated addresses and missing contract data have been corrected. This is almost always the biggest piece of work and almost always underestimated.

  2. Set up Zoho People

    With the file structure, leave types according to your own scheme and collective labour agreement, and the approval flows as they actually run, not as the handbook describes them.

  3. Migrate documents

    From the server to the digital employee file, straight away with the right retention periods and access rights.

  4. Open self-service to employees

    This is the moment the time savings become visible, because HR no longer processes every leave request by hand.

  5. Build the integration with the payroll package

    So the monthly round of changes runs automatically.

  6. Only then expand

    To recruitment, training and AI agents.

Scenario 2: you already have an HR system but are not satisfied

Replacing an existing system is different from starting from scratch. You already have digital files, processes and habits. The switch has to deliver something real.

When you are better off staying put. Is your current system running to your satisfaction, is it well connected to your other software, and do you have no need for recruitment, learning or AI in the same environment? Then switching is a project with no return. The honest advice in that case is: do not do it.

When switching makes sense:

  • Your HR system is cut off from the rest

    You work with Zoho CRM, Zoho Desk or Zoho Projects, but HR sits on an island. Every report that combines people data and business data is manual work.

  • You pay for modules you do not use

    Many HR packages sell an all-in package including payroll, while you have that processed elsewhere. You end up paying twice for the same component.

  • Every change means a quote

    An extra field, a different approval flow or a new report requires the supplier and an invoice. Zoho People is something you can largely configure yourself.

  • You have a recruitment tool next to your HR system

    Two databases, two subscriptions, and candidate data that has to be entered again when someone starts.

  • AI has been bolted on

    Many established HR packages have added AI features that only work within that one module. Agents that can reason across your entire business context require a platform built for that from the ground up.

  • You are growing internationally

    Several countries, several languages and several legal entities in one environment is a point where local packages often fall short.

What such a project looks like

A service provider with one hundred and twenty employees in the Netherlands and Belgium already works with Zoho CRM and Zoho Desk, but has HR in a separate package and recruitment in a third tool. Payroll runs through Loket.nl. The approach:

01

Export the current employee files

And map out which fields and history actually need to come along. Not everything is worth migrating.

02

Run in parallel

Set up Zoho People and Zoho Recruit next to the existing system and let them run in parallel for a while, so you can compare before switching over.

03

Build the integration with Loket.nl

And test it on a small group before moving the whole organisation over.

04

Switch over at one logical moment

Usually right after a payroll run or at the turn of the year.

05

Only then Zoho Learn and the AI agents

Roll them out only once the foundation is in place.

We now handle changes, leave and onboarding without paper and separate spreadsheets. That saves us a lot of admin every month.

Sample quote Real customer quote to follow

What you gain once it is in place

Organisations that set up their HR automation properly usually report the same three effects.

What it does not do: come up with your HR policy. Automation speeds up what you already do. If you are doing the wrong things, you will soon be doing them faster.

  • The administrative burden drops visibly

    Especially around leave, onboarding and the monthly round of changes.

  • Data quality goes up

    Which means reports on staff turnover, absence and staffing levels are undisputed for the first time.

  • HR shifts from executing to advising

    Simply because time is freed up and there are figures on the table the management team can work with.

Twee collega's bekijken samen een klantenportal op een laptop

This is where you start

HR automation does not start with software but with one decision: which system is from now on the single source of truth for your people data. Once that is Zoho People, the rest follows logically: Zoho Recruit at the front, Zoho Learn for knowledge and certification, Zia Agents to take over the executive work, and your existing payroll package at the back where it belongs.

It is that last choice that makes the difference between an HR environment that works and a project that grinds to a halt on Dutch payroll rules that could never have been made to fit.

More about Zoho People
Customer succes manager met headset in gesprek met een klant

Frequently asked questions about HR automation

  • Having recurring HR tasks carried out by software instead of people: onboarding, leave requests, absence registration, document management, appraisal cycles, expense claims and reporting. The goal is not only to save time but also to create a reliable data foundation, because meaningful HR analytics is impossible without automated processes.

  • No, and that is not the intention either. Zoho Payroll exists, but it is not available for the Netherlands. You keep your payroll processing in a Dutch package such as Loket.nl, Nmbrs or a similar system, and connect it to Zoho People so changes flow through automatically and payslips come back in the employee portal.

  • Through the API or the import route of the payroll package in question. Zoho People is the source for personal details, contracts, leave, absence and hours; the payroll package uses them to run payroll and sends payslips back. If there is no usable API, a file exchange or an RPA bot is a workable alternative. There is no ready-made standard connector, so this is always custom work, but custom work that quickly pays for itself in the monthly round of changes.

  • It is not the number of employees that matters, but the number of people keeping the administration and the number of processes with an approval step. In practice things start to pinch at around twenty to twenty-five employees, especially once several managers need to approve leave or statutory retention and certification requirements come into play.

  • Personnel files contain the most sensitive data you hold as an organisation, including absence information that is subject to extra rules. Pay attention to: role-based access so not everyone sees everything, retention periods that expire automatically, full logging of who viewed or changed what, and the location of your data storage. Keeping your salary data in a separate system with its own authorisation structure helps here.

  • They take over the executive and explanatory work: answering employee questions from your own policies and knowledge base, starting and monitoring onboarding tasks, pre-sorting applications, flagging that absence or staff turnover in a team is rising, and preparing reports with an explanation. Because they run inside Zoho, they work with the same permissions as the user they act for, and every action can be traced.

  • For an organisation of up to around fifty employees coming from Excel: a few weeks, most of which goes into cleaning up data and setting up processes. A migration from an existing HR system with a hundred-plus employees, several legal entities and a payroll integration takes several months, including a period in which both systems run in parallel.

  • Then the threshold is low. Zoho People, Recruit and Learn share the same user management, permissions and reporting layer as the rest of your Zoho environment. You can combine people data and business data in a single report (for example revenue per FTE or the staffing of a project team) without exports or integrations.

Want to know what this looks like for your organisation?

Mobile XL sets up HR environments on Zoho and builds the integrations with Dutch payroll packages such as Loket.nl and Nmbrs.

Request a consultationContact us