Accounts in applications
Nmbrs to Salesforce integration: Dutch employees from Nmbrs as Salesforce users
With an integration between Nmbrs and Salesforce, every new sales or service employee of your Dutch companies in Nmbrs automatically gets a Salesforce user with profile, role and manager. When someone leaves, the user is deactivated on that date and the licence is released, even if the rest of the Salesforce environment is managed globally.
What the integration does
International companies with Dutch entities in Nmbrs and one global Salesforce environment managed by head office often request a Salesforce user for a new Dutch colleague with a ticket to a team abroad. There are sometimes days between joining and a working user, and a departure is only noticed at a periodic check.
- The payroll bureau or HR enters the new employee in Nmbrs, in the right company.
- Nmbrs reports the change and KoppelHet reads employee, employment, job and department.
- If the job belongs in Salesforce, KoppelHet creates the user with profile, role, manager and Dutch language and time settings.
- A change of job or department updates profile and role without involving headquarters.
- On the end date the user is deactivated; their accounts and opportunities stay in their name until they are transferred.
What to watch for with Nmbrs and Salesforce
- The Salesforce environment of an international company holds users from many countries, while Nmbrs only knows the Dutch companies. KoppelHet only manages users with an Nmbrs employee number and leaves colleagues from other countries and headquarters administrators alone.
- Employee numbers in Nmbrs are unique per company, so number 1001 can exist in both entities. In Salesforce the number therefore gets a prefix per company and the company name goes along, so the integration never updates the wrong user.
- When an account manager moves to the other entity, Nmbrs records a termination and a new hire. A new Salesforce user would cost a second licence and leave their accounts with the old user. KoppelHet recognises the move and updates the existing user with the new number and company.
- The name setting in Nmbrs determines whether someone uses their own name or their partner's. When it changes, KoppelHet updates the last name in Salesforce but keeps the username, because Salesforce only accepts a new email address after confirmation.
- Job names in Nmbrs are often set up for the payslip and the collective agreement, with a code in front. A lookup table converts them to a job title and a profile in Salesforce; a job without a rule goes on a list instead of getting a default profile.
- Nmbrs knows the manager's number and name, but not their Salesforce user. KoppelHet looks it up through the employee number; if the manager works at headquarters and is not in Nmbrs, a fixed manager per department that you specify applies.
- Nmbrs holds citizen service numbers, salaries and bank details. The integration only reads employee and employment data with its own employer-level login, so no payroll data ends up in the CRM.
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.
Frequently asked questions
Does headquarters need to do anything for this integration?
Once: create an integration user and connected app in Salesforce, and choose the profiles and roles the Dutch colleagues get. After that it runs without tickets.
Can the payroll bureau trigger the integration by accident?
An employee entered by the bureau only becomes a Salesforce user if the job is in the lookup table. A test entry or a job without Salesforce therefore produces no user or licence.
Do colleagues in other countries go through this integration too?
No, they are not in Nmbrs. If they come from a global HR system, that can become a second source later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and only read scopes for employee and employment data and the company structure, per company, with webhooks on changes. The SOAP API stops on 1 March 2027.
- Salesforce is written through the REST API on the User object, with a connected app (OAuth 2.0) and an integration user with Manage Users. Required on create include Username (unique across all Salesforce environments), Alias (at most 8 characters), Email, LastName, ProfileId, TimeZoneSidKey (Europe/Amsterdam), LocaleSidKey (nl_NL), LanguageLocaleKey and EmailEncodingKey. EmployeeNumber at most 20 characters.
- On departure IsActive = false; if Salesforce refuses, UserLogin.IsFrozen = true and an alert to the administrator.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Salesforce | Notes |
|---|---|---|
Bedrijf en personeelsnummer | EmployeeNumber | With a prefix per company |
Roepnaam | FirstName | |
Achternaam volgens naamstelling | LastName | |
Zakelijk e-mailadres | Email en Username | |
Roepnaam + achternaam (ingekort) | Alias | |
Functie | Title, ProfileId en permission sets | Through a lookup table; Nmbrs codes stripped |
Afdeling | Department en UserRoleId | |
Bedrijf | CompanyName | |
Leidinggevende | ManagerId | Looked up through the manager's employee number |
Datum uit dienst | IsActive |
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