ISOWEEKNUM in Excel: Build Correct ISO Week and Week-Year Reports

• Introduced: the Microsoft function catalogue marks ISOWEEKNUM as an Excel 2013 addition; an exact first build or preview date is not established here.
• Availability: official help lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
• Checked: October 14, 2026; official ISOWEEKNUM reference. Documentation and independently modeled examples; no native Excel execution or broader platform certification.

=ISOWEEKNUM(date)

The one required argument is an Excel date value. There is no return_type argument. Use DATE to create unambiguous controls and format the output as Number rather than Date.

Microsoft’s WEEKNUM reference explains the ISO first-Thursday convention as System 2. Monday-first WEEKNUM mode 2 uses a different rule for week 1; it is not a substitute for ISO numbering near a year boundary.

=ISOWEEKNUM(DATE(2021,1,1))
=ISOWEEKNUM(DATE(2021,1,4))

Expected results are 53 and 1. Friday January 1, 2021 remains in the ISO week that began Monday December 28, 2020. Monday January 4 begins ISO week 1 of 2021.

The result 53 is a valid ISO week number, not evidence that the function misread January as December. The missing piece is the corresponding week-year.

=ISOWEEKNUM(DATE(2024,12,30))

Expected result: 1, belonging to ISO week-year 2025. That week begins Monday December 30 and contains Thursday January 2, 2025.

A label formed as YEAR(date)&"-W"&ISOWEEKNUM(date) would incorrectly produce 2024-W1 for this date. Preserve the difference between the date’s calendar year and the year owning its ISO week.

For date-only A2:

=YEAR(A2-WEEKDAY(A2,2)+4)

WEEKDAY with mode 2 numbers Monday as one. The expression moves to the Thursday of the containing week, whose calendar year is the ISO week-year under the documented convention.

For January 1, 2021 it moves to December 31, 2020, giving year 2020. For December 30, 2024 it moves to January 2, 2025, giving year 2025. This is a derived reporting formula, independently checked with calendar arithmetic.

=YEAR(A2-WEEKDAY(A2,2)+4)&"-W"&TEXT(ISOWEEKNUM(A2),"00")

Expected labels for January 1, 2021; January 4, 2021; and December 30, 2024 are 2020-W53, 2021-W01 and 2025-W01. The two-digit format makes week labels consistently shaped; it does not alter the numeric week.

Keep the original date in another column. A week key groups records and deliberately loses the individual day, so it should not replace a transaction or event date when that detail still matters.

Enter dates December 28, 2020 through January 3, 2021 in A2:A8, one day apart. ISOWEEKNUM returns 53 for all seven, and the derived key returns 2020-W53 for all seven.

Monday January 4 has key 2021-W01. If a report first separates records by calendar YEAR, it splits that seven-day ISO week into two buckets before the week calculation can group them correctly.

For a small independent aggregation control, assign amounts 10,20,30,40,50,60,70 to those seven dates. Their single ISO-week total is 280. Splitting by calendar year would give 100 for December’s four dates and 180 for January’s three, answering a different question.

For January 1, 2021, WEEKNUM(date,2) is 1 while ISOWEEKNUM is 53. For January 4 it is 2 while ISOWEEKNUM is 1. Monday starts alone do not make the functions equivalent.

The documented ISO mode WEEKNUM(date,21) gives the same expected ISO week numbers on these controls. Review WEEKNUM for its additional numbering modes, rather than changing a report’s convention silently.

Microsoft documents #NUM! for an invalid numeric date argument and #VALUE! for an invalid date type. The reference does not resolve every possible text, blank, Boolean or out-of-range coercion combination here, so the controls use valid modern numeric dates.

This guide does not infer a special preview build from its Excel 2013 catalogue marker, nor certify every historic serial boundary or client import path. A correct ISO number still needs the matching week-year and a clearly stated reporting convention.

• Microsoft ISOWEEKNUM reference.
• Editorial testing standards.

Expected results are independent calendar/arithmetic models or explicitly documented rules, not captured native output. Examples use English function names and comma separators. Input dates and schedules are fictional.