Social Security’s core job looks simple from the outside: verify identity, calculate a benefit, send a payment. Behind that transaction sits a sprawling data-matching operation that checks beneficiary records against outside sources most retirees never see — prison rosters, tax records, state vital-statistics files. A September 2026 audit put a number on that apparatus for the first time in years, and it is larger than most descriptions of the agency suggest.
Inside SSA’s 3,400-Agreement Verification Network
The Social Security Administration’s Office of the Inspector General reported on September 3 that the agency runs more than 3,400 data-exchange agreements with outside parties, including prisons, the Internal Revenue Service and state agencies. Those agreements exist to feed SSA the information it needs to keep beneficiary records accurate and stop improper payments before they go out. The agency checks incoming records against the Numident, its master file of personally identifiable information for everyone assigned a Social Security number, using four separate verification systems the audit examined.
Between fiscal years 2021 and 2025, those four systems processed 13.9 billion transactions built from external data. Of those, 1.3 billion — roughly one transaction in eleven — came back as a nonmatch, meaning SSA’s system could not confirm the incoming record belonged to the person on file. The OIG focused its review on that nonmatch pile to determine how many cases were genuine discrepancies versus limitations in the matching systems themselves.
Free first-day checklist: An overpayment notice sets its own deadline, and the first response decides which options stay open. Get the free overpayment response checklist.
Why Minor Name Discrepancies Register as Nonmatches
The audit’s central finding is not that matching failed broadly — it is that some of the failures were avoidable. Auditors sampled nonmatches and found that some of SSA’s automated systems rejected incoming data over minor name discrepancies that the agency’s own manual verification tolerances, or criteria used in other SSA systems, would have accepted as a match. None of the four Numident verification systems reviewed used the same matching criteria as the others, because each was built and is managed independently.
Michelle L. Anderson, the OIG’s Assistant Inspector General for Audit acting as First Assistant, said accurately identifying incoming data is fundamental to program integrity, and that fixing the inconsistency would reduce manual workloads and help prevent improper payments. The OIG’s own estimate frames the stakes in volume rather than dollars: a one-percentage-point improvement in the verified-match rate could produce millions of additional accurate matches every year, each one a case where SSA no longer has to fall back on a manual review or a wrong payment decision.
How a Prison Record Trips a Benefit Suspension
Correctional facilities are one of the named categories behind the 3,400 agreements, and the consequence for a beneficiary is direct. Retirement and disability payments stop once a recipient is convicted and confined for more than 30 consecutive days, though monthly benefits payable to family members on that person’s record can continue. Supplemental Security Income works differently: a recipient loses the SSI payment for any full calendar month spent in jail or prison, with no 30-day threshold. Both rules appear on SSA’s own incarceration page, which also instructs beneficiaries or their families to report a confinement directly rather than wait for a data match to catch it.
Restarting payments after release is not automatic. A beneficiary has to show proof of release, such as discharge papers, before SSA resumes a suspended benefit — which means a data match that arrives late, or a release record that never reaches SSA through one of the correctional-facility agreements, can leave a payment interrupted well past the date someone is actually eligible again.
Wage, Death and Marriage Records Feed the Same Pipeline
The IRS is the second named partner in the OIG report, and its role runs in both directions. Earnings and unearned-income data checked against SSA’s own records can affect the retirement earnings test for someone who claimed benefits early while still working, and it can affect Supplemental Security Income eligibility more broadly, since SSI counts unearned income and resources that outside records sometimes reveal months after a payment already went out. State agencies, the third named category, supply the death and marriage records SSA uses to catch benefits that should have ended or changed — a spousal benefit tied to a marriage state records show already ended, or a payment still going out weeks after a state’s vital-records office recorded a death.
None of these matches are announced in advance. A beneficiary typically learns a record didn’t line up only when a notice arrives stating that SSA has determined an overpayment occurred, describing the amount and the period involved.
The 30-Day Window to Contest a Wrong Match
Federal regulation gives every overpaid beneficiary two separate ways to push back, and OIG’s nonmatch findings are exactly the kind of error those rules were written to catch. A recipient can request reconsideration of the overpayment determination itself — arguing the match was wrong, the amount was wrong, or no overpayment happened at all — or request a waiver, arguing the overpayment was not their fault and that repaying it would cause financial hardship or otherwise be unfair. Both routes are set out in SSA’s codified overpayment appeal and waiver regulations, which trace back to a 1974 federal court order and a 1979 Supreme Court decision establishing that overpaid beneficiaries are entitled to a hearing before money is withheld.
The trigger date is the overpayment notice, not the underlying data match. Requesting reconsideration or waiver within 30 days of that notice keeps SSA from withholding money while the request is pending. SSA separately tells beneficiaries who plan to repay instead of appeal that a smaller monthly repayment rate is available through Form SSA-634, while beneficiaries seeking a waiver rather than repayment file Form SSA-632-BK, either online or by mail to a local field office. A waiver request that cannot be approved on paper alone entitles the beneficiary to a personal conference — an in-person hearing where they can testify, question witnesses and review the evidence SSA relied on before a final decision is made.
SSA has not disputed the OIG’s findings. The agency agreed to both recommendations in the report — building a process for its components to coordinate on matching criteria, and running periodic risk assessments to refine those criteria — but the report sets no completion date for either fix, leaving the current mix of inconsistent verification systems in place while beneficiaries remain the ones who catch a wrong match after the notice arrives, not before.
When A Data Match Becomes A Notice In The Mail
A nonmatch that turns into an overpayment notice rarely explains which SSA response path fits a given situation, and the notice’s own 30-day window does not pause while someone works that out. Reconsideration, waiver and a change in the repayment rate serve three different purposes, and picking the wrong one first can cost a beneficiary time that regulation otherwise protects.
The Social Security Check Protection Kit is an 18-page kit built around the three SSA forms that stop or pause collection (SSA-561, SSA-632, SSA-634) and a first-24-hours plan for a late or missing payment.
Look up the reconsideration, waiver and repayment-rate forms in the The Social Security Check Protection Kit.
This article was researched and drafted with the assistance of AI and reviewed by an editor.



