Absence and the Overlap With Time

Absence is adjacent to time recording, sold as a module, and frequently owned by a different system. The overlap is where the errors are.

Why they interact

Absence affects pay, and so do hours. Both feed the same calculation.

Entitlement accrues from hours worked in many arrangements, so the timesheet feeds the absence balance.

Public holidays interact with shift patterns, and the rules are specific.

A day cannot be both worked and absent, and something must enforce that.

Part-day absence has to combine with recorded hours on the same day.

One system or two

One system: no reconciliation, one calculation, simpler for the person.

And a weaker absence module, because products strong at time recording are rarely strong at leave policy, and the reverse.

Two systems: each does its job well, and now there is a boundary with a daily synchronisation and a reconciliation.

The deciding question is where entitlement policy lives. Complex accrual, carry-over and statutory leave rules belong in an HR system; simple ones can live in the timesheet product.

If two, the boundary

HR owns entitlement and balances.

The timesheet system owns recorded hours.

Absence flows into the timesheet system as a read-only day type, not as something editable there.

Hours flow to HR only if accrual depends on them.

Conflicts — a recorded shift on an approved leave day — are detected and reported, not silently resolved. Silent resolution in either direction produces a pay error.

The cases to test

A part-day absence with recorded hours on the same day.

Sickness during a booked holiday, where many jurisdictions require the holiday to be reinstated.

A public holiday falling on a non-working day for a part-time person.

Absence spanning a period boundary.

Retrospective absence entered after the period closed and exported.

These five find most of what is wrong, and products fail at least one routinely.

What to require

Conflict detection between recorded time and absence, reported rather than auto-resolved.

Absence visible on the timesheet so a person sees a complete week.

Correct treatment of part days.

A reconciliation between the two systems' view of who was absent when, run per period alongside the payroll one.

The conflict rule

What a system should do when time and absence disagree.

Detect and report, never auto-resolve.

A recorded shift on an approved leave day is either a cancelled holiday nobody updated or a wrongly recorded shift, and only a person knows which.

Silent resolution in either direction produces a pay error that nobody sees until the payslip.

Report it on the period-close checklist, which is where it belongs.

When one person owns the record

Independent workers still need a consistent distinction between worked time, availability and absence. A freelancer time tracking software workflow should be tested for corrections and non-working periods before it supports billing.