We find that many companies do not take advantage of the opportunities around collisions between attendance and absence in the system. The collisions should help ensure that codes that are not allowed to register at the same time are not registered at the same time.
The collisions occur when transferring time from the timesheet to HR, and when registering directly in the absence infotypes. This is especially relevant when using temporary codes for absence, such as undocumented sick leave etc. These codes should be overwritten by real codes when documentation is available. In addition, it may make sense to block the recording of certain types or all attendance for specific absence codes. This could be overtime for sick leave or certain types of leave. There are also some absence codes that should not be recorded at the same time, such as sick leave and leave of absence.
The system allows different reactions for collisions:
- No reaction
- Warning
- Overwrite (delimitation of existing codes)
- Error message
Several also benefit from creating their own absence codes for graded absence versus full-time absence, and long leave versus short welfare leave.
It is also possible to set up your timesheet so that you cannot enter multiple occurrences at the same time if you use a time.
Sariba has good experience in documenting the collisions that lie in the system in a collision matrix so that it is easier to keep track of which codes collide or react to each other. We also have extensive experience with which codes are appropriate to have in order to ensure proper registration in relation to reimbursement and A-melding, as well as various codes for timesheets of deviations at the scheduled time (negative time) or registration of all time (positive time).
Please contact Sariba if you have any questions about this.