A letter from the Social Security Administration says the name and Social Security number on one of your W-2s don't match SSA's records. Your first instinct might be to panic — about the employee, about your liability, about what the letter implies. Take a breath. The letter itself tells you, in plain language, not to jump to conclusions. And as of this month, SSA's own watchdog has confirmed that the agency's matching systems flag records over trivial spelling differences its own reviewers would accept as matches.
More than 70% of the records that generate these letters belong to native-born U.S. citizens, according to the SSA Office of the Inspector General. A no-match is usually a typo, a name change nobody reported, or a data-entry slip — not evidence of anything about anyone's right to work. What it is evidence of is a payroll-records problem you need to fix, because the IRS can fine you per incorrect W-2, and handling the letter the wrong way can expose you to discrimination claims.
This guide walks through exactly how a small employer should respond: the steps to take, the lines to never cross, and how to keep it from happening again.
What the Letter Actually Is
The "no-match letter" is formally called an Employer Correction Request Notice, or EDCOR. SSA sends it after processing the W-2 wage reports employers file each year, when at least one employee's name-plus-SSN combination doesn't match SSA's records.
Its purpose is narrow and administrative: SSA wants to credit earnings to the right worker's record so future benefit calculations are correct. SSA states explicitly that it is not a law enforcement agency and that a no-match provides too little information to determine its cause. The agency resumed sending these letters broadly in 2019 — by late that year nearly 600,000 employers had received one — after the Inspector General found that roughly three-quarters of employers with mismatched wage items had never been notified at all. Today, any employer with even a single mismatched wage item can expect one.
Read the letter carefully and you'll find its most important sentence: you should not use it to take adverse action against an employee — laying off, suspending, firing, or discriminating — just because a name or SSN doesn't match SSA's records. That warning is doing a lot of work. Everything below flows from taking it seriously.
Why a No-Match Happens (Usually Something Boring)
Before assuming the worst, run through the common causes, because one of these is overwhelmingly the likely explanation:
- Typos and transposed digits. A single flipped digit in a nine-digit SSN, or a misspelled first name, generates a no-match. Payroll data gets re-keyed more often than owners realize.
- Unreported name changes. Marriage, divorce, or a court-ordered change updates the employee's life immediately but updates SSA's records only when the worker tells SSA. If your W-2 shows the new married name while SSA still holds the maiden name, that's a mismatch.
- Hyphenated, compound, and multi-part names. "Garcia-Lopez" vs. "Garcia Lopez" vs. "GarciaLopez," suffixes (Jr., III) included on one record and not the other, and inconsistent treatment of middle names all generate mismatches.
- Employer record errors. The W-4 says one thing, your payroll system says another, and the W-2 inherited the wrong version. Stale data from onboarding is a classic source.
- SSA's own matching tolerances. In September 2026, the SSA Inspector General reported that SSA's automated verification systems reject records over minor name discrepancies — its example was "Ginnie" versus "Jinnie" — that the agency's own manual reviewers are allowed to treat as matches. In other words, some no-matches are artifacts of rigid matching software, not errors by anyone.
Actual SSN misuse exists, but it is a small slice of the total. That 70%-citizens statistic is worth keeping front of mind every time you open one of these letters.
What to Do: A Step-by-Step Response
There is no statute that prescribes an exact procedure or deadline — an old federal "safe harbor" rule with fixed response clocks was proposed in 2007 and later rescinded, so there is no magic timetable today. What the Department of Justice's guidance for employers describes is a reasonable, documented, good-faith process. Follow it the same way for every employee, every time.
Step 1: Check your own records first
Within a few weeks of receiving the letter, compare the flagged name and SSN against your source documents: the employee's Form W-4, your payroll system, and the hiring paperwork. Look specifically for transcription and keying errors. In a large share of cases, the mistake is yours, and you'll spot it here.
If you find your error, correct it in your payroll system and file a corrected wage report — Form W-2c — with SSA, and give the employee their corrected copy. SSA accepts corrections through Business Services Online (BSO), including W-2c Online filing, and offers free AccuWage software to validate correction files before you submit them.
Step 2: If your records look right, notify the employee — in writing
When your side checks out, tell the affected employee about the mismatch promptly and in writing. Keep the message factual and neutral: SSA could not match the name/SSN combination on the W-2; this does not by itself mean anything about work authorization; please confirm the information and contact the local Social Security office to resolve any discrepancy in SSA's records.
Ask the employee to verify that the name and SSN you have on file match their Social Security card exactly, and advise them to visit or call SSA if everything on your end already matches. Document the date you notified them and keep a copy of the notice.
Step 3: Follow up and file corrections
Give the employee a reasonable opportunity to resolve the matter with SSA, then follow up. If corrected information comes back, file the W-2c promptly. If the employee confirms your records are already correct and SSA still shows a mismatch, the discrepancy sits with SSA's records and the employee's follow-through — your job is to show you acted promptly, consistently, and in good faith, and to keep records proving it.
Step 4: Verify before you file next time
SSA offers a free Social Security Number Verification Service (SSNVS) through BSO that lets employers verify employee names and SSNs before filing W-2s. Running new-hire information through SSNVS during onboarding — for every new hire, as a standard step — catches most of these problems at zero marginal cost. It is the single highest-leverage habit in this entire guide.
What to Never Do: The Lines That Create Liability
This is the section that matters most, because the mistakes here are the ones that generate enforcement actions and lawsuits. The anti-discrimination provision of the Immigration and Nationality Act (INA § 274B), enforced by the Department of Justice's Immigrant and Employee Rights Section, is the backstop — and a no-match letter gives you no cover under it.
Never take adverse action based on the letter alone. Do not fire, suspend, demote, lay off, cut hours, or reassign someone just because their name appears in a no-match letter. The letter warns against this explicitly, and doing it anyway can support claims of national-origin or citizenship-status discrimination under federal law, plus exposure under state fair-employment laws.
Never demand a new Form I-9 or specific documents. A no-match letter is not a basis to reverify employment eligibility. Do not ask the employee to complete a new I-9, and do not demand they produce a specific document — no "bring me your green card" or "show me a new Social Security card." Requiring particular documents beyond what the I-9 process allows is document abuse under the INA, and selective reverification targeted at workers you assume to be foreign-born is a textbook discrimination fact pattern.
Never run existing employees through E-Verify because of the letter. E-Verify is a new-hire system used at the time of hire (where the employer participates or is required to). Selectively screening your existing workforce in response to a no-match creates the same discrimination risk as selective reverification — and E-Verify was never designed as a no-match resolution tool.
Never treat the letter as proof of unauthorized work — to anyone. Not in a termination memo, not in a conversation with a manager, not in gossip around the office. A no-match letter "alone is not a statement about an employee's immigration status," in the Justice Department's words. Acting or speaking as though it were is how a paperwork problem becomes a liability problem.
Never apply your follow-up process unevenly. If you give one worker two weeks to visit SSA and another worker two days, or if you follow up rigorously with some employees and shrug with others, the inconsistency itself becomes evidence. One written procedure, applied identically to every flagged employee regardless of accent, surname, or perceived national origin.
Violations of the INA's anti-discrimination provision can bring orders for back pay, civil money penalties assessed per affected individual, and compliance monitoring — an expensive outcome for a letter that started as a typo.
The Money Side: Incorrect W-2s Carry IRS Penalties
Separate from the employment-law risk, mismatched wage reports are incorrect information returns, and the IRS can penalize those under Internal Revenue Code sections 6721 (failure to file correct returns with SSA) and 6722 (failure to furnish correct statements to employees). Both penalties can apply to the same bad W-2.
For returns required to be filed in calendar year 2026, the per-return penalties under section 6721 are tiered by how fast you fix the problem: $60 per return if corrected within 30 days of the due date, $130 if corrected after 30 days but by August 1, and $340 if corrected after August 1 or never — with annual maximum caps of $683,000, $2,049,000, and $4,098,500 respectively. Intentional disregard starts at $680 per return with no annual cap. Smaller businesses with average gross receipts of $5 million or less face lower caps, but the per-return amounts still add up fast across a workforce.
The tiered structure is the IRS telling you exactly what it wants: find errors early and correct them fast. That is another reason to run SSNVS verification at onboarding and to reconcile your payroll register to your filed W-3 and quarterly Forms 941 before the January filing deadline — every mismatch you catch yourself is a $340-per-head problem you never create.
Keep Clean Payroll Records and This Gets Easy
Notice how every step in the response process assumes you can quickly answer basic questions: What name and SSN did the employee give at hire? What did the W-4 say? What did you actually file? Employers with tidy payroll records resolve no-match letters in an afternoon; employers with messy ones spend weeks reconstructing what happened and file their W-2c corrections late, climbing the penalty tiers while they dig.
Build these habits into your routine: verify every new hire's name/SSN combination through SSNVS as part of onboarding, reconcile gross payroll from your payroll register to your Forms 941 each quarter and to the W-3 at year end, and keep W-4s, correction filings, and no-match correspondence filed together by tax year. Separately tracking wages, withholding, and employer payroll taxes in your books — rather than letting net pay be the only number you watch — makes every filing-season reconciliation dramatically simpler.
Simplify Your Financial Management
Responding to a no-match letter is really an exercise in having payroll records you can trust on short notice. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
