Managing absences in Factorial with AI starts where the request actually lands: in Factorial. Thursday, 09:12. Clara opens Factorial on her phone, taps on 15-19 December and requests five days of Urlaub. The request shows up on Anna’s dashboard, two minutes later it shows up again as an email, and by Friday afternoon Anna still has eleven other requests from the same week waiting in her inbox. Twelve approvals, three team calendars to cross-check, two Krankmeldungen without a certificate yet, the home-office plan for next week, and still no answer to Clara. This guide shows how to hand the reading, checking and chasing to Superkind’s native Factorial integration, step by step, without taking the decision out of Anna’s hands. Below you will see how Superkind’s ready-made AI team for Factorial absences reads, checks and prepares every absence for you.
Factorial is a Barcelona-based HR platform and the fastest-growing choice for small companies and the Mittelstand in the DACH region after Personio. It already does the hard part: central employee file, vacation balances, Abwesenheitsarten for Urlaub, Krankheit, Home Office and Sonderurlaub, team calendar, hourly or half-day entries, electronic signatures and calendar sync with Google Calendar and Outlook. Superkind does not replace it. Superkind works directly with it, through the native integration, like a colleague who reads every request before it reaches you.
Key takeaways
The AI prepares, you approve - Superkind reads the Factorial request, checks the balance, the team calendar and the blocked periods, and posts a one-line summary in Teams or Outlook with Approve or Reject. You decide, the connector writes the decision back to Factorial.
Every absence type in one flow - vacation (Urlaub), sick leave (Krankheit) with certificate chase, home office under your 3-office-days rule, and Sonderurlaub all go through the same AI team, with the Factorial balances and policies you already set up.
Explain it once, it keeps running - a rule like “Vacation under 5 days with balance left and no team clash: auto-prepare for the manager in Teams” turns one request into a weekly routine.
Get a ready-made AI team for Factorial - Superkind comes with an HR team (Absence Manager, Team Calendar Scout, Sick-Leave Tracker, Home-Office Planner) that works inside Factorial automatically. Start for free with unlimited users, or build your own.
Keep HR data in Europe - names, sickness days and team plans belong in Europe. Factorial is hosted in the EU and Superkind is hosted in Europe, GDPR compliant and never trains on your data.
Your AI team for Factorial absences
What does it mean to manage absences in Factorial with AI?
Managing absences in Factorial with AI means an AI employee connects to your Factorial account, reads every new absence request the moment it is created, checks the balance, the team calendar, the blocked periods and the policy, and prepares the decision for a manager inside the channel the manager already uses (Outlook, Teams, Slack or the Superkind web app), while Factorial stays the system of record and the approval stays with a person. The AI reads, compares and drafts. The click stays with your HR team. One example is Superkind: a ready-made AI team with a native Factorial integration that handles vacation, sick leave, home office and Sonderurlaub, hosted in Europe.
The difference to a plain workflow in Zapier: an AI employee understands plain English or German and the context of your team. It knows that Clara’s five days in December cross the works council blocked period for the warehouse team, that the certificate for last week’s sick leave is already in the upload folder, and that Anna, not the HR mailbox, is the right approver for the support team.
How it works with Superkind: your AI team for Factorial absences
Superkind is the AI employee for your team: you write to Superkind by email (Outlook or Gmail), in Microsoft Teams, in Slack or in the Superkind web app, like you would write to a colleague, and Superkind does the task in your programs. Hosted in Europe, GDPR compliant, with 1,500+ integrations into the systems where your HR work already lives: Factorial, Personio, DATEV, SharePoint, Google Workspace, Outlook, Teams and Slack. The Factorial connector is native, so Superkind can list employees, read time off and balances, check attendance, list shifts, upload documents and (with your approval) approve a request or update a profile.
You do not start from scratch: Superkind comes with ready-made AI employees that run inside Factorial for you. They work on their own in the background, and the sensitive step waits for you if you want it to. Use them right away, adapt them, or build your own.
Absence Manager
AI employee for Factorial absences
Urlaubsantrag drops into Factorial, email lands in your inbox, approval slips through the week. As soon as a new absence request appears in Factorial, the Absence Manager checks the balance, the team calendar, the blocked periods and overlaps, and posts a one-line summary in Teams with Approve or Reject. You click, it writes the decision back to Factorial through the native Superkind integration.
Team Calendar Scout
AI employee for team planning
Three absences in one small team on the same Monday, and nobody notices until Friday. Every morning the Team Calendar Scout reads the Factorial team calendar for the next four weeks, finds thin coverage days per team and location, and posts a short list in Teams with the names and dates. Runs on its own, no approval needed.
Sick-Leave Tracker
AI employee for sick leave
Someone calls in sick on Monday, the AU certificate (electronic eAU or paper) is due later in the week, and three Fridays later HR still chases the paperwork. The Sick-Leave Tracker checks Factorial every day for sick leave without a supporting document attached. After the legal deadline it sends a friendly reminder in Outlook with the Factorial upload link. Private details stay private.
Home-Office Planner
AI employee for home office
Your rule is three office days per week, home office recorded in Factorial. The Home-Office Planner reads the week in Factorial, posts the home-office list for each team in Teams on Friday for the next week, and writes to anyone whose plan does not match the rule. You decide who it writes to and whose name goes to the manager instead.
Every Friday at 16:00: post next week's home-office plan per team and flag anyone off the 3-office-days rule.
Reasoning ⌄Next week: 42 colleagues planned, 38 within the 3-office-days rule, 4 above. Posts drafted per team.
Runs automatically every Friday 16:00
Every employee is ready to use right away. Or build your own on the platform.
From the first request to your own app
The same path is told once on this topic. Each stage builds on the last:
- 1
Start
Ready in minutes. Sign up for free at app.superkind.ai, connect your Factorial account, and watch Superkind draft the summary for the first ten open absence requests in Teams or Outlook.
- 2
Relief
Tasks become routines. Every new Urlaub request follows the same drafting path, and the approval step waits for the manager, because that is how you set it up. Routine steps like the home-office plan and the certificate reminder run on their own.
- 3
Knowledge
Learns from day one. Your Company Brain grows with every absence: blocked periods per team, who approves whom, how Sonderurlaub is handled, which teams need extra coverage on Mondays. When the HR lead changes, the knowledge stays.
- 4
Growth
When it gets more complex, you do not start over. Build a custom team-coverage app with its own interface on the Superkind platform, on top of what Superkind already knows about your Factorial teams. Built yourself or with the Superkind team, and it all belongs to you.
Connect your Factorial to Superkind
Start for free in Outlook, Teams or Slack.

What you need
Check these points before you start. Most of them are already in place in any company running Factorial today.
Checklist before the first connection
- A Factorial account where your absences live, with the Abwesenheitsarten you use (Urlaub, Krankheit, Home Office, Sonderurlaub and any custom type)
- Factorial’s own calendar sync to Google Calendar or Outlook already set up for the team calendar (optional but helpful)
- A clear list of approvers per team (the Vorgesetzter in Factorial), and the blocked periods per team or location
- Agreed thresholds (for example “vacation longer than 10 days: second approval by management”)
- Outlook, Gmail, Microsoft Teams or Slack as the channel where approvers already work; Superkind uses the one they prefer
- A Factorial admin who can create the API token and confirm which areas (employees, time off, attendance, documents) the AI employee may use
- A free Superkind account at app.superkind.ai
- Thanks to the 1,500+ integrations in Superkind, Factorial can be connected alongside Outlook, Teams, SharePoint and DATEV without new tools or custom code
Step by step with Superkind in Factorial
Six steps from the first connection to a full absence routine that runs on its own. Each step is something you can do today.
Step 1: Connect Factorial and your channels
Sign up at app.superkind.ai and connect Factorial as the system of record. An admin in Factorial creates the API token in Einstellungen and confirms which areas the AI employee may use: employees, time off, attendance, shifts, documents. Then add the channels your team already works in: Outlook or Gmail for email approvals, Microsoft Teams or Slack for the chat channel approvals, SharePoint or Google Drive if you store HR documents there.
- Check - the Factorial connector uses only the permissions the admin agreed to, and the audit log records every action.
- Tip - start with one team (for example support or sales DACH) before you roll it out company-wide.
Step 2: Tell Superkind who approves what
Send Superkind the rules the way you would brief a new HR colleague. Short sentences, concrete thresholds, one topic per line. The rules become part of the Company Brain and apply to every request from now on.
Vacation under 5 days with balance left and no team clash: prepare the approval for the Vorgesetzter in Teams. Vacation longer than 10 days: ask for the second approval from management. Blocked periods per team come from Factorial. Sick leave: send the AU reminder on day 4 if no certificate is uploaded.
Superkind confirms with “Noted.” From now on every Urlaubsantrag in Factorial follows this logic, and you can change the rule any time by sending a new message.
Step 3: Let the Absence Manager handle every new request
A new absence request in Factorial triggers the Absence Manager. Through the native connector it reads the type (Urlaub, Krankheit, Home Office, Sonderurlaub), the period (full day, half day or hours), the remaining balance and the Factorial team calendar for overlaps. Then it posts a one-line summary in the approver’s preferred channel.
New request: Clara Neumann, vacation 15-19 Dec (5 days). Balance ok (17 days left). No team overlap. No blocked period. Ready for your OK.
Anna clicks Approve in Teams. Superkind writes the decision back to Factorial, which emails Clara and updates the team calendar. If Factorial’s calendar sync to Outlook is on, the absence already shows up as Out of Office in the shared Outlook calendar, exactly as Factorial handles it today.
Step 4: Chase missing sick-leave certificates
Every morning the Sick-Leave Tracker checks Factorial for Krankmeldungen whose supporting document is still missing after the deadline. In Germany, Section 5 of the Entgeltfortzahlungsgesetz requires the AU certificate by the fourth day of continued sickness in most cases. Superkind reads the sick-leave list, matches it with the documents folder, and drafts a short Outlook reminder with the Factorial upload link for anyone past the deadline. The diagnosis stays private, only the date range leaves Factorial.
@Superkind send the AU reminder to the two colleagues who are past the 3-day deadline. Friendly tone, Factorial upload link, no team-wide note.
The electronic AU (eAU) between the health insurance and your payroll provider is a separate route through KV-Connect and keeps running the way it does today. Superkind only chases the proof when the deadline is missed.
Step 5: Keep the team calendar healthy
The Team Calendar Scout reads the Factorial team calendar four weeks ahead, finds thin coverage days and posts them in Teams with the names and dates. For small companies that is where most Monday-morning surprises come from.
Coverage check next 4 weeks: 3 days in Support (Munich) with only 2 of 5 colleagues in, 2 days in Sales DACH with only 3 of 7 in. Full list in thread.
Anna sees the dates, nudges the teams and, if needed, asks Superkind to hold off on new approvals for those exact days. The rule goes into the Company Brain and applies to the next cycle too.
Step 6: Run the weekly home-office plan
If your company has a hybrid rule, the Home-Office Planner runs every Friday at 16:00. It reads the home-office entries for next week in Factorial, posts the plan per team in Teams, and writes a short Outlook message to anyone off the 3-office-days rule. You choose whether the message goes to the person or the manager.
Every Friday at 16:00: post the home-office plan per team for next week and flag anyone above 2 home-office days. Send a friendly nudge, not a complaint.
Factorial stays the one place where the data lives. Superkind only reads and writes what the connector allows, and every step is logged.
Set it up as a routine
Once ten or twenty absences have gone through cleanly, stop telling Superkind one by one. Give it the week, Superkind reads Factorial, groups the work by approver, and sends the drafts out before the week starts.
Every Monday at 8:30: group every open Factorial absence by approver, send each approver one Teams summary, ping the approvers of requests older than 3 working days.
- Daily - new requests, with a one-line summary and the Approve / Reject card for the right manager.
- Weekly - a team-coverage report per location and department with the thin days called out.
- Monthly - an overview of absence types by team, the vacation balances that will carry into the new year, and the certificate rate for sick leave.
When it grows, for example several legal entities on separate Factorial accounts or a special rule per Bundesland public holiday, you do not start over. On the Superkind platform you build a custom coverage app with its own interface, on top of everything Superkind already knows. Built by your team or together with the Superkind team, and it belongs to you. The 1,500+ integrations keep the app connected to Factorial, DATEV, Outlook and Teams without new middleware.
Data protection and EU hosting
Safe by default
Absence data is personal data. Factorial is hosted in the EU, and Superkind processes it in Europe and never trains models on it.
- Hosted and processed in Europe
- GDPR compliant
- Aligned with the EU AI Act
- No training on your data
- DPA through the Trust Center
Absences carry names, dates, and, for sick leave, data that touches Article 9 GDPR (special category). Factorial is a Barcelona-based Spanish company and hosts customer data inside the EU. Superkind adds the AI layer on top and keeps the same European path.
What this means for absences: the names, balances and sick-leave dates Superkind reads in Factorial, the drafts it prepares for Anna, and the reminders it sends never leave the EU and are not used to train a model. Works council (Betriebsrat) co-determination rights on leave scheduling under Section 87(1) No. 5 Betriebsverfassungsgesetz are preserved, because the rules you agreed are the rules Superkind applies, nothing else.
Other ways to handle Factorial absences
Superkind is not the only way. Here is an honest comparison of the common options.
| Way | Effort | Error risk | Best for |
|---|---|---|---|
| Superkind | Low: native Factorial integration, rules in plain language | Low: checks balance, team calendar and blocked periods, approval where you want it, EU hosting | HR teams and team leads running Factorial across Outlook, Teams, Slack and SharePoint, with 1,500+ integrations |
| Factorial alone | Low: everything in one app | Low in the app, higher when approvals sit in email or chat | Teams happy to approve inside Factorial, without cross-system context |
| Zapier or Make on top of Factorial | Medium: pick triggers and steps, maintain Zaps yourself | Medium: brittle on edge cases, no plain-language rules, often non-EU hosting | Admins happy to maintain a Zap library and move data between tools |
| Excel export plus Outlook | High: export, filter, copy, email by hand | Medium: outdated balances, no automatic coverage check | Small teams with a handful of absences a month |
| Manual, in Factorial only | High when volume grows | Medium: missed deadlines, overlooked overlaps | Very small teams with few requests a week |
The main gap with generic automation tools is context: Superkind reads the request, the balance and the team calendar together, in the channel where the approver already is. For a wider view of AI in HR see the AI for HR: tools, examples and tips guide and the AI tools for Personio piece for teams that run on the other side of the fence.
Common mistakes
These five mistakes cost the most time when teams start to manage Factorial absences with AI.
- Letting AI click Approve on its own - keep the click with a person for anything binding. Superkind reads, checks and prepares; the manager decides.
- Skipping the blocked periods - Factorial already knows the works-council blocked periods per team. Point Superkind at them before the first approval, otherwise it will contradict rules you already agreed.
- Treating sick leave like vacation - sickness data is Article 9 GDPR. Keep the diagnosis inside Factorial. Superkind only chases the proof when the EFZG deadline is missed.
- One channel for every team - sales approves in Teams, warehouse answers on email. Superkind uses the channel each approver prefers through the 1,500+ integrations, so adoption does not depend on a new tool.
- Forgetting the audit log - every read, draft and write by Superkind is logged. Turn the log on from day one and share it with the works council. It is the fastest way to build trust.
6 tips for managing absences in Factorial with AI
1. Start with one team and one absence type
Pick the support or sales team and run vacation only for the first two weeks. One well-mapped rule beats a half-finished policy copied from the handbook.
2. Write the rules the way you brief a new manager
“Vacation under 5 days with balance left and no team clash: auto-prepare for the Vorgesetzter. Vacation longer than 10 days: second approval by management.” Short sentences work better than scoring matrices.
3. Put approvals where the approver already is
If your warehouse lead lives in Outlook and your sales lead in Teams, approvals go there. Superkind uses the same rules and the same Factorial connector in every channel across the 1,500+ integrations.
4. Keep works-council rights visible
Section 87(1) No. 5 Betriebsverfassungsgesetz gives the Betriebsrat co-determination on leave scheduling. Agree the blocked periods and the approval chain in writing, keep them in Factorial, and Superkind applies them. Share the audit log, not screenshots.
5. Make data protection a set-up argument
Factorial is EU-hosted and so is Superkind. In the first meeting with your works council or data-protection officer, name both facts, show the DPA from the Trust Center and align the EU AI Act Article 4 AI literacy page. Most of the questions stop there.
6. Let it run before you build more
Resist the urge to automate the exception first. Run the standard flow for a month, read the weekly report, then decide what the next rule should be. The Company Brain captures every decision, so the second iteration is cheap.
Conclusion
Managing absences in Factorial with AI does not mean software approves vacation. It means the reading, the balance check and the coverage check are done for you, your rules are applied every time, and, where you want it, a manager clicks Approve before anything is written back to Factorial. The fastest way to see whether it fits: connect your Factorial to Superkind, let the Absence Manager run on one team for a week and compare the drafts with how you would have decided yourself. If you want to look wider first, read the AI for HR guide or the sister piece AI tools for Personio. For broader onboarding examples see AI-powered employee onboarding and the onboarding of AI employees itself.
Frequently Asked Questions
Yes. Factorial is a native Superkind integration with a managed connector. Superkind can list employees and contract versions, read time off and balances, check attendance, prepare approvals and, with your approval, create or update employees, approve a request and upload documents. The actions the AI employee uses depend on the use case your admin sets up, and Factorial stays the system of record.
The AI employee works with every absence type you have in Factorial, including vacation (Urlaub), sick leave (Krankheit), home office, special leave (Sonderurlaub) and the custom types you define yourself. Factorial lets you create as many Abwesenheitsarten as you need, with hourly, half-day or full-day entries, and Superkind reads them the same way you set them up.
The approval only becomes binding when a responsible person clicks Approve. Superkind reads the request, checks the balance, the team calendar and the blocked periods and shows a one-line summary in Teams or Outlook. The approving manager decides, and the decision is written back to Factorial through the connector. Works council (Betriebsrat) co-determination rights on leave scheduling under Betriebsverfassungsgesetz Section 87(1) No. 5 are respected, because the rules you set are the rules Superkind applies.
Superkind checks Factorial every day for sick leave without a supporting document and sends a friendly reminder past the deadline required by Section 5 of the Entgeltfortzahlungsgesetz (EFZG, usually by the fourth day of continued sickness). Private details such as diagnoses stay inside Factorial. The electronic AU (eAU) still flows between the health insurance and your payroll provider through the official KV-Connect route, not through Superkind.
Employee data is special-category data and belongs in Europe. Factorial is a Barcelona-based Spanish company hosted inside the EU, and Superkind is hosted and processed in Europe, GDPR compliant and aligned with the EU AI Act, does not train on your data and signs a DPA (AVV) through the Trust Center. Spain's AEPD is Factorial's supervisory authority; the Spain-Germany leg is covered by the EU-wide one-stop-shop under GDPR.
You start for free at app.superkind.ai with up to EUR 150 in credits, no credit card and no sales call. For regular HR work the Business plan starts at EUR 50 per month for the whole company with unlimited users, and an approval or reminder task typically costs between 50 and 500 credits. EUR 100 covers up to 1,000 tasks or 5,000 questions. As of October 2026. Factorial's own licence is on top of that.
Only if you set it up that way, and the skill's recommendation is: do not. Keep approvals with a manager for anything binding, and let Superkind handle the reading, checking and reminding. For the few routine cases where a pure rule applies (for example "home office under the 3-day rule: auto-confirm"), you can take the approval off, but the default stays with a person.
Related Articles
- AI for HR: Tools, Examples and Tips
- AI Tools for Personio
- AI-Powered Employee Onboarding
- Onboarding Your AI Employees
Sources
- Factorial Help Center - About absences and approvals
- Factorial Help Center - Sync Factorial with your calendar app
- Factorial - Urlaubsverwaltung und Abwesenheitsmanagement
- Factorial - Outlook Calendar integration
- Factorial - Google Calendar integration
- Gesetze im Internet - Entgeltfortzahlungsgesetz (EFZG) Section 5
- Gesetze im Internet - Bundesurlaubsgesetz (BUrlG)
- Gesetze im Internet - Betriebsverfassungsgesetz Section 87 (works council co-determination)
- EUR-Lex - Regulation (EU) 2024/1689 (EU AI Act)
- GKV-Spitzenverband - Elektronische Arbeitsunfähigkeitsbescheinigung (eAU)
Connect your Factorial to Superkind.
Start for free in Outlook, Teams or Slack. Or let us show you in 30 minutes how it runs in your Factorial.

