Benutzen sie die linke oder die rechte Maustaste, um zur jeweils vorherigen bzw. nachfolgenden Änderung zu gelangen.
erste | letzte |
Änderungen von: | |
bis: | |
Typ: | |
erste | letzte |
Note: This section deals with recording an exit in Personalwolke Time.
You can find information on recording an exit in HR-Expert under Registration of Terminations in HR-Expert
Contents of this chapter:
The following must be observed in the event of leaving with regard to the settlement of Personalwolke:
If the leaving date is not set in advance, time recording will continue and the account values will be incorrect.
In this case, the leaving date must be set retrospectively, and daily payroll accounting must be started from the leaving date (detailed description below).
If an employee leaves the company and their data is still to be analysed, the following steps are necessary for the departure:
Attention: if you want to delete the affiliation to previous Loose groups, please use the "Delete" function (see screenshot below)!
Please bear in mind that every active employee must be assigned to a hierarchical group. It is not possible to delete such an assignment without reorganising it
If the data is no longer required, a person can be deleted (note: this will delete all time recording data):
ATTENTION: if you confirm the pop-up with "Delete", the person's data will be irrevocably deleted. This data can no longer be analysed or restored!
It can happen that only the "Active user" tick is removed for an employee who has left the company, but the leaving date is not set. This results in the time accounts being calculated continuously, meaning that the employee still has a target time and, due to their non-attendance, earns minus hours even though they have actually left.
In this case, the leaving date must be entered retrospectively, and the daily payroll run must then be started from the leaving date. As a result, the account calculation is rolled up again and the leaving date is taken into account.
Instructions:
Please note that the date on which daily accounting is started must not be before the leaving date, as otherwise information such as the release authorisations (monthly release, 10h / 50h cap cancellation, etc.), daily programmes, holiday entitlement values, etc. will be lost. The existing data is overwritten with the current values.
Example:
Monthly releases cannot be sent for approval in advance for departures during the month. These can only be sent on the last day of the month.
The statistics also only show account values from the end of the month. Therefore, if an employee has left during the month, the values for the month in which they left are not displayed in the Personalwolke monthly statistics analyses.
Mime Type | text/xml | text/xml | |
Datei-name | |||
Größe (in Bytes) | 8024 | 8001 |
Version 5 von Renate Fuchs-Schreiber
am 03.11.23 15:51:49 Name: Termination of an employee in Personalwolke Time Variante: main - en Status: Entwurf |
Version 6 von Renate Fuchs-Schreiber
am 03.11.23 16:04:40 Name: Termination of an employee in Personalwolke Time Variante: main - en Status: Veröffentlichung |