Only accepted absences are transmitted. At each synchronization time the updated and recently accepted absences are transferred. As long as an absence application has the "new" status, this data is not transferred to Personio:
If a previously accepted absence is subsequently rejected, it will also be removed in Personio.
Important:
During the initial transfer all(!) historical data will be transferred as well.
First time set-up
The different absence reasons have to be assigned between Personio and shyftplan as part of the onboarding project, so that an n:1 assignment is established between shyftplan and Personio. Whenever a new reason is added, it must be configured accordingly.
In addition to the name in Personio, please provide the associated TimeOffTypeID to your Customer Success Manager for this purpose. You can get this from the URL in Personio.
shyftplan/Personio views:
Onboarding:
Please provide a mapping table for the absence reasons:
Personio absence reason | Personio TimeOffTypeID | shyftplan absence reason |
sickness | 471190815 | sickness |
What data is transferred to Personio?
Personio | shyftplan | status | comment |
Start_date | starts_at | SYNCHED | |
End_date | ends_at | SYNCHED | |
comment | note | SYNCHED | Custom text transferred and also technical info (sickness cert. presented and example: System Note: "[vacation] 30.09.2020 - 01.10.2020 (2 days)") |
absence type | absence reason | SYNCHED | |
sickness certificate | NOT SYNCHED | Personio API does currently not accept documents. |