EVEN in Collabora Office: Round Away from Zero to an Even Integer

• Introduced: documented by Collabora Office 26.04; the original introduction release is not established.
• Availability: EVEN is documented in the official 26.04 Calc Help.
• Scope: desktop Calc documentation; separately deployed Online and mobile versions have not been verified.
• Checked: October 13, 2026, against the official EVEN reference. Documentation check; not a native application test. Expected examples are independently calculated.

=EVEN(number)

The official Collabora reference describes positive inputs moving upward and negative inputs moving downward to the next even integer. “Away from zero” summarizes those two directions without confusing them with ordinary nearest-number rounding.

The returned value is divisible by two. EVEN does not report TRUE or FALSE about whether the original value is even; it calculates a new numeric result where necessary.

Enter these numeric inputs in A2:A8 and put =EVEN(A2) in B2, filling down.

A tiny move beyond an even integer can cause a two-unit jump. That is the intended boundary behavior, not an ordinary rounding-to-two-decimal-places effect.

Negative values show why “round up” is ambiguous. The result −4 is less than −3.2 on the number line, while its magnitude is larger. Use the away-from-zero rule when explaining the function.

A positive attendance count of 17 is stored in D2. Seats are arranged in complete pairs.

=EVEN(D2)

Expected result: 18 seats. The number of pairs is =EVEN(D2)/2, expected to be 9. The spare-seat count is =EVEN(D2)-D2, expected to be 1.

These are three different quantities: seats, pairs and unused capacity. Label the outputs accordingly. The model assumes a nonnegative integer attendance count; fractional people or negative counts need validation before rounding.

=EVEN(2.1)
=ROUND(2.1;0)

Expected results: 4 and 2. EVEN satisfies an even-integer, away-from-zero requirement. ROUND chooses the nearest integer and does not ensure a pair-sized capacity.

This difference matters near every positive even boundary. A rounding rule chosen for display precision should not be substituted for a capacity rule simply because both are called rounding functions.

For a positive numeric requirement in G2, scaling before and after EVEN can enforce a four-unit capacity:

=2*EVEN(G2/2)

With G2 equal to 9, the expected result is 12. Dividing by two gives 4.5, EVEN raises that to six, and multiplying by two gives twelve. With G2 equal to 12, the result stays 12.

This expression follows the stated scaling rule; it is not a separate rounding mode inside EVEN. For negative inputs it also moves away from zero, which may be inappropriate for a stock or capacity interpretation. Keep operational counts inside their intended domain.

The official documentation explicitly shows zero returning zero. Compare:

=EVEN(0)
=EVEN(0.01)

Expected results: 0 and 2. Zero does not request a pair; any small positive nonzero requirement moves to at least two under this rule.

If the positive fraction represents a measurement rather than a count, decide whether pair rounding has a sensible meaning. The function will calculate a number without knowing the units or the business policy.

If a result seems too large, inspect whether the input is just above an even boundary. Display additional decimals and check upstream arithmetic. Changing a display to show an even-looking integer does not change the stored input.

Use EVEN for even capacity or an explicit even-integer transformation. Use a parity test when you only need a Boolean classification, and use a decimal-rounding function when a specified number of decimal places is the real requirement.

A native test should record the Collabora build and reproduce all seven boundary values, the pair capacity and the scaled multiple-of-four example. The expected outputs above are independently calculated, not target-application execution results.

• Collabora Office 26.04: EVEN, checked October 13, 2026.
• Editorial standards.