FLOOR in SoftMaker PlanMaker 2026: rounding to multiples

• Introduced: Documented by PlanMaker 2016; the original introduction version is not established.
• Availability: Documented in PlanMaker 2026, with matching syntax in the 2024 reference. This is not a final working-version endpoint.
• Scope: The current reference belongs to the 2026/NX manual family; FreeOffice and individual mobile-build availability are not established here.
• Checked: October 14, 2026, against the official function reference. Documentation and independent calculation; no native test.

FLOOR trims a number down to the nearest allowed increment, not simply a specified decimal precision. With 137 budget units and a step of 25, =FLOOR(137,25) has the expected result 125. A planner can use the function to find the largest complete batch, carton, pallet allocation or time block that does not exceed the available quantity (for positive inputs).

For positive inputs, it selects the greatest multiple not exceeding the input. For negative inputs with a negative base, PlanMaker’s documented rule is to move toward zero: =FLOOR(-42.5,-1) → -42. That is why the function should not be described as the ordinary mathematical floor for every signed input. SoftMaker explicitly says mixed signs yield #NUM!. 2026 FLOOR.

FLOOR is useful for complete batches, lower bounds in budget bands and allowed price steps. For a round-up allocation use CEILING; for nearest multiple use MROUND; for decimal-place rounding use ROUND or ROUNDDOWN. They answer different questions even where examples happen to match. The official PlanMaker 2026 functions list each as a distinct function. FLOOR · MROUND.

=FLOOR(Number, Base)

The PlanMaker 2026 and 2024 English pages document both arguments, no optional default, and a #NUM! error when Number and Base carry opposite signs. A positive input and negative base is not a supported technique for reversing the rounding direction. This page does not invent behavior for base zero or missing arguments because the short vendor entry does not specify it. 2026 · 2024.

Locale and interface: the comma in FLOOR(Number, Base) is exactly the delimiter printed in the English help. Some installations may use translated names and input separators; confirm the accepted punctuation in the installed function assistant. The manual documents the formula-entry dialog and leading = separately. Entering formulas.

Create a new worksheet, type these headers into A1:F1: Scenario, Number, Base, Formula, Expected result, Numeric check. Enter the values listed below into columns A–C in rows 2–10, as ordinary numeric cells, preserving negative signs. Put the indicated formula in D2 and fill it through D10. Column E displays the separately calculated expected answers; enter them as numeric values for the verification calculation. (The table’s formula strings are the ones to type, not text to paste into numeric cells.)

In F2, enter =ABS(D2-E2)<0.000000001 and fill through F10. TRUE means the calculated and expected numbers differ by less than the stated tolerance. Increase displayed precision if the outputs look the same but the check fails.

Documented sign-mismatch diagnostic: in a different empty cell, try =FLOOR(5,-2). Both arguments have opposite signs; the manufacturer’s documentation explicitly specifies #NUM!. Check the input signs instead of masking the error.

Count complete batches without exceeding supply

Suppose H2 = 137 available units and H3 = 25 units per complete bundle. =FLOOR(H2,H3) gives 125 units in complete bundles. =FLOOR(H2,H3)/H3 gives 5 complete bundles, while =H2-FLOOR(H2,H3) shows 12 leftover units that cannot make another bundle. This differs from a round-up procurement question; use the latter only when you actually need additional inventory.

Set a downward price step, without only changing display

With H2 = 12.38 and H3 = 0.05, =FLOOR(H2,H3) has expected numeric output 12.35. If you merely change the number format, the numeric calculation remains based on the original 12.38. The 0.05 example is a mathematical price-step illustration, not a tax or payment compliance policy.

Lower bound for a positive resource interval

With H2 = 73 minutes available and H3 = 15 minutes per complete block, =FLOOR(H2,H3) yields 60 minutes (four blocks), with 13 minutes remaining. A calendar interval that must cover the entire 73 minutes instead requires CEILING, which would yield 75.

Negative adjustments reveal the sign convention

For H2 = -57 and H3 = -12, the documented toward-zero direction for negative inputs yields =FLOOR(H2,H3) → -48 by decimal arithmetic. A careless mathematical-floor assumption would make it more negative, but that is not the convention SoftMaker documents here. The pair (-57,-12) is valid; (-57,12) has opposite signs and is documented to yield #NUM!.

The companion rounding direction

For the same positive (21,5) input, CEILING has the expected result 25 while FLOOR has the expected result 20. On the signed input (-42.5,-1), their expected results are -43 and -42 respectively. Their official documentation pages are CEILING and FLOOR.

Excel comparison needs care: Microsoft’s Excel FLOOR reference documents FLOOR(-2.5,-2) → -2, which agrees with the PlanMaker 2026 sign-matching mathematical expectation for that particular case. Microsoft separately describes positive numbers with negative significance as #NUM!; the entire mixed-sign and zero-input matrix is not proven equal across applications. PlanMaker’s more general vendor text says the arguments must have the same sign. Do not claim full compatibility from one matching example.

• Opposite signs: SoftMaker documents #NUM! when Number and Base have different signs. A negative Base is not a switch that reverses the rounding rule.
• Unexpected negative result: FLOOR reduces the absolute magnitude. Compare the signed examples before choosing a rule for corrections or losses.
• Formula rejected: Both arguments are required. Check the leading =, numeric input cells and the separators accepted by the installed function assistant.
• Display differs from the calculation: Number formatting hides decimal places without changing the stored value. The worksheet checks use a tolerance because fractional steps such as 0.05 can introduce representation differences.
• Zero Base, blanks, text or extreme values: The short vendor entry does not establish a complete error/coercion matrix. Validate inputs; no exact behavior for those cases is claimed here.

For decimal places, see ROUND, ROUNDUP and ROUNDDOWN. For nearest-multiple rounding, see MROUND.

• PlanMaker 2026 — FLOOR: current function definition and vendor examples.
• PlanMaker 2024 — FLOOR: earlier documented syntax.
• PlanMaker 2016 manual: historical function entry, page 533.

Example verification: Expected values were calculated independently using exact decimal and rational arithmetic. No PlanMaker or Excel application execution is claimed. Vendor-documented errors are distinguished from input cases whose behavior still needs a native check.