Federal agencies flagged roughly $186 billion in improper payments across 64 programs in fiscal year 2025, an increase of $24 billion over the prior year, according to GAO’s April 2026 payment integrity report. The government’s front-line response to that number is a Treasury data-matching system most grantees have never logged into. Do Not Pay federal payment verification is the screen your organization passes through before an award is signed and again before every dollar leaves the Treasury — and almost nothing about it is visible from your side of the transaction.

Do Not Pay Federal Payment Verification Runs Four Times

Grant guidance usually mentions Do Not Pay once, in the context of pre-award review, and moves on. Treasury’s own operating manual describes something considerably wider. Chapter 6000 of the Treasury Financial Manual instructs agencies to build verification into four distinct points in the money lifecycle.

The first is pre-award verification: screening applicants to confirm eligibility before an award is made or a benefit approved. This is the checkpoint that appears in 2 CFR 200.206, which requires the agency to review eligibility and financial-integrity information in OMB-designated databases under the Payment Integrity Information Act before making an award.

The second is pre-payment verification: confirming recipient eligibility before disbursement, including ongoing eligibility for recurring payments. If your award pays in quarterly drawdowns, this screen fires quarterly.

The third is payment verification, and it is the one most grantees do not know exists. Payments disbursed through Treasury are screened automatically at the moment of disbursement, independent of whatever the awarding agency already checked. Treasury applies configurable business rules that can return a payment before certification. The agency then has to review the return, reconcile it, and decide whether to resubmit.

The fourth is post-payment analysis, where match results feed corrective actions and recovery efforts — the mechanism by which a payment you already spent becomes a payment someone wants back.

Four screens means four independent opportunities for a records problem to surface, and they are not redundant. Clearing pre-award review tells you nothing about whether your October drawdown will clear. Organizations building a compliance calendar for federal grant awards tend to map deadlines and reports; almost none map payment screens.

What Actually Gets Matched: Your EIN, Not Your Merits

The system does not evaluate your program. It performs identifier matching. According to the Congressional Research Service, Treasury’s working system queries multiple databases simultaneously using unique identifiers of the intended recipient — Social Security number, taxpayer identification number, employer identification number, or Unique Entity Identifier — alone or combined with a first name, last name, or business name. It uses exact match logic.

Exact match logic is the entire story for a legitimate grantee. The databases behind Do Not Pay federal payment verification include the Death Master File, debarment and exclusion records, and bank-account validation sources. As of March 2025, Treasury facilitated access to at least 19 of them. Your organization is unlikely to appear on an exclusion list. Your organization is quite likely to have a legal name in SAM.gov that differs by a comma from the name on your IRS determination letter, or a signatory whose Social Security number collides with a death record that was recorded in error.

That distinction reframes what preparation means. There is no narrative to strengthen and no reviewer to persuade. The only lever is whether the strings of characters your organization has registered across SAM.gov, the IRS, your bank, and the awarding agency’s payment system are identical to one another. This is a records-hygiene problem wearing a fraud-prevention costume.

Where the mismatches actually originate

Four sources produce most of them: a legal entity name updated in one system and not the others; a UEI attached to a parent organization while the award names a subsidiary; a bank account closed or converted during a merger; and an authorized representative’s personal identifiers, which enter the screen for sole proprietors, single-member LLCs, and many small nonprofits applying for small business grant programs.

A Returned Payment Doesn’t Come With a Letter

Here is the asymmetry that makes this worth your attention. When an application is rejected, you get a letter. When a payment fails verification, you get silence and a delay.

Treasury’s process notifies the agency that a payment failed screening, through existing payment channels, before agency certification. Full match results land in the Do Not Pay Web Portal — a portal your organization has no login for. The agency reviews the return, reconciles reports, and determines whether resubmission is required. If the agency is legally required to disburse anyway, it can resubmit using an override code or negotiate a custom business rule with Treasury.

None of those steps generate a notice to you. From the recipient’s chair, a screening failure looks exactly like a slow accounts-payable department. That is why the practical advice differs from ordinary compliance advice: if a drawdown you expected in two weeks has not landed in four, the right move is not to wait politely. Ask your grants officer directly whether the payment was returned in screening and, if so, which data element triggered it. Naming the mechanism gets you a faster answer than asking about the status of a payment.

It also matters that a match is not a determination. The Congressional Research Service is explicit that the system does not automatically stop a transaction, and that matching does not necessarily mean a recipient is ineligible. The statute itself, at 31 U.S.C. 3354, contemplates circumstances where law requires a payment regardless of a flag. The flag creates friction and delay, not a verdict — but friction on a reimbursement-based award is a cash-flow event, and organizations financing federal work out of their own reserves feel it immediately.

The December 27 Rule That Gives You an Error-Correction Right

The most consequential recent change is not a regulation. It is a short statute.

The Ending Improper Payments to Deceased People Act (P.L. 119-77) was approved on February 10, 2026, and its amendments take effect on December 27, 2026. It does two things that cut in the recipient’s favor. First, it bars the Commissioner of Social Security from recording a death on a shared record unless there is clear and convincing evidence that the individual should be presumed deceased. Second, when someone is incorrectly identified as deceased, it requires notification of any agency operating under a cooperative arrangement — including the entity running the Do Not Pay working system.

Read plainly, that is the first federal error-correction plumbing built specifically around this screen. Until now, a person wrongly listed in death data had to chase the correction agency by agency. After December 27, the correction is supposed to propagate.

The surrounding policy has moved in the opposite direction — toward more screening, faster. Executive Order 14249 directed Treasury to enhance verification of payments made on agencies’ behalf, and OMB Memorandum M-25-32, issued August 20, 2025, streamlined agency access by directing agencies to add a Privacy Act routine use permitting disclosure of records to Treasury and by establishing criteria for a four-year waiver of computer matching agreements. Agencies have been publishing those routine-use notices through 2026. Object class 41.0 — grants, subsidies, and contributions — sits squarely inside the waiver-eligible list.

The direction of travel is unambiguous: more data flowing into the screen, more automatic returns, and one narrow statutory channel for fixing a specific class of error. Treasury reports the program helped prevent, detect, and recover $11.7 billion in fiscal year 2025, per the Bureau of the Fiscal Service. A program producing that number does not get smaller.

The Reconciliation Drill: Make Your Identifiers Agree Before You Draw Down

Because the screen is mechanical, the preparation is mechanical too. Run this before your next award start date, not after a payment goes missing.

1. Pull four name strings side by side. Your IRS determination letter or EIN assignment notice, your SAM.gov entity registration, your bank’s account title, and the applicant name on the award document. Character-for-character. Abbreviations, punctuation, “Inc.” versus “Incorporated” — all of it.
2. Confirm the UEI belongs to the entity that signed. Parent-subsidiary and fiscal-sponsor arrangements are the most common source of a legitimate mismatch. If a sponsor is the applicant of record, the sponsor’s identifiers govern the payment.
3. Validate the bank account as an account title, not a number. Account ownership and status are screened data points, not just routing accuracy. A closed account from a prior banking relationship is a silent failure.
4. Check the individual identifiers you did not think were in scope. Sole proprietors, single-member entities, and small organizations where a founder’s SSN functions as the taxpayer ID are screened as individuals.
5. Fix the source, then wait for propagation. Correcting SAM.gov does not retroactively correct the IRS record or your agency’s payment file. Sequence the corrections and allow validation time before the first drawdown.

This drill takes an afternoon and belongs in the same block of work as SAM.gov renewal. If you are still deciding which programs to pursue, it is worth doing the same identifier check before you apply — a searchable grant database will tell you what you are eligible for, but only your own records tell you whether a payment will clear. The same reconciliation applies to organizations pursuing nonprofit grant funding, where fiscal sponsorship arrangements make the applicant of record ambiguous more often than anywhere else.

Frequently Asked Questions

Can my organization see its own Do Not Pay record?

No. The Do Not Pay Web Portal is built for federal agencies and for states administering federally funded programs. There is no recipient-facing lookup and no self-service dispute form. Your practical route is to ask the awarding agency’s grants or payment office whether a specific payment failed screening and which data element caused it, then correct the underlying record at its source — SSA, IRS, SAM.gov, or your bank.

Does a match automatically stop my payment?

No. Do Not Pay federal payment verification surfaces information; the agency makes the eligibility determination. Statute at 31 U.S.C. 3354 explicitly recognizes that a payment may be legally required even when a recipient is flagged as potentially ineligible. Treasury’s separate payment-verification layer can return a payment before certification, but agencies may resubmit using documented override codes or agency-specific custom rules.

Are subrecipients screened too?

The verification obligation attaches to the entity being paid, so a pass-through entity’s payments to subrecipients are not automatically run through Treasury’s system the way a federal disbursement is. But pre-award risk review at the prime level increasingly incorporates the same databases, and pass-through entities carry their own monitoring duties. Assume a subrecipient with a records problem becomes your problem.

What changes on December 27, 2026?

Amendments under P.L. 119-77 take effect. The Social Security Administration may not record a death on a shared record without clear and convincing evidence, and it must notify agencies with cooperative arrangements — including the Do Not Pay working system — when someone was incorrectly identified as deceased. It is a correction mechanism for one specific and unusually damaging category of false match.

Does this apply to state-administered federal money?

Yes. The Payment Integrity Information Act extends access to states and their agents responsible for reducing improper payments in federally funded, state-administered programs, and Treasury has built state-facing data hubs. If your funding arrives through a state agency rather than directly from Washington, the same identifier logic applies one layer down.

Bottom Line: Treat Verification as a Records Deadline

The instinct with a compliance topic is to add it to a checklist and revisit it when something breaks. That instinct fails here, because Do Not Pay federal payment verification breaks quietly and on someone else’s screen. There is no rejection letter to react to and no portal to check.

So convert it into something you can actually schedule. Put the identifier reconciliation drill on the calendar at two fixed moments: thirty days before any award start date, and alongside your annual SAM.gov renewal. Those are the two points where a mismatch is cheap to fix. Every other point, it costs you a delayed drawdown on money you have already spent.

One more specific recommendation, tied to the mechanism rather than to good hygiene generally: if your organization has ever had a founder, board treasurer, or authorized representative erroneously reported as deceased — a more common records failure than most people assume — the December 27 effective date is your action date. Confirm the correction has been made at SSA and ask your awarding agency to verify it has propagated. If you would rather have someone track the compliance and payment calendar for an active award instead of building it yourself, OpenGrants’ managed grant writing and grant management services cover exactly this layer of the work.