53-Week Years — When They Happen and Why They Cause Problems in Payroll, Retail, and Finance

Most years have 52 ISO weeks. Every few years, a year has 53. When it does, payroll runs an extra cycle, retail year-on-year comparisons break, broadcast schedules shift, and quarterly reports don't add up the way they did last year.

The 53rd week isn't random. It follows a predictable pattern. But because it happens infrequently — roughly once every five or six years — teams that haven't seen it before often don't realise what's happening until they're already dealing with the consequences.

When Does a Year Have 53 ISO Weeks?

A year gets a 53rd ISO week when January 1 falls on a Thursday, or when it is a leap year and January 1 falls on a Wednesday.

The underlying reason: ISO weeks run Monday to Sunday, and week 1 is the week containing the year's first Thursday. In most years, 365 days divide into exactly 52 weeks and 1 day — so the year "uses up" 52 full Monday-to-Sunday blocks with one leftover day that rolls into the next year. But in long years (where the day-of-week alignment lines up just right), there's enough room for a 53rd full week before the year ends.

53-week years from 2015 to 2040:

Between 2000 and 2100, 71 years have 52 weeks and 29 years have 53 — roughly one in three years, though the gaps are uneven. You can go 6 years without one (2021–2026) or have them closer together (2015, 2020).

How to Tell Whether a Given Year Has 53 Weeks

The most direct way: check whether December 28 exists in week 53. December 28 is always in the last ISO week of the year by definition (it's always within 3 days of December 31, and the last full week always contains it). If ISOWEEKNUM(December 28, year) returns 53, that year has 53 weeks.

from datetime import date

def has_53_weeks(year):
    return date(year, 12, 28).isocalendar()[1] == 53

has_53_weeks(2026)  # True
has_53_weeks(2027)  # False

-- PostgreSQL
SELECT EXTRACT(week FROM DATE '2026-12-28');  -- 53
SELECT EXTRACT(week FROM DATE '2027-12-28');  -- 52

isoWeek(new Date('2026-12-28'))  // 53
isoWeek(new Date('2027-12-28'))  // 52

The Payroll Problem

In a 52-week year, a company running weekly payroll processes exactly 52 pay runs. In a 53-week year, there are 53.

For monthly-salaried employees this doesn't matter — salary is divided by 12 regardless of weeks. But for weekly or bi-weekly payroll it creates real issues:

Weekly payroll: 53 pay runs instead of 52. If employees are paid a fixed weekly amount, total annual compensation comes out higher than the annual salary figure. A $52,000/year employee at $1,000/week gets $53,000 in a 53-week year.

Bi-weekly payroll: Most years have 26 bi-weekly runs. A 53-week year can have 27, depending on where your payroll cycle starts. Employees paid $2,000 per run receive $54,000 instead of $52,000.

The annual budget doesn't match. Payroll budgets are usually set as annual figures. The extra run creates an unplanned expense that can run to millions of dollars for a large employer.

How companies handle it:

• Some reduce the final paycheck to make the annual total come out right — legally this is fine as long as it's disclosed, but employees notice
• Some treat the extra week as a bonus — simpler but more expensive
• Some adjust contributions and deductions (pension, benefits) pro-rata across the extra run
• Best practice is to communicate it in advance and set payroll policy at the start of the year

The issue recurs every 5–6 years and still catches companies off guard because payroll teams turn over and institutional knowledge is lost.

Retail: The 52-Week vs 53-Week Comparable Problem

Retailers that organise their fiscal calendar around weeks — which is most major chains — face a structural year-on-year comparison problem.

A 53-week fiscal year has one more week of trading than a 52-week year. That extra week of revenue makes the full-year number look bigger, but it's not growth — it's just more time. When the following year reverts to 52 weeks, it looks like a decline, even if underlying weekly performance improved.

Example:

• Fiscal 2026 (53 weeks): $530M revenue at $10M/week average
• Fiscal 2027 (52 weeks): $520M revenue at $10M/week average

Revenue fell $10M. But performance was flat. Without adjusting for the extra week, the year-on-year comparison is misleading.

The standard fix: Retailers publish "comparable week" or "like-for-like" figures that exclude the 53rd week from the prior year's comparison. In earnings reports you'll see language like "on a 52-week comparable basis" precisely for this reason.

The rebase problem: After a 53-week year, the calendar shifts by one week. Week 1 of the following fiscal year starts one week later than it did after the previous 52-week year. This means the same calendar week in two adjacent years contains different trading days — comparing "week 14" of 2027 to "week 14" of 2026 compares different sets of dates. Retailers publishing weekly comp figures have to rebase the prior-year series every time a 53-week year occurs.

Broadcast: The 53-Week Schedule Shift

Broadcasting organises its entire commercial calendar around ISO weeks. Advertising is bought and sold in weekly slots. Ratings are aggregated by week. Programming schedules are planned a full year in advance by week number.

A 53-week year forces a one-week shift in every subsequent year's schedule relative to the prior year's. If a season finale aired in Week 20 last year, it will air in Week 20 again this year — but Week 20 this year corresponds to different calendar dates, because the 53-week year reset the alignment.

For networks running multi-year franchise programming this matters: event dates (award shows, sporting finals, seasonal programming) anchor to specific calendar dates, but the weekly schedule anchors to week numbers. In 53-week years these come into conflict.

The broadcast industry typically handles this by publishing a schedule rebase at the start of each year showing how current-year weeks map to prior-year weeks for comparison purposes.

Financial Reporting: The 4-4-5 Calendar

Many companies don't report by calendar month at all. They use a fiscal calendar divided into 13 weeks per quarter, organised in a 4-4-5 pattern (4 weeks, 4 weeks, 5 weeks per quarter). This gives four perfectly equal quarters of 91 days each — a cleaner basis for comparison than calendar months, which range from 28 to 31 days.

In a 53-week year, the 4-4-5 calendar has one extra week to accommodate. Companies handle this differently:

• Some add it to the final quarter (making Q4 a 5-4-5 or 4-5-5 quarter)
• Some add it to Q1 or to the second quarter of the fiscal year
• Some keep a fixed rule (e.g. "extra week always goes in Q4") for consistency

Investors and analysts know to adjust for this. Company earnings releases in 53-week years typically include a note stating that the period contains an extra week and showing what the comparable 52-week figure would have been.

The 4-4-5 calendar users include most major US retailers, many consumer goods companies, and a significant portion of the hospitality and food service industry. If you've ever wondered why a company's fiscal year ends on January 29 rather than January 31, it's because they're snapping to the nearest Saturday at the end of the 52nd or 53rd week.

Manufacturing and Supply Chain: Week-Based Production Planning

Manufacturing plants don't plan by month — they plan by week. A production run is scheduled for a specific ISO week. Raw material deliveries are timed to arrive by Week 12. Finished goods ship in Week 14.

A 53-week year adds a week of capacity that doesn't appear in a 52-week plan. This can be a good thing (extra production time to build inventory before a seasonal peak) or a complication (the 53rd week falls between two fiscal years and capacity isn't budgeted).

Supply chain contracts often specify delivery in terms of ISO weeks. A contract stating "delivery by Week 10" is unambiguous — it means the week containing the Monday of Week 10 in the relevant year. But if the contract was written in a 52-week year and the delivery falls in a 53-week year, the mapping of week numbers to dates shifts, and both parties need to check that their systems agree.

How to Future-Proof Systems for 53-Week Years

Store the ISO week year, not just the week number. Week 1 of 2026 and week 1 of 2025 are different weeks. A database column holding just 1 is ambiguous. Always store the pair: (iso_year, iso_week).

Build 53-week awareness into year-end processes. Any system that runs "once per week per year" — payroll cycles, weekly reports, scheduled jobs — should handle 53 iterations gracefully rather than stopping at 52.

Flag 53-week years in your fiscal calendar at the start of the year. Know in advance whether the current fiscal year will have an extra week. Don't let it be a surprise in December.

Test with 53-week dates. When writing date-handling code, include dates like December 29–31, 2026 in your test suite. These are the most likely to expose week-numbering bugs.

Communicate to employees before payroll surprises them. If your payroll system will run an extra cycle, tell employees in January, not in December when they've already spent the money they expected.

53-Week Years at a Glance

The next several 53-week years, with the relevant calendar boundaries:

Each 53-week year, the week that "shouldn't exist" is just a normal week — it starts on a Monday and ends on a Sunday like any other. The strangeness is entirely in how systems that assume 52 weeks handle it.

Use the ISO Week Number Calculator to check week numbers for any date, or see what week it is today.