COUPDAYSNC in Collabora Office: Count Days Remaining Until the Next Coupon

=COUPDAYSNC(Settlement; Maturity; Frequency [; Basis])

Settlement is the purchase/settlement date, Maturity is the expiry date, and Frequency is the required number of payments per year. Basis selects the day-count convention and defaults to zero.

Use explicit date values, preferably DATE formulas, rather than ambiguous date-looking text. Frequency is a number of payments per year, not a number of months: 1, 2, and 4 mean annual, semiannual, and quarterly payments. Monthly frequency 12 is outside the stated contract.

The function returns a number of days, not a date. The maturity date may be several coupon periods away; it is not necessarily the next coupon date. There are no arguments for price, yield, coupon amount, or a special first/last coupon schedule.

Enter =DATE(2001;1;25) in A2 and =DATE(2001;11;15) in B2. Put 2 in C2 and 3 in D2. In E2 use:

=COUPDAYSNC(A2;B2;C2;D2)

The documented result is 110. The regular semiannual next coupon date is 2001-05-15, as confirmed by the companion COUPNCD example in the same vendor help.

The independent actual-day check =DATE(2001;5;15)-A2 gives 110. This ordinary subtraction is a check for the actual-day example; it is not a universal replacement for a 30/360 day count.

Keep E2 formatted as a number. Formatting 110 as a date would display an unrelated serial-date interpretation and obscure what the function actually returned.

Use settlement 2026-10-17, maturity 2028-01-15, frequency 2, and basis 3, entered through DATE and numeric cells as above. A regular semiannual schedule has its next coupon on 2027-01-15.

The independently expected COUPDAYSNC result is 90, calculated from October 17 to January 15. The remaining actual calendar days to maturity are much larger, so subtracting settlement directly from maturity answers a different question.

If a result is unexpectedly large, first check whether you accidentally used maturity as the immediate next-payment date in a separate manual formula.

For the first documented schedule, the preceding coupon is 2000-11-15. There are 71 actual days from that date to settlement and 110 from settlement to the next coupon, totaling 181.

For the newer regular schedule, the previous coupon is 2026-07-15. The split is 94 elapsed plus 90 remaining, totaling 184 actual days. These explicit date splits help diagnose an incorrect assumed coupon boundary.

The companion COUPDAYS control under basis three is 182.5, showing why the full convention-based period measure need not equal the actual-day sum. Do not “repair” COUPDAYSNC by subtracting elapsed actual days from a different convention’s denominator.

Suppose E5 contains the remaining-day count 90 from the second example. A planning threshold can be expressed as:

=IF(E5<=100;"Within 100 interest days";"Later")

The independent expected label is Within 100 interest days. IF turns the numeric measure into a label, but the label should retain the fact that the count follows the selected basis.

A threshold in business days, calendar hours, or actual days under a different basis is not equivalent. The function does not consult holidays or move payment dates to an observed working day. Do not use the label as a substitute for the actual contractual payment calendar.

Check settlement and maturity order, a permitted frequency, and the intended basis. The dedicated source does not enumerate native handling of invalid dates, fractional frequency, text coercion, settlement exactly on a coupon date, or all month-end adjustments. Those cases are not established here.

The worked schedules deliberately avoid odd coupon periods and month-end boundaries. If a security has irregular first or last coupons, its special dates cannot be encoded with this function’s four arguments alone. ROUND can simplify displayed amounts elsewhere, but it cannot correct an incorrectly modeled schedule.

The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.

The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.

• Collabora Office 26.04: COUPDAYSNC (checked October 17, 2026).
• Editorial testing standards.