Fifty-Two Pay Weeks Never Quite Fill a Year
Payroll is one of the few places where the gap between a week and a year has consequences you can be sued over. A weekly cycle pays 52 times, a fortnightly one 26 — and 26 × 14 is 364 days, which is not a year. The missing day and a quarter accumulates quietly until it surfaces as an extra pay date that nobody budgeted for, or as an annual-leave entitlement that comes out slightly short when it is finally converted from weeks into the days an employee actually books.
Where the Missing Days Show Up
Whole weeks cannot tile a year
Two cycles that never align
Leave is legislated in weeks
An extra period is a real cost
Putting a Week Count on the Annual Line
The input is usually a count somebody has already produced: weeks worked, weeks of leave taken or owed, weeks of a fixed-term engagement, or the number of pay periods a cycle will produce next year.
Enter the week count
Type 52, 26 or 5.6 into the left field and read the year fraction as you type. A comma is accepted where you would write a decimal point, so 5,6 entered on a European keyboard is understood as 5.6.
Read the fraction as a share of the year
The result is directly a proportion: 5.6 weeks of leave shows as 0.1073, meaning 10.73 % of the calendar year is paid non-working time. Multiply by an annual salary and you have the cost of the entitlement.
Reverse it to size a cycle
The swap control (↔) turns the page into years → weeks, which answers the question a payroll calendar actually starts from: one year is 52.1775 weeks, so a fortnightly cycle covers 26.08875 periods and the fraction is what eventually becomes a 27th.
Copy the bare figure into the payroll model
The copy control on each field gives digits with no unit and no separators, ready to be multiplied by a salary or an hourly rate in a spreadsheet. Ctrl + C inside a field does the same.
Pay Cycles and the Weeks They Cover
Six cycles in common use, with how much of a 52.1775-week year each one actually accounts for. The weeks-per-period column is exact for the week-based cycles and an average for the date-based ones, whose real periods vary in length from one month to the next.
| Pay cycle | Periods a year | Weeks per period | What the calendar leaves over |
|---|---|---|---|
| Weekly | 52 (occasionally 53) | 1 | 52 weeks is 364 days, so 1.2425 days a year go unpaid by the cycle; after about 5.6 years that becomes a 53rd pay week. |
| Fortnightly / biweekly | 26 (occasionally 27) | 2 | Same 364-day shortfall, but it needs 14 days to make a whole period — roughly 11 years between 27-date years. |
| Four-weekly | 13 | 4 | Also 364 days, and the tidiest to reconcile: thirteen equal periods, one of which always falls in a different month from last year. |
| Semi-monthly | 24 | 2.1741 (average) | Nothing left over — the periods absorb the odd days — but individual periods run from 13 to 16 days, which complicates weekly overtime. |
| Monthly | 12 | 4.3481 (average) | Covers the year exactly. The cost is that a "month" of pay is nearly four and a third weeks, not four, so weekly rates never divide cleanly. |
| Quarterly | 4 | 13.0444 (average) | Used for directors' fees and some commission schemes; the quarter is 13 weeks plus a fraction, never a round 13. |
The split runs straight down the table. The first three cycles are built from whole weeks and therefore cover 364 days, leaving a remainder that eventually forces an extra pay date. The last three are built from calendar dates, cover the year exactly, and pay for it with periods of uneven length. There is no cycle that is both, which is why the choice is really about whether you would rather manage an occasional extra period or a permanently irregular one.
What This Pair Does in a Payroll Year
Entitlements priced as you type
Both fields convert live, so trying 4, 5.6 and 6 weeks of leave in turn gives three year-fractions to multiply against a salary without pressing anything.
Both directions of the payroll question
Swapping the pair turns "how much of a year is this" into "how many weeks does a year hold", which is where a pay calendar and a 27th-period reserve both start.
Fortnights and days in the same list
The searchable dropdowns hold every time unit in the app, including the fortnight, so a two-week cycle and an entitlement quoted in days can be compared without leaving the page.
Enough decimals for an accrual rate
Results carry up to eight decimals, so 0.01916535 for a single week survives being multiplied by a headcount instead of rounding to a misleading 0.02.
Questions Payroll Gets About Weeks and the Annual Total
Why does a fortnightly payroll occasionally run to 27 pay dates?
Because 26 fortnights cover 364 days and the year is 365.2425, leaving 1.2425 days unclaimed every time. That surplus accumulates until it reaches a full 14-day period, which takes about 11.3 years — hence the familiar rule that a 27-date year comes round roughly once a decade. The same mechanism gives a weekly payroll a 53rd pay week about every 5.6 years, because it only has to accumulate 7 days. For hourly staff the extra period is genuine additional cost. For salaried staff nothing extra is owed, but dividing the annual salary by 27 instead of 26 makes every cheque about 3.7 % smaller, which is worth announcing before it happens rather than after.
Is semi-monthly pay just fortnightly pay under another name?
No, and the difference is exactly two pay dates a year. Fortnightly is a rolling 14-day cycle that floats against the calendar and produces 26 periods; semi-monthly is pinned to dates such as the 15th and the last day, producing 24. In weeks, a fortnightly period is exactly 2 while a semi-monthly one averages 2.1741 but ranges from about 1.86 to 2.29 depending on the month. That variability is why hourly and shift-based employers usually avoid semi-monthly: overtime under weekly-threshold rules has to be calculated on work weeks that no longer line up with the pay period, so a single week can straddle two cheques. Salaried payrolls prefer it, because 24 equal instalments reconcile neatly against monthly accounts.
How much of a year is a statutory leave entitlement?
The EU minimum of 4 weeks converts to 0.0766 years, or 7.67 % of the calendar. The UK's 5.6 weeks — 28 days for a five-day worker, bank holidays included or not depending on the contract — is 0.1073 years, 10.73 %. Entitlements are drafted in weeks rather than days precisely so they scale: someone working three days a week gets 5.6 of their weeks, which is 16.8 days, with no separate rule needed. Converting to a year fraction is what turns the entitlement into a budget line, because multiplying it by total payroll gives the annual cost of holiday cover before any replacement staffing is considered.
How does leave accrue for someone on irregular weekly hours?
By percentage of hours worked rather than by weeks elapsed, and the percentage comes straight out of this conversion. If 5.6 of a worker's 52 weeks are holiday, only 46.4 are actually worked, so the entitlement is 5.6 ÷ 46.4 = 12.07 % of hours worked — the figure that appears throughout UK guidance for irregular-hours and part-year staff. The common mistake is to use 5.6 ÷ 52 = 10.77 % instead, which understates the accrual by about a tenth because it treats holiday weeks as working weeks. Note too that the divisor is 52, not 52.1775: accrual rules use whole working weeks, while the year fraction used for costing does not.
Should an annual figure be built on 52 weeks or on 52.1775?
It depends on whether you are counting events or measuring elapsed time. Anything that happens once per week — a pay run, a timesheet, a shift rota — is counted with whole numbers, so 52 (or 53) is correct and 52.1775 is meaningless. Anything expressed as a rate over time — an accrual, a cost per year, an average weekly figure derived from an annual total — should use 52.1775, because that is genuinely how many weeks a year contains. Mixing them causes a 0.34 % error, small on one salary and material across a large payroll: a weekly rate derived by dividing an annual salary by 52 is 0.34 % higher than the true weekly equivalent, and paying it 53 times in a long year compounds the same gap again.
No comments yet. Be the first to comment!