Payroll integration
Sympa to Nmbrs integration: HR changes from Sympa to Dutch payroll
With an integration between Sympa and Nmbrs, new employees, contract and salary changes and terminations of the Dutch entity go from Sympa to Nmbrs, with the right effective date and without double entry. KoppelHet only includes approved rows, also with multiple Nmbrs companies, your own pay components and changes with a validity period.
What the integration does
Anyone using Sympa for HR and having Dutch entities paid in Nmbrs, often by an accounting firm, retypes new employees and pay rises. A rise still awaiting approval in Sympa sometimes already ends up in the payroll run.
- HR records a new employee or change in Sympa for a Dutch BV.
- KoppelHet reads the changed employees and only includes approved rows.
- Per BV KoppelHet puts the employee into the right Nmbrs company, with the effective date from Sympa.
- Salary components go to the pay components in Nmbrs through a lookup table.
- Before the cut-off KoppelHet checks that everything is processed and reports what could not go through.
What to watch for with Sympa and Nmbrs
- With two Dutch BVs that are each a Nmbrs company of their own, KoppelHet splits employees per BV over the right companies.
- Payslips, annual statements and the calculated hourly wage are in Nmbrs. KoppelHet can put selected data back into Sympa, for example the payslip in the record, if you want.
- A Sympa interface may make one hundred API calls per hour by default. For an initial load or a collective pay rise for hundreds of employees that takes hours. KoppelHet schedules such a large delivery outside office hours and checks afterwards that everything arrived.
- Working hours and salary can have a validity period in Sympa and wait for approval. KoppelHet only includes approved rows and puts them in the Nmbrs period in which the effective date falls, so a raise from the first of the month is paid in that period.
- A Sympa environment for multiple countries does not know Dutch payroll concepts such as the payroll tax credit, collective agreement or pension scheme. The payroll bureau fills those in Nmbrs, and KoppelHet does not overwrite them.
- Each organisation sets up salary components in Sympa itself. A lookup table links them to pay components in Nmbrs; a new component without an agreement becomes an alert to payroll instead of a silent pay line.
- The payroll bureau gives the integration access to your companies only in Nmbrs. The bureau's other clients stay out of view.
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
What stays with the payroll bureau?
Collective agreement, payroll tax credit, pension and the payroll run itself. The integration delivers the HR changes and does not overwrite those settings.
What about audit logging, GDPR and our integration platform?
Every change is in the audit logging of the KoppelHet platform, so payroll and the auditor can see what was passed on when. You are the controller and KoppelHet is the processor, under a data processing agreement; the Sympa interface only contains the fields in the design. An existing integration platform is left alone.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Sympa through the Sympa Integration API (OData v4) on its own interface with X-ApiKey, with $filter on modified and the entity, valid table rows with since, until or at, and approved rows through $expand with Approval eq 5.
- 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 Sympa | Field in Nmbrs | Notes |
|---|---|---|
Personeelsnummer | Personeelsnummer | |
Voornaam, achternaam, geboortedatum | Persoonsgegevens | |
Adres | Adres | |
Bankrekening | IBAN | |
Entiteit | Nmbrs-bedrijf | One Nmbrs company per Dutch BV |
Startdatum en einddatum dienstverband | Dienstverband (in en uit dienst) | |
Werktijd (tabelregel met geldigheid) | Rooster en uren per week | |
Salaris (tabelregel met geldigheid) | Salaris met ingangsperiode | |
Kostenplaats | Kostenplaats | |
Salariscomponent | Vaste looncomponent | Through a lookup table |
Related
Greenhouse → Sympa
Greenhouse to Sympa integration: hired candidate as a data card with contract row in Sympa
Recruitee → Sympa
Recruitee to Sympa integration: hired candidates as a data card in Sympa
SmartRecruiters → Sympa
SmartRecruiters to Sympa integration: ready to onboard becomes a data card in Sympa
Sympa → 4PS Construct
Sympa to 4PS Construct integration: fitters of the Dutch employer from Sympa in 4PS, with cost centre as a dimension