ISEVEN in Excel: Test Parity After Truncation
Use Excel ISEVEN with negative decimals, strict integer quantity checks and identifier-based grouping, without mistaking parity for rounding.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: ISEVEN tests whether the integer obtained after truncating a number is even. =ISEVEN(8.9) is TRUE because 8.9 is truncated to 8; the function does not certify that the original input was an integer.
Availability and version history
- Introduced: first introduction version is not established by the official history reviewed; the current product list is not a launch record.
- Availability: official help lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
- Checked: October 14, 2026; official ISEVEN reference. Documentation and independently modeled examples; no native Excel execution or broader platform certification.
Syntax and documented boundary
=ISEVEN(number)
The number argument is required. Decimal fractions are discarded before the parity test. Microsoft also documents #VALUE! for nonnumeric inputs. Exact numeric-text, blank and Boolean coercion details are not fully demonstrated by the dedicated reference, so the validation workflow below explicitly requires ISNUMBER before proceeding.
An even integer is divisible by two with no remainder. Zero is even. Negative signs do not change the parity of an integer.
Example 1: distinguish truncation from rounding
Put these numeric inputs in A2:A9. Fill =TRUNC(A2) in B2 and =ISEVEN(A2) in C2.
| Input | Truncated integer | Expected ISEVEN |
|---|---|---|
| 8 | 8 | TRUE |
| 9 | 9 | FALSE |
| 8.9 | 8 | TRUE |
| 9.9 | 9 | FALSE |
| -8.9 | -8 | TRUE |
| -9.9 | -9 | FALSE |
| 0 | 0 | TRUE |
| -0.9 | 0 | TRUE |
The two negative decimal controls are particularly useful. Truncation moves toward zero; it does not round down to the next more-negative integer. For -8.9, TRUNC gives -8 but INT gives -9. Consequently =ISEVEN(TRUNC(-8.9)) is TRUE while =ISEVEN(INT(-8.9)) is FALSE.
Neither result means Excel disagrees about parity. You asked it to inspect two different integers.
Example 2: require positive, whole, even quantities
A packing rule might allow positive integer quantities divisible by two. ISEVEN alone would incorrectly accept 8.9 and zero. Use this explicit validation formula:
=IF(ISNUMBER(A2),IF(A2>0,IF(A2=TRUNC(A2),ISEVEN(A2),FALSE),FALSE),FALSE)
For the eight numeric controls above, only 8 passes. Both odd integers and all fractional inputs fail; negative and zero quantities also fail. Add a text control ="8" and an error control =NA() in separate rows: both fail the initial type test without being accepted as quantities.
If zero is legitimate for your field, change the positive rule to A2>=0. If negative even integers represent valid adjustments, remove the sign restriction while keeping the integer and numeric-type checks. These are data-policy choices, not changes to ISEVEN itself.
Example 3: separate two groups by a stable integer identifier
Enter integer IDs 101, 102, 103, 104, 105, 106 in E2:E7. In F2 use:
=IF(ISEVEN(E2),"Group B","Group A")
Fill down. The labels are A, B, A, B, A, B, with “Group ” preceding each letter. Sorting the rows by another field does not change the label associated with a given ID, because the formula tests the ID value rather than its row position.
For an intentionally position-based alternation starting at E2, use =ISEVEN(ROW()-ROW($E$2)+1). It gives FALSE, TRUE, FALSE, TRUE, FALSE, TRUE across rows 2–7. Inserting, deleting or hiding rows is not a promise of stable record assignment or visible-row reindexing. Choose ID-based or position-based grouping according to the actual requirement.
Errors and related operations
=ISEVEN("East") is the documented nonnumeric kind of #VALUE! case. Do not expect every unsuitable input to return FALSE. The strict validation formula deliberately produces FALSE for excluded types instead.
EVEN returns a rounded even number; it does not return the Boolean parity answer supplied by ISEVEN. ISODD tests the opposite parity for valid numeric inputs. TRUNC and INT explain the two negative-decimal transformations used above.
These finite controls do not establish meaningful integer parity beyond Excel’s stored numeric precision. Avoid using large identifiers that have already lost digits as numeric parity keys.
References and verification
The datasets are fictional. Expected results follow the cited rules and independent arithmetic or type models; they are not native application captures. Examples use English function names and comma argument separators.