Decathlon
Retail
Decathlon Netherlands uses Nmbrs as the HR source for SailPoint, so identities and access in the global IAM platform match the Dutch personnel records. A second integration brings employees into Shuttel for business mobility.
Identity and access management
Nmbrs to SailPoint integration: Dutch personnel records as the IAM source
With an integration between Nmbrs and SailPoint, SailPoint knows new, changed and departed Dutch employees from Nmbrs in time, so access to systems is granted automatically and revoked on the last working day. SailPoint only receives the data it needs for roles, no salary or BSN.
What the integration does
International organisations that manage access worldwide in SailPoint while the Dutch personnel records are in Nmbrs do not know new Dutch colleagues in SailPoint in time. A departure in Nmbrs only reaches SailPoint through a manual report, and roles that rely on department and job are wrong for the Dutch employees.
- Payroll processes a new employee in Nmbrs.
- KoppelHet completes what SailPoint requires, such as a unique username and a work email address, and checks that nothing is missing.
- SailPoint collects the data and creates or updates the employee's identity.
- Based on start date, department and job, SailPoint grants the right access in the connected systems.
- After the end date SailPoint revokes access. KoppelHet reports employees that SailPoint would reject in advance.
What to watch for with Nmbrs and SailPoint
- SailPoint requires a username, work email address and surname for every identity. Nmbrs often has no business email for a new employee yet. KoppelHet completes it according to the agreed naming rule, otherwise SailPoint rejects the identity.
- A global organisation has several HR sources in SailPoint. The priority of the Nmbrs source decides which source wins if someone also appears as an employee elsewhere.
- Employee numbers in Nmbrs are unique per company, not across the environment. With several Dutch companies KoppelHet makes the username unique with a company code, because SailPoint rejects duplicates.
- SailPoint reads the data at fixed moments, not when Nmbrs changes. A departure therefore works with a date; access lapses once the end date has passed, even if it was in Nmbrs weeks earlier.
- SailPoint does not need to write anything back to Nmbrs. KoppelHet delivers the data in a form a standard SailPoint source can read, so the SailPoint team does not have to build its own Nmbrs integration.
- Nmbrs is a payroll package with BSN, salary and bank details. Only the data needed for roles and joining and leaving goes to SailPoint, so the global IAM platform holds no Dutch payroll data.
- Roles in SailPoint are usually defined globally, while job names in Nmbrs are Dutch. A lookup table maps each Nmbrs job to the job code that the SailPoint roles use.
This integration is also part of joiner, mover, leaver.
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.
Price indication · Basic
Customer case
How it runs at Decathlon
How these organisations use the integration. The configuration differs for each customer.
Frequently asked questions
Who manages what, the SailPoint team or KoppelHet?
The SailPoint team manages roles and rules in SailPoint. KoppelHet makes sure the Nmbrs data is complete and ready on time, and reports it when something is missing.
What if the manager works in another country?
They are then not in Nmbrs. We agree how SailPoint finds the manager, for example through the email address.
Does this also work for Shuttel or other systems?
Yes. The same Nmbrs source can also go to Shuttel for business mobility. That is a separate integration.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- The target is SailPoint Identity Security Cloud. KoppelHet offers the data as an authoritative source, as a flat file (read and aggregate only) or through the Web Services connector for REST.
- Required attributes uid (User Name), email (Work Email) and lastname; a missing or duplicate attribute causes an identity exception. Every identity belongs to exactly one identity profile; the profile priority decides which source wins.
- The identity profile maps the attributes to identity attributes and calculates the lifecycle state from start and end date with a transform.
- Nmbrs is read through the Nmbrs API, without BSN and salary.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in SailPoint | Notes |
|---|---|---|
Personeelsnummer met bedrijfscode | uid (User Name) | Must be unique; a duplicate uid causes an identity exception |
Zakelijk e-mailadres | email (Work Email) | Required in SailPoint; empty for many new employees |
Achternaam volgens naamstelling | lastname | |
Roepnaam | Identity attribute voor voornaam | |
Functie | Identity attribute voor functie | Basis for roles |
Afdeling | Identity attribute voor afdeling | |
Leidinggevende | Identity attribute voor manager | Reference to the manager's uid |
Nmbrs-bedrijf | Identity attribute voor entiteit | |
Datum in dienst en datum uit dienst | Lifecycle state via transform |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll