VLOOKUP Returns the Wrong Value
Your VLOOKUP calculates without complaint, but spot-checking reveals it's pulling the wrong person's data — the most dangerous failure because nothing looks broken.
Excel & Google Sheets
This formula works in both Excel and Google Sheets.
How it works
A wrong value is worse than an error code, because nothing flags it — the report just ships with bad data. The top cause is omitting the fourth argument: without FALSE, VLOOKUP does an approximate match, which assumes the lookup column is sorted and happily returns the nearest smaller value from unsorted data. Always write FALSE (or 0) for exact match. Second, the column number counts positions inside the table range, so inserting or deleting a column in the lookup table silently shifts what column 3 means — your formula now returns the neighboring column. Third, when the lookup column contains duplicate keys, VLOOKUP returns only the first match and ignores the rest, which looks correct until you compare against the second record. Check for duplicates with =COUNTIF(Sheet2!A:A,A2) — anything above 1 means your "match" is really a coin flip that always lands on the first row.
When to use it
Audit these three causes whenever lookup results fail a spot check, after columns are inserted into the lookup table, or when the lookup column may contain duplicate IDs.
Common mistakes
Got a file full of these?
Open it in your browser — every error cell gets highlighted with its fix. Nothing is uploaded.
Did this formula help?
Engine-verified against the sample data aboveLast reviewed 2026-07-08