Payroll integration
SuccessFactors to Nmbrs integration: HR changes straight into payroll
With an integration between SAP SuccessFactors and Nmbrs, new employees, contract changes, salaries, allowances and bonuses of the Dutch entities reach the right Nmbrs company automatically. Every change keeps its effective date from SuccessFactors, and payroll no longer pulls anything from reports or emails.
What the integration does
Anyone using SAP SuccessFactors Employee Central for HR and Nmbrs for Dutch payroll, with a separate Nmbrs company per legal entity, pulls changes from Employee Central reports and enters them by hand. Bonuses and allowances arrive by email.
- HR records a hire, job or pay change in SuccessFactors.
- KoppelHet picks up the change and uses the legal entity to decide which Nmbrs company the employee belongs to.
- A new employee then appears in that company, with address, bank account, contract and schedule.
- Salary and recurring allowances reach Nmbrs as fixed wage components, one-off payments as a variable component in the right period.
- An end date in SuccessFactors sets the end date in Nmbrs. Payroll sees errors per company in the KoppelHet platform.
What to watch for with SAP SuccessFactors and Nmbrs
- Nmbrs keeps fixed and variable wage components apart. Recurring pay from SuccessFactors becomes fixed components that run until stopped; one-off payments only apply in the pay period.
- A group with several Dutch entities has one Nmbrs company per entity. The legal entity in SuccessFactors decides which Nmbrs company the change lands in.
- If an employee moves between Dutch entities, in Nmbrs that is a termination at one company and a new hire at the other. KoppelHet performs both on the same date.
- SuccessFactors records the time of each change with a time zone. KoppelHet uses that, so a change around midnight does not slip between two rounds.
- Nmbrs retires its old integration method on 1 March 2027. We build new Nmbrs integrations on the new one straight away.
- Payroll tax credit and pension are only in SuccessFactors when the Dutch country fields are set up. Otherwise they stay in Nmbrs and the integration does not overwrite them.
- Salary in SuccessFactors is often an annual amount. KoppelHet converts it to the monthly amount Nmbrs expects, taking the contracted hours into account.
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
Are employees from other countries included?
No. The integration only includes the Dutch entities.
Can payslips go back to SuccessFactors?
That is a separate flow we look at per customer. By default this integration runs from SuccessFactors to Nmbrs.
What if a pay component has no counterpart in Nmbrs?
Payroll first creates the wage component in Nmbrs. Until then the change waits with a notification in the platform.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SuccessFactors Employee Central is read through the OData API on lastModifiedDateTime (with time zone offset). Entities PerPerson, PerPersonal, PerNationalId (country NLD), EmpEmployment, EmpJob (company, standardHours, costCenter), EmpPayCompRecurring and EmpPayCompNonRecurring.
- Nmbrs is written through the Nmbrs REST API; the SOAP API is retired from 1 March 2027. Dutch tax fields only through country-specific fields.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Nmbrs | Notes |
|---|---|---|
PerPerson.personIdExternal | Personeelsnummer | |
PerNationalId.nationalId (country NLD) | BSN | |
PerPersonal.firstName, lastName | Voornaam, tussenvoegsel, achternaam | |
EmpEmployment.startDate | Datum in dienst | |
EmpJob.company | Nmbrs-bedrijf | Each Dutch legal entity maps to one Nmbrs company |
EmpJob.standardHours | Rooster (uren per week) | |
EmpPayCompRecurring | Salaris en vaste looncomponenten | Per pay component a translation to an Nmbrs wage component |
EmpPayCompNonRecurring | Variabele looncomponent | |
EmpJob.costCenter | Kostenplaats | |
EmpEmployment.endDate | Datum uit dienst |
Related
Ashby → SAP SuccessFactors
Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central
Bullhorn → SAP SuccessFactors
Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central
Carerix → SAP SuccessFactors
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
Greenhouse → SAP SuccessFactors
Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central