Creation of persons in the future & past

New employees are often not aren't created in the system exactly on the day they join. For this reason, Personalwolke Time supports different scenarios for a new person

• subsequently or 
• in the future 

in the system.

 In In our system, person master data records have a "Valid from" and a "Valid to" date. When a new person is created, this data is filled automatically and cannot be changed manually. 

To enable time recording into the past for subsequently created persons, the field "Start of time recording" must be set to a date in the past.

Relevante Parametersparameters

The following values parameters must be entered under "Modules" -> "Time recording" in the person master record.

 A description of the remaining fields can be found under "Field Description Master Record  Record"  Feldbeschreibung Stammsatz

Start of time recording

If you check the checkbox "Activate time recording" in the Modules / Time recording tab, you must enter the start date of time recording correctly.  The start date of the time recording must be set to the day before the day from which times are to be recorded in the system.

This date cannot be in the future. It can cannot also not be the current date. It must be a date in the past, such as yesterday. If the current date is entered, it is automatically replaced with yesterday's date when saving.

This is useful so that you can already enter the remaining leave and other values for the previous day, so that you have already settled values in the system from the entry date.

Example:

• Entry date: per 01.01.
• Person is created on 808.1 in the personnel cloud.01. in Personalwokle
• The start date of Time Management must be set to 31.12. so that times can be recorded as of 1.1the time recording can start with 01.01.

Entry date

When you create a person, you must specify the entry date.   It can then This enables that this person can be displayed in various evaluations.

Fictitious entry date

The fictitious entry date is important if an employee has an earlier, fictitious entry date due to previous employment periods being taken into account. The system therefore separates a) the actual entry date and b) the fictitious entry date, which is then also used to calculate the leave entitlement.

Example:

• Entry date: per 01.07.
• creditable prior periods of employment: 6 months
• Fictitious entry date: 01.01 01.

Examples of the personal system

Example 1: The employee is already in the company and is created later in time recording:

1. Time recording is activated by the entry date into the past. The postings must then be entered subsequently.
2. Time recording is activated with the current time. Afterwards, the balance values and vacation data (described below) must be manually added via the correction client (to be found under "Administration" -> "Time management" -> "Correction client").

Example 2: Employees join the company for the first time:

1. The employee can be created in advance in the Webdesk Personalwolke and only activated for time recording on the entry date. 
   Example: Entry date: 01.04.
   The employee is created on March 25.03. so that the information already exists and the personnel cloud with the entry date can be used fully.
   Time recording must then be activated on 101.4 04. as of 31.03..
2. The employee can be created on the entry day and time recording can be activated on the previous day.
   Example: Entry date: 01.04
   The employee is created in the system on 04/01 and the start date of Time Management is set to 3/31. This enables the employee to record his or her working times and absences as of 04/01.

Vacation entitlement

For new employees, you must specify the leave entitlement and the "key date of addition" so that the new leave entitlement is added to the addition date. If the new annual leave is credited per calendar year, you must enter 01.01 as the key date for the addition. If the entry date is relevant, the entry date must be entered here.

If an employee is created in the personnel cloud who is already in the company, the days since the last addition and possibly the entitlement from the previous year or previous year must also be entered. These are entered in the correction client under "Administration" -> "Time management" -> "Correction client". There the view must be switched to the daily view and the correct values must be entered on the first day in the time recording.

Example:

If Max Mustermann has entered on 01.01.2015 and is then created on 01.04.2016 in time recording, the vacation values must be stored as follows:

• Holiday entitlement: 25
• Date Added: 01.01.2015
• Days since last added: 31 (January) + 29 (February 2016 leap year)+ 30 (March) + 1 (current day) = 91 days  
• Holidays used up in 2015: 8 days
• Spent vacation in 2016: 7 days
• Remaining leave previous year: 10 days
• Remaining vacation total: 35 days (10 remaining days from 2015 + 25 days from 01.01.2016, vacation days are always deducted from the oldest remaining vacation first until they are used up)

Aliquoting of the year of entry

The parameter "Factoring the entry year" controls whether the leave entitlement is to be added on a pro rata basis in the first six months and must be set to "legally compliant".

If the employee is subsequently created in time recording and the entry date is not in the current year, then set this parameter to "No".

Example:

• Mr. Mustermann joined on 06.03.2015. 
• Mr. Mustermann's company has been created in the personnel cloud since 01.012016. 
• Time recording is therefore activated for Mr. Mustermann as of 31.12.2015. 
• If the factoring of the entry year is activated, the leave entitlement is added to him in 2016 on a factoring basis. 
• As a result, he or she would not receive the 25 leave days specified on 03/06/2016.
• In this case, the parameter "Factoring the entry year" must be set to "No".