Leave, absence and time
Tamigo to AFAS integration: worked hours from Dutch stores to AFAS, employees and pay agreements back
With an integration between Tamigo and AFAS Profit, the worked hours, overtime and premium hours of Dutch sites go to AFAS automatically after review, on the right pay component and in the right payroll period. New employees, contract type and contract hours come from AFAS into Tamigo, so scheduling and payroll work from the same agreements.
What the integration does
Organisations that plan in Tamigo and run Dutch payroll in AFAS Profit download the Tamigo export every month, filter out the Dutch locations and import the hours into AFAS. New employees only reach Tamigo when a manager creates them personally.
- HR records a new employee in AFAS with contract type, contract hours and organisational unit.
- KoppelHet puts the employee in Tamigo at the store that belongs to the unit, with the agreements from AFAS.
- Employees work their shifts and review their own hours in Tamigo before they go to payroll.
- After review KoppelHet retrieves only the hours of the Dutch sites, with the overtime and premium hours Tamigo has calculated.
- The hours appear in AFAS per pay component, in the period your payroll team uses.
Back: Worked hours per wage code as payroll change · Overtime and premium hours per type
What to watch for with Tamigo and AFAS Profit
- Tamigo calculates overtime, bank holiday, weekend and night hours itself, with settings per country and collective agreement. AFAS can also derive premiums from hour types linked to a pay component per agreement. KoppelHet records beforehand which side calculates the premium, so a Sunday shift is not paid extra twice.
- Tamigo often plans several countries in one environment, while AFAS only pays the Dutch entity. The integration filters by site and sends only hours from Dutch stores to AFAS; the other countries keep their own payroll route.
- Tamigo can deliver hours per shift or as a total per payroll period. Per shift fits employees with a daily schedule in AFAS. For employees with a schedule in hours per week AFAS cannot process hour types per day; for them KoppelHet books the period total.
- In Tamigo employees review their own worked hours before they go to payroll. The integration only retrieves hours after that point, so a correction by the employee does not arrive after the payroll run.
- Tamigo aims to be the source for contract types and wage codes, fed from the HR system. That is why contract type and contract hours first go from AFAS to Tamigo, and the wage codes in Tamigo map to the same pay components as in AFAS. Tamigo then calculates with the contract that is also in the payroll run.
- Tamigo lists AFAS on its own integrations page, under both payroll and HR, but does not publicly describe what that connection transfers. Check with Tamigo what is already running before custom work starts, so two routes do not book the same hours.
- October's hours can land in AFAS in October, retroactively, or in the current November run. Tamigo closes periods on its own dates; KoppelHet aligns both to the method your payroll team uses.
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
Do absence and sickness go to AFAS too?
Tamigo records absence, but in AFAS sickness belongs in absence management and not in payroll changes. The first version only sends worked hours and premiums; absence can be added later as an extension.
What if a store has no entry in the translation table yet?
Then the employee is not created and an alert appears in the platform. Once the table is completed the next round picks them up.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- According to its own site Tamigo has an open API to integrate with HR, payroll and point-of-sale systems. We found no public API documentation (endpoints, authentication); the technical set-up on the Tamigo side is agreed with Tamigo.
- In AFAS we book the hours as payroll changes through the UpdateConnector HrCompMut (HrCompMutGUID for corrections to a known line). If hours per shift go through project costing, they use PtRealization with hour types linked to a pay component per agreement.
- AFAS is read with a dedicated GetConnector on employees, employments, contract type, schedule and organisational unit, without salary or citizen service number.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Tamigo | Field in AFAS Profit | Notes |
|---|---|---|
Medewerker (EmId) | Medewerkernummer in Tamigo | Fixed key between both packages |
Organisatorische eenheid | Winkel (afdeling) in Tamigo | Through a translation table |
Contracttype en uren per week | Contracttype en contracturen in Tamigo | |
Looncode in Tamigo (terug) | Looncomponent in AFAS | One table, maintained by payroll |
Uren per looncode (terug) | Aantal in de loonmutatie | |
Periode in Tamigo (terug) | Salarisperiode in AFAS |
Related
Tamigo → Nmbrs
Tamigo to Nmbrs integration: employees from Nmbrs in scheduling, worked hours back as wage components
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit