Collabora Office EFFECT_ADD: Effective annual rate from nominal compounding
Convert a positive nominal annual rate with EFFECT_ADD, preserve its integer period binding and distinguish its zero-rate restriction from EFFECT.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =EFFECT_ADD(0.12;12) independently gives approximately 0.1268250301, or 12.68250301% effective annually, for a 12% nominal annual rate compounded monthly. Enter 0.12 or 12%, not the number 12, for a twelve-percent rate.
Syntax and model
=EFFECT_ADD(NominalRate; NPerY)
NominalRate is the annual nominal rate. NPerY is the number of equal compounding periods per year. Both are required. The official help describes conversion to an effective annual rate.
The formula is (1+NominalRate/NPerY)^NPerY−1. It assumes that each period uses the same rate and that interest compounds according to that schedule. It does not incorporate account fees, taxes, irregular cash flows or a product’s legally defined disclosure calculation.
The exact analysis add-in requires NominalRate > 0 and a converted NPerY of at least 1. In particular, zero nominal rate is rejected by EFFECT_ADD even though an effective zero rate is mathematically well-defined and is accepted by the unsuffixed EFFECT implementation.
Worked example: monthly compounding
Enter B2 = 0.12 and B3 = 12. Use =EFFECT_ADD(B2;B3).
The periodic rate is 0.12/12 = 0.01. One unit grows to 1.01^12, approximately 1.12682503013197, after twelve periods. Subtracting the initial unit gives 0.1268250301319697.
A percentage display expresses that as 12.6825030132%. The underlying decimal and displayed percentage describe the same rate. A cell containing the number 12 without a percent sign means a nominal rate of 1,200%, a very different input.
The increase above 12% is the result of compounding, not an additional nominal fee. The independent calculation uses high-precision decimal exponentiation; it is not output from a native Collabora session.
Advanced use: compare frequencies at one nominal rate
For the same nominal 12%:
| Formula | Independent effective annual rate |
|---|---|
=EFFECT_ADD(0.12;1) |
0.12 |
=EFFECT_ADD(0.12;4) |
0.12550881 |
=EFFECT_ADD(0.12;12) |
0.1268250301319697 |
Annual compounding gives the nominal rate itself. Quarterly compounding uses 3% per quarter, so 1.03^4−1 = 0.12550881. Monthly compounding produces the result above. This comparison holds the nominal rate fixed; it does not imply that unrelated financial products with different fees and cash-flow terms can be ranked from this formula alone.
The vendor’s separate example =EFFECT_ADD(0.0525;4) independently gives approximately 0.0535426674, matching the help’s rounded 5.3543% presentation. Preserve enough decimal precision before formatting a comparison table.
If you already have an effective annual rate, do not feed it to EFFECT_ADD as though it were nominal. A periodic rate consistent with an effective annual value e over m periods is (1+e)^(1/m)−1, a different transformation.
Integer binding and zero restriction
NPerY is bound as a signed 32-bit integer in the add-in. The caller uses GetInt32, which approximately truncates finite fractional input toward zero. Thus =EFFECT_ADD(0.12;12.9) follows the twelve-period path, not a 12.9-period compounding model. =EFFECT_ADD(0.12;0.9) becomes zero periods and is rejected.
The getEffect evaluator throws IllegalArgumentException for periods below 1 or nominal rate at or below zero, and checks the calculated result for finiteness. The error’s localized UI representation is unverified here. Supplying a negative nominal rate is also outside this add-in’s supported domain.
Distinction from EFFECT and compatibility naming
Unsuffixed EFFECT explicitly returns zero for zero nominal rate. EFFECT_ADD instead rejects it. The suffix is therefore meaningful even though positive-rate integer-period examples commonly agree.
The help describes _ADD names as Excel 2003 compatibility functions. That broad description does not substitute for exact source inspection or prove every cross-product coercion and export behavior. This guide’s scoped evidence is the selected Collabora Linux package source and the small independent calculations above.
Do not round the periodic rate prematurely when constructing a separate audit calculation. Rounding the final displayed percentage is a presentation choice; changing the inputs before exponentiation changes the model’s result.
Product scope, compatibility and evidence
This guide covers the new Collabora Office desktop for Linux, using the Flathub source tag coda-26.04.4.3-1 and commit 81339d176148d0d5c81ff05d82540f58f8aaa117. The official desktop release notes and Linux package manifest identify that product/build. The package manifest is a dated observation from October 18, 2026, rather than an installed-binary check.
The 26.04 function help and exact evaluator source were inspected on October 18, 2026. Expected examples were independently calculated; no Collabora application was run. Expected scalar results were derived from the documented contracts, inspected source and independent calculations; native output formatting and error localization have not been tested. Classic, Online/CODE, other operating systems and file-format round trips require their own checks.
Availability here is established from the function-specific help and the mapped package source. Related functions may have different arguments or boundary rules. The first Collabora release introducing this function is not established by the reviewed sources. No cited retirement or deprecation notice was found. Unknown introduction dates do not imply that the function is deprecated. File-format round trips require separate verification.
Related functions
- EFFECT: compare the unsuffixed zero-rate behavior
- CUMIPMT_ADD: use a correctly matched periodic rate in a payment schedule