← All functions

YEARFRAC

Quirk found

Category: Date and time · Last tested 2026-09-01

Real compatibility results for the YEARFRAC function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.

Support matrix

EngineDocumentedLive-testedVerdict
Excel (desktop)Yes No โ€” documented only n/a
Excel for the web— Yes (recalc, 2026-09-01) Supported, behaves as documented
Google SheetsYes Yes (Drive import, 2026-08-29) Supported, behaves as documented
LibreOffice CalcYes Yes (25.8.7.3, 2026-07-29) Quirk found

LibreOffice version history

We executed the same test cases under each LibreOffice release to show exactly when YEARFRAC’s support changed — not documentation claims, real results.

LibreOffice versionVerdictTested
24.2.0.3 Quirk found 2026-08-29
24.8.7.2 Quirk found 2026-08-29
25.2.0.3 Quirk found 2026-08-29
25.8.7.3 Quirk found 2026-07-29

Why isn't YEARFRAC working in LibreOffice?

YEARFRAC exists in LibreOffice 25.8.7.3, but it is not a drop-in match for Excel — our executed tests found real behavioral differences (detailed in the test results on this page). If a formula that works in Excel or Google Sheets misbehaves in LibreOffice, compare your usage against the failing cases above before assuming your data is wrong.

Discovered quirks

Executed test cases

Excel for the web (executed 2026-09-01 via OneDrive recalculation)

These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.

FormulaDescriptionResultExpectedVerdict
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30)) Default basis 0 (US/NASD 30/360): treats every month as 30 days. Days = 6*30+29 = 209, over a 360-day year -> 209/360. Source: https://support.microsoft.com/en-us/office/yearfrac-function-3844141e-c76d-4143-82b6-208454ddc6a8 (worked example rounds to 0.58055556) 0.5805555555555556 0.5805555555555556 Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),1) basis 1 (Actual/actual): actual 211 calendar days between the two dates, divided by 366 since the enclosing 1-year span (Jan 2012-Jan 2013) is a leap year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57650273. 0.5765027322404371 0.5765027322404372
Provenance

211/366 = 0.5765027322404372, matching Microsoft's documented rounded example (0.57650273) to 8 decimal places. Actual/actual leap-year-boundary handling is a documented high-divergence area across spreadsheet engines.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),2) basis 2 (Actual/360): actual 211 calendar days divided by a fixed 360-day year. Source: Microsoft YEARFRAC docs basis table. 0.5861111111111111 0.5861111111111111
Provenance

211/360 = 0.5861111111111111.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),3) basis 3 (Actual/365): actual 211 calendar days divided by a fixed 365-day year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57808219. 0.5780821917808219 0.5780821917808219
Provenance

211/365 = 0.5780821917808219, matches Microsoft's documented rounded example exactly.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),4) basis 4 (European 30/360). For this particular date pair neither day-of-month is the 31st, so the European day-count adjustment never triggers and the result equals basis 0's 209/360. 0.5805555555555556 0.5805555555555556
Provenance

European 30/360 only differs from US 30/360 when a start/end day-of-month is 31; with day 1 and day 30 as here, both conventions compute 209/360 identically.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),9) basis values outside 0-4 are documented as invalid. #NUM! #NUM!
Provenance

Microsoft docs: 'invalid basis values (< 0 or > 4) return a #NUM! error.'

Matched

Google Sheets (executed 2026-08-29 via Drive import)

Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.

FormulaDescriptionResultExpectedVerdict
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30)) Default basis 0 (US/NASD 30/360): treats every month as 30 days. Days = 6*30+29 = 209, over a 360-day year -> 209/360. Source: https://support.microsoft.com/en-us/office/yearfrac-function-3844141e-c76d-4143-82b6-208454ddc6a8 (worked example rounds to 0.58055556) 0.5805555556 0.5805555555555556 Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),1) basis 1 (Actual/actual): actual 211 calendar days between the two dates, divided by 366 since the enclosing 1-year span (Jan 2012-Jan 2013) is a leap year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57650273. 0.5765027322 0.5765027322404372
Provenance

211/366 = 0.5765027322404372, matching Microsoft's documented rounded example (0.57650273) to 8 decimal places. Actual/actual leap-year-boundary handling is a documented high-divergence area across spreadsheet engines.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),2) basis 2 (Actual/360): actual 211 calendar days divided by a fixed 360-day year. Source: Microsoft YEARFRAC docs basis table. 0.5861111111 0.5861111111111111
Provenance

211/360 = 0.5861111111111111.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),3) basis 3 (Actual/365): actual 211 calendar days divided by a fixed 365-day year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57808219. 0.5780821918 0.5780821917808219
Provenance

211/365 = 0.5780821917808219, matches Microsoft's documented rounded example exactly.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),4) basis 4 (European 30/360). For this particular date pair neither day-of-month is the 31st, so the European day-count adjustment never triggers and the result equals basis 0's 209/360. 0.5805555556 0.5805555555555556
Provenance

European 30/360 only differs from US 30/360 when a start/end day-of-month is 31; with day 1 and day 30 as here, both conventions compute 209/360 identically.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),9) basis values outside 0-4 are documented as invalid. #NUM! #NUM!
Provenance

Microsoft docs: 'invalid basis values (< 0 or > 4) return a #NUM! error.'

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-07-29)

FormulaDescriptionResultExpectedVerdict
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30)) Default basis 0 (US/NASD 30/360): treats every month as 30 days. Days = 6*30+29 = 209, over a 360-day year -> 209/360. Source: https://support.microsoft.com/en-us/office/yearfrac-function-3844141e-c76d-4143-82b6-208454ddc6a8 (worked example rounds to 0.58055556) 0.580555555555556 0.5805555555555556 Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),1) basis 1 (Actual/actual): actual 211 calendar days between the two dates, divided by 366 since the enclosing 1-year span (Jan 2012-Jan 2013) is a leap year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57650273. 0.576502732240437 0.5765027322404372
Provenance

211/366 = 0.5765027322404372, matching Microsoft's documented rounded example (0.57650273) to 8 decimal places. Actual/actual leap-year-boundary handling is a documented high-divergence area across spreadsheet engines.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),2) basis 2 (Actual/360): actual 211 calendar days divided by a fixed 360-day year. Source: Microsoft YEARFRAC docs basis table. 0.586111111111111 0.5861111111111111
Provenance

211/360 = 0.5861111111111111.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),3) basis 3 (Actual/365): actual 211 calendar days divided by a fixed 365-day year. Source: Microsoft YEARFRAC docs worked example rounds to 0.57808219. 0.578082191780822 0.5780821917808219
Provenance

211/365 = 0.5780821917808219, matches Microsoft's documented rounded example exactly.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),4) basis 4 (European 30/360). For this particular date pair neither day-of-month is the 31st, so the European day-count adjustment never triggers and the result equals basis 0's 209/360. 0.580555555555556 0.5805555555555556
Provenance

European 30/360 only differs from US 30/360 when a start/end day-of-month is 31; with day 1 and day 30 as here, both conventions compute 209/360 identically.

Matched
=YEARFRAC(DATE(2012,1,1),DATE(2012,7,30),9) basis values outside 0-4 are documented as invalid. #VALUE! #NUM!
Provenance

Microsoft docs: 'invalid basis values (< 0 or > 4) return a #NUM! error.'

Mismatch

Docs & syntax

Related how-to recipes

Where YEARFRAC behaves differently

Compared against other functions