HR to ERP
Rippling to Dynamics 365 integration: Rippling workers as employees with department dimension in Business Central
With an integration between Rippling and Microsoft Dynamics 365 Business Central, every worker from Rippling becomes an employee in the Business Central company of their legal entity, with job title, work email and the department as default dimension. A termination in Rippling sets the employee in Business Central to terminated, with the end date included.
What the integration does
Organisations that use Rippling for HR and Dynamics 365 Business Central for finance and projects add employees to Business Central by hand, company by company. Department changes in Rippling then do not reach the dimensions, and postings on departed employees remain possible.
- Every hour KoppelHet fetches the changed workers, with legal entity and department.
- Per worker KoppelHet picks the Business Central company; each company has its own API path.
- The employee is created or updated on the stored ID.
- The department goes along as default dimension, if that value exists in Business Central.
- On a termination KoppelHet fills the end date and sets the status to terminated.
What to watch for with Rippling and Microsoft Dynamics 365
- The employee resource in the Business Central API has no field for department or manager. KoppelHet therefore puts the department from Rippling as default dimension on the employee, so postings and time entries on that employee get the department automatically. The manager stays in Rippling.
- Dimension values are read-only in the Business Central API. KoppelHet therefore cannot create a new department from Rippling in Business Central itself. KoppelHet then creates the employee without that dimension and asks finance to add the value; the dimension follows in the next run.
- Every Business Central company has its own employee list and its own path in the API. Rippling links each worker to a legal entity. KoppelHet translates the legal entity into the right company; if someone moves to another entity in Rippling, they are terminated in the old company and created in the new one.
- On a termination Rippling records the type, including offer declined, rescinded or reneged. Business Central has inactive as well as terminated. KoppelHet sets an employee who never started to inactive without end date, so turnover figures in Business Central only count real leavers.
- A new job title in Rippling has its own effective date, which can fall after the day the change was entered. Business Central only keeps the current job title. KoppelHet only updates the job title on the effective date from Rippling, so documents show the old title until that day.
- Rippling returns the employee number as a number, while an employee's number in Business Central is a code field that also allows letters. KoppelHet takes the number from Rippling unchanged, so finance and HR look at the same number, and checks beforehand that it is still free in the target company.
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 this also work with Dynamics 365 Finance?
This page assumes Business Central. For Dynamics 365 Finance we choose the right interface at the start.
Do hours or payroll costs go along?
Not in this integration. They can be added 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.
- Rippling through the REST API - List workers with filter on updated_at, expand on user, legal_entity and department, limit up to 100 with cursor; fields number (integer), status, start_date, end_date, title, title_effective_date, work_email and termination_details.type (including OFFER_DECLINED, RESCIND, RENEGE). Scope workers.read.
- Business Central through API v2.0 per company - employees (number, givenName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated; no field for department or manager) and defaultDimensions with parentType Employee and postingValidation (Code_Mandatory, Same_Code, No_Code). dimensionValues GET only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in Microsoft Dynamics 365 | Notes |
|---|---|---|
number | number | Text field in Business Central |
user (naam) | givenName, surname | |
work_email | email | |
legal_entity (expand) | Bedrijf (companies) | Lookup table |
title (title_effective_date) | jobTitle | |
department (expand) | defaultDimensions (Employee) | Existing dimension value |
start_date | employmentDate | |
end_date en status TERMINATED | terminationDate en status Terminated |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension