CUMIPMT Function (Calligra Sheets)

• Introduced: Original introduction release not established; the inspected release is not an introduction date.
• Available: Registered in Calligra Sheets 26.08.2, verified from first-party released source retrieved on October 18, 2026.
• Retired or deprecated: Neither is established by the inspected sources. The function remains registered; retirement and deprecation are different claims.
• Evidence: Selected formulas were executed in the Calligra Sheets 25.04.2 GUI on October 18, 2026. The native-results section lists those observations separately from independent arithmetic and source analysis. 26.08.2 was source-checked only.
• Entry style: English function names, semicolon argument separators and decimal points. Use DATE constructors instead of ambiguous date text. Optional-argument brackets shown in syntax are not entered literally.

=CUMIPMT(rate; periods; value; start; end; type)

All six arguments are required; there are no optional defaults. The internal model uses a zero future balance and a constant rate/payment. There is no fee, balloon, irregular-date or variable-rate argument. For a nominal 12% annual rate with monthly periods, use 0.12/12 and the number of months; do not mix monthly rate with annual period counts.

On a fresh worksheet, enter these inputs:

1. In B8 enter =CUMIPMT(B1;B2;B3;B4;B5;B6).
2. Expect −33.1519817529, or a displayed currency outflow of −33.15 after formatting to two decimals.
3. Keep B8 unrounded for reconciliation. The leading minus sign follows the cash-flow convention; it does not mean the lender pays interest to the borrower.
4. As an independent control, calculate the level payment and roll forward the opening balance period by period.

The independent level-payment magnitude is 1200 × 0.01 / (1 − 1.01^(−12)) = 106.6185464140. For each end-of-period payment, interest equals opening balance × 1%; the remaining payment reduces principal.

Summing the three signed interest amounts gives the expected CUMIPMT value. These calculations use independent decimal arithmetic. The selected native results below separately agree with them.

For the same loan, periods 4 through 12 have expected interest −46.2705752152. Periods 1 through 12 have expected interest −79.4225569681. The first-three and remaining-nine amounts add to the full-year total within rounding.

Use =CUMIPMT(0.01;12;1200;4;12;0) for the later range. Start/end are inclusive, so using 3 as the second range’s start would count period 3 twice. A single-period call with start=end=1 gives −12, which is a useful boundary control.

A displayed positive expense can be produced by negating the returned total in a separate reporting formula. Preserve the underlying signed calculation so it can reconcile with the negative payment and principal components. Do not add the original 1,200 to this interest total: principal repayment is a different component.

The source’s interest helper first computes ordinary end-of-period interest. For any nonzero type, it divides that interest by 1+rate, including period 1. Thus =CUMIPMT(0.01;12;1200;1;1;1) is source-predicted to return −11.8811881188, from −12/1.01. A standard annuity-due first payment made immediately would carry zero elapsed-period interest.

The full type-1 range is source-predicted as −78.6361950179, simply the type-0 interest total divided by 1.01. The selected 25.04.2 native run confirmed this implementation behavior; it is not an endorsement of the timing model. Do not use type 1 for a beginning-payment loan without separately reconciling every period to the intended schedule. See interest helper.

• The source returns its internal errorVALUE for rate ≤ 0, nonpositive periods or principal, start outside 1…periods, end before start, or end beyond periods. The selected zero-rate native test displayed #VALUE!; the other validation branches were source-checked only. A zero-interest loan is mathematically meaningful, but this function rejects rate 0.
• Start/end/type pass through integer conversion. Use actual whole-number period inputs; fractional/text conversion is not established by the ordinary examples.
• The body checks whether type conversion produced an error but does not restrict the resulting integer to 0 or 1. Use only those intended choices; arbitrary nonzero type values are not a supported modeling shortcut.
• Positive principal represents borrowed funds received; calculated payments are negative outflows. Negating a result for a presentation label is different from changing the principal sign, which the function rejects.
• The model does not round every payment to cents. A real lender’s cent-rounded schedule can differ slightly; reconcile against the contract’s rounding and final-payment rules.
• Large period ranges run a loop over included payments in the interest calculation. Keep checks bounded and do not interpret successful evaluation as a performance guarantee for enormous inputs.

The Financial module registers COM.SUN.STAR.SHEET.ADDIN.ANALYSIS.GETCUMIPMT as an alternate name for CUMIPMT. It invokes the same implementation. An alias registration does not establish a workbook import/export guarantee, identical error behavior in other products or availability in every packaged build.

• PMT calculates the constant payment.
• SUM totals a separately constructed interest schedule.
• POWER supports the independent payment calculation.
• KDE CUMIPMT handbook documents the function interface.
• Released function implementation provides the actual validation and calculation rules.

These formulas were recalculated in Calligra Sheets 25.04.2 from a prepared ODS workbook and saved by the application. The table records the native-saved results. Other scenarios remain independent expectations or source analysis unless listed here.

Screenshot: Native Calligra Sheets 25.04.2. Selected cell B2 evaluates =CUMIPMT(0.01;12;1200;1;1;0) and displays -12.0000000000. Column B contains application results; column C contains the corresponding formula text. The type-1 rows also confirm the nonzero first-payment interest described above.

These observations cover only the listed cases in 25.04.2. They do not establish execution in 26.08.2, another locale, general workbook compatibility or the economic validity of unsuitable inputs.