Treasury says a new government-wide verification system screened more than 1.1 billion federal payments worth roughly $3.7 trillion during fiscal 2026. The larger story is not simply a technology upgrade. It is a change in operating doctrine: verify recipients, accounts, and eligibility before taxpayer money leaves the government.
On October 6, the Treasury Department and its Bureau of the Fiscal Service reported that the Do Not Pay program expanded from roughly 4 percent of federal programs having access to all legally authorized data sources at the end of fiscal 2025 to approximately 99 percent during fiscal 2026. Treasury also said agencies screened more than 2.3 billion records, up from 641 million a year earlier, and added nine new datasets.
The most tangible result disclosed was narrow but important: Treasury identified and returned approximately 13,500 payments totaling $175 million that otherwise would have gone to deceased individuals. Bank-account ownership and Taxpayer Identification Number checks also became fully operational on September 30. Those controls give agencies another chance to catch mismatches before disbursement.
Executive Takeaways
- Scale: Treasury says it screened more than 1.1 billion payments worth about $3.7 trillion in fiscal 2026.
- Reach: approximately 99 percent of federal programs can now access all Do Not Pay data sources for which they are legally authorized, versus about 4 percent at the end of fiscal 2025.
- Documented intervention: approximately $175 million across 13,500 payments to deceased individuals was identified and returned.
- Strategic shift: the government is moving from recovery after a bad payment toward verification before funds leave Treasury.
- Accountability gap: access and screening volume are inputs. Congress and taxpayers still need outcome measures covering prevented loss, false positives, appeals, delays, privacy, and program-by-program performance.
What Treasury Actually Reported
Treasury’s October 6 release describes three distinct changes. First, it accelerated access to Do Not Pay, a government-wide service that lets federal agencies and federally funded state-administered programs check authoritative data before an award or payment. Second, it broadened the underlying information. The nine new datasets include business-registration information from OpenCorporates, selected verification against the Social Security Administration’s Numident data, and grantee audit findings from the Federal Audit Clearinghouse. Third, Treasury added payment-level verification for bank-account ownership and the presence and format of Taxpayer Identification Numbers.
These are related controls, but they do not do the same job. An eligibility check asks whether a person or organization is entitled to receive a payment. An identity check asks whether the applicant is who the applicant claims to be. An account check asks whether the destination account belongs to the intended recipient. A tax-identifier check can flag missing or malformed records. Strong payment integrity requires all four questions because a legitimate beneficiary can still be paired with a compromised account, while a valid bank account can still belong to an ineligible claimant.
The legal and policy foundation predates this week’s announcement. The Payment Integrity Information Act of 2019 governs Do Not Pay and requires federal agencies to use it for eligibility verification. President Donald Trump’s Executive Order 14249, issued March 25, 2025, directed Treasury to strengthen pre-certification verification, expand standardized payment information, and reduce fragmentation across federal disbursing offices. An August 2025 Office of Management and Budget memorandum then streamlined agency access while directing privacy protections.
“Pay and chase” accepts the loss first and starts the investigation second. Pre-payment verification tries to reverse that sequence.
Why the Shift Matters
Federal fraud exposure is not a rounding error. The Government Accountability Office estimates direct annual fraud losses between $233 billion and $521 billion, based on fiscal 2018 through 2022 data. GAO separately reported $162 billion in estimated improper payments for fiscal 2024 across 68 reporting programs. Those categories overlap but are not identical: fraud involves intentional deception, while an improper payment can result from administrative error, missing documentation, an incorrect amount, or payment to an ineligible recipient.
That distinction matters when judging Treasury’s results. A returned payment to a deceased person is improper, but the public release does not establish that every case was fraudulent. Some could involve delayed death reporting, agency records that were not updated in time, survivor-benefit complications, or other administrative causes. The defensible conclusion is that pre-payment verification found a material set of payments that required return or correction. It is not evidence that every flagged payment reflected a criminal scheme.
Prevention is generally cheaper than recovery. Once money moves to a fraudulent or mistaken recipient, investigators may need subpoenas, bank cooperation, civil collection, administrative offsets, or criminal prosecution. Some funds cross borders or disappear through mule accounts before an agency recognizes the problem. A reliable pre-disbursement control can stop the loss at the gateway and preserve scarce investigative resources for sophisticated networks.
There is also a national-security dimension. Federal payment systems contain high-value identity, banking, grant, vendor, and program data. Criminal organizations and hostile foreign actors can exploit weak identity proofing, shell companies, stolen credentials, or compromised accounts. Better validation does not eliminate those threats, but it raises the cost of impersonation and creates stronger data trails for investigators.
The Numbers Need Context
Treasury’s headline metrics are impressive, yet scale alone is not proof of effectiveness. Screening 2.3 billion records could reflect useful coverage, repeated checks, broader data matching, or some combination. Verifying $3.7 trillion does not mean $3.7 trillion was suspicious. And moving from 4 percent to 99 percent program access does not show how consistently each program uses the data or acts on results.
The $175 million in returned payments provides a concrete outcome, but it equals less than one-hundredth of one percent of the $3.7 trillion screened. That is not an argument against the system. A control can be valuable even when most legitimate payments pass cleanly. It does mean performance should be judged through avoided loss, accuracy, speed, and cost—not by raw screening volume.
False positives are the central operational risk. If a legitimate Social Security recipient, farmer, veteran, contractor, or disaster survivor is incorrectly flagged, a delayed payment can cause real hardship. Treasury says the controls were designed to protect legitimate payments and that access is governed by privacy, security, and user controls. Congress should still demand published service standards: how quickly exceptions are resolved, how many legitimate payments are delayed, which data source produced the alert, and how recipients correct bad records.
Confirmed Facts Versus RedWaveBrief Analysis
Confirmed: Treasury reported 99 percent program access, 2.3 billion record screenings, more than 1.1 billion payment screenings worth approximately $3.7 trillion, nine additional datasets, and approximately $175 million in returned payments involving deceased individuals. Treasury also said bank-account and TIN verification became fully operational on September 30.
Analysis: centralized verification should reduce some preventable losses, improve investigative targeting, and make payment controls more consistent. However, the October 6 release does not provide a full net-savings calculation, the false-positive rate, administrative cost, program-level results, or the number and duration of legitimate payment holds. Those metrics are necessary before anyone declares the system a complete success.
Three Conditional Scenarios
Base case — steady operational improvement. Agencies integrate the expanded data, most legitimate payments continue without disruption, and preventable losses decline gradually. Treasury publishes clearer program-level reporting while remaining cases move through existing adjudication and recovery channels.
Upside — a durable federal fraud firewall. Real-time account ownership, identity, eligibility, and tax-record checks become standard across Treasury and non-Treasury disbursing offices. Agencies share validated signals under strict privacy rules. Fraud rings face faster interdiction, while legitimate recipients gain a simple correction and appeals path.
Downside — more friction without measurable savings. Agencies count database matches as victories, false positives delay benefits and vendor payments, and inconsistent data creates disputes. If Treasury reports only inputs—records screened and programs connected—Congress cannot determine whether the system saves more than it costs.
Practical Implications
For taxpayers: pre-payment controls offer a credible path to reduce losses, but public confidence depends on transparent outcomes and respect for due process.
For benefit recipients: names, addresses, taxpayer identifiers, death records, and bank ownership should be accurate across agencies. A mismatch may now be detected earlier, but recipients need prompt notice and a clear remedy.
For federal contractors and grantees: legal business names, registration records, audit findings, tax identifiers, and account ownership are more likely to be checked together. Compliance teams should reconcile those records before submitting invoices or award documents.
For Congress: oversight should focus on net prevented loss, confirmed fraud, improper-payment reductions, false-positive rates, payment delays, privacy incidents, appeals, and cost per intervention. Those measures reveal more than the number of databases connected.
Action Checklist
- Verify that federal benefit and vendor profiles use the same legal name and current address as tax and banking records.
- Keep authorized contacts, taxpayer identifiers, and payment accounts current.
- Respond promptly to agency requests for identity, eligibility, or account documentation.
- Do not treat a match or hold as a final fraud determination; request the specific correction and review process.
- Watch for impersonation scams. Treasury verification does not require giving credentials to unsolicited callers or email senders.
What to Watch
- Fiscal 2027 onboarding: whether the remaining programs complete access and integrate screening into normal workflows.
- Outcome reporting: net prevented loss, recoveries, confirmed improper payments, false positives, and payment delays.
- Bank-account verification: evidence that the September 30 controls stop account-takeover and redirection schemes without blocking legitimate recipients.
- Privacy and security: audits showing that expanded data access remains purpose-limited, logged, and protected.
Choose Our Next Deep Dive
Which issue should RedWaveBrief examine next: federal benefit identity verification, contractor payment controls, state-administered program fraud, or privacy safeguards for government data matching?
Ask the Analyst
Have you encountered a federal payment hold, identity mismatch, or account-verification problem? Send your question to support@redwavebrief.com.
Sources & Methodology
This analysis relies on the Treasury Department’s October 6, 2026 results release; Bureau of the Fiscal Service documentation for Do Not Pay; Executive Order 14249 and the related Office of Management and Budget memorandum; and Government Accountability Office reports on fraud and improper payments. Treasury’s operational totals are presented as agency-reported results. RedWaveBrief distinguishes improper payments from proven fraud and labels forward-looking conclusions as conditional analysis.
- U.S. Treasury — Fiscal 2026 fraud and improper-payment prevention results
- Bureau of the Fiscal Service — About Do Not Pay
- Executive Order 14249 — Protecting America’s Bank Account
- OMB Memorandum M-25-32
- GAO — Improper payments and fraud risk management
Read Also
Treasury Cut 125 Names From Its Sanctions Lists: What Modernization Must Deliver →