Accrued Leave, and the Arithmetic Nobody Checks
Where leave calculations go wrong at the end of employment: the accrual date, carried-over days, part-time and irregular hours, and leave taken in advance.
Check the leave figure against the actual dates rather than accepting what the system reports, because the system is calculating from a leave year, a start date and an accrual rule that may all have changed since the person joined. Accrued leave is the component of a final payment most often wrong, and the error is almost never deliberate.
The payment question in “Accrued Leave, and the Arithmetic Nobody Checks” depends on a complete and correct work record, not simply the latest dashboard total. For organisations researching employee time tracking, view the solution can connect hours with projects and approvals, provided disputed entries remain correctable and payroll applies the relevant contract and local rules.
It is also the component people check. Somebody who cannot evaluate whether their notice pay is right can count the days they did not take, and will.
For an independent reference relevant to “Accrued Leave, and the Arithmetic Nobody Checks”, consult the Dark Reading security coverage. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
Where the errors come from
- The accrual is calculated to the wrong date — the notice date rather than the termination date, or the last working day rather than the end of garden leave.
- Carried-over days from the previous leave year are omitted or double-counted.
- A mid-year change in hours is applied to the whole year rather than pro-rated across the two parts.
- Public holidays are treated inconsistently with how they were treated during employment.
- Leave booked but not yet taken is deducted as though it had been.
- Days taken in advance of accrual are not accounted for at all.
The first of these is the most common and the most consequential. Somebody on three months' garden leave usually continues to accrue, and a figure computed to the day they stopped coming in will be short by a quarter of a year.
The date the accrual runs to
Employment ends on the termination date. Where notice is worked or served on garden leave, accrual normally continues through it. Where notice is paid in lieu, employment has ended and the position depends on the arrangement and on local rules.
That distinction is worth writing on the calculation itself: which date was used and why. It makes the figure checkable by somebody else, which is the whole purpose of writing it down.
Changes in hours mid-year
Somebody who worked five days a week until August and three days a week afterwards has not accrued at either rate for the whole year. The calculation has to be split at the point of change, and most systems handle this badly or not at all.
The same applies to anybody whose hours vary — irregular shifts, term-time work, annualised arrangements, casual hours. How entitlement is calculated for these is genuinely difficult, differs between jurisdictions, and has changed in some of them. It is a question for somebody qualified in the place concerned rather than one to settle from a spreadsheet.
Leave taken in advance
Somebody who took their whole year's holiday in February and leaves in April has taken more than they accrued. Whether that can be recovered from the final payment depends on what the contract says and on what local rules permit.
Both halves of that sentence matter. A contractual right to recover is not automatically a right to deduct from a final payment, and the two questions are separate. Where the contract is silent, the realistic answer is often that nothing can be recovered.
Booked but not taken
Days in the system marked as booked for next month are not days taken. They should be added back before the accrual is calculated, and they routinely are not — which produces a shortfall the person will notice immediately.
The reverse error also happens: leave taken in the final week, approved verbally and never entered, which produces an overpayment that is embarrassing to correct afterwards. Reconcile the record against the calendar before the figure is finalised.
Requiring leave to be taken during notice
Where the contract permits it, requiring somebody to take accrued leave during a notice period reduces the final payment and is a legitimate operational choice. It also has to be done properly — with whatever notice the rules require, and before the period is nearly over.
Deciding in the last week that the remaining days will be treated as taken is not that. Whether it can be done at all, and how much notice it needs, is a question for somebody qualified in the place concerned and is worth settling as a standing position rather than case by case.
The daily rate used to pay it
Paying nine days of accrued leave requires a daily rate, and there is more than one way to arrive at one — annual salary divided by working days, divided by calendar days, or an average of recent earnings where pay varies.
Which is correct depends on the contract and on local rules, and for anybody with variable pay it is genuinely difficult. What matters operationally is that the same method is used consistently and that the breakdown says which one. A figure the person cannot reproduce is a figure they will query.
Writing the calculation down
The final payment breakdown should show the leave figure as working, not as a number: entitlement for the year, pro-rated to the termination date, plus carryover, less days taken, equals days paid, at this daily rate.
Five lines. It converts the most queried item in the payment into something the person can check themselves, and it is the single cheapest way to prevent the correspondence that otherwise follows.