When you import absence history from another system, the contract start date recorded in Selfcare is often later than the first absence in the file. An absence before the contract start proves the person already worked there, so the start date is wrong. Without correcting it, holidays (férias) in those years were rejected, because before the hire date the holiday entitlement is zero.
The option Adjust the contract start date to the oldest absence fixes this during the import. It is on by default.
To prepare the file, download the absences template in the Upload step of Import absences, as .xlsx or .csv. See Import templates.
Who can use it
The owner and HR, the same people who can import absences.
What happens with the option on
- For each person in the file, Selfcare finds the absence with the oldest start date, of any type (holidays, sick leave, absences, leave). Rows without a valid date are ignored.
- If that date is earlier than the start of the person's oldest contract, the contract now starts on that date.
- The change is recorded in the audit log, person by person, with the old and the new date.
- That person's year-end holiday closures are recalculated with the new hire date.
- Only then is the holiday balance checked and the absences saved.
At the end, the import result shows, for each person, the old and the new contract date and how many absences were accepted thanks to the adjustment.
When the contract is not adjusted
- The person has no contract. The absence import never creates contracts. The person is listed in the result and the absences are imported as usual.
- The adjustment would overlap another entry in the contract history (for example, a change of hours already recorded before the new date). The contract stays as it is and the person is listed in the result. Everyone else in the file is still imported. Fix the contract on the employee file (ficha) and import again.
Turning the option off
In the Options step of the absence importer, turn off Adjust the contract start date to the oldest absence. Contracts stay as they are and holidays in years before the hire date are still rejected.
ClanHR migration
The same option is in the ClanHR migration settings, also on by default:
- A contract created by the migration starts on the oldest absence if that is earlier than the start date coming from ClanHR.
- On a re-import with the option on, contracts already created with the wrong date are corrected too. With the option off, an existing contract is never changed.