Payroll integration
Zoho People to Nmbrs integration: HR changes from Zoho People ready for the payroll run
With an integration between Zoho People and Nmbrs, new employees, contract and salary changes and departures go from Zoho People to the right Nmbrs company, with the effective date from the form. The payroll bureau no longer receives lists by email and keeps the Dutch payroll rules in Nmbrs itself.
What the integration does
Companies that use Zoho for CRM and accounting and Zoho People for HR often have a bureau run the Dutch payroll in Nmbrs. Every month an export from Zoho People goes to the bureau, which has to find the differences itself.
- Every fifteen minutes KoppelHet requests the employee records changed since the previous round.
- Per record KoppelHet determines which Nmbrs company the employee belongs to and which fields actually changed.
- New employees arrive in Nmbrs with personal details, IBAN, BSN, employment and hours.
- Salary changes go to the Nmbrs period of their effective date.
- Before the cut-off KoppelHet compares all Dutch employees and reports to the bureau what differs.
What to watch for with Zoho People and Nmbrs
- Zoho People can return records added or changed after a given moment, with that moment in milliseconds. KoppelHet uses the moment of the last processed change as the starting point for the next round, so a change that comes in during a round is not lost.
- Each employee record comes back in full, even if only a phone number changed. KoppelHet compares the record with the previous state and only writes to Nmbrs when a field that matters for the payroll run changes.
- Zoho People has no fixed place for a Dutch legal entity. At the start we agree which field determines the Nmbrs company, for example the location; an employee without that value does not go to Nmbrs but becomes an alert to HR.
- Salary rows with an effective date usually sit in a tabular section of the form. If the effective date falls in a Nmbrs period the bureau has already closed, the bureau gets an alert; KoppelHet does not post back silently.
- Zoho People allows at most two hundred records per request and four hundred requests per minute, with a five-minute lock above that. During the initial load of Nmbrs KoppelHet splits employees over pages and waits between pages, so other Zoho integrations keep working too.
- For this integration KoppelHet only gets read access to forms in Zoho People. Nothing goes back to Zoho People, and an error in the integration cannot change HR data.
- The payroll bureau gives KoppelHet access in Nmbrs only to this employer's companies. Every change is in the platform's logging, so the bureau can look back at what came from Zoho People.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why every fifteen minutes and not immediately?
A webhook from a Zoho workflow is possible too, but a missed notification would then go unnoticed. Fetching every fifteen minutes is fast enough for a monthly payroll run and misses nothing.
What does the bureau still do itself in Nmbrs?
Collective agreement, pension, payroll tax credit and the payroll run. The integration delivers the changes from Zoho People and leaves those settings alone.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Zoho People is read through GET /people/api/forms/employee/getRecords with OAuth 2.0 (header Authorization Zoho-oauthtoken, scope ZOHOPEOPLE.forms.READ), parameters sIndex, limit (at most 200) and modifiedtime (milliseconds). Response with ModifiedTime per record and tabular sections in tabularSections. Threshold of four hundred requests per minute with a five-minute lock; error code 7021 above two hundred records.
- Nmbrs is written through the Nmbrs REST API with OAuth 2.0 and an employer-level login. The SOAP API stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Zoho People | Field in Nmbrs | Notes |
|---|---|---|
EmployeeID | Personeelsnummer | |
Voornaam, achternaam, geboortedatum | Persoonsgegevens | |
Adresvelden | Adres | |
Eigen velden BSN en IBAN | BSN en IBAN | Field names per customer |
Vestiging of juridische entiteit (eigen veld of lookup) | Nmbrs-bedrijf | |
Datum in dienst en vertrekdatum | Datum in en uit dienst | |
Uren per week | Rooster | |
Salarisregel uit de tabelsectie | Salaris met ingangsperiode |
Related
Recruitee → Zoho People
Recruitee to Zoho People integration: hired candidates in the Zoho People employee form
Teamtailor → Zoho People
Teamtailor to Zoho People integration: hired candidates as a record in the Zoho People employee form
Zoho People → Active Directory
Zoho People to Active Directory integration: HR drives the domain account, not the other way round
Zoho People → AFAS Profit
Zoho People to AFAS integration: new hires and changes to Dutch payroll