Governmental and Nonprofit Audit Update
Uniform Guidance Updates: Procurement, Subrecipient Monitoring, and Grant Documentation
Plain-English guidance for local governments and nonprofits managing federal awards under 2 CFR Part 200
Quick answer
The 2024 Uniform Guidance revisions are no longer a future issue. For many federal awards issued on or after October 1, 2024, local governments and nonprofits should confirm that procurement policies, threshold schedules, noncompetitive procurement documentation, subrecipient risk assessments, subaward files, and grant records align with current 2 CFR Part 200 and the specific award terms. The best audit defense is a complete grant file that shows what was required, what was approved, what was purchased, who reviewed it, and how compliance was monitored.
At a glance
| Topic | What local governments and nonprofits should know |
|---|---|
| Applies to | Recipients and subrecipients of federal awards, including local governments, authorities, special districts, school districts, nonprofit organizations, and other entities subject to 2 CFR Part 200. |
| Timing | OMB directed federal agencies to make the 2024 revisions effective for federal awards issued on or after October 1, 2024. Older awards may be handled differently depending on agency implementation, award terms, amendments, or pass-through guidance. |
| Procurement focus | Documented procurement procedures, current thresholds, price reasonableness, quotes or proposals, conflicts of interest, competition, noncompetitive procurement justifications, and required contract clauses. |
| Current threshold context | As of this newsletter, the general FAR micro-purchase threshold is $15,000 and the general simplified acquisition threshold is $350,000, with important exceptions and lower thresholds possible under state law, local policy, or award terms. |
| Subrecipient monitoring focus | Subrecipient-versus-contractor determinations, SAM.gov exclusion checks, required subaward information, risk assessments, monitoring activities, corrective action follow-up, and Single Audit review when applicable. |
| Documentation focus | Grant files should support award terms, budgets, expenditures, drawdowns, prior approvals, procurement, subrecipients, reports, equipment, cost sharing, program income, and closeout. |
| Best first step | Create a federal award inventory and update the grant administration checklist, procurement policy, and subrecipient monitoring templates before the next major purchase, reimbursement request, or audit. |
Why these updates matter
The Uniform Guidance is the rulebook many local governments and nonprofits must follow when they receive, spend, or pass through federal awards. The 2024 revisions to 2 CFR Part 200 were intended to clarify requirements, reduce unnecessary burden, and improve federal award management. That does not mean documentation is less important. In many cases, the revised guidance makes it even more important to show how the organization applied its policies and the award terms.
For audit purposes, the most important question is often not whether management believed a transaction was reasonable. The question is whether the file shows that the transaction was allowable, properly approved, procured under the correct method, charged to the correct award, and supported by enough documentation for someone outside the organization to understand the decision.
By April 2026, many federal awards now in progress are subject to the revised guidance, revised agency terms and conditions, or pass-through updates. Organizations should not assume that last year's procurement checklist, subrecipient agreement, or grant file structure is still complete.
What changed in plain English
The 2024 revisions did not eliminate the need for strong grant administration. They changed terminology, increased or clarified certain thresholds, emphasized plain language, and updated several sections that affect how awards are administered and monitored.
For local governments and nonprofits, the practical areas most likely to affect daily grant management are procurement, subrecipient monitoring, financial management, internal controls, award documentation, required certifications, and records retention.
The safest approach is to read each award and subaward as its own compliance document. The Uniform Guidance provides the baseline, but the award terms, agency regulations, pass-through requirements, state law, local ordinance, and board-approved policies may impose additional or lower thresholds.
- Do not rely only on the grant name or Assistance Listing number.
- Do not assume every federal program uses the same procurement or reporting details.
- Do not treat a vendor agreement as a subaward or a subaward as a vendor contract simply because the document uses a particular label.
- Do document the basis for each major grant compliance decision.
1. Start with the award terms before spending money
Every federal award file should begin with the award document and the terms and conditions. This may sound obvious, but many audit issues begin when staff rely on a budget, reimbursement form, or old grant file without confirming the current award requirements.
The award file should clearly identify the federal agency or pass-through entity, Assistance Listing number and title, Federal Award Identification Number, period of performance, budget period, approved budget, indirect cost rate, cost sharing requirements, reporting deadlines, and any special conditions.
This is also where management should identify whether the award involves construction, equipment, infrastructure, domestic preference or Buy America requirements, program income, subrecipients, participant support costs, personally identifiable information, or other terms that require special documentation.
- Award documents and amendments.
- Approved budget and budget revisions.
- Terms and conditions, including agency-specific or pass-through conditions.
- Reporting calendar and responsible staff.
- Required prior approvals.
- Contact information for the agency or pass-through entity.
- Closeout instructions and records retention requirements.
2. Update procurement policies and threshold schedules
Procurement is one of the most common grant compliance risk areas because it combines federal rules, state law, local policy, program requirements, and judgment. A good procurement file should make the method obvious.
Written procurement procedures should explain which threshold applies, who approves the purchase, what competition is required, what documentation is retained, how conflicts of interest are handled, and when noncompetitive procurement may be used.
As of this newsletter, the general FAR micro-purchase threshold is $15,000 and the general simplified acquisition threshold is $350,000. Recipients and subrecipients may have lower thresholds under state law, local ordinance, grant terms, or their own policies. In practice, the lowest applicable threshold is often the safest threshold to apply.
- Review the procurement policy for consistency with current 2 CFR Part 200.
- Update threshold tables and approval matrices.
- Document whether the organization uses any authorized higher micro-purchase threshold.
- Train purchasing staff, department heads, program managers, and credit card users.
- Use standard procurement file checklists for federal award purchases.
Procurement method snapshot
| Procurement method | When it generally applies | What the file should show |
|---|---|---|
| Micro-purchase | At or below the applicable micro-purchase threshold. | Reasonable price support, business purpose, award charged, approval, receipt or invoice, and equitable distribution among qualified suppliers when practicable. |
| Simplified acquisition | Above the micro-purchase threshold and at or below the applicable simplified acquisition threshold. | Price or rate quotations from an adequate number of qualified sources, basis for vendor selection, approval, and support that the purchase was allowable and within the award period. |
| Formal procurement | Above the applicable simplified acquisition threshold. | Public notice when required, sealed bids or proposals, specifications or scope, evaluation factors, bid/proposal tabulation, award decision, rejected bid justification when applicable, contract, and required clauses. |
| Noncompetitive procurement | Only under limited circumstances permitted by 2 CFR 200.320. | Written justification, the specific permitted reason, price reasonableness, emergency or single-source support when applicable, and federal agency or pass-through written approval when required. |
3. Pay special attention to micro-purchases and simplified acquisitions
Micro-purchases are intended to reduce administrative burden for small purchases, but they are not documentation-free. The organization should still retain enough support to show the price was reasonable and the purchase was necessary, allowable, and charged to the correct award.
The revised guidance allows a recipient or subrecipient to self-certify a micro-purchase threshold up to $50,000 annually if specific requirements are met and documentation is maintained. A threshold above $50,000 requires approval from the cognizant agency for indirect costs. Management should not use a higher threshold casually or informally; it should be supported by policy, risk assessment, and documentation.
Simplified acquisitions require price or rate quotations from an adequate number of qualified sources. Unless the federal agency specifies otherwise, the organization may exercise judgment in determining what number is adequate. That judgment should be documented so the file explains why the organization believed the competition was sufficient.
- For micro-purchases, document price reasonableness even if formal quotes are not required.
- For simplified acquisitions, keep quote requests, vendor responses, screenshots, emails, or other evidence of market research.
- For purchases near a threshold, document the calculation and avoid splitting purchases to evade competition requirements.
- For credit cards and online purchases, retain itemized receipts, business purpose, approval, and grant coding support.
4. Noncompetitive procurement should be the exception, not the habit
Noncompetitive procurement is allowed only in specific circumstances. A common audit problem is that the file explains why management preferred a vendor, but not why competition was not required or not feasible under the Uniform Guidance.
A strong noncompetitive procurement file identifies the permitted basis, explains the facts, documents price reasonableness, and includes approval from the federal agency or pass-through entity when required. Emergency or public exigency documentation should be tied to the time period when competition was not practicable; it should not be used to justify unrelated later purchases after the immediate condition has passed.
Sole-source purchases also need care. A vendor may be familiar, local, responsive, or historically reliable, but those facts alone do not automatically make the vendor the only source.
- Identify the specific noncompetitive procurement basis used.
- Explain why competition was not required or not feasible.
- Retain evidence supporting single-source, emergency, written approval, inadequate competition, or micro-purchase treatment.
- Document price reasonableness.
- Include approval by the appropriate official before the purchase whenever practicable.
5. Build a better procurement file
The procurement file should tell the story from need to payment. Auditors and grant monitors should be able to see what was purchased, why it was needed, how the vendor was selected, how the price was evaluated, who approved it, what award was charged, and whether the goods or services were received.
A practical federal procurement checklist should be short enough for staff to use but complete enough to address the real compliance risks.
- Purchase request or scope of work.
- Grant budget line or award authorization.
- Procurement method and threshold used.
- Conflict-of-interest documentation when applicable.
- Quotes, bids, proposals, or sole-source justification.
- Price or cost analysis when required.
- Domestic preference, Buy America, recovered materials, or other program-specific considerations when applicable.
- Vendor selection and approval.
- Contract or purchase order with required federal clauses.
- Invoice, receipt, proof of receipt, payment support, and accounting code.
6. Decide whether each relationship is a subrecipient or contractor relationship
Subrecipient monitoring begins with the correct classification. The name of the agreement is not controlling. A document called a contract may still create a subrecipient relationship, and a document called an agreement may be a procurement contract.
The practical question is whether the other party is carrying out part of the federal program or simply providing goods or services to the recipient or subrecipient. This determination should be documented before the agreement is signed.
| Question | Subrecipient indicators | Contractor indicators |
|---|---|---|
| What is the relationship? | Carries out part of a federal program. | Provides goods or services for the organization's use. |
| How is performance measured? | Measured against federal program objectives. | Measured by contract deliverables, price, quality, and schedule. |
| Who makes program decisions? | Has responsibility for programmatic decision-making. | Follows the buyer's specifications or statement of work. |
| Who must follow program requirements? | Responsible for applicable federal program compliance requirements. | Generally not subject to program compliance requirements solely because of the contract. |
| What is the public purpose? | Implements a program for a public purpose. | Provides ancillary goods or services in a competitive marketplace. |
7. Strengthen subrecipient monitoring documentation
A pass-through entity must monitor subrecipients based on risk. Monitoring does not have to look the same for every subrecipient, but the file should show that management made a risk-based decision and followed through.
Before making a subaward, the pass-through entity should verify that the potential subrecipient is not suspended, debarred, or otherwise excluded from receiving federal funds. The subaward should also clearly identify the federal award information, including the subrecipient name and Unique Entity Identifier, FAIN, award date, period of performance, budget period, amounts obligated, Assistance Listing number and title, federal agency, pass-through entity, whether the award is for research and development, and the indirect cost rate.
Monitoring should continue during the award. Reviewing a signed subaward at the beginning is not enough if reports are late, performance problems arise, costs appear unsupported, or the subrecipient has Single Audit findings that affect the award.
- Document the subrecipient-versus-contractor determination.
- Verify exclusion status in SAM.gov before issuing the subaward.
- Complete a risk assessment based on experience, audit results, personnel or system changes, and other monitoring information.
- Include all required federal award information in the subaward.
- Review financial and performance reports.
- Follow up on significant developments, audit findings, site visit results, or adverse conditions.
- Verify whether the subrecipient is required to have a Single Audit.
- Use training, technical assistance, site visits, or agreed-upon procedures when risk warrants additional monitoring.
- Document corrective action and closeout.
8. Keep grant documentation tied to the ledger
Grant documentation should not live only in emails, department folders, reimbursement portals, or one employee's memory. The file should tie to the accounting records and support the reports submitted to the federal agency or pass-through entity.
The financial management requirements in 2 CFR Part 200 emphasize identifying federal awards, tracking expenditures, maintaining source documentation, comparing expenditures to budgets, safeguarding assets, and using written procedures for payments and allowable costs. These requirements are practical audit readiness principles as much as compliance rules.
For many organizations, the most useful improvement is a grant file index that mirrors the audit and monitoring questions.
- Award, amendments, terms, conditions, and correspondence.
- Approved budget, budget revisions, and prior approvals.
- General ledger activity and reconciliation to reimbursement requests or drawdowns.
- Allowability support, including invoices, payroll records, time and effort documentation when applicable, and cost allocation support.
- Cash management support showing drawdowns were timed to actual needs.
- Procurement files and contract files.
- Subrecipient files and monitoring evidence.
- Cost sharing, matching, program income, and indirect cost support.
- Equipment and property records when grant funds were used to acquire assets.
- Performance reports, financial reports, certifications, closeout documentation, and record retention notes.
9. Watch the certifications and record retention requirements
Financial reports and subrecipient requests for payment or reports include certification language that should not be treated as a routine signature. The person signing or approving the report should have enough internal support to know the information is true, complete, and accurate.
Record retention is also broader than keeping a few reimbursement packets. Recipients and subrecipients generally must retain federal award records for three years from the date of submission of the final financial report. For awards renewed quarterly or annually, the period generally runs from the date of submission of the applicable quarterly or annual financial report. Longer retention may apply when litigation, claims, audit findings, written notices, property records, indirect cost proposals, or other exceptions are involved.
A practical retention checklist should identify the grant closeout date, final report submission date, property disposition date when applicable, and any unresolved audit or monitoring issues that extend the period.
Uniform Guidance implementation checklist
| Action | Why it matters |
|---|---|
| Inventory federal awards and subawards. | Management needs to know which awards are active, which version of the guidance applies, and which departments are responsible for compliance. |
| Update procurement policies and thresholds. | Policies should reflect current 2 CFR Part 200, FAR thresholds, state and local law, and award-specific requirements. |
| Create procurement templates. | Standard forms reduce missing support for quotes, approvals, conflicts, noncompetitive justifications, and required clauses. |
| Add a subrecipient-versus-contractor decision form. | The classification drives whether procurement rules or subrecipient monitoring requirements apply. |
| Perform SAM.gov exclusion checks before subawards. | Pass-through entities must verify that subrecipients are not suspended, debarred, or otherwise excluded. |
| Use a subrecipient risk assessment. | Monitoring should be based on risk rather than a one-size-fits-all process. |
| Build a grant file index by award. | A complete file supports reporting, reimbursement, monitoring, closeout, and audit requests. |
| Reconcile grant reports to the ledger. | Reports should agree to accounting records and be supported by source documentation. |
| Review prior approvals and budget changes. | Certain budget, scope, personnel, subaward, and period-of-performance changes may require approval before action is taken. |
| Check the current Compliance Supplement. | Auditees and auditors should consider current program-specific compliance requirements for Single Audit planning and support. |
Suggested implementation timeline
| Timing | Suggested action |
|---|---|
| Before applying or accepting an award | Read the NOFO and draft award terms, identify match, reporting, procurement, subrecipient, equipment, and Buy America or domestic preference requirements. |
| At award setup | Create the grant file, assign owners, record Assistance Listing and FAIN information, set up accounting codes, and build the reporting calendar. |
| Before purchases | Determine the procurement method, verify the applicable threshold, check policy requirements, document competition or justification, and retain approval. |
| Before issuing subawards | Document subrecipient-versus-contractor status, perform exclusion checks, complete risk assessment, and include required subaward information. |
| Monthly or quarterly | Reconcile grant activity, review drawdowns and reports, monitor subrecipients, resolve exceptions, and update the grant file. |
| Before audit or closeout | Tie the grant file to the ledger, SEFA, financial reports, procurement files, subrecipient monitoring, equipment records, and final reporting support. |
Questions management and governance should ask
- Which federal awards are active, and which version of the Uniform Guidance and award terms apply?
- Do procurement policies reflect current thresholds and the lowest applicable federal, state, local, and award requirements?
- Can staff identify the procurement method used for each federal purchase?
- Do micro-purchase files show price reasonableness and approval?
- Do simplified acquisition files include quotes from an adequate number of qualified sources?
- Are noncompetitive procurements supported by a specific permitted basis and written justification?
- Did we document whether each agreement is a subrecipient relationship or contractor relationship?
- Are subrecipient risk assessments completed before or shortly after subaward issuance?
- Do subrecipient files include SAM.gov exclusion checks and monitoring evidence?
- Do grant reports, reimbursement requests, and drawdowns tie to the general ledger?
- Are required certifications signed by an official who has adequate support?
- Can we locate the complete grant file without relying on one employee's inbox or memory?
Frequently asked questions about Uniform Guidance updates
What is the Uniform Guidance?
The Uniform Guidance is the common name for 2 CFR Part 200, which establishes uniform administrative requirements, cost principles, and audit requirements for many federal awards.
Do the Uniform Guidance updates apply to local governments and nonprofits?
Yes, when a local government or nonprofit is a recipient or subrecipient of a federal award subject to 2 CFR Part 200. The specific requirements also depend on federal agency regulations, award terms, pass-through requirements, and applicable state or local rules.
When did the 2024 Uniform Guidance revisions become effective?
OMB directed federal agencies to implement the 2024 revisions for federal awards issued on or after October 1, 2024. Agencies could elect to apply the revisions to earlier awards, but they were not required to do so.
What is the current micro-purchase threshold for federal grant procurement?
As of this newsletter, the general FAR micro-purchase threshold is $15,000, with important exceptions. A recipient or subrecipient may establish a higher micro-purchase threshold up to $50,000 through annual self-certification if the Uniform Guidance requirements are met and documentation is maintained.
What is the current simplified acquisition threshold?
As of this newsletter, the general FAR simplified acquisition threshold is $350,000, with important exceptions. Recipients and subrecipients may establish lower thresholds through policy, state or local law, or award terms.
Can we use noncompetitive procurement for federal grant purchases?
Only in limited circumstances allowed by 2 CFR 200.320, such as micro-purchases, single-source availability, public exigency or emergency, written approval from the federal agency or pass-through entity, or inadequate competition after soliciting several sources. The file should include a written justification.
What is subrecipient monitoring?
Subrecipient monitoring is the pass-through entity's risk-based oversight of a subrecipient to help ensure the subrecipient complies with federal statutes, regulations, and the terms and conditions of the subaward and achieves performance goals.
How do we decide whether an entity is a subrecipient or a contractor?
The decision is based on the substance of the relationship. A subrecipient carries out part of a federal program and is responsible for program requirements. A contractor generally provides goods or services for the organization's use in a procurement relationship.
What should be included in a grant file?
A grant file should include the award, amendments, budget, terms and conditions, approvals, ledger support, reimbursement or drawdown support, procurement files, subrecipient monitoring, reports, certifications, equipment records, correspondence, closeout documents, and retention information.
How long should federal grant records be retained?
Federal award records generally must be retained for three years from submission of the final financial report or, for quarterly or annual renewals, from submission of the applicable quarterly or annual financial report. Exceptions can extend the retention period.
What is the best first step to prepare for an audit of federal awards?
Start with a federal award inventory. Then update procurement and grant administration checklists, reconcile each award to the ledger, identify subrecipients, and build a complete file for each award.
Closing thought
The Uniform Guidance updates should not be viewed as a one-time policy edit. They affect the daily decisions that happen before a purchase is made, before a subaward is issued, before a reimbursement request is submitted, and before the audit begins.
A good federal grant file should answer five basic questions: what was required, what was approved, what was spent, how was compliance monitored, and where is the support?
Please contact your Gabridge & Company engagement team with questions about applying the Uniform Guidance to procurement, subrecipient monitoring, grant documentation, or audit readiness.
Sources and standard references
- 2 CFR Part 200, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards, including Subparts D, E, and F.
- 2 CFR 200.302, Financial management; 2 CFR 200.303, Internal controls; 2 CFR 200.317 through 200.327, Procurement Standards; 2 CFR 200.331 through 200.333, Subrecipient Monitoring and Management; 2 CFR 200.334, Record retention requirements; and 2 CFR 200.415, Required certifications.
- 2 CFR 200.501, Audit requirements, including the $1,000,000 Single Audit threshold for non-Federal entities expending federal awards during the fiscal year.
- 48 CFR 2.101, Federal Acquisition Regulation definitions for micro-purchase threshold and simplified acquisition threshold, as amended for current acquisition-related thresholds.
- Office of Management and Budget Memorandum M-24-11, Reducing Burden in the Administration of Federal Financial Assistance, April 4, 2024.
- Office of Management and Budget, Guidance for Federal Financial Assistance, Federal Register, 89 FR 30046, April 22, 2024.
- Office of Management and Budget, Compliance Supplement, 2 CFR Part 200 Appendix XI, current edition applicable to Single Audit planning and testing.
This newsletter is intended for general informational purposes only and should not be considered accounting, auditing, tax, legal, grant management, procurement, cybersecurity, or other professional advice. Each organization should evaluate federal awards based on its own facts, award terms, federal agency guidance, pass-through requirements, state and local law, policies, systems, and risks.
