HR to ERP
Factorial to Dynamics 365 integration: employees from Factorial in Business Central, per entity and with cost centre
With an integration between Factorial and Microsoft Dynamics 365 Business Central, every employee from Factorial reaches the Business Central company of their legal entity, with the cost centre as default dimension and the contract end date. KoppelHet sets out how entities, cost centres and terminations land in Business Central.
What the integration does
Organisations that use Factorial as their HR system and Business Central for finance in several countries want employees per company and with the right cost centre in Business Central, and a departure that shows there in time.
- Factorial reports a new, changed or departing employee; KoppelHet fetches the employee and cost centres.
- The legal entity determines the Business Central company.
- The employee is created or updated, with the cost centre as default dimension.
- A move to another entity terminates the employee in the old company and creates them in the new one.
- On the contract end date the status becomes terminated.
What to watch for with Factorial and Microsoft Dynamics 365
- Business Central keeps its own employee list per company. KoppelHet translates the entity from Factorial into the right company, so an employee of the Spanish entity does not end up in the Dutch company.
- Factorial records cost centres per employee with a percentage and a period. In Business Central the cost centre becomes a default dimension on the employee, and dimension values are read-only in the API. KoppelHet takes the cost centre with the largest percentage and links it to a dimension value finance has already created.
- A move to another entity creates a new contract in Factorial from an effective date, and until that day the employee stays with the old entity. On that day KoppelHet sets an end date in the old Business Central company and creates the employee in the new one, so postings up to the change date stay in the old company.
- Factorial distinguishes the end of the contract and the moment access to Factorial stops. Business Central has an end date and a status. KoppelHet fills the end date with the end of the contract and only sets the status to terminated once that date has passed.
- Factorial sends its own webhook when a termination is reversed. KoppelHet then removes the end date in Business Central and sets the employee back to active, so someone who stays does not disappear from finance's selection lists.
- Factorial distinguishes the work address (email, falling back to the login address) and the personal address (personal_email). Business Central has email and personalEmail for them. KoppelHet keeps the two apart, so finance in Business Central ends up at the work address.
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.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Factorial API (version 2026-10-01) with OAuth 2.0 - employees (legal_entity_id, company_identifier, email, terminated_on), finance/cost_center_memberships (cost_center_id, start_date, end_date, percentage), employee_updates/terminations (contract_end_date, terminated_on), contracts/legal_entity_changes. Webhooks for Employee creates, updates, terminates and unterminates.
- Business Central through API v2.0 per company - employees (number, givenName, surname, email, employmentDate, terminationDate, status Active, Inactive or Terminated) and defaultDimensions with parentType Employee and postingValidation; dimensionValues GET only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in Microsoft Dynamics 365 | Notes |
|---|---|---|
company_identifier | number | |
first_name, last_name | givenName, surname | |
email | email | |
legal_entity_id | Bedrijf (companies) | Lookup table |
cost_center_memberships (hoogste percentage) | defaultDimensions (Employee) | Existing dimension value |
Startdatum contract | employmentDate | |
contract_end_date | terminationDate en status Terminated | |
personal_email | personalEmail | Kept apart from the work address |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll