COUPNCD in Collabora Office: Find the Next Regular Coupon Date
Find Collabora COUPNCD dates, format serial results correctly, audit annual versus semiannual schedules, and avoid treating maturity as the next payment.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =COUPNCD(DATE(2001;1;25);DATE(2001;11;15);2;3) has documented date result 2001-05-15. It returns the first interest-payment date after settlement; format the result as a date.
Syntax and arguments
=COUPNCD(Settlement; Maturity; Frequency [; Basis])
Settlement is the purchase/settlement date. Maturity is the expiry date, which anchors the regular schedule. Frequency is required, while Basis is optional and defaults to zero.
| Basis | Documented day-count convention |
|---|---|
| 0 or omitted | US NASD, twelve 30-day months |
| 1 | Actual days in months and actual days in the year |
| 2 | Actual days in months, 360-day year |
| 3 | Actual days in months, 365-day year |
| 4 | European method, twelve 30-day months |
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 result is a date value, not a day count or a payment amount. There is no argument for holidays, business-day adjustment, an issue date, or an irregular first coupon. A mathematically regular coupon date need not be the operational bank-processing date.
Example: reproduce the vendor date
Put =DATE(2001;1;25) in A2, =DATE(2001;11;15) in B2, 2 in C2, and 3 in D2. In E2 enter:
=COUPNCD(A2;B2;C2;D2)
Format E2 as YYYY-MM-DD. The documented expected display is 2001-05-15. The semiannual schedule reaches maturity on November 15, so the preceding scheduled payment in that year is May 15.
As an independent audit, =E2-A2 should represent 110 actual days for these dates. The related COUPDAYSNC example explicitly gives 110 under basis three. This subtraction checks the date output without confusing it with a convention-based day count for every other basis.
Example: compare annual and semiannual schedules
Use the same 2001 dates and basis three, but put frequency 1 in a second row. The independently modeled annual schedule’s next date is 2001-11-15, while frequency 2 gives the documented 2001-05-15.
The annual case has only the maturity-year payment remaining before maturity; the semiannual case has an earlier payment. Frequency is therefore essential to finding the date. A maturity date alone does not define the payment calendar.
These additional schedule outputs are independent expectations from the regular-frequency model, not native executions.
Advanced example: a quarterly schedule crossing a year boundary
Enter settlement 2026-10-17, maturity 2028-01-15, frequency 4, and basis 3. The regular quarterly dates around settlement are 2026-10-15 and 2027-01-15.
The independently expected next coupon is 2027-01-15. October 15 has already passed, so it cannot be the first coupon after settlement. The next date is 90 actual days after October 17.
List the modeled schedule explicitly when auditing: January 15, April 15, July 15, and October 15. Changing settlement to an ordinary date before October 15 would move the next coupon back into October. Exact coupon-day equality behavior is outside the tested controls in this guide.
Advanced application: build a dated planning label
Keep the returned date in E5 as a numeric date. Use a separate F5 cell for =E5-A5, giving 90 in the newer example. A threshold label can then use IF, such as =IF(F5<=100;"Review upcoming coupon";"Later").
The independent expected label is Review upcoming coupon. Retain E5 as the actual scheduled date so the label does not become the sole record. A reminder threshold does not alter the security’s schedule or establish an investment recommendation.
DAY or MONTH can inspect components of the returned date. Extracting a month number loses the year, so do not use that number alone to order future payments across December and January.
Errors and limitations
If the output looks like an integer, apply date formatting before assuming the calculation failed. If the displayed date is wrong, check frequency, maturity, and the actual underlying date values.
The dedicated help does not fully define invalid-input error codes, all month-end adjustments, or settlement exactly on a coupon date. The examples use valid dates and regular schedules away from those boundaries. Irregular coupons and observed working-day shifts require additional information not accepted by this function’s syntax.
Availability and verification
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.
References
- Collabora Office 26.04: COUPNCD (checked October 17, 2026).
- Editorial testing standards.