COUPNCD
Quirk foundCategory: Financial · Last tested 2026-09-01
Real compatibility results for the COUPNCD 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
| Engine | Documented | Live-tested | Verdict |
|---|---|---|---|
| Excel (desktop) | Yes | No — documented only | n/a |
| Excel for the web | — | Yes (recalc, 2026-09-01) | Supported, behaves as documented |
| Google Sheets | Yes | Yes (Drive import, 2026-08-31) | Supported, behaves as documented |
| LibreOffice Calc | Yes | 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 COUPNCD’s support changed — not documentation claims, real results.
| LibreOffice version | Verdict | Tested |
|---|---|---|
| 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 COUPNCD working in LibreOffice?
COUPNCD 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
-
=COUPNCD(A2,A3,3,A5) on
LibreOffice Calc returned
#VALUE!, but the documented/expected
result is #NUM!.
Provenance
Excel documents: "If frequency is any number other than 1, 2, or 4, COUPNCD returns the #NUM! error value."; MISMATCH vs expected: expected '#NUM!', got '#VALUE!'
-
=COUPNCD(A2,A3,A4,5) on
LibreOffice Calc returned
#VALUE!, but the documented/expected
result is #NUM!.
Provenance
Excel documents: "If basis < 0 or if basis > 4, COUPNCD returns the #NUM! error value."; MISMATCH vs expected: expected '#NUM!', got '#VALUE!'
-
=COUPNCD(A3,A2,A4,A5) on
LibreOffice Calc returned
#VALUE!, but the documented/expected
result is #NUM!.
Provenance
Excel documents: "If settlement >= maturity, COUPNCD returns the #NUM! error value."; MISMATCH vs expected: expected '#NUM!', got '#VALUE!'
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.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =COUPNCD(A2,A3,A4,A5) | Microsoft's documented worked example: the next coupon date after settlement, semiannual | 40678 | 40678ProvenanceMicrosoft's page publishes this example's result as the date 15-May-11. The function is documented to return "a number that represents the next coupon date", and 2011-05-15 is serial 40678 in the 1900 date system (days since the 1899-12-30 epoch, confirmed by Python date arithmetic). Setup serials are the dates Microsoft's page prints: 40568 = 2011-01-25 (settlement), 40862 = 2011-11-15 (maturity), frequency 2 (semiannual), basis 1 (actual/actual). Counting coupon dates back from maturity in six-month steps gives 2011-11-15, 2011-05-15, 2010-11-15, so the settlement date falls in the coupon period 2010-11-15 to 2011-05-15, so the next coupon after 2011-01-25 is 2011-05-15 |
Matched |
| =COUPNCD(A2,A3,1,A5) | The same bond paying annually instead of semiannually | 40862 | 40862ProvenanceWith frequency 1 the coupon dates are 2011-11-15 and 2010-11-15, so the next coupon after the 2011-01-25 settlement is 2011-11-15 = serial 40862 -- which for this bond coincides with the maturity date. This discriminates the frequency argument, which the documented example alone does not |
Matched |
| =COUPNCD(A2,A3,3,A5) | A frequency of 3, which is not one of the permitted values | #NUM! | #NUM!ProvenanceExcel documents: "If frequency is any number other than 1, 2, or 4, COUPNCD returns the #NUM! error value." |
Matched |
| =COUPNCD(A2,A3,A4,5) | A day-count basis of 5, above the documented maximum of 4 | #NUM! | #NUM!ProvenanceExcel documents: "If basis < 0 or if basis > 4, COUPNCD returns the #NUM! error value." |
Matched |
| =COUPNCD(A3,A2,A4,A5) | Settlement and maturity swapped, so settlement is after maturity | #NUM! | #NUM!ProvenanceExcel documents: "If settlement >= maturity, COUPNCD returns the #NUM! error value." |
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.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =COUPNCD(A2,A3,A4,A5) | Microsoft's documented worked example: the next coupon date after settlement, semiannual | 40678.0 | 40678ProvenanceMicrosoft's page publishes this example's result as the date 15-May-11. The function is documented to return "a number that represents the next coupon date", and 2011-05-15 is serial 40678 in the 1900 date system (days since the 1899-12-30 epoch, confirmed by Python date arithmetic). Setup serials are the dates Microsoft's page prints: 40568 = 2011-01-25 (settlement), 40862 = 2011-11-15 (maturity), frequency 2 (semiannual), basis 1 (actual/actual). Counting coupon dates back from maturity in six-month steps gives 2011-11-15, 2011-05-15, 2010-11-15, so the settlement date falls in the coupon period 2010-11-15 to 2011-05-15, so the next coupon after 2011-01-25 is 2011-05-15 |
Matched |
| =COUPNCD(A2,A3,1,A5) | The same bond paying annually instead of semiannually | 40862.0 | 40862ProvenanceWith frequency 1 the coupon dates are 2011-11-15 and 2010-11-15, so the next coupon after the 2011-01-25 settlement is 2011-11-15 = serial 40862 -- which for this bond coincides with the maturity date. This discriminates the frequency argument, which the documented example alone does not |
Matched |
| =COUPNCD(A2,A3,3,A5) | A frequency of 3, which is not one of the permitted values | #NUM! | #NUM!ProvenanceExcel documents: "If frequency is any number other than 1, 2, or 4, COUPNCD returns the #NUM! error value." |
Matched |
| =COUPNCD(A2,A3,A4,5) | A day-count basis of 5, above the documented maximum of 4 | #NUM! | #NUM!ProvenanceExcel documents: "If basis < 0 or if basis > 4, COUPNCD returns the #NUM! error value." |
Matched |
| =COUPNCD(A3,A2,A4,A5) | Settlement and maturity swapped, so settlement is after maturity | #NUM! | #NUM!ProvenanceExcel documents: "If settlement >= maturity, COUPNCD returns the #NUM! error value." |
Matched |
LibreOffice Calc 25.8.7.3 (tested 2026-08-31)
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =COUPNCD(A2,A3,A4,A5) | Microsoft's documented worked example: the next coupon date after settlement, semiannual | 40678 | 40678ProvenanceMicrosoft's page publishes this example's result as the date 15-May-11. The function is documented to return "a number that represents the next coupon date", and 2011-05-15 is serial 40678 in the 1900 date system (days since the 1899-12-30 epoch, confirmed by Python date arithmetic). Setup serials are the dates Microsoft's page prints: 40568 = 2011-01-25 (settlement), 40862 = 2011-11-15 (maturity), frequency 2 (semiannual), basis 1 (actual/actual). Counting coupon dates back from maturity in six-month steps gives 2011-11-15, 2011-05-15, 2010-11-15, so the settlement date falls in the coupon period 2010-11-15 to 2011-05-15, so the next coupon after 2011-01-25 is 2011-05-15 |
Matched |
| =COUPNCD(A2,A3,1,A5) | The same bond paying annually instead of semiannually | 40862 | 40862ProvenanceWith frequency 1 the coupon dates are 2011-11-15 and 2010-11-15, so the next coupon after the 2011-01-25 settlement is 2011-11-15 = serial 40862 -- which for this bond coincides with the maturity date. This discriminates the frequency argument, which the documented example alone does not |
Matched |
| =COUPNCD(A2,A3,3,A5) | A frequency of 3, which is not one of the permitted values | #VALUE! | #NUM!ProvenanceExcel documents: "If frequency is any number other than 1, 2, or 4, COUPNCD returns the #NUM! error value." |
Mismatch |
| =COUPNCD(A2,A3,A4,5) | A day-count basis of 5, above the documented maximum of 4 | #VALUE! | #NUM!ProvenanceExcel documents: "If basis < 0 or if basis > 4, COUPNCD returns the #NUM! error value." |
Mismatch |
| =COUPNCD(A3,A2,A4,A5) | Settlement and maturity swapped, so settlement is after maturity | #VALUE! | #NUM!ProvenanceExcel documents: "If settlement >= maturity, COUPNCD returns the #NUM! error value." |
Mismatch |
Docs & syntax
- Excel (desktop): official documentation
- Google Sheets: official documentation
- LibreOffice Calc: official documentation
Where COUPNCD behaves differently
- Bond and treasury functions after a migration: what actually breaks
Executed across 26 fixed-income functions and 161 cases: ODDFPRICE and ODDFYIELD are literal stubs in LibreOffice, TBILLPRICE prices a two-year bill, INTRATE's default basis loses a day, and MDURATION is wrong on actual/actual. 83 of 84 documented #NUM! cases arrive as #VALUE!. Google Sheets matched 127 of 161.