Payroll integration
Cezanne HR to AFAS integration: the Dutch employer from Cezanne in AFAS Profit Payroll
With an integration between Cezanne HR and AFAS Profit, employees of the Dutch employer in Cezanne go to AFAS automatically, with employment, working time pattern, base salary and bank account on their effective date. HR manages everyone in Cezanne; payroll runs in AFAS without retyping.
What the integration does
Organisations that use Cezanne HR as the HR system for several countries and run payroll in the Netherlands with AFAS Profit enter every new employee in both systems. Because Cezanne and AFAS both keep everything with effective dates, the history quickly drifts apart without an integration.
- HR creates an employment at the Dutch employer in Cezanne.
- KoppelHet reads person, employment, working time pattern, salary and bank account through the Cezanne API.
- AFAS receives the new employee through the onboarding process; HR completes payroll tax, collective agreement and pension.
- New records in Cezanne go to contract, schedule, salary or bank account in AFAS with their effective date.
- When the employment in Cezanne gets a real end date, KoppelHet sets the end date in AFAS.
What to watch for with Cezanne HR and AFAS Profit
- Every employment in Cezanne belongs to a company through a CompanyCode. KoppelHet only includes employments with the code of the Dutch employer, even if the same person previously worked in another country.
- Cezanne sets the end date of an ongoing employment to 31 December 2999. KoppelHet reads that as no end date, so nobody ends up in AFAS with a termination in the distant future.
- The Cezanne API works with a token that a user approves after logging in, and that token only sees what that user may see in Cezanne. We therefore create an integration user who only sees the Dutch employer; other countries stay out of reach.
- In Cezanne webhooks are only in the People PLUS+ package. Without that package KoppelHet reads the tables every hour with an OData filter on the Dutch employer.
- Working time patterns in Cezanne come from a template, such as Full Time, with an effective date. The FTE and the hours per day are in separate tables; KoppelHet combines them into the AFAS schedule with hours and days.
- Salary is stored in Cezanne as a compensation item with a code, such as BASE. Only that item goes to AFAS as salary; allowances and benefits from Cezanne only become a pay component when we agree it together.
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
We have the People package, without PLUS+. Is it still possible?
Yes. The API is in both packages. Without webhooks KoppelHet reads every hour, and always in full before the payroll run.
Is the BSN in Cezanne?
It can be, as an identifier with its own document type. If you do not record it in Cezanne, HR adds it in AFAS during onboarding.
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 API (v7 dataservice.svc) with OAuth 2.0 - People, Employments, EmploymentContracts, EmployeeWorkingTimePattern, EmployeeWorkingTimePatternFTE, EmployeeWorkingTimePatternDetails, Compensation, BankDetails and LegalIdentifiers, filtered on PersonCode and CompanyCode. Webhooks per trigger (add, edit, delete) with People PLUS+.
- AFAS through HrOnboarding the first time and then KnEmployee with AfasContract, AfasTimeTable, AfasSalary and AfasBankInfo, with an app connector that holds only these connectors.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Cezanne HR | Field in AFAS Profit | Notes |
|---|---|---|
PersonCode | Vrij veld bij de medewerker | Key |
People (FirstName, FamilyName, DateOfBirth, Gender) | KnPerson | |
Employments.CompanyCode | Werkgever | Only the Dutch CompanyCode |
Employments.HireDate | Datum in dienst | |
Employment Contracts (EffectiveFrom, EffectiveTo) | AfasContract | |
Employee WTP en WTP - FTE | AfasTimeTable | |
Compensation met CompItemCode BASE | AfasSalary | |
BankDetails (EffectiveFrom, AccountNumber) | AfasBankInfo | |
LegalIdentifiers met documentsoort BSN | BSN | |
Employments.TerminationDate | Datum uit dienst | 31-12-2999 means open-ended |
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
ASCezanne HR → Arbodienst (SIVI)
Cezanne HR to the occupational health service via SIVI: sickness absence events as absence reports
Cezanne HR → DATEV
Cezanne HR to DATEV integration: the German company from Cezanne HR to the tax adviser