Leave leakage: when leave is taken but never recorded

When someone is away from work and nobody records it, two things happen at once. The person gets a paid day off. The leave balance in payroll does not move. That gap has a name in Australian payroll and HR practice: leave leakage.

Leave leakage is leave taken but never recorded — often unrecorded annual leave, sometimes a sick day or half-day that never reaches the system. Balances look healthier than they should, the leave liability on the balance sheet is wrong, and on termination unused annual leave is paid out in cash. Days already taken can be paid again.

This piece is for finance directors, people ops leads, bookkeepers and SMB owners who need the liability to match reality.

What leave leakage actually is

Datacom describes leave leakage clearly: a salaried employee is absent, the leave is not recorded (by accident or design), the organisation’s leave liability is not reduced, and the employee still gets a paid day off.

In a healthy cycle, annual leave taken reduces the employee’s balance and the employer’s accrued liability. In a leakage cycle, the day is still paid but the liability stays put. The cost stays invisible until you reconcile days away against approved leave — or until termination forces a payout on an overstated balance.

Datacom reports a concrete test: during a holiday period, one organisation emailed all staff and reconciled automated out-of-office replies against approved leave. Leave valued at over $250,000 was recovered — even though it only caught people who had set an out-of-office reply. Absence was visible somewhere; it was missing from the leave ledger payroll trusts.

Why staff skip the leave form

Remote and hybrid work made the problem easier to miss. A manager knows someone took a sick day, a school-run half-day, or stretched a long weekend into Tuesday — yet the form never lands. Paper processes make it worse: Datacom notes leave forms can go missing after manager approval, so the day off happens and payroll never sees it.

Common patterns Australian teams recognise: “I’ll put it in later”; verbal approval with no payroll entry; half-days that feel too small to log; leave beside public holidays where the calendar looks covered but annual leave is not deducted.

None of this requires bad intent. Process friction is enough. The result is unrecorded annual leave and balances that drift upward relative to days actually worked.

Why the balance sheet gets it wrong

Annual leave is a liability. It accrues as people work and should reduce as leave is taken and recorded. If taken leave is not recorded, the liability does not fall when it should. Finance sees a figure that looks prudent — “we owe a lot of leave” — when part of it is days already consumed.

A related gap: some organisations never surface the liability on the balance sheet at all. Finlert’s leave liability playbook reports that in surveys Finlert conducted, over 43% of respondents said they never post Leave Liability to the Balance Sheet in Xero. That is about accounting presentation in Xero, not leave-leakage prevalence — but if the liability is neither posted nor reconciled to days actually taken, leadership under-sees both the entitlement and the data quality behind it. Finlert also notes hybrid leave taken without official recording, and that stopping accumulation starts with closing leakage.

For directors and bookkeepers, the question is not only “how big is the liability?” but “how much is real unused leave, and how much was already taken?”

Termination turns bad data into cash

Under Australian law, unused annual leave does not sit forever as a soft number. The Fair Work Ombudsman is plain: unused annual leave gets paid out when employment ends. Final pay includes wages owing and any annual leave owing (including loading where it would have been paid if leave were taken during employment). Sick and carer’s leave is not paid out; annual leave is.

When leave leakage has left balances overstated, termination turns the error into cash. The employee is entitled to be paid for leave showing as unused. If some of those days were already taken and never deducted, the business pays twice — once as salary for the unrecorded day away, and again as unused leave on exit. Leave leakage is a finance problem as much as a people-ops one.

What payroll tools report — and what they cannot see

Payroll and leave modules are only as good as the transactions entered into them. They report accrued balances, projected liability and approved requests. They will not invent a deduction for a day nobody submitted.

Competitors and payroll tools, in that sense, report the balances payroll already has. They do not independently know who was away last Tuesday. If the leave form is the only source of truth, every skipped form is a silent overstatement.

Closing leave leakage needs a second input: evidence of days actually taken, reconciled against payroll — as a one-off (like Datacom’s out-of-office check) or each pay cycle.

Muster approaches this from the evidence side: it reads signals your tools already hold, like calendar out-of-office events, Slack and Teams status, and email auto-replies, to work out who was on leave. Each of those days is checked against your leave system, so leave nobody lodged shows up before the pay run, not years later at termination. Nobody fills in an extra form, and you confirm every flag before anything changes. Payroll still owns the official balance; the point is to stop feeding it inflated “unused” leave that was never unused.

A practical check for Australian employers

You do not need a full remediation project to see whether leave leakage is material:

1. Pick a recent holiday window. Compare out-of-office replies or manager knowledge against approved leave in payroll for the same dates.
2. Sample half-days and “WFH but offline” days. These are where forms are most often skipped.
3. On every termination, re-check leave history with the manager before final pay. Fair Work still requires unused annual leave to be paid out on the correct entitlement — getting the balance right protects both compliance and cash.
4. Decide whether leave liability sits on the balance sheet and who reviews it. Finlert’s finding — over 43% of respondents never posting leave liability to the Xero balance sheet — is a reminder that “we don’t book it” is not the same as “we don’t owe it.”

These steps reduce the gap between days taken and days recorded.

Getting leave liability closer to the truth

Leave leakage is undramatic until it is expensive. Staff skip forms. Balances stay high. Leave liability looks larger than the unused leave that remains. On termination, unused annual leave is paid out — so unrecorded leave becomes a real overpayment.

Treat leave as a balance-sheet and final-pay problem, not only an HR form problem, and you are better placed to keep records accurate, stay aligned with Fair Work, and stop paying for days already taken.

If payroll only shows what was already entered, capture the days actually taken and reconcile every cycle. Muster is built for Australian teams that want that check every cycle, from the signals their tools already hold — so leave liability stays closer to reality and final pay does not quietly fund leave leakage.