Main content

Excel #N/A Error: Causes and Proven Fixes

By Szabó Gergő · Updated

#N/A means Excel did not find a match. It is the expected lookup miss, not a broken workbook, until the miss is accidental.

Syntax and arguments

=IFNA(lookup_formula, fallback)
lookup_formula
XLOOKUP, VLOOKUP, MATCH, or XMATCH that may miss.
fallback
Text or number to show when nothing matches.

#N/A examples

01
Friendly lookup miss

XLOOKUP cannot find G2.

=IFNA(XLOOKUP(G2,A2:A100,D2:D100),"Not found")

IFNA keeps other errors visible and only catches #N/A.

02
Trim before matching

IDs in A have trailing spaces.

=XLOOKUP(TRIM(G2),TRIM(A2:A100),D2:D100)

Mismatched spaces are a common hidden cause of #N/A.

03
Match numbers stored as text

G2 is numeric and column A is text.

=XLOOKUP(TEXT(G2,"0"),A2:A100,D2:D100)

Both sides must share a type: all text or all numbers.

Common mistakes

  • Wrapping the whole model in IFERROR

    Prefer IFNA on lookups so #REF! and #DIV/0! still appear.

  • Approximate VLOOKUP on unsorted IDs

    Use FALSE or XLOOKUP exact match for codes and names.

  • Lookup array does not include the value

    Confirm the ID exists on the lookup sheet and that filters are not hiding it.

#N/A FAQ

Is #N/A always a bug?

No. Missing product codes should return #N/A or a planned fallback. Unexpected #N/A on IDs that exist is the bug.

Why does MATCH return #N/A?

The lookup value is not in the array, or match_type does not match how the data is sorted.

Does FILTER return #N/A?

FILTER returns #CALC! when empty unless you pass if_empty. Lookups are the usual #N/A source.