Extended HR Employee synchronization

HR synchronization scenario is a scenario when you want to keep track or change employee information. Be aware that information that you see as HR could be as broad as possible and affect the payment or the payslip of an employee. This article will provide you with general information about what you will have to take into account. HR applications often store more data of employees than described in the basic employee synchronization scenario. The Partner app is the system of record and employee data is synchronized from the Partner app → Nmbrs. In this case, the employee sync scenario will generally consist of two phases.

When starting with this scenario, we assume that Getting started API is known.

Data and data flow

This integration scenario is a two-way integration.

  1. Initial setup. Employee data is available in Nmbrs, the Partner App or both. Employees between both applications need to be mapped, compared and linked for future changes. The basic employee synchronization scenario can be used for initial mapping.
  2. Future changes. Changes to the employee are inserted in the Partner app and synchronized with Nmbrs. New employees are created in the Partner app and synchronized to Nmbrs. These changes can be made with the following endpoints.



  • employee.info
  • employee.employment
  • employee.orgstructure


  • Create employee
  • Update employee personal info
  • Update employee department
  • Update employee function
  • Update employee address (not introduced yet)



  • PersonalInfo_UpdateCurrent
  • Department_UpdateCurrent
  • Function_UpdateCurrent
  • Address_InsertCurrent
  • Employment_GetAll_AllEmployeesByCompany
  • Contract_GetAll_AllEmployeesByCompany
  • SVW_GetAll_AllEmployeesByCompany
  • Salary_GetAll_AllEmployeesByCompany
  • Schedule_GetAll_AllEmployeesByCompany

See how do I check for mutations for specific methods. 


Knowledge base