What This Bill Does
H.R. 8463, the Pre-Payment Fraud Prevention and Treasury Data Access Act, would require federal agencies to do more fraud and eligibility checks before certifying payments. It directs agencies and Treasury to verify things like available funds, correct payee information, valid tax or ID numbers, bank-account validity, and whether a payee is deceased, before a voucher can be approved. The bill also expands Treasury’s access to data assets used by the Do Not Pay system and requires agencies to use fraud-risk indicators in improper-payment reviews. It affects federal agencies, Treasury, payment certifying officials, and anyone receiving federal awards or payments.
- Creates new 31 U.S.C. 3325a pre-certification rules before a payment voucher can be approved.
- Requires checks on available funds, correct payee name, and valid taxpayer or ID numbers.
- Treasury can return vouchers that do not meet the new verification requirements.
- Agencies must screen recipients against Do Not Pay data assets before awards or payment requests.
- Treasury must publish a System of Records Notice for Do Not Pay data assets and may add more data categories.
Who This Bill Affects
For most people, this bill would not change taxes or benefits directly, but it could affect anyone who gets paid by the federal government, receives a federal award, or is involved in a federal contract or grant. Those recipients may have to provide more identifying information and may see more pre-payment checks on bank accounts, payee status, and eligibility before money is released. The practical upside is fewer erroneous or fraudulent payments; the trade-off is more verification and possible delays when agencies have to satisfy the new pre-certification rules.
See how this bill affects you — sign in for a personalized analysisWho Supports & Opposes This
- Federal oversight and anti-fraud advocates They would argue the bill closes gaps that let improper payments go out before agencies verify basic facts like account validity, payee identity, and whether funds were actually available. The new pre-certification requirements are designed to stop losses before they happen rather than trying to recover money later.
- Taxpayers and budget watchdogs They would likely support stronger screening because the bill explicitly targets financial loss to the government through fraud-risk indicators, Do Not Pay screening, and Treasury review of vouchers. Even modest reductions in improper payments can save public money and improve confidence in federal spending.
- Agencies handling grants, contracts, and benefits Some agency managers may support the bill if it gives them clearer Treasury guidance and a formal exemption process. The ability to request exemptions with a remediation plan could help agencies tailor compliance to operational realities while still improving controls.
- Federal program administrators They may worry the new checks will add paperwork, slow disbursements, and require system changes to meet Treasury’s pre-certification deadlines. Agencies that process large volumes of payments could face higher administrative burdens and more returned vouchers.
- Grant recipients, contractors, and vendors They may object that more front-end verification could delay legitimate payments and create extra documentation demands, especially when bank-account or identifier data must be validated. Smaller entities may find the compliance process harder to navigate.
- Privacy and civil-liberties advocates They may be concerned about Treasury’s expanded access to data assets and the publication of routine uses, especially where personally identifiable information is involved. Even with access controls and System of Records Notices, broader data sharing can raise concerns about surveillance, data matching errors, and misuse.
Key Implications
-
““may not certify a voucher ... until the following requirements are met””
This makes the listed checks mandatory before payment approval, not optional best practices. In practice, agencies would have to verify key payment details earlier in the process or risk being unable to certify the voucher.
-
““A valid social security number ... or payee ID number is provided for each payee””
Payments would depend on having acceptable identifying information on file when applicable. That can reduce fraud and duplicate or mistaken payments, but it can also create friction for recipients whose records are incomplete or inconsistent.
-
““the account number ... is held at a financial institution and is open, valid, and belongs to the payee””
Treasury and agencies would be pushed to confirm that the destination account is real and tied to the intended recipient. This is meant to prevent misdirected or stolen payments, including account-takeover schemes.
-
““The Secretary shall publish and maintain a System of Records Notice for the Do Not Pay system””
Treasury would have to publicly document what data assets are in the system, how they are used, and what access controls apply. That increases transparency, but it also formalizes broader data sharing for payment screening.
-
““design and apply fraud-risk indicators to the programs identified””
Agencies would need to use objective signals such as anomalous payment patterns or verified data mismatches in improper-payment reviews. That could improve detection of suspicious activity, but it also depends on the quality of the data and analytics used.
Latest Status
June 9, 2026
Received in the Senate.
Take Action
Get more from BillBoard
Free tools to understand, respond to, and track this bill.
Ask AI about this billData sourced from api.congress.gov.