The bill adds a new statutory authority that lets federal program agencies temporarily delay, condition, or segment disbursement requests when objective fraud signals or Do Not Pay matches indicate elevated risk. It also directs the Secretary of the Treasury to return certified payment vouchers and issue corrective-action orders in those circumstances, and it creates procedural guardrails for agencies to follow when they pause payments.
This matters because it converts existing operational practices around improper-payment screening into formal law, allocates new duties among agencies and Treasury, and creates both a timetable for review and a narrow legal safe harbor for officials acting in good faith. Program offices, certifying and disbursing officials, payees, and Treasury will see new compliance, notification, and technical requirements that will affect cash flow and operations across many federal benefit and assistance programs.
At a Glance
What It Does
The bill adds section 3337 to title 31 U.S.C., authorizing agency heads to take corrective actions—delay, condition, or segment a disbursement request—when objective fraud‑risk indicators or a Treasury Do Not Pay match exist, and directing the Secretary of the Treasury to return certified vouchers and issue corrective‑action orders. It requires agencies to document the basis for pauses and to limit them to the portion and duration necessary to verify eligibility or payment accuracy.
Who It Affects
Agencies that administer federally funded financial assistance or public-benefit programs, certifying and disbursing officials under section 3325, the Department of the Treasury (including the Do Not Pay system), OMB, and payees who receive federal payments. Inspectors General and federal law enforcement may interact via case‑by‑case exemptions.
Why It Matters
By codifying payment‑pausing authority, the bill changes how improper payment risk is managed: it formalizes the use of analytics and payment‑validation services, imposes notice-and-contest procedures on agencies, and creates operational tasks (segmentation logic, documentation, notifications) that agencies must build into IT and business processes.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a standalone statutory authority (new section 3337) that lets agencies step in and take a corrective action on a payment before final certification when an objective fraud signal exists. That authority is not unlimited: the agency must base the pause on documented, objective indicators; apply it narrowly to the portion of the payment that appears risky; and keep the hold in place only as long as needed to verify eligibility or correct an error.
Treasury plays two gatekeeping roles. First, the Secretary can return a certified payment voucher to a certifying official and issue a corrective‑action order when Treasury believes a payment carries elevated fraud risk or when a payee is flagged in Do Not Pay or other Treasury validation services.
Second, Treasury is responsible for issuing implementing regulations (within 180 days and updated annually) in consultation with OMB, which sets the framework agencies must follow for notifications, contest procedures, and segmentation rules.When an agency pauses a payment the bill requires prompt notice to the payee that explains the pause, identifies the fraud‑risk indicator relied upon, and describes the review process. Agencies must provide a way for payees to contest factual errors or provide clarifying information; the bill sets a floor on timing: agencies must issue the payment no later than 45 days after the pause begins, or within 7 days after a payee files a contest under the agency’s process.
The bill also directs agencies to allow routine, historically consistent payment amounts to proceed while holding only anomalous or unusually large portions for review.The statute preserves law‑enforcement exceptions: agencies, in consultation with Treasury and the Attorney General, may waive the pause requirements where an active criminal investigation would be jeopardized. It also creates a legal safe harbor: federal officers and employees acting in good faith under the authority are protected from personal liability, and the bill amends section 3527 to clarify that accountable officers are not automatically liable where payments resulted from good‑faith compliance with the new pause authority.
Finally, the statute defines key terms—'routine, historically consistent payment amount' and 'fraud‑risk indicator'—to anchor agencies’ implementation and to constrain arbitrary use of the tool.
The Five Things You Need to Know
The bill adds 31 U.S.C. §3337 giving agency heads explicit authority to delay, condition, or segment disbursement requests when objective fraud‑risk indicators or Treasury validation matches indicate elevated risk.
When Treasury determines elevated fraud risk or a Do Not Pay match, it may return a certified payment voucher to the certifying official and issue a corrective action order to the agency.
Agencies must notify payees about pauses, identify the fraud‑risk indicator relied upon, provide a contest process, and reissue payment no later than 45 days after the pause began or within 7 days after a timely payee contest.
The statute requires agencies to let routine, historically consistent payment amounts proceed while holding only the anomalous or high‑risk portion of a payment (segmentation) wherever practicable.
The bill amends 31 U.S.C. §3527 to add a good‑faith compliance defense for accountable officers who make payments under the new pause/segmentation authority.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the measure as the "Stopping Fraudulent Payments Act." This is procedural but signals congressional intent to focus the statute on preventing fraudulent or improper payments.
Agency duty to pause or segment before certification
Requires the head of any agency that runs a federal financial assistance or public‑benefit program to take corrective action—temporarily delay, condition, or segment a disbursement request—prior to certifying a payment under section 3325 when there is sufficient reason to conclude the payment presents elevated fraud risk. Practically, agencies will need to designate officials who can make these determinations and to integrate fraud‑risk signals into pre‑certification workflows.
Treasury authority to return vouchers and order corrective actions
Gives the Secretary of the Treasury authority to return certified payment vouchers to certifying officials and to issue corrective‑action orders when Treasury determines a payment is high‑risk or a payee is flagged in Do Not Pay or other Treasury validation services. That places Treasury centrally in the review chain and creates a formal mechanism for Treasury to intervene after voucher submission but before disbursement.
Documentation, narrow application, payment notice, and timelines
Obligates agencies to base pauses on objective, documented fraud‑risk indicators and to confine corrective actions to the payment portion creating elevated risk. It requires agencies to provide prompt notice to affected payees describing the pause, the indicator relied upon, and an internal contest process; sets a deadline for agencies to issue delayed payments (no later than 45 days after the determination or within 7 days of a payee contest). Operationally this will require process maps for notice delivery, evidence retention, and an intake channel for payee contests.
Segmentation, law‑enforcement exemptions, and liability protection
Directs agencies to allow routine, historically consistent amounts to proceed while holding only anomalous portions, reducing blunt full‑payment holds. It also permits case‑by‑case waivers when federal law enforcement notifies agencies that pauses would jeopardize active investigations, and shields officers and employees from personal liability for good‑faith actions under the section.
Rules of construction, regulations, and definitions
Clarifies that the new authority does not supersede program‑specific statutes, requires Treasury (in consultation with OMB) to issue implementing regulations within 180 days and annually thereafter, and defines key terms such as 'routine, historically consistent payment amount' and 'fraud‑risk indicator' so agencies and auditors have statutory anchors for implementation and review.
Good‑faith defense added for accountable officers
Modifies the relief‑of‑accountable‑officers statute to add that an accountable officer is not liable for loss or deficiency if the improper payment resulted from a good‑faith effort to comply with the new §3337 authority. This practical change reduces the personal liability risk for certifying and disbursing officials who act to stop suspected fraud.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Treasury and program integrity offices — gain formal statutory authority and a clear process to stop or limit suspected fraudulent disbursements, which can reduce improper‑payment losses and centralize validation actions.
- Federal program managers and auditors — receive statutory definitions and regulatory guidance (from Treasury and OMB) to standardize how fraud signals are handled, improving consistency across programs.
- Law enforcement and Inspectors General — the statute expressly preserves and coordinates exemptions for active investigations, helping avoid procedural conflicts between payment stoppage and criminal probes.
Who Bears the Cost
- Payees, particularly individuals and small organizations — face payment delays, additional administrative steps to contest pauses, and potential cash‑flow disruption if a routine payment is misflagged or if contest processes are slow.
- Agency operations and IT teams — must build segmentation logic, integrate Do Not Pay and other validation services, document objective fraud indicators, and staff contest‑processing functions, all of which carry implementation and recurring costs.
- Certifying and disbursing officials — will carry increased workload and new decision points before voucher certification, even though the bill provides a limited good‑faith defense; the administrative burden may be substantial for high‑volume programs.
- Department of the Treasury and OMB — must produce initial regulations within 180 days and maintain annual updates, which creates recurring rulemaking and oversight obligations that will require staff time and coordination across agencies.
Key Issues
The Core Tension
The central dilemma is straightforward: the statute gives agencies and Treasury the authority to stop money quickly to prevent fraud, but doing so risks harming legitimate payees and imposing substantial operational complexity; policymakers must balance stopping immediate losses against protecting timely access to benefits and ensuring consistent, auditable application.
The statute puts a premium on objective, documented fraud indicators but leaves significant discretion in how agencies determine what counts as 'objective' and 'anomalous.' That opens the door to differing interpretations across programs: a payment pattern that looks anomalous in one program may be normal in another. Agencies will need clear, defensible thresholds and audit trails to avoid both overreach and inconsistent application that could trigger legal challenges or political scrutiny.
Operational complexity is a second tension. Segmentation reduces blunt stops but multiplies transactions and reconciliation steps.
IT systems that push single aggregated payments will need redesigns to split amounts, track held portions, and reconcile later releases. The 45‑day outside deadline balances preventing indefinite holds against the administrative reality of complex verification, but 45 days can be a long time for beneficiaries who lack cash reserves.
Reliance on Do Not Pay and similar validation services improves scalability but risks amplifying upstream data errors: a false positive in a central validation service can cascade across multiple programs, damaging payees and requiring time‑consuming remediation.
Finally, the bill creates legal shields—good‑faith defenses and limitations on personal liability—that protect federal employees but also shift risk. That protection helps officials act, but it also reduces incentives for careful use if agencies lack robust oversight.
The delegation of rulemaking to Treasury and OMB is intended to fill gaps, yet the effectiveness of the statute will hinge on the quality and speed of those regulations and on agencies’ resources to implement them.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.