Executive Order 14249: Protecting America's Bank Account Against Fraud, Waste, and Abuse
President: Donald J. Trump
Directed Treasury and paying agencies to consolidate payment information, expand verification and strengthen controls over federal disbursements and receipts.
Status: In effect.
Is Executive Order 14249 still in effect? Yes. OMB’s August 20, 2025 guidance implements its payment-screening and privacy directions, and Treasury’s July 21, 2026 announcement reports a deceased-payee verification safeguard under the order. Those are specific implementation steps, not proof that every consolidation or reporting requirement has been completed. OMB M-25-32; Treasury implementation announcement.

What does Executive Order 14249 do?
The order directs Treasury and agencies to screen payments before certification, improve payment identifiers, consolidate financial systems and move disbursing functions to Treasury where law permits. Its separate deadlines matter: 30 days for Treasury to assess delegated disbursing authority, 90 days for agency compliance plans and relevant Privacy Act notice reviews, and 180 days for specified OMB guidance and Treasury’s implementation report. Signed sections 3–7.
Later primary evidence reviewed September 24, 2026: A Privacy Act notice added a routine use that the agency said was required by this order and OMB guidance. Official source. The cited steps do not establish every downstream effect.
Reading the operative provisions of Executive Order 14249
EO 14249 directs Treasury and agencies that make federal payments to improve the government’s control over disbursements and receipts. It focuses on verifying payees, reviewing payment data, detecting suspicious patterns and coordinating information across financial systems. The Federal Register text of EO 14249 assigns responsibilities to Treasury and agency leadership; the concrete safeguards depend on subsequent implementation.
Payment integrity work can involve checking whether a payee is eligible, whether an amount matches an approved obligation and whether a transaction is duplicated. Those checks can prevent improper payments, but an anomaly is a signal for review rather than proof of wrongdoing. Agencies need to distinguish deliberate fraud from data-entry errors, stale records, household changes or timing differences between systems. Any suspension, denial or recovery action still has to follow the governing program statute and provide whatever notice or appeal process applies.
The order’s coordination goals also have to coexist with privacy and financial-security protections. Agencies should limit access to officials with a legitimate role, protect sensitive account information and maintain audit trails that show how a payment decision was reached. Common tools can improve oversight across programs, but they do not authorize disclosure beyond what law permits. A meaningful assessment of results would report verified improper payments prevented, amounts recovered, false alerts and corrected errors—not just the volume of data matched. This makes it possible to judge whether the system reduces waste while treating eligible recipients fairly.
Before and after
Before the order
Treasury operated government-wide payment systems with agencies retaining legal responsibility for program eligibility and payment decisions.
Existing statutes, regulations and constitutional limits continued to govern the subject.
After the order
Treasury and agencies were directed to improve identifiers, data standards, verification and access controls without displacing program statutes.
Later rules, contracts, grants or enforcement decisions retain their own procedures and review paths.
A Privacy Act notice added a routine use that the agency said was required by this order and OMB guidance.
In July 2026, Treasury reported that its deceased-payee screening returned more than 4,900 payments worth about $99 million to originating agencies for review before disbursement. That is an agency-reported screening result, not a finding that every flagged payment was fraudulent or a measured total of recovered money. A later State Department matching notice illustrates the next step: State must independently verify a potential match and provide notice and an opportunity to contest an adverse finding before affecting an annuity or beneficiary payment. July 21 announcement; State notice, review safeguards.
Who had to do what
| Agency or official | Direction | Timing |
|---|---|---|
| Treasury Secretary, consulting OMB | Update verification guidance and systems; use lawful matching-agreement waiver authority; guide access to necessary payment data and provide an agency exemption-request process. | No universal fixed guidance date in sections 3–4; routine-use review has a separate 90-day agency deadline. |
| Agency heads and certifying officers | Use required precertification checks; send payment files with Treasury-required lead time, or as early as reasonably practicable for same-day payments; protect sensitive data. | Before certification/disbursement; ongoing; sections 3(b),4,7(c). |
| Agency heads | Review and modify relevant Privacy Act system notices as applicable; submit OMB a compliance plan covering disbursing transitions, systems, verification and improper-payment information. | Within 90 days of signing; sections 3(d),7(a). |
| OMB Director, consulting Treasury for non-CFO agencies | Issue consolidation guidance for CFO Act agencies and single-provider transactional-service guidance for non-CFO Act agencies. | Within 180 days; non-CFO guidance as soon as practicable within that limit; section 5(a)–(b). |
| CFO Act agency heads and all agency heads | Use marketplace financial-management solutions as specified; keep core systems compliant with accounting/reporting standards and Treasury requirements. | CFO solutions as soon as practicable; continuing systems compliance; section 5(c)–(d). |
| Treasury Secretary | Assess delegated disbursing authority and issue revocation notices where appropriate; plan payment centralization and coordinate agency transition plans. | Delegation assessment/notices within 30 days; no separate calendar deadline for the centralization/transition plans; section 6. |
| Defense Secretary, Homeland Security Secretary, Attorney General and other covered statutory disbursing agencies | Work with Treasury to delegate performance of disbursing activities to its Chief Disbursing Officer, except classified payments and subject to law. | No fixed calendar deadline; section 6(b). |
| Remaining non-Treasury disbursing offices and agencies with delegated authority | Remaining offices report to Treasury’s central system; covered agencies decommission internal payment systems unless Treasury authorizes or law requires otherwise. | Daily reporting for remaining offices; no separate decommissioning date; section 6(c),(f). |
| Treasury Secretary | Send the President an implementation-progress report through the Assistant to the President for Economic Policy. | Within 180 days of signing; section 7(b). |
Signed order, sections 3–7. The economic-policy assistant receives the report; the financial-management office administers the marketplace. Neither mention assigns that office a separate dated deliverable.
What happened next
EO 14249 was signed; publication followed March 28. Official source.
The 30-day Treasury delegation-assessment deadline fell on this date; this is not evidence that a centralization plan was delivered. Official source.
Agency 90-day compliance plans were due, as OMB’s later memorandum confirms. Delivery by every agency is not established here. Official source.
OMB issued M-25-32 on routine-use notices and a defined matching-agreement waiver, preserving other privacy safeguards. Official source.
EPA published its Compass records notice. It scheduled the new routine use for May 18 unless comments required changes, distinct from the notice’s April 16 action date. Official source.
Treasury announced the deceased-payee verification safeguard and reported returning flagged payments to agencies for review. Official source.
State published a Foreign Service annuity-matching notice invoking the order and describing independent verification and contest protections. Official source.
Legal and source detail
How it works legally
Treasury may improve payment processing but cannot change statutory eligibility or withhold congressionally required payments without lawful grounds. Privacy, tax secrecy, due process and the Payment Integrity Information Act continue to apply.
The order invokes Treasury disbursing and certifying-officer functions in 31 U.S.C. 3321 and 3528 and the Do Not Pay framework in 31 U.S.C. 3351 and following. Its matching direction concerns the statutory power to waive the agreement requirement in 5 U.S.C. 552a(o), not the entire Privacy Act. OMB’s guidance requires compatible routine uses, advance publication and only relevant, necessary disclosures; the order specifically identifies health records as information not needed for the payment-verification purpose. Sections 3–4 and 7–8; OMB guidance, Appendixes I–II.
Sources by type
If a source is unavailable, first check the cited publisher or another official repository. The cited publisher remains the authority.
Primary and official sources
Orders, laws, court records and official implementation material.
- Privacy Act of 1974; System of Records (opens in a new tab) Official record
- Authenticated signed order: exact duties and separate deadlines
- OMB M-25-32, August 20, 2025: implementation and privacy safeguards
- Treasury, July 21, 2026: reported deceased-payee safeguard
- Federal Register, September 15, 2026: State annuity matching and independent review
How we checked this
Last checked against the sources above on October 16, 2026. How we research →