PV in Collabora Office: Discount Payments and a Terminal Balance
Use Collabora PV to separate an annuity from a terminal amount, audit discounting, and keep timing and rate units explicit.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =PV(10%;3;100;1000;0) has expected result −1000. From an investor’s viewpoint, it is an initial outflow that balances three receipts of 100 and a terminal receipt of 1000 at a 10% periodic discount rate.
Syntax and cash-flow viewpoint
=PV(Rate; NPer; Pmt [; FV [; Type]])
Rate is the per-period rate, NPer the number of payment periods and Pmt the constant payment. Optional FV is a remaining terminal value. Type zero means payments at period end and Type one means payments at period beginning; the Collabora reference explicitly documents that timing convention. These examples supply both optional arguments.
A negative result is not inherently an error. The positive receipts are balanced by a negative present cash flow. Use a consistent viewpoint before deciding whether a report should display the result’s sign or its magnitude.
PV calculates a value under supplied constant-rate assumptions. It does not determine an appropriate discount rate or include omitted costs and irregular cash flows.
Example 1: discount each receipt separately
Enter 10%, 3, 100, 1000, 0 in B2:B6, labeled Rate, Periods, Payment, Terminal value and Type. Calculate =PV(B2;B3;B4;B5;B6) in B8.
The independent positive magnitude is 100/1.1 + 100/1.1² + 1100/1.1³ = 1000. The final period contains both its ordinary 100 payment and the terminal 1000. The function result uses the opposite sign, −1000.
The annuity alone has present magnitude approximately 248.685199098. The terminal 1000 has present magnitude approximately 751.314800902. Adding these components confirms the full result.
Example 2: compare beginning payments
=PV(10%;3;100;1000;1) has expected result approximately −1024.868519910. Moving the three payments one period earlier multiplies the annuity component by 1.1. The terminal balance remains at the end of the three-period horizon.
Do not also move the terminal FV to the beginning merely because Type is one. Type controls the periodic payments. Keeping that distinction explicit avoids discounting the terminal value for the wrong number of periods.
Advanced application: build a transparent discount table
Enter periods 1, 2, 3 in A10:A12 and receipts 100, 100, 1100 in B10:B12. Put =B10/(1+$B$2)^A10 in C10 and fill down. =SUM(C10:C12) should have independent target 1000.
This table is valuable when reviewing a model with another person: it shows exactly what money appears in each period. Compare its sum with =-PV(B2;B3;B4;B5;B6) only after confirming the signs and end-of-period schedule match.
For irregular dates, a simple period index is not a substitute for an explicit dated discounting model. PV’s constant-period structure is appropriate only when the modeled intervals align.
Advanced application: separate units from formatting
If a nominal annual rate is 12% with monthly periods, use Rate=12%/12 and express NPer in months. If the stated annual rate is effective, derive the monthly equivalent with (1+annual_rate)^(1/12)-1 instead. These conventions differ.
Do not enter a currency amount formatted as a date or a whole number 10 when 10% was intended. Formatting changes the display; numeric Rate=10 means 1000%, whereas 10% means 0.1.
Boundaries and troubleshooting
At zero rate, =PV(0;3;100;1000;0) has independent target −1300, since no discounting occurs. That boundary is a mathematical check, not a recorded native test.
If you want only a terminal-value calculation, set Pmt explicitly to zero. If you specify Type but have no terminal balance, supply FV=0 rather than leaving an intermediate placeholder ambiguous.
Unexpected signs usually point to an inconsistent cash-flow viewpoint. Unexpected magnitudes often point to mismatched rate/period units or a terminal value counted twice. The reviewed source does not establish all invalid-input error codes, so this guide makes no native error-code guarantee.
Availability and verification
Collabora Office 26.04 desktop help documents PV. The official snapshot was retrieved on 2026-10-13 and hash-verified for this guide on October 15, 2026. Online/mobile support is not inferred from this desktop documentation.
First introduced release and last functioning version are unknown. No native Collabora execution was performed. Expected outputs are independent arithmetic or equation controls, not captured application results. Exact native error behavior, additional versions and extreme numerical cases remain unverified.
References
Formulas use English function names and semicolon separators. The help advises supplying earlier optional arguments when a later optional argument is needed; the worked formulas use explicit values.