📋 Before you start: This article covers Employee field mapping, which is an optional step within the Nmbrs Payroll integration. Make sure you have first completed the integration setup described in the Nmbrs Payroll integration article.

Configure Employee field mapping

Employee field mapping enables users to map available Nmbrs unsupported fields on Tellent HR. In the integration listing in the section Employee field mapping, on Map employee profile fields, there are multiple sections of fields that can be mapped as such: Basic info, Birth info, Contact info, Partner info, Social security, Bank account, Address, Employment. Each has its subset of employee fields. These are sections and fields coming from Nmbrs, and we provide you with the option to map your tellent HR employee data fields with Nmbrs.

⚠️ Important: Setting a non-required mapped field to empty in Tellent HR will not remove the existing value in Nmbrs. To delete a value, it must be cleared directly in Nmbrs.

Tellent HR custom fields

A Nmbrs section, containing a few custom fields, will be added to your account under Profile fields management upon accepting the terms and conditions to enable field mapping with Nmbrs:

If a field you need is not available in the mapping options, you can create it as a custom field in the employee profile. Go to Settings > Employee data > Profile Fields Management and add the field to the relevant section. It will then appear as a mapping option.

We recommend creating the following custom fields in Tellent HR to map with Nmbrs fields, based on the data you'd like to send to Nmbrs:

Prefix
Initials
Country of birth
Private mobile phone
Other phone
Partner prefix
Partner name
Ascription code
Account description
Bank city
Bank name
House number
House number addition
Seniority date

⚠️ Important: when creating custom fields in Tellent HR, be sure to respect Nmbrs field formats as described below under each field section below.

Map employee profile fields

If you want to keep only the default mapping, you don't need to do anything else.

To map additional fields, first create the Employee type field in profile fields management, then come back to the integration settings to complete the mapping. This field is required by Nmbrs, so without it, you won't be able to save new mappings.

Basic info

This section covers the core employee identity fields. Two fields are required, if either is missing or invalid, the employee will not be created in Nmbrs:

Last name: must not be empty.
Employee type: must match a valid Nmbrs value: Applicant, New Hire, Payroll, Former Payroll, External, Former External, or Rejected Applicant. Defaults to New Hire when no mapping is configured.

Other fields: First name, First name in full, Prefix, Initials, Employee number. Employee number must contain digits only (for example: 42 or 1234). If it contains letters or dashes, Nmbrs will not accept it, and the field will be left blank.

Birth info

Maps birth-related fields to Nmbrs. Available fields: Date of birth, Country of birth, Nationality, Gender.

⚠️ Important: For Gender, only Male, Female, and Unspecified are accepted by Nmbrs. An unrecognized value will be forwarded as-is and may cause an error.

For the Country of birth: provide country ISO codes like NL (Netherlands 🇳🇱), DE (Germany 🇩🇪), FR (France 🇫🇷), GB (United Kingdom 🇬🇧), PL (Poland 🇵🇱).

Contact info

Maps employee contact details. Available fields:

Private email → Personal email
Business email → Account email
Business phone → Work phone 1
Business mobile phone → Work phone 2
Private phone → Personal phone
Private mobile phone
Other phone

Partner info

Maps partner-related fields. Available fields: Partner prefix, Partner name, Ascription code, Marital status.

Note: Ascription code is a Dutch legal code that determines how an employee's surname is displayed after marriage or registered partnership (for example, own name only, partner's name only, or a combination of both). It must contain digits only; if it contains letters or other characters, Nmbrs will not accept it, and the field will be left blank. This section is skipped if no data is provided.

We recommend providing the Marital Status in the Nmbrs section of the employee profile:

Social security

Contains one field: Social security number (required when mappings are configured), mapping to Insurance number in Tellent HR. If empty, the section is skipped.

⚠️ Important: This section is non-blocking: if the bank account is invalid, the bank account is skipped, but the employee is still created.

Bank account

This section maps the bank account details with Nmbrs standard bank type. The only required field is IBAN → Account number in Tellent HR.

Other fields: Account number, Account description, Bank city, Bank name, Bank account type.

⚠️ Important: This section is non-blocking: if the bank account is invalid, the bank account is skipped, but the employee is still created.

Address

This section maps the employee's Home address. Three fields are required: Street, City, and Country.

Other fields: House number, House number addition, Postal code, State / Province (→ County in Tellent HR).

⚠️ Known limitation: Address data only syncs correctly when field mappings are configured. For quality standards, it is recommended to have the address section fully completed and mapped.

⚠️ Important: This section is non-blocking: if the address is invalid, the sync is skipped, but the employee is still created. It can be resynced afterward.

Employment

Contains 4 fields: Start date, Seniority date, End of service date, End reason. The start date is required to properly create an employee, but the rest of the fields can stay empty. And to properly end an employment, you’ll need to provide both an end date and an end reason.

⚠️ Important: This section is non-blocking: if the start date is not available, this section is skipped, but the employee is still created. It can be resynced afterward.

Field reference

The following fields are mapped automatically by the system:

Tellent HR field	Nmbrs field	Required	Example data	Notes
Employee number	Employee Number	No	6	Employee number field
First name	First name	Yes	Thomas
First name	First name in full	No	Thomas
Last name	Last name	Yes	de Ruiter
Employee type	Employee type	Yes	New Hire	Newly created (Nmbrs Section)
Date of birth	Date of birth	No	12-03-1986
Gender	Gender	No	Male	Male/Female/Unknown
Nationality	Nationality	No	NL	ISO code format
Account email	Business email	No	thomas.de.ruiter@demo.nl
Work phone 1	Business phone	No	0625262728
Work phone 2	Business mobile phone	No
Personal phone	Private phone	No
Marital status	Martial status	No	Single
Social Security Number	Social Security Number	Yes	190757772
Personal email	Private email	No	thomas.de.ruiter@private.nl
Work email	workEmail	No
Employment start	startDate	Yes	01-01-2021	Employment field
Account number	IBAN	Yes	IBAN NL91 ABNA 0417 1643 00	Bank account field
Street	Street	Yes	Scheldestraat	Address field
City	City	Yes	Amsterdam	Address field
Postal code	Postal Code	No	1078GK	Address field
County	State / Province	No	Noord-Holland
Country	Country	Yes	NL	ISO code format
Employment end	End of service date	No
End of service reason	End reason	No

FAQs

General

How do I access the field mapping settings?

Go to Settings > Configuration > Integrations > Apps > Nmbrs , select your connection, and open the Employee field mapping tab.

What sections are available for field mapping?

Nmbrs organizes employee fields into eight sections: Basic info, Birth info, Contact info, Partner info, Social security, Bank account, Address, and Employment. Each section contains specific Nmbrs fields you can map to Tellent HR employee profile fields.

Field mapping

Which fields are required for an employee to sync to Nmbrs?

The required fields are: Last name, Social Security Number, Employment start date, IBAN, Street address, City, and Country. If any of these is missing or invalid, the employee will not be created in Nmbrs.

What is "Employee type" and which values are accepted?

Employee type must match a valid Nmbrs value: Applicant, New Hire, Payroll, Former Payroll, External, Former External, or Rejected Applicant. When no mapping is configured, it defaults to New Hire.

If I clear a mapped field in Tellent HR, will the value also be removed in Nmbrs?

No. Setting a non-required field to empty in Tellent HR will not remove the existing value in Nmbrs.

What gender values does Nmbrs accept?

Nmbrs only accepts Male, Female, and Unspecified. If you use a different value, Nmbrs may not accept it, and an error could occur.

Are all fields in the Field reference table required?

No — only fields marked "Yes" in the Required column must be present. Fields marked "No" are optional; the employee can still sync to Nmbrs without them.

Can I map custom Tellent HR fields to Nmbrs?

Yes. First create the corresponding Employee fields in Profile Fields Management, then return to the integration settings to complete the mapping.

What happens if I only configure mappings for some sections?

If you set up field mappings for some sections (for example, Basic info or Bank account) but leave other sections unconfigured, those unconfigured sections are completely skipped — no data is sent for them, even if the employee has that data in Tellent HR. For example, if you configure Bank account mappings but leave Address unconfigured, the employee's address will not sync to Nmbrs at all. To make sure all data is sent correctly, configure mappings for every section you want to use.

I've updated the IBAN and address, but the changes aren't showing in the Employee record in Nmbrs. Why?

If you have updated the IBAN and address in Tellent HR and synced it with Nmbrs, make sure to select the most recent period in Nmbrs to see the update:

Nmbrs Employee field mapping