Custom HR Office integration development
Appfront builds custom HR Office integrations that connect your HR administration with payroll, ATS, accounting, SSO and onboarding. Via the HR API and webhooks, we synchronise employee changes, leave, sickness absence and terms of employment in both directions, with an audit trail, conflict resolution and GDPR-compliant data minimisation. Your HR team enters changes once, and all connected systems stay accurate.
What is an HR Office integration?
HR Office is a Dutch HRIS (HR Information System) that organisations use for personnel administration, leave and sickness absence registration, basic salary data, onboarding/offboarding and performance reviews. For most SMEs, HR Office is the source of truth for who is employed, on what terms and in which role — but it is almost never the only system that deals with those employees.
In practice, a custom integration means that new employees flow automatically from HR Office to your payroll provider, get an account in Microsoft Entra or Okta, are enrolled in your onboarding platform and appear in your accounting as a payroll cost item. Changes (salary increase, contract change, leaving employment) flow in both directions, and HR Office remains the central source of truth for who is allowed what and who earns what.
Appfront builds these integrations on a GDPR-first principle: only the necessary fields per target system, documented purpose limitation, an audit trail of every PII change and clear agreements on the source of truth. Also see our broader approach to API integrations and our integration services.
One source of truth for your employees
HR Office is leading for personal and contract data. Changes made there flow, verified, to payroll, IAM, ATS and accounting — no duplicate entry and no drift between systems.
Leave and absence synchronised
Leave requests, sickness reports and reintegration milestones are synchronised with time registration, payroll and workforce planning. No more separate Excel trackers or manual handovers.
GDPR with an audit trail
Every PII movement between systems is recorded: what was sent, where to, why (purpose limitation) and who changed it. In the event of a data breach or a query from the Dutch Data Protection Authority, your record of processing activities is watertight.
Our development process for HR Office integrations
We work to a method that puts the most sensitive decisions first: which system is the source of truth for which field, which data may and may not be passed on, and who sees what. From that analysis through to go-live and ongoing management, every step is aimed at an integration your HR team can understand themselves and that the Dutch Data Protection Authority has no reason to worry about.
We map out which employee fields live in which system, what the source of truth is per field, and which data may or may not be synchronised for GDPR reasons.
We design the event flows, choose between real-time and batch, record the purpose limitation per field and define a retry and error-handling strategy.
Implementation with idempotency keys, structured logging, an audit trail and monitoring. You see working integrations per target system along the way.
A controlled go-live per integration with data validation and a safety net, followed by ongoing management, monitoring and proactive further development.
What an HR Office integration delivers in practice
Every HR Office integration is set up specifically for your adjacent systems, your payroll vendor, your ATS and the way your organisation handles onboarding and offboarding. Below are the features we deliver most often for organisations that use HR Office as their central HRIS.
HR Office to payroll
Integration with NMBRS, Visma-Loon, ADP or Loket: basic salary data, contract changes, absence updates and cost centre assignments flow automatically to the payroll administration. No more Excel exchanges at every month-end close.
HR Office to ATS
A seamless handover from Recruitee, Homerun or BambooHR to HR Office on hire: candidate data, contract type, start date and cost centre are transferred once. Hire events trigger the rest of the chain — payroll record, email account, onboarding.
SSO and account provisioning
When someone joins, HR Office automatically triggers an account in Microsoft Entra or Okta with the right groups, licences and application permissions for their role. When someone leaves, the account is deactivated within minutes, so no more forgotten accounts.
Onboarding flows
A new employee in HR Office automatically starts an onboarding journey in Appical or a custom onboarding app: welcome emails, tasks for the manager and IT, identity-verification forms and a first-day checklist, all triggered by a single hire event.
Accounting integration
Payroll costs, holiday pay accruals, cost-centre allocation and pension contributions flow from HR Office (or the payroll layer) to Exact, Twinfield or AFAS. Month-end closes become predictable and the finance department stops double-checking figures.
Time tracking & workforce
Reconcile hours from Mtime, Uren.nl or a custom tool with contract hours in HR Office, and sync leave balances with workforce planning in Quinyx or Ortec. Manager dashboards show in real time who is working where, on which contract and with what balance.
Typical use cases in practice
An HR Office integration looks very different from one organisation to the next. We see a few patterns come up again and again, and for each of them we have a working setup that pays attention to field mapping, GDPR purpose limitation and proper retry and error handling.
SMEs with a growing payroll administration
Organisations growing beyond 50 employees that can no longer cope with exchanging Excel files between HR and payroll. Salary changes, contract amendments and sickness absence reports flow automatically from HR Office to NMBRS, Visma Loon or Loket, with no more monthly hand-over. See also our API integrations.
Recruitment-to-payroll chain
Companies with their own ATS, often Homerun, Recruitee or a custom recruitment platform, that want to automate the transition from candidate to employee. On hire, the data flows from the ATS to HR Office and from there to payroll, SSO and onboarding, with no double entry or forgotten accounts.
Healthcare and municipal organisations
Sectors with strict GDPR requirements around sickness absence, reintegration and special categories of personal data. We build integrations that document the purpose limitation per field, send only the necessary data between systems and deliver an auditable record of processing activities, in line with Dutch Data Protection Authority requirements.
Multi-location organisations
Companies with multiple sites, changing roster locations and arrangements set by collective labour agreements (CAO). HR Office consolidates the personnel administration centrally; integrations ensure that workforce management, time tracking and payroll apply the right rules per location and CAO.
Technology we use
We build HR Office integrations using the REST API and webhooks of your HRIS, combined with the backend stack that suits you. The exact choice depends on your payroll vendor, ATS and IAM provider, so that your own team can manage or further develop the integrations.
If you recruit with the Ubeeo recruitment system and want hired candidates to flow automatically into your HR system, take a look at our Ubeeo integration.
If you want to record per employee which information about terms of employment has been provided, take a look at our file on the obligation to inform employees about their terms of employment.
If you work with Buddee instead of this package, take a look at our page on a Buddee integration.
Why Appfront for your HR Office integration?
Appfront has extensive experience building HRIS and payroll integrations for SMEs in the Netherlands. We always begin with a thorough analysis of the existing systems, processes and GDPR implications, because an HR integration must be not only technically sound but also legally defensible and functionally valuable.
For less critical scenarios we often recommend an iPaaS solution such as Zapier or Make. But once the GDPR risk becomes high, the volume large, or the logic complex (multiple systems, conflict resolution, audit requirements), iPaaS falls short. That is when we build custom middleware that follows your situation rather than the other way round.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
Also see our broader services around API integrations, middleware, custom software and the wider integrations page.
- Experience with HRIS integrations and payroll providers in the Netherlands
- Specialist in event-driven sync (hire, mutate, terminate)
- Familiar with source-of-truth mapping per field
- GDPR-first design: purpose limitation, data minimisation, audit trail
- Secure by default: API key rotation, webhook signature validation
- Idempotency, retries and dead-letter queues from day one
- Honest advice: iPaaS where it works, custom where it has to be
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing IT landscape
Security and privacy in HR Office integrations
HR data is among the most sensitive personal data within an organisation. Salary information, sickness absence, reintegration reports and contract details also partly fall under special category personal data. Appfront builds every HR integration to the OWASP ASVS standard and a GDPR-first principle. Among other things, that means API keys in secure vaults, webhook signature validation, scoped OAuth permissions and regular audits of data flows.
For every field that travels between two systems, we document the purpose limitation: why this data may go from A to B, on what legal basis, and how long it is retained. The resulting audit trail serves as evidence in your record of processing activities and helps you with any questions from the Dutch Data Protection Authority or in the event of a data breach.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant data processing and data minimisation per field
- Purpose limitation documented per integration direction
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable PII changes
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management following best practices
- Documentation for your record of processing activities
Frequently asked questions about HR Office integrations
Answers to the questions we get asked most often about HR Office integrations.
We regularly integrate HR Office with payroll providers such as NMBRS, Visma-Loon, Loket and ADP; with ATS platforms such as Recruitee, Homerun and BambooHR; with SSO/IAM solutions such as Microsoft Entra and Okta; with accounting packages such as Exact, Twinfield and AFAS; and with onboarding, workforce and time-tracking tools. Which system sits on the other side mainly determines how much custom work the middleware layer needs; the approach and the GDPR foundation stay the same.
That depends on the type of event and its sensitivity. We usually build hire and terminate events (account creation in SSO, payroll record) in real time via webhooks, so a new employee can log in straight away. Salary changes going to payroll can run in batches at month-end close, because the payroll run waits for that anyway. Absence notifications go to workforce planning in real time, with periodic reconciliation to accounting. We make that choice explicit for each flow, together with your HR and finance team.
Source-of-truth conflicts are by far the biggest pitfall in HR integrations. For each field we define which system is leading: HR Office is usually the source for personal, contract and role data; payroll is leading for gross salary history and cumulative figures; SSO is leading for account status and groups. If a change is made in a non-leading system, it triggers either a warning or a forced override towards the leading system, depending on what is legally and operationally correct. No implicit "last update wins" logic.
For each integration direction, we document which fields are exchanged and why (purpose limitation). Fields that the target system doesn't need are not sent, even if the API accepts them. Special-category personal data (such as reasons for absence) is only transferred where legally required and with an explicit legal basis. Every mutation is recorded in an audit log with a timestamp, source system, target system and the fields changed (not the values themselves, to prevent logging leaks). This material feeds directly into your record of processing activities.
For simple, linear integrations between two systems, iPaaS works well and we'll recommend it. It becomes too limited as soon as the volume gets too high for Zapier tasks, the logic branches across more than two systems, conflict-resolution rules are needed, GDPR purpose limitation must be visible per field, or you need retry/idempotency guarantees that iPaaS doesn't reliably offer. Custom middleware costs more upfront, but avoids the creeping maintenance problem that makes iPaaS flows unmanageable after a year.
With almost every HRIS integration, we run into a field that exists in the source or target system but is missing or limited in the API. We then choose between three options: an intermediate layer that manages the data outside the API (for example custom fields or an extension table), a temporary manual step that is explicitly documented in the process, or talking to the vendor about extending the API. We always document which fields travel outside the standard API, never hiding them.
The cost is determined by the number of systems to be integrated, the complexity of the field mapping, the GDPR requirements (a municipality or care organisation is stricter than the average SME), the required sync frequency and the amount of custom work in the conflict resolution. Ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.
Yes. Appfront regularly takes over existing HR integrations, even if they were originally set up by another party or via an iPaaS. We review the data flows, error handling, GDPR documentation and monitoring, document how things currently work and draw up improvement proposals. From that point on, we can handle changes, extensions and ongoing maintenance, including timely API key rotation and periodic security checks.
Talk to us about your HR Office integration
Tell us which systems you want to connect to HR Office (payroll, ATS, SSO, accounting, onboarding) and which processes still run manually or via Excel today. We're happy to help think through field mapping, source of truth and GDPR purpose limitation. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.