Contact

FLOOR in Collabora Office: Round Down with Signed Steps and Modes

Math Intermediate Collabora Office Calc

Learn Collabora FLOOR’s sign rules, optional arguments and negative modes with complete-batch and pooled-capacity examples.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: FLOOR rounds positive values downward to a multiple. =FLOOR(29;8) is expected to return 24. A negative input uses Collabora’s signed-significance and mode rules.

Availability and version history

  • Introduced: original Collabora release and launch date are not established by the sources reviewed.
  • Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
  • Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
  • Checked: October 14, 2026. Complete function-specific documentation and independent arithmetic controls; no native Collabora test was performed.

Syntax and defaults

=FLOOR(number[;significance[;mode]])

Optional significance defaults to +1 or -1 according to the input’s sign. Positive number with positive significance rounds toward zero. When both are negative, omitted or zero mode rounds away from zero; nonzero mode rounds toward zero.

Opposite signs for number and significance produce a documented error, whose exact label is not pinned here. FLOOR.MATH has a different significance-sign rule.

Examples use English function names and semicolon separators. Negative-number direction means movement on the number line, not simply deleting a fractional part.

Example 1: use only complete batches

A task can consume items only in groups of eight. Put available quantities 29, 32, 35 and 41 in A2:A5:

=FLOOR(A2;8)

Expected usable quantities are 24, 32, 32 and 40. Dividing by eight gives 3, 4, 4 and 5 complete batches. Unused quantities are 5, 0, 3 and 1.

A requirement to cover every item would need an upward-rounding policy instead. This example deliberately counts only complete usable batches.

Example 2: distinguish the two negative modes

=FLOOR(-29;-8)
=FLOOR(-29;-8;0)
=FLOOR(-29;-8;1)

Expected results are -32, -32 and -24. Omitted mode agrees with zero. Nonzero mode changes the direction only for the documented negative-number, negative-significance case.

=FLOOR(-29;8) has opposite signs and is a documented error case. Do not infer FLOOR.MATH’s sign-insensitive behavior for the unsuffixed function.

Advanced example: show both policies beside signed adjustments

Enter -41, -32 and -29 in D2:D4. Fill down:

=FLOOR(D2;-8;0)
=FLOOR(D2;-8;1)

Expected first-column results are -48, -32 and -32. The second column gives -40, -32 and -24. An exact multiple, -32, remains unchanged under either policy.

If these quantities represent a real adjustment, specify which direction is intended before selecting a mode. A function cannot determine the meaning of “conservative” for a signed quantity without that policy.

Advanced example: pooling changes complete-batch capacity

Two stores each hold 15 usable items:

=FLOOR(15;8)+FLOOR(15;8)
=FLOOR(15+15;8)

Expected usable totals are 16 and 24. Separate batching uses eight items at each store. Combining all 30 items permits three complete batches, using 24 items.

The pooled result assumes items may actually be transferred and combined. Rounding the total is not a substitute for modeling physical restrictions.

Default integer rounding and export

=FLOOR(3.45) is expected to give 3, while =FLOOR(-1.234) gives -2. The negative default therefore differs from truncation toward zero; see TRUNC.

Collabora documents exporting its FLOOR as Excel’s FLOOR.MATH and describes FLOOR.XCL for the legacy Excel FLOOR mapping. Actual export/import was not executed here, and the cited Excel version dates are not Collabora release dates.

Zero significance, type coercion, exact native errors and extreme floating-point boundaries remain outside the checked controls.

References and verification

The complete function section was reviewed. Worked results are independently checked expectations; native execution and unlisted edge cases remain unverified.