PTO Accrual Methods, Compared

There is one question underneath all of this. On any given day, how much paid time off does this person actually have. An accrual method is a rule for turning employment into entitlement, and the four in common use differ in when the entitlement appears rather than in how much of it exists over a full year.

That timing is not a detail. It decides what happens when somebody books three weeks in February, what a leaver is owed in March, and how much unused time the company is carrying at any moment. Pick the method that gives you the answer you want in those three situations.

The full allowance appears at the start of the leave year and is drawn down as time is booked. Somebody with 20 days has 20 days available on the first morning of the year, whether or not they have worked a day of it.

It is the easiest method to explain and by far the easiest to plan around, which is why small teams gravitate to it. Everybody knows what they have, and booking a fortnight in February needs no arithmetic from anyone.

Where it costs you

• An employee who takes three weeks in January and resigns in February has taken time they had not earned, and recovering it is awkward at best.
• The company carries the full year's liability from the first day of the year rather than building it up.
• Every mid year joiner needs a proration rule, which somebody has to choose and write down. The proration guide covers the options.

Entitlement arrives in twelve instalments. A 20 day allowance adds 1.67 days at the start of each month, so the balance grows through the year and reaches the full allowance in the final month.

This is the method that keeps entitlement and service in step. A leaver in March has earned a quarter of the year and the balance already says so, with no separate calculation. It is also the method that produces the awkward February conversation, where somebody wants a fortnight in the sun and has earned three and a bit days.

Most companies that accrue monthly let a balance go negative for a booking, on the understanding that it will be earned back before the leave is taken. That is a sensible accommodation and it needs a written limit, because an exception without a limit becomes the policy.

Accrual does not have to be monthly. Per pay period is just as common, so a fortnightly payroll adds a twenty sixth of the allowance each run. The principle is identical and only the size of the instalment changes.

Where hours vary week to week, accruing per hour worked is the only method that stays fair. Divide the annual allowance in hours by the annual working hours to get the rate, then multiply by the hours actually worked.

It is the standard approach for hourly and shift based work, and it is often the shape required where local law sets a minimum accrual for paid sick time. It also depends entirely on accurate timekeeping, because the accrual is only ever as good as the recorded hours.

The real cost is comprehension. Very few people can tell you what 0.0385 hours per hour worked means for their summer holiday, so showing the balance in days as well as hours is worth the effort.

Unlimited paid time off removes the balance rather than changing how it fills. There is no accrual, no carryover, and usually nothing to pay out on leaving, because nothing accrued.

It suits companies where output is visible and managers are trusted to approve or refuse on the merits. It suits thin management and an overwork culture much less well, because the allowance was the one signal telling people they were entitled to rest. Tracking still matters, for the reasons set out in the unlimited PTO guide.

Under roughly ten people, an annual grant is almost always right. The administrative saving from accrual is tiny at that size, and the clarity of a single number is worth a great deal. The exception is a team hiring steadily, because every mid year joiner then needs a proration decision.

Between ten and fifty, monthly accrual starts to earn its keep. Joiners and leavers become routine rather than occasions, and a balance that is correct on any given day removes a recurring calculation from somebody's week.

Above that, the method usually follows the payroll system rather than the other way round, and mixed setups become normal: salaried staff on an annual grant, hourly staff accruing per hour, and a separate sick balance following whatever local rules require.

Headcount is the weaker signal though. The stronger one is how much your headcount moves. A stable team can run an annual grant at any size. A team with regular joiners, leavers and contract changes wants accrual, because accrual is self correcting and a grant is not.

Switching mid year is where balances get quietly destroyed. The safe sequence is to close the current leave year on the old method, settle carryover under the old rule, then start the new leave year on the new method. Changing halfway through means every balance in the company needs a manual reconciliation, and somebody will be worse off than they were the day before.

Tell people before the boundary rather than after it. The usual complaint after a move from annual grant to monthly accrual is not that the annual total fell, because normally it did not. It is that somebody planned a June holiday against a balance that no longer exists in June.

If you are writing the change up, the policy guide has the structure and the carryover guide covers the boundary itself. The tracker on this site supports annual, monthly and unlimited policies, as a team default and as a per person override, so a mixed setup does not need a second tool. Try it on your own numbers.