COUPPCD Function in Google Sheets: Formula, Examples & Troubleshooting

=COUPPCD(settlement, maturity, frequency, [day_count_convention])

The required arguments are settlement date, maturity date, and yearly coupon frequency. Google permits frequencies 1, 2, or 4. The optional day-count convention defaults to 0. Its documented choices are 0 US NASD 30/360, 1 Actual/Actual, 2 Actual/360, 3 Actual/365, and 4 European 30/360. Supply dates using DATE or another date conversion rather than ambiguous text. Google COUPPCD reference.

The previous coupon date is not necessarily the date the security was issued, bought, or last traded. It describes the payment schedule used by the function. The signature does not accept an issue date or a separate custom list of payment dates.

Assume a regular hypothetical bond pays January 15 and July 15, ending January 15, 2028. Use:

1. In B7 enter =COUPPCD(B2,B3,B4,B5).
2. Apply a date display to B7.
3. The expected date is January 15, 2026.
4. Enter =B2-B7 in B8 and display it as a number. The expected elapsed calendar interval is 59 days.

The independent calendar check steps back from maturity by regular six-month intervals. January 15 and July 15 bracket the March 15 settlement, so January 15 is the preceding schedule date.

Under the date system described by Google’s DATE reference, January 15, 2026 corresponds to serial 46,037. A numeric display of that value is not by itself evidence that the coupon calculation failed. Conversely, changing a text cell’s visual format does not establish that it became a valid date.

Enter these alternative settlement dates in D2:D4:

Use DATE formulas to construct D2:D4. In E2 enter =COUPPCD(D2,$B$3,$B$4,$B$5) and fill down. In F2 use =D2-E2 and fill down.

This illustrates a schedule boundary without asserting the exact behavior of settlement on the coupon date itself. The previous-date result changes when settlement moves across the scheduled July 15 payment; it is not a continuously moving “six months ago” date.

For a review flag in G2, use =IF(F2>120,"Long elapsed interval","Shorter elapsed interval"). Fill down to obtain Shorter elapsed interval, Long elapsed interval, and Shorter elapsed interval. The threshold is an arbitrary inspection rule for this example, not a financial risk classification or accounting standard. Google IF reference.

B8 contains elapsed actual days. It is not an interest amount, and a financial day-count convention may not equal ordinary date subtraction. To calculate an accrued amount, you would also need the security’s rate, principal, relevant coupon length, and applicable terms.

Similarly, a previous coupon date by itself does not reveal whether a payment was actually received. It is a schedule calculation, not a transaction-history lookup. Keep any payment-status data in separately sourced fields.

Unexpected prior month: check frequency and maturity together against the security’s real schedule. The examples assume regular coupon intervals consistent with maturity.

Invalid frequency: use the documented values 1, 2, or 4. A number of months between payments is not the same input as payments per year.

Date-input problems: construct unambiguous dates with DATE. Inspect imported text before using it in the function.

Boundary cases: the reviewed page does not fully specify same-day settlement, fractional date serials, end-of-February schedules, or every invalid-input error. This guide does not promise a particular error code or rounding behavior for those cases.

Irregular first or last coupons: do not treat this four-argument regular-schedule example as a verified model for a custom prospectus calendar. There is no issue-date or first-coupon parameter here.

Google currently documents COUPPCD. Its introduction, retirement, and last functioning version are not established. Matching names in other spreadsheets do not establish identical date-boundary behavior.

Reviewed October 17, 2026: Google COUPPCD, DATE, and IF.

Related published guides: DATE, IF, and DAYS360.