Accrued PTO Is a Debt: How to Calculate Your Leave Liability

Somewhere in every diligence questionnaire, and at every year-end close, the same request appears: accrued leave liability as of the reporting date, per person. Companies that can press a button send a CSV and move on. Companies that can't lose a week to spreadsheet archaeology: exporting balances nobody fully trusts, chasing managers about days approved verbally in March, and multiplying whatever survives by salaries in a tab with no owner. The gap comes down to whether leave balances were treated as real numbers all year. This post is about the number itself: what it is, why it belongs on your books whether you track it or not, and which policy decisions quietly control its size.

Unused days are money you owe

An accrued vacation day that hasn't been taken is a debt. In most EU jurisdictions, untaken statutory leave is payable in cash when someone leaves, priced at their salary on the way out, not the salary they earned the days under. So every day sitting in a balance is a payment you may have to make at today's payroll rates, and auditors treat it that way: whether or not you track it, they'll accrue it. If you can't produce a per-person figure, an estimate goes in the accounts instead. Either way a number gets booked; tracking decides whether it's yours.

Put a number on it

Northlake has 15 people. Salaries average €60,000, which across roughly 250 working days a year prices a day of anyone's time at about €240. At year-end, people carry an average of 6 unused vacation days each.

15 people × 6 days = 90 days. 90 days × €240 = €21,600.

That's the order of magnitude for a small, reasonably healthy team: more than four months of one salary, sitting on the books as time owed. And it's the floor, because salary understates what a day costs the employer. Add social contributions and the real figure lands noticeably higher; the multiplier depends on your country, and your accountant knows it by heart.

Now the compounding part. Suppose nobody books an extra day, and January brings an 8% raise round. The same 90 days now cost about €23,300. The liability grew by €1,700 while everyone was at their desk. Unused leave is one of the few debts that reprices itself upward at every salary review, which is exactly why finance people get twitchy about big balances.

What makes it grow

Three drivers, usually working together. Generous carryover lets days survive December, so the debt rolls forward and stacks. A book-nothing culture keeps supplying it: when leadership never takes a visible holiday and every request feels like an apology, balances climb quietly. And raises do the rest, as Northlake's arithmetic shows: the same ten unused days get more expensive every review cycle without a single new transaction.

The levers you actually control

Cap the carryover. Unused days carry into the next year up to the policy's cap, and anything above it expires. SquadBear's default cap is 5 days. That's the structural backstop: no balance can compound past entitlement plus cap, so the debt has a per-person ceiling.

Apply it gently. A use-it-or-lose-it rule works when people hear about it in September, with enough runway to actually book something. Announced in December, it converts into panic leave, and days taken under duress aren't rest.

Make booking normal before Q4. The cheapest liability reduction is leave actually taken, spread across the year. Managers taking real holidays does more here than any policy text. If you want a concrete ritual, review balances at midyear and nudge while the calendar still has room:

"List everyone carrying more than 10 unused vacation days, so I can talk to their managers before Q4 books up."

What not to do. Don't force-assign leave in the last week of December to shrink the number, and don't cut the carryover cap retroactively on days people already earned. Several jurisdictions restrict how and when statutory leave can expire, and both moves burn trust for a one-time saving.

The leave types that never show up

A leave type with no balance produces no liability line. SquadBear models unlimited types as a policy that accrues 0 days a year: no ledger, no running balance, nothing to run out of, and nothing for a liability report to price. Sick leave defaults to exactly this, unlimited and auto-approved, and the balance-sheet angle is an underrated argument for keeping it that way: a rationed sick-day allowance pushes people to work while ill and adds one more accrued number to reconcile. Unlimited removes both.

Unlimited vacation is a murkier story. In much of the EU a statutory minimum of paid vacation exists whether or not your tool shows a balance, so "unlimited" doesn't make the exit-payout question disappear; it makes it harder to compute. Treat that one as a policy-design debate, not a reporting trick.

Where the number lives

Reports → Leave is the managers-and-admins page holding SquadBear's three leave analytics: an absence summary (who was off and for what, over a chosen range), the leave liability snapshot, and the Bradford factor for absence patterns. The liability report is the one your accountant wants: for a chosen year, each person's remaining balance per leave type, exactly the per-person figure the diligence request asks for. Export it with the CSV button and hand it to finance; they multiply days by their own loaded rates and book the accrual with the judgment that's theirs to apply. Unlimited types don't appear, because there's nothing to price.

With an AI assistant connected, the whole exercise is a sentence:

"Give me this year's leave liability per person and per leave type as CSV for finance."

Start before the questionnaire arrives

A liability report is only as good as the balances underneath it, which is the case for accrual mechanics you can trust rather than a spreadsheet; we walked through those in PTO accrual, explained. Start free and the default policies (annual accrual, a 5-day carryover cap, unlimited sick leave) produce a clean liability snapshot from day one, or ask the demo to pull the report on sample data.

The usual disclaimer, sincerely meant: none of this is accounting, tax or legal advice. How the accrual gets booked, which leave types are payable at exit in your jurisdiction, and what your loaded day rate is are questions for your accountant.

Related reading: CapEx vs. OpEx for engineering time, the other hours-and-money number finance will eventually ask you to prove.