Grant Recordkeeping: Federal Requirements Guide
Updated 26 official sources
Quick Answer: Grant recordkeeping under 2 CFR 200.302 means a financial system that ties every cost to a specific federal award, and 2 CFR 200.334 requires keeping those records for 3 years from the final financial report, longer if an audit or claim is open.
Full answer and how we checked it
Grantsights analysis of 26 HHS OIG audits of nonprofits found 15 cited missing or inadequate documentation.
Data note: Retention, access, financial-management, and internal-control rules were checked October 17, 2026 against the current eCFR text of 2 CFR Part 200, which hasn't changed since the October 1, 2024 revision took effect. Award terms and agency requirements can add record or data obligations.
Source review by Grantsights, July 26, October 9, and October 17, 2026: On October 17, Grantsights checked 2 CFR 200.302, 200.303, 200.334, 200.336, 200.337, and 200.338 against the current eCFR text, compared the pre-revision text from September 30, 2024, and read the summaries of 26 HHS Office of Inspector General audits of individual nonprofits. On October 9 we checked 2 CFR 200.430 and 200.511. In July we rechecked NSF and NIH data-management guidance. Federal rules state what the records must show, but the award file still has to connect payroll, procurement, property, program income, subawards, cost sharing, and program data to the specific award and report period.
In this guide
- The Core Rule: 2 CFR 200.334 Record Retention
- What 2 CFR 200.302 and 200.303 Require From Your Records System
- What Records to Keep: The Complete Checklist
- Electronic vs Paper Records
- Data Management Plans: NSF, NIH, and Beyond
- PII Protection Requirements
- Freedom of Information Act Considerations
- How to Organize Grant Files: A Folder Structure
- Document Retention Schedules
- What HHS OIG Audits Found About Nonprofit Recordkeeping
- What Happens During an Audit: What Auditors Request
- Common Recordkeeping Failures (and How to Avoid Them)
- Cloud Storage and Security Best Practices
- The Records That Disappear Right Before an Audit
- What 2 CFR 200 Doesn't Tell You About Grant Recordkeeping
- Sources
If you're a grants manager, finance director, or program coordinator at a nonprofit responsible for audit-ready grant recordkeeping, this guide covers how to set up and run the system, not only how long to keep the files.
Good recordkeeping isn't exciting, but it's what separates organizations that get through audits from those that spend months reconstructing documentation they should have filed years ago.
Federal grant recordkeeping isn't optional. It's regulated under 2 CFR 200 Subpart D, and the consequences for failure range from questioned costs to repayment demands to specific award conditions. This guide covers what to keep, how to build the system that holds it, how to organize it, and what happens when an auditor shows up. For the date math on each retention clock, use the grant records retention guide.
OMB published proposed revisions to the government-wide grant rules in the Federal Register on May 29, 2026 (opens in a new tab), with comments due July 13, 2026. Until a final rule is published, the October 2024 text cited below is the rule that applies.
The Core Rule: 2 CFR 200.334 Record Retention
The baseline requirement is short. 2 CFR 200.334 (opens in a new tab) sets the standard retention period at 3 years from the date you submit your final financial report for the award. For awards renewed quarterly or annually, the 3 years run from the submission date of the relevant quarterly or annual financial report.
The same section says agencies and pass-through entities may not impose any other retention requirements except the ones it lists. Those exceptions are:
- Pending litigation, claims, or audits (a): If any of these begins before the 3-year period ends, keep the involved records until the matter is resolved and final action is taken.
- Written extension (b): The agency, pass-through entity, cognizant agency for audit, oversight agency for audit, or cognizant agency for indirect costs can notify you in writing to extend the period.
- Property and equipment (c): Records for property and equipment acquired with federal support are kept for 3 years after final disposition, not 3 years after the award ends. If you bought a microscope in year 1 of a 5-year grant and still have it 10 years later, you're still keeping its records.
- Records held by the agency (d): The 3-year requirement doesn't apply to records transferred to or maintained by the federal agency.
- Post-period program income (e): If the award terms require reporting on program income earned after the period of performance, keep those records for 3 years from the end of your fiscal year in which the income was earned.
- Indirect cost and rate records (f): Supporting records for indirect cost proposals, cost allocation plans, and similar rate computations run 3 years from submission when they're submitted for negotiation, or from the end of the fiscal year they cover when they aren't.
Practical Advice
Write the trigger date for every clock into the award's file on the day it happens: the actual final report submission date, the equipment disposition date, the date an audit closes. A retention schedule only works if somebody recorded the date that starts it. Keeping everything forever isn't automatically safer, because the access rights in 2 CFR 200.337 last as long as you hold the records. Keep records for a documented reason, and destroy them only through a written approval step.
Looking for your next grant?
About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.
No spam. Unsubscribe anytime.
What 2 CFR 200.302 and 200.303 Require From Your Records System
Retention rules say how long. 2 CFR 200.302 (opens in a new tab) says what the system has to do while the award is running, and it lists 7 required elements in paragraph (b). According to 2 CFR 200.302(a), your financial management system must be able to prepare the required reports and trace expenditures far enough to show the funds were used as the award allows. Every record must be supported by source documentation.
| 200.302(b) requirement | What to set up | What an auditor asks for |
|---|---|---|
| (1) Identify every award | A unique fund or project code per award, tagged with the Assistance Listing title and number, federal award identification number, year issued, and awarding agency or pass-through entity | The SEFA tied to the ledger |
| (2) Accurate, current, complete financial results | Monthly close by award; reports built from the ledger, not a side spreadsheet | Federal financial reports reconciled to the general ledger |
| (3) Amount, source, and expenditure of funds | Records of authorizations, obligations, unobligated balances, assets, expenditures, income, and interest, each with source documents | Invoices, receipts, payroll support for sampled transactions |
| (4) Control over funds, property, and assets | Approval rules, segregation of duties, an equipment inventory | Approval trail and inventory records |
| (5) Budget vs. actual by award | A monthly budget-to-actual report per award | Budget comparison and approved revisions |
| (6) Written payment procedures (200.305) | A drawdown procedure that minimizes the time between drawdown and payment | Drawdown records matched to paid expenses |
| (7) Written allowability procedures | A cost-allowability checklist tied to Subpart E and award terms | The written procedure and evidence it was followed |
2 CFR 200.303 (opens in a new tab) then requires you to establish, document, and maintain effective internal control over the award, which should align with the GAO "Green Book" or the COSO framework. Paragraph (e) is the one that reaches your data. The October 2024 revision added the word "cybersecurity": you must now take "reasonable cybersecurity and other measures" to safeguard protected personally identifiable information and other information the agency, pass-through entity, or you consider sensitive. Grantsights compared the current text against the version in effect on September 30, 2024, which required only "reasonable measures."
The common mistake here is treating the accounting software as the records system. The software holds the ledger. The records system is the ledger plus the folders, the naming rules, the access controls, and the written procedures that let a stranger rebuild any charge from the source document.
What Records to Keep: The Complete Checklist
Federal regulations don't provide an exhaustive list. The current 2 CFR 200.334 says the records to be retained "include but are not limited to, financial records, supporting documentation, and statistical records." Here's what that means in practice, sorted into 5 record groups.
Financial Records
- General ledger entries for all grant-related transactions
- Bank statements and reconciliations
- Invoices, receipts, and purchase orders for all expenditures charged to the grant
- Payroll records including timesheets, pay stubs, and payroll registers
- Travel authorizations and expense reports with receipts
- Equipment purchase documentation (for items at or above $10,000, or your lower capitalization threshold) including quotes, purchase orders, and receiving reports
- Drawdown records from PMS (Payment Management System) or ASAP, reconciled to your accounting system
- Indirect cost rate agreement and supporting calculations
- Cost sharing/matching documentation showing the source, amount, and valuation of your match
- Budget modification requests and approvals
- Subaward agreements and invoices (up to the first $50,000 of each subaward is included in your MTDC base)
Personnel Records
- Position descriptions for all grant-funded staff
- Time and effort records that reflect the work actually performed, as 2 CFR 200.430(g) (opens in a new tab) requires
- Compensation records showing that salaries are consistent with the organization's established pay scale
- Fringe benefit calculations and supporting documentation
- Hiring documentation for grant-funded positions (especially if the position required specific qualifications listed in the proposal)
Programmatic Records
- The funded proposal (your complete application as submitted)
- Notice of Award and all award modifications
- Terms and Conditions of the award
- Progress reports (annual, semi-annual, or quarterly as required)
- Final technical report
- Performance data and outcomes documented in your reporting
- Meeting minutes from advisory boards, steering committees, or project team meetings
- Participant records (enrollment data, eligibility, service delivery logs, required background checks)
- Publications and products resulting from the award
Procurement Records
2 CFR 200.318(i) (opens in a new tab) requires records "sufficient to detail the history" of each procurement, including the rationale for the method, contract type, contractor selection or rejection, and the basis for the price.
- Written procurement policies and procedures
- Solicitation documents for competitive procurements
- Evaluation criteria and scoring used to select vendors
- Contracts and purchase orders with vendors
- Evidence of competition (price or rate quotes for small purchases, bids or proposals above the simplified acquisition threshold)
- Noncompetitive procurement justifications naming which circumstance in 2 CFR 200.320(c) (opens in a new tab) applied, such as a single source or written agency approval
- Conflict of interest documentation for procurement decisions
For more on procurement requirements, see the procurement standards for federal grants guide.
Compliance and Oversight Records
- Subrecipient monitoring documentation (risk assessments, monitoring reports, corrective actions), covered in the subrecipient monitoring guide
- Audit reports (Single Audit reports if your organization meets the current $1 million threshold)
- Corrective action plans for any audit findings
- Correspondence with the federal agency (program officer communications, grants management correspondence)
- Prior approval requests and responses (changes in scope, budget revisions, no-cost extensions)
- Closeout documentation including final inventories and property reports
Electronic vs Paper Records
Most grant files are now born digital, and the rule has caught up. 2 CFR 200.336 (opens in a new tab) states that when practicable, federal agencies, pass-through entities, and recipients must collect, transmit, and store award information in open and machine-readable formats. The practical test is whether you can still open, read, and print a file for the full 3 years after the final report, plus any extension.
Requirements for Electronic Records
If you're storing records electronically (and you should be), build these 5 controls into the system:
- Accessibility: Records can be retrieved and read throughout the retention period. That means keeping access to the software or exporting to a format that doesn't need it.
- Integrity: Records haven't been altered since creation. Use version history, audit trails, and access logs.
- Reproducibility: You can produce readable copies on request. You don't need paper copies of unalterable electronic originals, and the agency or pass-through entity must accept or provide paper versions if asked.
- Security: Protection against unauthorized access, change, or deletion, which 2 CFR 200.303(e) now frames as a cybersecurity duty.
- Backup: A documented backup and recovery plan. Your grant records shouldn't exist in only one location.
Scanning Paper Originals
If you scan paper receipts and discard the originals, 2 CFR 200.336 requires a conversion procedure with periodic quality control reviews. Write it down: who scans, how a second person spot-checks a sample for legibility and completeness, and how often. A folder of scans with no documented review is a red flag in an audit, because nothing shows the copies are complete.
What Still Needs Paper (or Equivalent)
Some documents may need to be retained in their original form:
- Signed agreements (though electronic signatures are widely accepted under ESIGN and UETA)
- Original receipts if required by your organization's policies (many organizations accept scanned copies)
- Certified payroll records if required by Davis-Bacon or other prevailing wage requirements
Migration Planning
If you're switching accounting systems, cloud platforms, or document management systems, plan the migration of all grant records still inside a retention period. The new system must keep the same accessibility, integrity, and retention capabilities. Document the migration itself as part of your records, including a reconciliation showing that record counts and totals match before and after.
Data Management Plans: NSF, NIH, and Beyond
Research awards add a second layer: a formal plan for the data the project produces. NSF's plan is limited to 2 pages, and NIH's policy has applied since January 25, 2023. This goes beyond financial recordkeeping into the management of scientific and program data.
NSF Data Management and Sharing Plan
According to NSF, every proposal needs a data management and sharing plan (opens in a new tab) of 2 pages, and a project that won't produce data files a justification in its place. For a records system, the plan matters after the award too, because it's the standard your data files will be held to. It can cover:
- Types of data, samples, physical collections, software, curriculum materials, and other materials to be produced
- Standards for data and metadata format and content
- Policies for access and sharing, including protection of privacy, confidentiality, security, and intellectual property
- Policies for reuse, redistribution, and production of derivatives
- Plans for archiving and preserving access
NSF points to PAPPG II.D.2(ii) and Policy Notice NSF 26-202 for the general rules, and several directorates add their own. For example, the Social, Behavioral, and Economic Sciences directorate has its own data management guidance (opens in a new tab). The NSF data management plan guide covers how to write one.
NIH Data Management and Sharing Policy
NIH's Data Management and Sharing Policy (opens in a new tab), effective January 25, 2023, requires a DMS Plan for NIH-funded research that generates scientific data. Key elements include:
- Data types and estimated amount of data to be generated
- Tools, software, and code needed to access or manipulate the data
- Standards for data collection and metadata
- Data preservation, access, and associated timelines
- Access, distribution, or reuse considerations
- Oversight of data management during the award
According to NIH notice NOT-OD-21-013 (opens in a new tab), shared scientific data should be made accessible as soon as possible, and no later than the time of an associated publication or the end of the performance period, whichever comes first. Costs for data management and sharing can be included in your grant budget. For a step-by-step plan, see how to write a data management plan.
Other Agency Requirements
- DOE: According to the DOE data management requirements page (opens in a new tab), all DOE-funded research and development awards and contracts are subject to a DOE-approved Data Management and Sharing Plan.
- Other agencies: Many set data requirements in the funding notice or award terms rather than a standing policy page. Read the notice and the terms before you budget data storage.
PII Protection Requirements
The October 2024 revision of 2 CFR 200.303(e) requires "reasonable cybersecurity and other measures" to protect PII. Federal grant recipients often collect personally identifiable information from program participants, research subjects, or staff, so this applies to most service programs, not only research. If you keep participant files for 3 years after the final report, that's 3 more years of PII to protect after the work ends.
What Counts as PII
PII includes any information that can identify an individual, either alone or when combined with other data. This includes names, Social Security numbers, dates of birth, addresses, phone numbers, email addresses, medical records, educational records, and biometric data. Even combinations of seemingly harmless data points (zip code, birthdate, and gender) can identify a specific person.
Federal Requirements
- 2 CFR 200.303(e): Requires reasonable cybersecurity and other measures to safeguard protected PII and other information the agency, pass-through entity, or you designate as sensitive, consistent with applicable privacy laws.
- Privacy Act of 1974: Applies to federal agency systems of records. If your award has you operate a system for an agency, check the terms for Privacy Act duties.
- HIPAA: Applies to health information held by covered entities and their business associates.
- FERPA: Applies to education records maintained by educational institutions that receive U.S. Department of Education funds.
- Award terms: Some awards add breach-reporting duties for PII collected under the award. Read the terms and conditions before you collect anything.
Practical Safeguards
Take these 6 steps:
- Store PII on encrypted systems with role-based access controls
- Minimize PII collection. Don't collect data you don't need.
- De-identify data when possible, especially for reporting and analysis
- Train all staff who handle PII on protection requirements
- Have a breach response plan. Know who to notify and how quickly.
- Include data security provisions in all subaward agreements and contracts with vendors who access PII
Freedom of Information Act Considerations
The access and FOIA rules sit in 2 sections. Under 2 CFR 200.337 (opens in a new tab), the federal agency or pass-through entity, Inspectors General, the Comptroller General, and their authorized representatives have a right of access to any records pertinent to the award, plus timely and reasonable access to your staff for interviews. That right isn't limited to the 3-year retention period; it lasts as long as you keep the records. The same section requires measures to protect the names of crime victims, and routine monitoring doesn't justify seeing a victim's true name.
Under 2 CFR 200.338 (opens in a new tab), FOIA doesn't apply to records that remain under your control, except as 2 CFR 200.315 requires for certain research data. You aren't required to permit public access to your records unless federal, state, local, or tribal law requires it. But records you provide to a federal agency generally will be subject to FOIA and its exemptions.
What's Generally Releasable Once the Agency Holds It
- Applications, reports, and other documents you've submitted, subject to the FOIA exemptions below
- Award amounts and basic project information
- Published results and publicly available data
- Research data relating to published findings that the agency used in developing an action with the force and effect of law, which you must provide on request under 2 CFR 200.315(e)
What's Typically Protected
- Trade secrets and confidential commercial or financial information (FOIA Exemption 4)
- Pre-decisional and deliberative agency communications (FOIA Exemption 5)
- Personnel, medical, and similar files where release would be a clearly unwarranted invasion of privacy (FOIA Exemption 6)
Practical Implications
When you submit documents to a federal agency, assume they could eventually be released under FOIA. Don't include unnecessary PII in reports. If a document contains confidential business information, mark it clearly. Keep your internal working files, such as draft budgets and staff notes, in your own system rather than attaching them to agency submissions.
How to Organize Grant Files: A Folder Structure
Set up the folder structure in the first 30 days after the Notice of Award, before the first drawdown. A consistent structure across all grants prevents the document hunts that happen when an auditor calls. Here's a recommended layout:
Top-Level Folder: [Grant Number] - [Short Title]
``` 01-Award-Documents/ Notice-of-Award.pdf Terms-and-Conditions.pdf Award-Modifications/
02-Proposal/ Submitted-Narrative.pdf Budget.xlsx Budget-Justification.pdf Supporting-Documents/
03-Financial/ Ledger-Reports/ Drawdowns/ Budget-vs-Actual/ Cost-Sharing-Documentation/
04-Personnel/ Effort-Reports/ Position-Descriptions/ Timesheets/
05-Procurement/ Vendor-Contracts/ Competitive-Bids/ Noncompetitive-Justifications/
06-Subawards/ [Subawardee-Name]/ Agreement.pdf Invoices/ Monitoring-Reports/
07-Reporting/ Progress-Reports/ Financial-Reports/ Final-Report/
08-Compliance/ Audit-Documentation/ Corrective-Actions/ Agency-Correspondence/
09-Equipment/ Inventory/ Purchase-Documentation/ Disposition-Records/
10-Closeout/ Final-Inventory.pdf Final-Financial-Report.pdf Closeout-Checklist.pdf ```
The grant closeout checklist lists what belongs in the last folder.
Naming Conventions
Use consistent file naming: YYYY-MM-DD_DocumentType_Description. For example: 2026-03-15_Invoice_LabSupplies_VendorName.pdf. This makes files sortable by date and findable by type.
Link the Ledger to the Folder
Put the document's file name, or a document ID, in the memo field of each journal entry. When an auditor samples a transaction, the path from ledger line to source document should take one search, not a hallway conversation.
Access Controls
Not everyone who works on a grant needs access to all files. Limit financial records and PII to authorized personnel. Keep a list showing who can view and edit each award's folders, and update it when people change roles.
Document Retention Schedules
Every retention clock in 2 CFR 200.334 starts with a date, and most start 3 years after an event your system has to capture. The table below shows which event starts each clock and where to record it. For worked examples of the date math, see the grant records retention guide.
| Record type | Clock starts at | Authority | Where the system records the start date |
|---|---|---|---|
| Award financial and program records | Submission of the final financial report (3 years) | 2 CFR 200.334 | Closeout folder: save the submission receipt |
| Records involved in litigation, a claim, or an audit | Resolution and final action | 2 CFR 200.334(a) | Hold flag on the award folder until a closure letter is filed |
| Records under a written extension | Date set in the notice | 2 CFR 200.334(b) | Compliance folder: file the notice |
| Property and equipment records | Final disposition (3 years) | 2 CFR 200.334(c) | Equipment inventory: disposition date column |
| Post-period program income | End of the fiscal year earned (3 years) | 2 CFR 200.334(e) | Program income log by fiscal year |
| Indirect cost proposals and allocation plans | Submission, or end of the covered fiscal year | 2 CFR 200.334(f) | Rate folder: submission receipt or fiscal-year label |
| Research data (NIH) | Per the approved DMS Plan and award terms | NIH DMS Policy | Data plan folder |
| IRB records for human subjects research | At least 3 years after completion of the research | 45 CFR 46.115(b) (opens in a new tab) | IRB file |
Agency rules can still matter for specific programs, so check the award terms and the agency's own regulations for the program before you set a destruction date.
What HHS OIG Audits Found About Nonprofit Recordkeeping
Grantsights analysis of HHS Office of Inspector General audits found that 15 of 26 audits of individual U.S. nonprofits (58%) cited missing or inadequate documentation. Method: we pulled every report in the HHS OIG reports listing (opens in a new tab) filtered to audits in the grants category (201 reports on October 17, 2026), kept the 26 issued from October 1, 2017 through September 30, 2026 whose single auditee is a U.S. nonprofit (universities, governments, tribes, foreign organizations, and a joint NIH audit excluded), and counted a report when its summary says the organization lacked, didn't maintain, or couldn't provide documentation supporting costs, matching contributions, or required program files.
| What the documentation gap covered | Audits | Share of 26 |
|---|---|---|
| Costs or non-Federal match (some also had program-file gaps) | 10 | 38% |
| Program case or personnel files only | 5 | 19% |
| No documentation finding in the summary | 11 | 42% |
Two patterns change what a nonprofit should do next. First, 5 of the 15 documentation findings were about program files only, such as missing evidence of background checks or of how a child was released to a sponsor. Apply the same filing standard to case files that you apply to invoices. Second, 4 of the 10 cost findings involved the non-Federal match or salary support, both areas where the paperwork is easy to put off until closeout. 24 of the 26 audits were issued from October 2017 through 2021, and only 2 date from 2022 or later, so treat this as a pattern across past audits, not a current rate.
Case Study: Henry J. Austin Health Center
HHS OIG report A-02-17-02002 (opens in a new tab) (February 2018) audited Henry J. Austin Health Center, a health center in Trenton, New Jersey, that received $8.3 million in Community Health Center Program grants. According to the HHS OIG audit report, it didn't track grant expenditures separately from other operating expenses, didn't reconcile actual expenditures to the budgeted amounts it used to draw funds, and didn't maintain documentation supporting certain expenditures. OIG couldn't determine whether $8,000,453 in claimed costs were allowable and found $243,066 unallowable. That's a 2 CFR 200.302 failure more than a filing failure: without a separate code for each award, no folder structure could have rebuilt the charges.
Heluna Health (2024)
HHS OIG report A-04-22-02037 (opens in a new tab) (July 2024) reviewed $588 million in CDC COVID-19 funds that Heluna Health, a California nonprofit, claimed. 139 of 146 sampled items generally complied. For 3 items, Heluna Health didn't maintain adequate documentation, and some costs weren't consistent with award purposes, which led to $3,585,834 in unallowable costs. 4 more items were start-up advances without adequate support. According to OIG, the cause was that Heluna Health didn't require the California Department of Public Health to submit underlying support for costs it claimed, and OIG recommended Heluna Health work with CDC to determine the allowable portion of $366,850,858 in start-up costs. If you pass funds through, your records system has to hold your subrecipients' support too.
Pathways for Children and Lincoln Hall Boys' Haven
In report A-01-18-02503 (opens in a new tab) (November 2019), OIG found Pathways for Children, a Massachusetts Head Start grantee, fell $296,982 short of its required non-Federal share, in part because it couldn't provide documentation showing that the special-education (IEP) expenses it counted as match were allowable. In report A-02-16-02007 (opens in a new tab) (February 2019), Lincoln Hall Boys' Haven couldn't identify the actual expenditures behind the $29.8 million it charged to its program, and OIG recommended it provide documentation or refund the federal government.
What Happens During an Audit: What Auditors Request
If your organization expends $1 million or more in federal awards during a fiscal year beginning on or after October 1, 2024, you'll undergo a Single Audit under 2 CFR 200 Subpart F. Here's what to expect.
Phase 1: Planning and Risk Assessment
The auditor identifies your major programs (based on total expenditures and risk factors), reviews prior audit findings, and assesses internal controls. They'll request your Schedule of Expenditures of Federal Awards (SEFA) early in the process.
Phase 2: Document Requests
Auditors will request documentation across several compliance areas, per OMB's Compliance Supplement (opens in a new tab):
- Activities Allowed/Unallowed: Evidence that expenditures align with the approved scope of work
- Allowable Costs: Supporting documentation for sampled transactions (invoices, timesheets, travel receipts)
- Eligibility: Documentation proving participants or subrecipients meet eligibility criteria
- Matching: Evidence of cost sharing amounts, sources, and valuation
- Period of Performance: Proof that costs were incurred within the authorized period
- Reporting: Copies of submitted reports and underlying data
- Subrecipient Monitoring: Risk assessments, monitoring visit reports, and subrecipient audit follow-up
- Procurement: Competitive bidding documentation, vendor selection criteria, and contract files
Phase 3: Testing
Auditors select samples of transactions and test them against the compliance requirements. Sample sizes depend on the auditor's risk assessment and the size of each program. They'll trace each one from the general ledger to the supporting documentation. If a receipt is missing, a timesheet doesn't reflect the work, or a purchase lacks competitive quotes, that becomes a potential finding.
Phase 4: Findings and Resolution
If the auditor identifies noncompliance, they report it as a finding. Under 2 CFR 200.511(a) (opens in a new tab), your organization must prepare a corrective action plan for current-year audit findings, not only those with questioned costs over the $25,000 reporting threshold. The federal agency reviews findings and determines whether to sustain questioned costs (requiring repayment) or allow them. The Single Audit requirements guide covers the thresholds in more detail.
Common Recordkeeping Failures (and How to Avoid Them)
In the 26 HHS OIG nonprofit audits above, documentation gaps showed up in 15. Common mistakes include:
1. Time and Effort Records Built From Estimates
Staff charged to the grant didn't complete time records, or the records didn't reflect the work actually performed. Under 2 CFR 200.430(g), budget estimates alone don't support salary charges. In OIG report A-03-16-00250 (opens in a new tab), Youth For Tomorrow - New Life Center allocated $1.5 million in staff salaries using estimates. Fix: Use after-the-fact time records and a regular certification cycle. The time and effort reporting guide explains the standard.
2. Inadequate Procurement Documentation
Purchases made without evidence of competition. No quotes on file, no vendor evaluation criteria, no record of why a noncompetitive method was allowed. Fix: Require a procurement checklist for every purchase and keep a procurement file that meets 2 CFR 200.318(i).
3. Unsupported Cost Sharing
The proposal committed to $100,000 in matching funds, but there's no documentation proving it was provided or how it was valued. Fix: Track cost sharing in real time using the same documentation standards as direct costs. Don't wait until closeout to reconstruct your match. The cost sharing and matching guide covers valuation.
4. Comingled Records
Grant-funded activities mixed with general operating records so thoroughly that auditors can't tell which costs belong to which award. This is what sank the Henry J. Austin Health Center charges. Fix: Use unique cost codes or account strings for each grant from day one.
5. Destroyed Records Before the Retention Period Ended
An office cleanup or system migration deleted grant records still within the 3-year retention window. Fix: Use a records retention schedule with a formal review before any records are destroyed. Never destroy records for awards with unresolved audit findings.
6. No Backup System
All grant records existed on one server that crashed, or in one filing cabinet that was damaged. Fix: Keep redundant backups in at least 2 physical or cloud locations. Test your backup restoration process at least once every 12 months.
Cloud Storage and Security Best Practices
Most organizations now use cloud-based systems for grant records, and 2 CFR 200.303(e) makes their security settings part of your internal controls. Here's how to set them up in 3 steps.
Choosing a Platform
Use business-grade platforms (Microsoft 365, Google Workspace for Nonprofits, Box, Dropbox Business) that offer:
- Encryption at rest and in transit
- Role-based access controls
- Audit trails showing who accessed and modified files
- Version history (needed for tracking document changes)
- Compliance certifications (SOC 2, or FedRAMP where an agency requires it)
Security Controls
- Turn on multi-factor authentication for all users
- Restrict sharing settings to prevent unauthorized external access
- Review access permissions every 3 months, especially when staff change roles
- Disable access immediately when employees leave the organization
- Use data loss prevention (DLP) tools to keep PII from being shared inappropriately
Retention and Deletion
Configure your cloud system to match your retention schedule. Some platforms offer retention policies that prevent deletion before a set date. When the retention period expires, follow your formal records destruction process, including documentation that records were destroyed and approval from the appropriate authority.
The Records That Disappear Right Before an Audit
Any charge should pass a 3-step trace: ledger line, source document, and the approval or receiving record that connects them. Often the missing piece isn't a receipt. It's context. An invoice is there, a general ledger entry is there, but the document connecting the two, such as a purchase order, receiving report, or written approval from the program officer, is gone. That gap turns an allowable cost into a questioned cost just as reliably as a missing receipt does.
Payroll costs can be questioned during a Single Audit, even when nobody doubts the work happened, if the time records don't hold up. Under 2 CFR 200.430(g) (opens in a new tab), salary charges must rest on records that accurately reflect the work performed and are backed by internal controls; budget estimates alone don't qualify. The current rule doesn't say who must sign an effort certification, but if your records fall short, the agency can require personnel activity reports with prescribed certifications under 200.430(g)(8). Resolving that kind of policy gap can take months of back-and-forth with the federal program officer.
The NIH Data Management and Sharing Policy created a recordkeeping layer many organizations haven't fully absorbed. NIH says recipients must carry out data management and sharing as described in the approved plan as a term and condition of award, report on it in annual progress reports, and work with the NIH program officer to get review and approval when the plan changes. A lab that switches repositories mid-project without that approval has a compliance gap even if the data are intact, so file each approved change with the award.
The 2024 revisions to 2 CFR 200 raised the equipment threshold from $5,000 to $10,000 per unit, or your lower capitalization level. That sounds like less recordkeeping, but it can create confusion if your records mix the old and new thresholds across multi-year awards. An organization that starts treating items under $10,000 as supplies without updating its written policy could draw a controls finding because the policy doesn't match practice, even if the underlying transactions are allowable. Keep your written policies synchronized with your actual practices, and record the effective date of any threshold change. The equipment management guide covers inventory rules.
Organizations managing multiple concurrent awards should build their folder structure before the money arrives, not after. Reconstructing grant files after a staff departure takes far longer than filing the documentation correctly from the start. A 2-hour setup at award start prevents a 2-week scramble at closeout or when an auditor calls.
What 2 CFR 200 Doesn't Tell You About Grant Recordkeeping
The 3-year retention rule is a minimum, not a maximum. If there's an open audit, dispute, or litigation, you must keep records until the issue is resolved and final action is taken, even if that's years after closeout. Organizations that destroy records at the 3-year mark sometimes lose the documentation they need to answer a finding.
The regulation doesn't name a system. 2 CFR 200.302 lists what the system must do, not which software or folder layout to use. That's a design choice you have to document in written procedures, and an auditor tests whether you follow your own procedures.
Electronic records need a migration plan. If you're storing grant records in a system you might leave (a specific cloud vendor, an old version of accounting software), plan how you'll export and preserve those records before switching. A system change is an easy moment for records still inside the retention window to vanish.
Program files count as much as the ledger. In 5 of the 15 HHS OIG audits with documentation findings, the gap was in case or personnel files, not invoices. If your grant pays for services, the service records are grant records.
Once your records system is in place, use the free Grantsights grant search to find the next award your files can support, or see Grantsights pricing.
Sources
- 2 CFR 200.334 - Record retention requirements - eCFR (opens in a new tab)
- 2 CFR 200.302 - Financial management - eCFR (opens in a new tab)
- 2 CFR 200.303 - Internal controls - eCFR (opens in a new tab)
- 2 CFR 200.336 - Methods for collection, transmission, and storage of information - eCFR (opens in a new tab)
- 2 CFR 200.337 - Access to records - eCFR (opens in a new tab)
- 2 CFR 200.338 - Restrictions on public access to records - eCFR (opens in a new tab)
- Regulation for Federal Financial Assistance, proposed rule, May 29, 2026 - Federal Register (opens in a new tab)
- HHS OIG audit reports, grants category - oig.hhs.gov (opens in a new tab)
- Preparing Your Data Management and Sharing Plan - NSF.gov (opens in a new tab)
- NIH Data Management and Sharing Policy overview - NIH (opens in a new tab)
- DOE requirements and guidance for digital research data management - Energy.gov (opens in a new tab)
- Compliance Supplement - OMB (opens in a new tab)
- FEMA Grant File Documentation and Recordkeeping Tool (opens in a new tab)
- Part 200 Uniform Requirements - Office of Justice Programs (opens in a new tab)
Frequently Asked Questions
How long do you have to keep federal grant records?
Under 2 CFR 200.334, retain federal-award records for 3 years from the date you submit the final financial report. For awards renewed quarterly or annually, the clock runs from the submission date of each quarterly or annual financial report. If litigation, a claim, or an audit begins before the period ends, keep the involved records until the matter is resolved and final action is taken. A written notice from the agency or pass-through entity can extend the period, property and equipment records run 3 years from final disposition, and post-period program-income and indirect cost records follow their own clocks. The Grantsights grant records retention guide walks through each date.
What grant records do auditors request during a Single Audit?
Auditors typically request general ledger detail, bank statements, payroll records, and expense documentation for sampled transactions. They'll ask for the Schedule of Expenditures of Federal Awards (SEFA) early. For compliance testing, they want procurement files that show the history of each purchase under 2 CFR 200.318(i), personnel records that meet the 2 CFR 200.430(g) standards, subrecipient monitoring documentation, drawdown records reconciled to the ledger, matching documentation, and evidence that costs meet the allowability rules in 2 CFR 200 Subpart E. They'll also review internal controls and any corrective action plans from prior audits. Organizations that spend $1 million or more in federal awards in a fiscal year beginning on or after October 1, 2024 must have a Single Audit.
Can I keep federal grant records electronically?
Yes. Under 2 CFR 200.336, when practicable, federal agencies, pass-through entities, and recipients must collect, transmit, and store federal award information in open and machine-readable formats. You don't need to create and keep paper copies when the original records are electronic and can't be altered. You can also replace paper originals with electronic copies if the conversion process gets periodic quality control reviews that guard against alteration and keep the files readable. On request, the agency or pass-through entity must provide or accept paper versions. Plan for software changes, backups, and access controls so the files stay readable for the whole retention period.
What is a data management plan and which agencies require one?
A data management plan describes how you'll collect, store, share, and preserve the data your project produces. NSF requires a 2-page data management and sharing plan with every proposal, and a proposal that won't produce data must include a justification instead. NIH's Data Management and Sharing Policy, effective January 25, 2023, requires a DMS Plan for NIH-funded research that generates scientific data, and recipients report on it in annual progress reports. DOE says all DOE-funded research and development awards are subject to a DOE-approved Data Management and Sharing Plan. Other agencies set data requirements in the funding notice or award terms.
What happens if you lose federal grant records?
Under 2 CFR 200.403(g), costs must be adequately documented to be allowable, so a cost you can't support can be disallowed or questioned. A Single Audit auditor must report known questioned costs when known or likely questioned costs exceed $25,000 for a type of compliance requirement for a major program (2 CFR 200.516). The agency then decides whether you repay. In a February 2018 HHS OIG audit, Henry J. Austin Health Center hadn't kept documentation supporting certain grant expenditures, and OIG couldn't determine whether $8,000,453 in costs were allowable. Repeated failures can lead to specific conditions under 2 CFR 200.208 and other enforcement actions.
Who can look at our grant records, and does FOIA apply to them?
Under 2 CFR 200.337, the federal agency or pass-through entity, Inspectors General, the Comptroller General, and their authorized representatives have a right of access to records pertinent to the award, including timely access to staff for interviews, and that right lasts as long as you keep the records. Under 2 CFR 200.338, FOIA doesn't apply to records that stay under your control, except for certain research data under 2 CFR 200.315(e). Records you send to the agency generally are subject to FOIA and its exemptions.
Last updated October 17, 2026. Corrected October 17, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.
Related Guides
Complete Guide
Federal Grant Proposal Guide: Sections & Scoring
Federal grant proposals average 50-100 pages. This guide covers every section and scoring criteria for writing a proposal that reviewers score highly.
How to Write a Data Management Plan for Grants
NIH, NSF, DOE and NASA each want a data management and sharing plan. Compare 5 agencies' rules, page limits and review, plus 2 templates.
Pre-Award vs Post-Award Grant Management (2026)
Pre-award covers proposal to submission. Post-award covers spending to closeout. Learn both stages, staffing models, and 8 compliance checkpoints.
Best Grant Management Software for Nonprofits 2026
Best grant management software for nonprofits 2026: Instrumentl, Grantable, Grantseeker, and Euna Grants after GrantHub's 2026 shutdown, with prices.
GrantSolutions Outage? Federal Grant Systems Triage (2026)
GrantSolutions outage triage for 2026: check GrantSolutions support, Grants.gov maintenance, PMS payment issues, eRA Commons, and agency deadlines.
USASpending Data Guide 2026: API and Award Search
The USAspending.gov API is free with no key. Use the spending_by_award endpoint and grant codes 02-05 to pull federal grant awards by program or state.