Absence Monitor
Combines absence data from AFAS with employee, team, and scheduling data from ONS into a daily overview.
Overview
This automation reads absence combinations from AFAS and assesses the relevant days of absence per employee. It adds employee, team, schedule, and contract type data from ONS and generates a file at the daily level for further processing.
What has changed
- Absence data from AFAS and ONS are combined without manual lookups
- The daily-level file is ready for further processing
At a glance
In één oogopslag
Overzicht
This automation reads absence combinations from AFAS and assesses the relevant days of absence per employee. It adds employee, team, schedule, and contract type data from ONS and generates a file at the daily level for further processing.
Wat er verandert
- Absence data from AFAS and ONS are combined without manual lookups
- The daily-level file is ready for further processing
How it works.
What it does per employee
- Reads absence combinations from AFAS
- Filters and assesses the relevant days of absence per employee
- Adds employee, team, schedule, and contract data from ONS
- Generates a file at the daily level for further processing
Rules
The automation retains the relevant days of absence per employee and adds team, schedule, and contract data from ONS. Every run follows the same logic and is logged for review, leaving no room for guesswork.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.