← All functions

FVSCHEDULE

Quirk found

Category: Financial · Last tested 2026-09-01

Real compatibility results for the FVSCHEDULE 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-31) Supported, behaves as documented
LibreOffice CalcYes Yes (25.8.7.3, 2026-08-31) Quirk found

LibreOffice version history

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

LibreOffice versionVerdictTested
24.2.0.3 Quirk found 2026-08-31
24.8.7.2 Quirk found 2026-08-31
25.2.0.3 Quirk found 2026-08-31
25.8.7.3 Quirk found 2026-08-31

Why isn't FVSCHEDULE working in LibreOffice?

FVSCHEDULE 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
=ROUND(FVSCHEDULE(1,A1:A3),7) Microsoft's documented example: 1 unit of principal compounded at 9%, 11% then 10% 1.33089 1.33089
Provenance

Microsoft publishes this example (=FVSCHEDULE(1,{0.09,0.11,0.1})) with the result displayed as 1.3309. The documented computation -- principal times the product of (1+rate) over the schedule -- is exact here: 1 * 1.09 * 1.11 * 1.10 = 1.330890 with no rounding, so 1.33089 is asserted at 7 dp rather than the page's 4-dp display

Matched
=ROUND(FVSCHEDULE(10000,A1:A2),4) The schedule is applied multiplicatively to any principal 11025 11025
Provenance

10000 * 1.05 * 1.05 = 11025 exactly

Matched
=ROUND(FVSCHEDULE(1000,A1:A3),4) DIVERGENCE PROBE: Excel documents empty cells in the schedule as zeros (a 0% period), not as skipped 1210 1210
Provenance

Verbatim from Microsoft: 'The values in schedule can be numbers or blank cells; any other value produces the #VALUE! error value for FVSCHEDULE. Blank cells are taken as zeros (no interest).' So the blank is a 0% period: 1000 * 1.1 * 1.0 * 1.1 = 1210. An engine that silently skipped the blank would get the same answer here, but an engine that errored on the blank would not -- so this pins the documented 'blank means 0%' rule

Matched
=ROUND(FVSCHEDULE(1000,A1:A2),4) A negative rate in the schedule shrinks the principal 990 990
Provenance

1000 * 0.9 * 1.1 = 990 exactly

Matched
=FVSCHEDULE(1,A1:A2) Non-numeric values in the schedule are an error, not a zero #VALUE! #VALUE!
Provenance

Verbatim from Microsoft: 'any other value produces the #VALUE! error value for FVSCHEDULE'. Note this is the opposite of most statistical functions, which ignore stray text in a reference, and it differs from an empty cell, which the same sentence documents as a zero rate

Matched

Google Sheets (executed 2026-08-31 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
=ROUND(FVSCHEDULE(1,A1:A3),7) Microsoft's documented example: 1 unit of principal compounded at 9%, 11% then 10% 1.33089 1.33089
Provenance

Microsoft publishes this example (=FVSCHEDULE(1,{0.09,0.11,0.1})) with the result displayed as 1.3309. The documented computation -- principal times the product of (1+rate) over the schedule -- is exact here: 1 * 1.09 * 1.11 * 1.10 = 1.330890 with no rounding, so 1.33089 is asserted at 7 dp rather than the page's 4-dp display

Matched
=ROUND(FVSCHEDULE(10000,A1:A2),4) The schedule is applied multiplicatively to any principal 11025 11025
Provenance

10000 * 1.05 * 1.05 = 11025 exactly

Matched
=ROUND(FVSCHEDULE(1000,A1:A3),4) DIVERGENCE PROBE: Excel documents empty cells in the schedule as zeros (a 0% period), not as skipped 1210 1210
Provenance

Verbatim from Microsoft: 'The values in schedule can be numbers or blank cells; any other value produces the #VALUE! error value for FVSCHEDULE. Blank cells are taken as zeros (no interest).' So the blank is a 0% period: 1000 * 1.1 * 1.0 * 1.1 = 1210. An engine that silently skipped the blank would get the same answer here, but an engine that errored on the blank would not -- so this pins the documented 'blank means 0%' rule

Matched
=ROUND(FVSCHEDULE(1000,A1:A2),4) A negative rate in the schedule shrinks the principal 990 990
Provenance

1000 * 0.9 * 1.1 = 990 exactly

Matched
=FVSCHEDULE(1,A1:A2) Non-numeric values in the schedule are an error, not a zero #VALUE! #VALUE!
Provenance

Verbatim from Microsoft: 'any other value produces the #VALUE! error value for FVSCHEDULE'. Note this is the opposite of most statistical functions, which ignore stray text in a reference, and it differs from an empty cell, which the same sentence documents as a zero rate

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-08-31)

FormulaDescriptionResultExpectedVerdict
=ROUND(FVSCHEDULE(1,A1:A3),7) Microsoft's documented example: 1 unit of principal compounded at 9%, 11% then 10% 1.33089 1.33089
Provenance

Microsoft publishes this example (=FVSCHEDULE(1,{0.09,0.11,0.1})) with the result displayed as 1.3309. The documented computation -- principal times the product of (1+rate) over the schedule -- is exact here: 1 * 1.09 * 1.11 * 1.10 = 1.330890 with no rounding, so 1.33089 is asserted at 7 dp rather than the page's 4-dp display

Matched
=ROUND(FVSCHEDULE(10000,A1:A2),4) The schedule is applied multiplicatively to any principal 11025 11025
Provenance

10000 * 1.05 * 1.05 = 11025 exactly

Matched
=ROUND(FVSCHEDULE(1000,A1:A3),4) DIVERGENCE PROBE: Excel documents empty cells in the schedule as zeros (a 0% period), not as skipped 1210 1210
Provenance

Verbatim from Microsoft: 'The values in schedule can be numbers or blank cells; any other value produces the #VALUE! error value for FVSCHEDULE. Blank cells are taken as zeros (no interest).' So the blank is a 0% period: 1000 * 1.1 * 1.0 * 1.1 = 1210. An engine that silently skipped the blank would get the same answer here, but an engine that errored on the blank would not -- so this pins the documented 'blank means 0%' rule

Matched
=ROUND(FVSCHEDULE(1000,A1:A2),4) A negative rate in the schedule shrinks the principal 990 990
Provenance

1000 * 0.9 * 1.1 = 990 exactly

Matched
=FVSCHEDULE(1,A1:A2) Non-numeric values in the schedule are an error, not a zero 1.09 #VALUE!
Provenance

Verbatim from Microsoft: 'any other value produces the #VALUE! error value for FVSCHEDULE'. Note this is the opposite of most statistical functions, which ignore stray text in a reference, and it differs from an empty cell, which the same sentence documents as a zero rate

Mismatch

Docs & syntax

Where FVSCHEDULE behaves differently