COUPNCD Function (OpenOffice Calc)

• Introduced: First release not established; documented by OpenOffice.org 3.3.
• Supported in: Apache OpenOffice 4.1.16; this is a verified release, not a final supported version.
• Scope: Desktop Calc, English function names and semicolon-separated formulas.
• Checked: October 14, 2026. Eight ordinary reference formulas were recalculated from generated ODF in 4.1.16 on Linux x86-64, Build 9816. Source and independent arithmetic were checked.

COUPNCD returns the next coupon date strictly after settlement, represented as a spreadsheet date serial. It derives a regular schedule from maturity and coupon frequency. Format the result cell as a date to read its calendar meaning. Release implementation.

COUPNCD(Settlement;Maturity;Frequency[;Basis])

• Settlement: date at which the regular coupon schedule is evaluated.
• Maturity: later final coupon date; the schedule is anchored to this date.
• Frequency: 1, 2 or 4 payments per year.
• Basis: optional, defaults to 0: US 30/360. Other values are 1 actual/actual, 2 actual/360, 3 actual/365 and 4 European 30/360. The functions implement the release-specific rules discussed below.

The native column contains saved 4.1.16 results; independent references use high-precision arithmetic and the stated source rules. Values are shown to twelve decimal places where needed. Enter DATE expressions directly rather than locale-dependent date text.

Date serials below use the verified December 30, 1899 origin. Calendar interpretations are given in the practical discussion; applying a date format changes presentation, not the stored result.

For March 15, 2024 settlement, December 31, 2025 maturity and two payments per year, the next coupon is June 30, 2024. In the tested workbook’s December 30, 1899 date system this is serial 45473. The first five examples vary the basis while retaining that date.

When settlement is June 30, 2024 itself, the next coupon becomes December 31, 2024, serial 45657. COUPNCD does not return the current coupon date in that case; COUPPCD can.

With quarterly coupons on the same maturity-anchored schedule, January 15, 2024 is followed by March 31, 2024, serial 45382. An annual February-end schedule ending February 28, 2025 returns that maturity date as the next coupon after March 15, 2024.

The algorithm advances by 12/Frequency months, not by 365/Frequency days. Month-end anchoring is therefore important around February and 30-day months. Use COUPDAYSNC for a convention-based count from settlement, rather than subtracting date serials when the intended basis is 30/360.

The source rejects settlement on or after maturity and invalid frequencies. It uses a strictly-later comparison in the next-coupon search; the previous-coupon search has a different inclusive rule. Those comparisons explain the coupon-date example without relying on an ambiguous interpretation of “next.”

All native results were saved as scalar numbers and independently interpreted using the verified workbook date origin. No locale-specific date-format rendering or different date system was tested. A serial such as 45473 is not itself a day count to maturity. Odd first or final coupon structures need a separately specified schedule.

COUPPCD, COUPDAYSNC, COUPNUM.

• Function-specific release implementation
• GetCoupncd schedule/date helper
• lcl_GetCoupncd schedule/date helper
• ScaDate::setDay schedule/date helper
• ScaDate::getDate schedule/date helper
• ScaDate::getDiff schedule/date helper
• Maturity month-end preservation
• Optional basis conversion and validation

The generated ODF produced the informational load warning “Not all attributes could be read.” The sheet was hard-recalculated and saved separately. All eight ordinary function identities, inputs and results were reconciled; a stale SUM cache changed from 999999 to 3 and an uncached SUM returned 7. This establishes the stated examples, not every workbook style or invalid input. Other explanatory identities are independent calculations. The authoring-tool XLSX was not executed in OpenOffice, and its preview values are not the native results reported here.