NOMINAL_ADD Function (OpenOffice Calc)

• Introduced: First release not established; documented by OpenOffice.org 3.3.
• Supported in: Apache OpenOffice 4.1.16; no final supported release is established.
• Scope: English desktop Calc, Analysis add-in compatibility identity and semicolon-separated formulas.
• Checked: October 14, 2026. One ordinary English-name formula was directly entered and recalculated in 4.1.16 on Linux x86-64, Build 9816. The table contains independent references; the failed generated-ODF import is separate.

NOMINAL_ADD returns a nominal annual rate that compounds to the supplied effective annual rate at the specified frequency. It is the Analysis add-in counterpart of the separately registered core NOMINAL function. Release implementation.

=NOMINAL_ADD(EffectiveRate;Periods)

• EffectiveRate: positive effective annual rate as a decimal.
• Periods: positive integer number of equal compounding periods per year.

Both arguments are required. Periods is a signed 32-bit integer in the add-in interface. Use a strictly positive count even though the source’s initial guard is weaker at zero.

These values follow the stated mathematical formulas and the inspected integer-input contract. They are not presented as eight native executions. Results are rounded to twelve decimal places where needed.

An effective annual 12% with monthly compounding corresponds to nominal annual rate approximately 0.113865515215, or 11.3865515215%. Dividing that nominal quote by twelve gives the monthly rate. It is smaller than 12% because compounding supplies the rest of the annual growth.

For two periods the nominal rate is approximately 0.116601048852. With one period it is exactly the original 12%. These results answer a different question from EFFECT_ADD(0.12;12), which starts with a nominal 12% rather than an effective 12%.

The independent formula is m*((1+effective)^(1/m)-1). Raising 1+nominal/m to the power m recovers 1+effective. This round-trip is a useful check of which annual rate the original input represents.

For positive effective e, as m increases the nominal quote approaches LN(1+e). That limit is independent mathematics, not an execution claim for an extreme period count. Keep enough precision in the nominal rate before converting it back; a displayed percentage rounded to two decimals will not generally reproduce the original effective value exactly.

The source rejects EffectiveRate≤0 and a negative integer period count, but its initial guard does not reject zero. The subsequent formula divides by the period count. Use Periods≥1 explicitly; no zero-period result or displayed error was tested, and the lack of an initial guard is not a recommendation to supply zero.

All reference examples use positive rates and ordinary positive integer periods. Fractional conversion, text, blank cells and integer extremes remain outside this scope. This fixed-rate conversion does not determine the annualized cost of a loan with fees or irregular dated payments.

The directly entered English formula =NOMINAL_ADD(0.12;12) produced the saved result 0.113865515215. The English entry and its serialized identity were reviewed together; an ODF canonical spelling alone cannot distinguish every core function from its compatibility add-in.

An earlier generated ODF used fully qualified Analysis service names. All eight import-path attempts for this function displayed #NAME?, despite passing recalculation controls. Those errors do not establish that the English function is unsupported. They also do not count as successful reference-case executions. Do not copy a fully qualified storage name into a normal formula expecting it to behave like the English name.

NOMINAL, EFFECTIVE, RATE.

• Function-specific release implementation
• Separate English and ODF add-in identities

Only the single direct-entry case above is successful native function evidence in this guide. The remaining table values and explanatory identities are independently calculated. The failed generated-ODF workbook, including its informational attribute-load warning, is retained separately. No original XLSX execution, other locale, platform or release is implied.