OMB's Uniform Guidance Overhaul: What the 2 CFR 200 Rewrite Means for Nonprofits on Federal Grants

Roughly 30% of U.S. nonprofits that file a Form 990 report government grants as revenue, and for many of them federal dollars make up a third or more of the annual budget. So when the Office of Management and Budget quietly proposed the largest rewrite of federal grant rules since 2013, it wasn't an obscure procurement footnote — it was a direct threat to how thousands of organizations plan cash flow, staff programs, and close their books.

On May 29, 2026, OMB published a proposed rule that would replace the current Uniform Guidance (2 CFR Part 200) with what it's calling the "Uniform Grants Regulation." The public comment period closed July 13, 2026, and OMB is targeting an effective date of October 1, 2026 — the start of the federal fiscal year. If you run finance for a nonprofit, a university research office, a hospital system, or a state or local government agency that passes through federal funds, this is not a "someday" issue. It's a now issue.

Why This Rewrite Is Different From Past Updates​

The Uniform Guidance has been tweaked before — most notably in 2024, when OMB raised the Single Audit threshold and simplified some procurement rules. Those were adjustments. This is a structural change, and three pieces of it matter most for the people who actually manage the money.

1. It stops being "guidance" and becomes binding regulation​

Today, 2 CFR Part 200 functions as policy that federal agencies incorporate into grant terms — it guides behavior but isn't, by itself, an enforceable regulation the way the Federal Acquisition Regulation is for contracts. The proposed rule would reclassify it as a binding federal regulation. That sounds like a technical distinction, but it changes the legal footing of every compliance argument your organization has ever made with a program officer. Binding regulations are harder to negotiate around and easier for an Inspector General to cite in a finding.

2. Fixed-amount awards are going away​

This is the change with the most immediate accounting impact. Fixed-amount awards let a recipient get paid a set amount for hitting milestones or deliverables, without accounting for every dollar of actual cost — think of it as the grant equivalent of a fixed-price contract. OMB's proposal would eliminate them except where a specific statute requires them, pushing nearly all new awards toward cost-reimbursement, where you spend first and get reimbursed only after documenting the actual, allowable cost.

OMB's stated reason is that fixed-amount awards "can limit transparency and hinder effective oversight" because recipients aren't subject to the same routine financial monitoring. For an agency auditor, that's a reasonable argument. For a finance director, it means:

• More documentation, on every dollar. Direct labor, allocated overhead, and every invoice now needs to trace cleanly to the award, not just to a milestone.
• A cash-flow gap you'll need to fund. The typical lag between spending and reimbursement runs 30–60 days. A program burning $50,000 a month in real costs can leave your organization roughly $100,000 out of pocket at any given time, waiting on the federal payment system to catch up.
• New systems pressure, if you've never done cost-reimbursement before. Organizations that have built their entire federal-funding relationship around fixed-amount awards may be doing itemized cost accounting against a federal award for the first time.

3. "Termination for convenience" comes to grants​

Federal contracts have long allowed the government to end a contract "for convenience" — not because the contractor did anything wrong, but because priorities shifted. The proposed rule would import a version of that into grants: agencies could suspend or terminate a discretionary award at any time if it no longer aligns with current agency or administration priorities, not just for noncompliance.

Recipients would generally still recover allowable costs incurred through the termination date. But a discretionary termination wouldn't trigger the same hearing or appeal rights that a termination-for-cause does — your recourse would be a contract-style claim in the U.S. Court of Federal Claims, a slower and more expensive path than an internal agency appeal. (Notably, broadband programs like BEAD are proposed to be exempted from this authority.)

The Other Changes Finance Teams Shouldn't Skim Past​

Beyond the headline items, the proposal bundles in several requirements with direct budget and workflow implications:

• E-Verify and national-security screening for certain awards, adding a compliance step to hiring for grant-funded positions.
• Restrictions on advocacy activities and publication costs, narrowing what's an allowable use of grant funds.
• Tighter rules on professional dues, conferences, and meetings — dues would only be allowable "if necessary for the award and approved in advance by the agency," and conference/meeting costs would need explicit inclusion in the award terms before you spend against them.
• Expanded applicant risk assessments, meaning more due diligence — and more documentation to satisfy it — before an award is even made.
• Funding restrictions tied to DEI-related activities, gender-identity programs, and disparate-impact-based strategies, which recipients with existing programs in these areas will need to review against the final rule's language once published.

Common Mistakes That Get Amplified Under the New Rules​

Grant accounting mistakes that are merely risky today become much more consequential once fixed-amount awards disappear and reimbursement claims face more scrutiny. The ones auditors flag most often:

1. Double-dipping costs. Charging the same expense as both a direct cost on one grant and part of the indirect cost pool on another. This is one of the most common findings in Single Audits and gets worse when more awards move to itemized reimbursement.
2. Unsupported indirect cost rates. Organizations without a negotiated indirect cost rate agreement (NICRA), or that apply a flat percentage without documentation, are exposed the moment a reimbursement claim gets a closer look.
3. Missing time-and-effort documentation. Personnel costs charged to a federal award need to be backed by real time records — monthly reports approved by both employee and supervisor are the standard, not a retroactive estimate.
4. Unallowable items buried in cost pools. Auditors have disallowed costs as mundane as board-meeting snacks when they were folded into a cost pool allocated to federal awards, forcing a repayment.
5. Inconsistent allocation methodology. Using one cost-allocation approach for one funder and a different one for another, without a documented Cost Allocation Plan (CAP) that treats all funders consistently.

None of these are new rules. What's new is that a cost-reimbursement-first world gives federal reviewers far more transactions to check against them.

What to Do Before October 1​

1. Inventory your fixed-amount awards. Know which current and pipeline awards use this mechanism, and start modeling what a shift to cost-reimbursement would do to your cash position.
2. Stress-test your cash reserves against a 30–60 day reimbursement lag. If a major federally-funded program would leave you short, that's a line-of-credit or reserve conversation to have with your board now, not in November.
3. Get your indirect cost rate and cost allocation plan in writing. If you've been operating on an informal or estimated basis, this is the year to formalize it.
4. Read the professional-dues and conference-cost language carefully if your organization budgets for memberships or travel against federal awards — pre-approval requirements mean you can't assume July's plan is still allowable in November.
5. Watch the Federal Register for the final rule. Comments closed July 13; the substance could shift before the final version lands, but the direction — more documentation, more agency discretion, less cushion — is unlikely to reverse.

Why Clean, Granular Records Matter More Than Ever​

The thread running through every one of these changes is the same: the era of loosely-documented grant spending is ending. Cost-reimbursement awards live and die on your ability to show, dollar for dollar, what you spent and why it was allowable. A general ledger that lumps grant expenses into broad categories, or that can't produce a clean audit trail from an invoice to a specific award and cost objective, is going to struggle under this regime — even if every dollar was spent legitimately.

This is exactly the kind of problem plain-text accounting is built for. Beancount.io lets you tag every transaction with the metadata an auditor actually asks for — award number, cost objective, direct vs. indirect classification — directly in version-controlled, human-readable files. Because every entry has a full history, producing a defensible reimbursement claim or answering a Single Audit sample request is a matter of querying your ledger, not reconstructing a paper trail from memory. Get started for free and see how transparent, auditable records make regulatory changes like this one far less stressful to absorb.