Federal grant reporting means filing accurate financial, property and performance data on the schedule your award terms set, under the rules in 2 CFR Part 200. The core forms are the SF-425, SF-428 and SF-429, and the Single Audit threshold was updated for fiscal years beginning on or after 1 October 2024. If you manage a federal award, your immediate task is to build a reporting calendar against your Notice of Award and confirm your organisation's roles are current in SAM.gov.
TL;DR:
- Final recipient financial reports are due within 120 days of performance end, and subrecipient reports within 90 days; performance deadlines vary by type and tier.
- FSRS.gov ceased operating on March 8, 2025, and subaward filings now go through SAM.gov, where active UEIs and correct Workspace roles are essential.
- The revised Single Audit threshold applies to fiscal years beginning on or after October 1, 2024, so verify the current threshold before assessing audit exposure.
- Reconcile SF-425 amounts to the general ledger, connect performance claims to approved objectives and budget lines, and assign a second reviewer before filing.
- Awards funding equipment or real property may require SF-428 or SF-429 filings, depending on the agency’s capitalization threshold and award instructions.
Table of Contents
- Which reports you must submit and where to file them
- Reporting schedules and final-report deadlines you must calendar in
- Financial tracking and internal controls auditors expect
- Subrecipient monitoring and subaward reporting in SAM.gov
- Single Audit readiness and a phase-based reporting checklist
- Common errors and pitfalls in federal grant reporting
- Best practices for data collection and validation
- Using technology and tools to streamline reporting
- How to address and respond to a federal grant reporting audit or finding
- Keystone perspective: why mapped workflows and audit-ready evidence matter
- How Keystone can help with audit-ready reporting
- FAQ
- Sources
Which reports you must submit and where to file them
Most federal awards generate three categories of report: financial, property and performance. Each has its own form, trigger and filing channel, and missing one is one of the fastest routes to a finding.
The SF-425 (Federal Financial Report) is the OMB-approved vehicle for reporting cash drawn, expenditures and unobligated balances against your award. Agencies collect it at least annually and no more often than quarterly, as set out in 2 CFR §200.328. Common pitfalls include reporting cash drawn rather than cash expended, and failing to reconcile the SF-425 to your general ledger before submission.
Performance progress reports (PPRs) have to connect spending to actual accomplishments. 2 CFR §200.329 requires recipients to relate financial data to programme performance, so a PPR that lists activities without tying them to budget lines invites scrutiny.
SF-428 and SF-429 cover tangible personal property and real property respectively, triggered when your award funds equipment, land or buildings above your agency's capitalisation threshold.
- SF-425: expenditures, unobligated balances and cash management status.
- PPR: narrative and quantitative progress linked to approved objectives.
- SF-428: federally funded equipment and tangible personal property.
- SF-429: real property acquired, improved or disposed of under the award.
Your Notice of Award terms, and agency-specific guidance such as ACF's reporting instructions, often name the exact submission system, whether that is the Payment Management System, GrantSolutions or OLDC.
Reporting schedules and final-report deadlines you must calendar in
Timing rules sit in the same sections that define the forms themselves, and missing a window is treated the same as missing the report entirely.
- Agencies may require financial and performance reports no more than quarterly and no less than annually, per §200.328 and §200.329, unless your award terms set a different frequency.
- Final recipient financial reports are due no later than 120 days after the period of performance ends; subrecipients generally owe their final reports to the pass-through entity within 90 days.
- Performance reports follow parallel 30/90/120 day windows depending on report type and recipient tier, so check your specific award terms rather than assuming a single rule applies.
- Build in a buffer: submitting several business days ahead of the deadline gives you room to fix a rejected file or a system outage without breaching the actual due date.
Closeout reporting, including the final SF-425 and final PPR, should be scheduled the moment your period of performance end date is confirmed, not left until the deadline is imminent.
Financial tracking and internal controls auditors expect
Every number on an SF-425 has to trace back to a ledger entry, and every ledger entry has to trace back to supporting evidence. 2 CFR §200.303 requires recipients to establish and maintain effective internal control over federal awards, and auditors test against that standard under §200.514 during a Single Audit.
In practice, that means your financial entries need to connect to performance outputs rather than sitting in a separate spreadsheet. A dollar spent on training hours should map to the number of participants reported in your PPR, so a reviewer can follow the thread from invoice to outcome.
- Require documented approval before any federal award expenditure posts.
- Reconcile the ledger to the SF-425 before every submission, not after.
- Segregate duties between whoever approves spending and whoever records it.
- Retain supporting records for the period your award terms specify, typically three years from final report submission.
- Keep subaward, payroll and procurement evidence in a structure a reviewer can navigate without your explanation.
Pro Tip: Run your reconciliation on a fixed monthly date, not only when a report is due, so errors surface while they are still easy to fix.
A single ledger or an integrated reporting system that links financial codes to performance milestones removes much of the manual reconciliation that otherwise consumes staff time in the week before a report is due.
Subrecipient monitoring and subaward reporting in SAM.gov
If you pass federal funds to another organisation to carry out part of your award, you take on subrecipient monitoring obligations, and auditors will ask for the documentation that proves you met them: risk assessments, monitoring visit notes and subaward agreements with the required federal clauses.
FSRS.gov was retired on 8 March 2025, and subaward reporting functionality moved entirely to Sam. That means your organisation now manages reporting roles and Workspace permissions directly in SAM.gov rather than in a separate system.
- Confirm your entity's Unique Entity Identifier (UEI) is active and correctly linked in SAM.gov.
- Check that the people responsible for subaward reporting hold the correct Workspace roles.
- Verify pass-through award clauses are present in every subrecipient agreement.
- Keep subrecipient files, risk assessments and monitoring evidence in one accessible location.
Mis-mapped Workspace roles are one of the most frequent causes of delinquent subaward reports, since the person who used to file in FSRS may no longer hold reporting rights in the consolidated system.
Single Audit readiness and a phase-based reporting checklist
OMB raised the Single Audit threshold, effective for fiscal years beginning on or after 1 October 2024, so a recipient that previously sat below the old threshold may now find itself exempt, or vice versa depending on award activity. Confirm the threshold against your fiscal year before assuming your exposure.
The Compliance Supplement organises audit testing around 12 compliance requirement categories, and reporting, procurement, and subrecipient monitoring are almost always in scope regardless of programme.
- Continuous capture: log procurement decisions, payroll evidence and subaward documentation as they happen, not retrospectively.
- Period close: reconcile the ledger to the SF-425 and PPR data at each reporting interval.
- Supervisory review: a second person checks figures and supporting evidence before submission.
- Submission: file through the correct agency system ahead of the deadline.
- Closeout evidence handover: compile the full evidence file, ready for auditor request, before the award formally closes.
Auditors typically request procurement records, bank reconciliations, subaward files and performance evidence together, so a workflow that keeps these linked throughout the award period removes the scramble at audit time.
Common errors and pitfalls in federal grant reporting
The same handful of mistakes recur across agencies and sectors. Reporting cash drawn instead of cash expended on the SF-425 overstates or understates your financial position and forces a correction later. Submitting a PPR that describes activities without referencing the approved objectives or budget categories leaves a reviewer unable to confirm progress matches spending.
Treating subrecipient monitoring as a one-off check at award start, rather than an ongoing activity, is another frequent gap: auditors expect evidence of monitoring throughout the period, not a single risk assessment filed and forgotten. Missing the 90/120 day final-report windows because closeout wasn't calendared in advance is avoidable with a simple date entry at award setup.
Property reporting is often overlooked entirely. Organisations that purchase equipment or acquire real property under an award sometimes never file the SF-428 or SF-429 because no one assigned ownership of that task. Finally, inconsistent figures between the financial report and the performance report, caused by two people pulling numbers from different sources, are one of the most common findings auditors cite. The fix in every case is the same: assign clear ownership of each report, calendar the deadlines against the Notice of Award, and reconcile financial and performance data from a single source before anything is submitted.
Best practices for data collection and validation
Accurate reporting starts with where your numbers come from. Pull financial figures directly from your general ledger rather than from a budget tracker maintained separately, since the two can drift apart without anyone noticing until a report is due.
Validate performance data against source documents: attendance sheets, service logs or milestone sign-offs, rather than relying on staff recollection when a PPR is being drafted. Build a short pre-submission checklist that confirms the SF-425 totals match the ledger, the PPR narrative matches the reported figures, and any property additions have a corresponding SF-428 or SF-429 entry.
Assign a second reviewer to every report before it goes out, even when your team is small, since a fresh set of eyes catches transposition errors and mismatched periods that the preparer misses. Keep a running log of data sources for each report so that, months later, you or an auditor can trace a figure back to its origin without reconstructing the process from memory. Organisations that work across multiple federal programmes with different agency systems, such as Payment Management System for one award and GrantSolutions for another, benefit from a single internal tracker that notes which system each report goes to and when.
Using technology and tools to streamline reporting
Spreadsheets work for a single small award, but they become a liability once an organisation manages several federal grants with overlapping but distinct reporting calendars. A platform that maps your workflow against each award's specific reporting requirements removes the guesswork of remembering which form goes where and when.
Integrated systems that link financial codes to performance milestones cut down the manual reconciliation that otherwise happens in the days before a deadline, since the connection between a dollar spent and an outcome reported already exists in the data rather than being rebuilt each time. For payroll evidence specifically, electronic timekeeping systems built for audit readiness can verify hours charged to federal awards with location and identity checks, which strengthens the documentation behind labour costs on your SF-425.
Automated reminders tied to your actual award terms, rather than generic quarterly assumptions, reduce the risk of missing an agency-specific deadline. Whatever tools you choose, the goal is the same: a single source of truth that finance, programme staff and reviewers all pull from, so the numbers in your SF-425, your PPR and your ledger never diverge.
How to address and respond to a federal grant reporting audit or finding
When an auditor raises a finding, the first step is to understand precisely what evidence was missing or what control failed, rather than reacting to the headline description. Pull the specific transaction, report or period the finding references and trace it back through your records.
Respond within the timeframe your cognizant agency or pass-through entity sets, and provide a corrective action plan that addresses the root cause, not just the individual instance. If a finding relates to subrecipient monitoring, for example, the fix is a documented monitoring schedule going forward, not just a single retroactive site visit.
Keep a record of every finding and its resolution, since repeat findings across audit cycles signal to agencies that a control weakness was not genuinely fixed. Where a finding points to a systemic issue, such as inconsistent reconciliation between financial and performance data, treat it as a prompt to review your reporting workflow rather than patching the single report in question. Organisations managing federal construction or capital awards sometimes find findings tied to property reporting; reviewing capital planning and reporting processes alongside the audit response helps prevent the same gap recurring on the next award cycle.
Keystone perspective: why mapped workflows and audit-ready evidence matter
After 20 years working across healthcare, construction and government delivery, the pattern behind most federal grant findings looks the same: evidence exists somewhere, but nobody can produce it fast enough or in the shape an auditor expects. The forms themselves rarely cause failures. Disconnected systems do.
What changes the outcome is mapping the reporting workflow before the first report is due, so financial entries, performance evidence and subaward documentation sit in one traceable chain rather than three separate inboxes. Organisations that do this consistently see fewer findings, faster closeouts and far less ad-hoc reconciliation in the final week before a deadline.
— Peter
How Keystone can help with audit-ready reporting
We build mapped, auditable workflows for exactly this job. Videra PM and Videra Healthcare connect your financial tracking, performance evidence and subaward documentation in one place, and our consultancy team can help you design the reporting workflow around your actual award terms.
Get in touch to see how Videra fits your reporting calendar.
FAQ
What does a grant report look like?
A federal grant report typically combines a standard financial form, usually the SF-425, with a narrative or quantitative performance report that ties spending to progress against your approved objectives. Depending on your award, it may also include property forms such as the SF-428 or SF-429 if you acquired equipment or real property.
Is FFATA reporting still required?
Subaward reporting obligations that FFATA established still apply, but the filing system changed: FSRS.gov was retired on 8 March 2025, and subaward reporting now runs through SAM.gov. Recipients need to confirm their Workspace roles in SAM.gov to continue filing correctly.
How do I write a federal grant application?
A federal grant application generally requires a narrative describing the proposed project, a detailed budget, and supporting documents such as organisational certifications, matched to the specific funding opportunity announcement. Requirements vary significantly by agency and programme, so the funding opportunity announcement itself is the authoritative guide for format and content.
What is a US government grant?
A US government grant is an award of federal funds to a state, local government, organisation or individual to carry out a public purpose, made under terms set out in the Notice of Award and governed by 2 CFR Part 200. Unlike a contract, a grant does not purchase goods or services for the federal government directly, but it still carries binding financial and performance reporting obligations.
Sources
- eCFR: 2 CFR 200.328 Financial reporting
- Part 1 - Background, purpose and applicability (Compliance Supplement materials)
- Sam
- ACF grants reporting guidance (SF-425, SF-428, SF-429 explanations)