HR to ERP
Cezanne HR to Exact Online integration: cost centres per Dutch CompanyCode in Exact and a worklist for employees
With an integration between Cezanne HR and Exact Online, the cost centres that Dutch employees use in Cezanne are automatically in the Exact division of their CompanyCode, with code and name from Cezanne. New employees, leavers and cost centre changes go on a worklist for the administrator, because Exact Online only lets an integration read employees.
What the integration does
Organisations with HR in Cezanne and Dutch employers that book in Exact Online keep cost centres in two systems. A cost centre HR links to an employee in Cezanne is missing in Exact until finance finds out itself.
- Every hour KoppelHet reads the changed employments and cost centre deployments from Cezanne.
- Only employments at a Dutch CompanyCode continue, each to the Exact division of that code.
- KoppelHet creates a cost centre that is in use there but missing in Exact.
- New employees, leavers and cost centre changes go on the worklist; after the change in Exact the line disappears.
What to watch for with Cezanne HR and Exact Online
- Every employment in Cezanne belongs to an employer through a CompanyCode. In Exact every employer has its own division, with its own cost centres. KoppelHet links every Dutch CompanyCode to one division; employments at a British or Irish code stay outside the integration.
- The cost centre list in Cezanne can only be read through the API and does not belong to one CompanyCode. If KoppelHet took over the whole list, cost centres from other countries would end up in Exact. KoppelHet therefore only creates cost centres that Dutch employees of that division actually use.
- A cost centre in Cezanne has a validity, with 2999-12-31 as end date while it runs. Exact has an end date on a cost centre after which it is inactive. KoppelHet transfers a real end date from Cezanne and leaves out the year 2999, so old postings remain and no new ones are added.
- Cezanne can split an employee across several cost centres, with a working time percentage and one primary cost centre. An Exact department has one cost centre. KoppelHet compares the primary cost centre with that of the employee's Exact department and puts a difference on the worklist.
- A cost centre deployment in Cezanne has an effective date and a reason, such as a new hire. KoppelHet puts a change on the worklist with that effective date. Finance thus adjusts the department in Exact from the day the employee actually moves.
- Records in Cezanne carry a last modified date, and the OData service filters on it. Every hour KoppelHet only requests the changed employments and deployments. Webhooks only exist with People PLUS+; without that package the integration works on this hourly request.
- Cezanne's API only shows what the integration user may see on screen. An integration user who only sees the Dutch employers keeps employees and cost centres of other countries out of the integration, even if the filters are ever set wrong.
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
Why does KoppelHet not create the employee in Exact itself?
Exact Online's REST API only lets employees be read. KoppelHet therefore prepares everything on the worklist and checks the result at the next comparison.
Does the split across several cost centres go along?
No, only the primary cost centre counts for the comparison. The split stays in Cezanne and payroll.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Cezanne HR through the OData data service (JSON) with OAuth 2.0 and $filter, $select, $top, $skip and $orderby. Employments (PersonCode, CompanyCode, PrimaryEmployment, HireDate, TerminationDate with 2999-12-31 for an ongoing employment), CostCentres (read-only; CostCentreCode, CostCentreName, EffectiveFrom, EffectiveTo, ParentCostCentreCode) and CostCentreDeployments (PersonCode, EffectiveFrom, EffectiveTo, PrimaryCostCentre, CostCentreCode, WorkingTimePercentage, DeploymentReason, LastModifiedDate). Webhooks only with People PLUS+.
- Exact Online through the REST API with OAuth, per division. hrm/Costcenters with GET, POST, PUT and DELETE (Code and Description mandatory, EndDate for inactive, code only changeable by recoding). payroll/Employees (Code, StartDate, EndDate, Manager) and hrm/Departments (Code, Costcenter) GET only. API limits per minute and per day per division.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Cezanne HR | Field in Exact Online | Notes |
|---|---|---|
Employments.CompanyCode | Division | Only Dutch codes, through a table |
CostCentres.CostCentreCode | Costcenters.Code | |
CostCentres.CostCentreName | Costcenters.Description | |
CostCentres.EffectiveTo | Costcenters.EndDate | Not for 2999-12-31 |
PersonCode | Employees.Code (vergelijking) | |
CostCentreDeployments (PrimaryCostCentre) | Departments.Costcenter (vergelijking) | |
HireDate en TerminationDate | Employees.StartDate en EndDate (vergelijking) |
Related
Cezanne HR → Active Directory
Cezanne HR to Active Directory integration: domain accounts per employer and location
Cezanne HR → ADP iHCM
Cezanne HR to ADP iHCM integration: compensation, single payments and leavers to Dutch ADP payroll
Cezanne HR → AFAS Profit
Cezanne HR to AFAS integration: the Dutch employer from Cezanne in AFAS Profit Payroll
ASCezanne HR → Arbodienst (SIVI)
Cezanne HR to the occupational health service via SIVI: sickness absence events as absence reports