Subaward reporting in SAM.gov used to be the last line on a grants manager’s month-end list — a data-entry chore that, at worst, produced a single audit finding somebody wrote a corrective action plan about. That has been repriced twice in the last eighteen months. The filing system moved off FSRS.gov entirely, and the proposed rewrite of federal grants rules now names a missed subaward report as a reason an agency can terminate your award. The deadline never moved. The consequence did.

A Missed Filing Is Now Named in the Termination Clause

On May 29, 2026, OMB and the federal grantmaking agencies published a proposed rule rewriting the government-wide framework for federal financial assistance, converting the Uniform Guidance into the Uniform Grants Regulation. Buried inside the discretionary-termination section is a sentence that changes how seriously a grants office should treat month-end filing. The proposed rule text published in the Federal Register states that agencies propose changes “related to further ensuring that pass-through entities follow through on their statutorily-required responsibility to report subawards on SAM.gov,” and the revised termination provision specifically calls out “the failure of the recipient to report subawards on SAM.gov pursuant to the award term required by 2 CFR part 170” as conduct that supports termination.

Read that against how the duty was previously enforced. Before, a late or missing subaward report surfaced in a Single Audit, generated a finding, and got resolved through a corrective action plan. The award kept running. Under the proposed language, the same fact pattern sits inside the clause an agency reaches for when it wants to end the relationship. That is a different risk category. It is the difference between a compliance defect you fix and a compliance defect that hands someone else an option.

Two caveats matter. This is a proposed rule, not a final one, and the comment record was enormous. OMB signaled it intends to issue a final rule effective October 1, 2026, though appropriations fights over the implementation date have made that target unstable. More importantly, none of that changes what you owe today. The reporting obligation lives in 2 CFR part 170 and in the award term already stapled to your existing agreement. The proposed rule raises the price of ignoring a duty you already have.

The Filing System Moved and Your Old Login Did Not Follow

FSRS.gov went dark the evening of March 6, 2025, and subaward reporting went live inside SAM.gov on March 8, 2025. This was not a domain redirect. It was a migration into a permissions model, and that is where recipients get stuck.

Per the SAM.gov transition guidance, an entity that needs to report subawards must hold either the Data Entry role or the Administrator role, with subaward reporting permission attached, for the specific entity it is filing for. Users who held an FSRS.gov account before January 30, 2025 can sign in with their legacy FSRS credentials once to connect the accounts. Anyone who created or changed FSRS permissions after that date has to request the Data Entry role through their SAM.gov Workspace and explicitly ask for subaward reporting permission in the request comments. Those requests route to your Entity Administrator, and if that person left the organization, you are now solving an entity administrator succession problem on a clock you did not set.

This is the quiet failure mode of the migration. The obligation is unchanged and the deadline is unchanged, but the person who used to file may no longer be able to. Nobody sends a notice. You discover it on the twenty-eighth of the month, when a subaward issued five weeks ago still has nowhere to go. Recipients tracking their broader compliance posture across federal grant programs should treat this as an access problem to solve before it becomes a reporting problem.

Run a Role Preflight Before Your Next Subaward Closes

The check takes ten minutes. Sign in to SAM.gov, open your Workspace, and select My Roles. Confirm three things: that a reporting role is assigned, that it is assigned to the correct entity UEI (organizations with multiple registrations routinely have the role on the wrong one), and that at least two people hold it. Single-person coverage on a monthly statutory deadline is not coverage. Do this before the next subaward is executed, not after.

What Actually Triggers a Report: $30,000, First Tier, Month-End Plus One

The mechanics are narrower than most people assume, and the narrowness is what causes misses. Under the award term at 2 CFR part 170, Appendix A, a recipient must report each first-tier subaward that equals or exceeds $30,000 in federal funds. First tier means the subawards you issue directly. Your subrecipient’s own subawards are not yours to file, and your subrecipients do not report their subawards from you — the pass-through entity is the filer.

The timing rule is a rolling monthly one, not an annual one: report no later than the end of the month following the month the obligation was made. A subaward executed on November 7 is due by December 31. Because the clock restarts every month, there is no single annual deadline to anchor to, which is precisely why organizations that treat this as a year-end task accumulate months of late filings.

Three edge cases account for most misses. First, threshold crossings: an initial subaward below $30,000 becomes reportable the moment a modification pushes cumulative federal funding to $30,000 or more, and the report should reflect the total. Second, the vintage rule: subawards issued on or before September 30, 2020 carry the older $25,000 threshold, which still matters for long-running awards. Third, the small-entity exemption — a recipient with gross income under $300,000 in the previous tax year is exempt from the award term’s reporting requirements, an exemption smaller nonprofit grant recipients frequently do not realize applies to them.

On the data side, you need the Federal Award Identification Number to pull up the prime award, the subrecipient’s UEI, your own subaward ID, the federal dollar amount, the subaward date, a project description, and place of performance. Subrecipients must have a UEI, but under 2 CFR 25.300(a) they are not required to complete a full SAM registration to receive a subaward — a distinction worth putting in writing before a subrecipient stalls a project trying to register for something they do not need.

The Affiliate Transfer Loophole Is Closing

The proposed rule reaches something recipients have handled inconsistently for years: money that moves to an affiliate, a subsidiary, or a related organization. Historically many organizations booked those flows as internal allocations, which meant no subaward classification, no subaward report, and no visible line on USAspending.gov.

The proposed revisions to the subrecipient monitoring and management sections would require pass-through entities to classify transfers to affiliates and subsidiaries as either subawards or contracts, on the substance of the relationship, rather than treating them as internal transfers. If the substance is a subaward, the SAM.gov filing obligation attaches with it. Analysts reviewing the proposal have flagged this as one of the sleeper provisions: misclassification would produce reporting deficiencies, and reporting deficiencies now feed the termination clause discussed above.

The proposal also would eliminate fixed amount subawards, pushing those relationships toward cost-reimbursement structures. That matters here because it removes a category of arrangement organizations sometimes used to keep a relationship administratively light. If your organization runs money through a related entity or a shared-services affiliate, the classification memo you have been meaning to write is now the document that decides whether you have a reporting gap.

The Consequence Ladder, From Audit Finding to Debarment

The escalation path was never hidden — it was just rarely climbed. OMB’s Controller Alert on subaward reporting instructs agencies that when noncompliance cannot be remedied through additional award conditions, they are encouraged to temporarily withhold cash payments pending correction, disallow all or part of the cost of the noncompliant activity, wholly or partly suspend or terminate the award, initiate suspension or debarment proceedings under 2 CFR part 180, and withhold further awards for the program.

Note the first rung. Cash withholding is a liquidity event, not a paperwork event. An organization operating on reimbursement can absorb an audit finding indefinitely; it cannot absorb a payment hold for a quarter.

The audit side is equally specific. The OMB Compliance Supplement directs auditors to select a sample of first-tier subawards, trace reported data elements back to source documentation, test mathematical accuracy, and confirm the action was reported no later than the last day of the month following the month of obligation. Four distinct findings can result: the entity did not report, did not report timely, reported an incorrect amount, or omitted key data elements. Filing something is not the same as filing it correctly, and three of those four findings hit organizations that believed they were compliant.

Context for why enforcement is tightening: the proposed rule’s preamble cites a 2023 GAO review identifying challenges with the completeness and accuracy of subaward data displayed on USAspending.gov. When the underlying dataset is known to be incomplete, the policy response lands on the parties who populate it. Agencies would be required to monitor recipient compliance and take corrective action, and recipients would have to confirm in performance reports that all subawards issued during the period were reported. Readers who track this kind of regulatory movement can follow it through our grants industry news coverage.

Frequently Asked Questions

Who files the subaward report, the pass-through entity or the subrecipient?

The pass-through entity files. Subrecipients do not report their own subaward information into SAM.gov. What subrecipients owe you is data — their UEI, and in some cases executive total compensation information — which you then submit as part of your report. If your subaward agreements do not obligate subrecipients to provide that information on a timeline that lets you meet the month-end deadline, amend the template.

What happens if a subaward starts under $30,000 and later grows past it?

It becomes reportable. Once a modification raises cumulative federal funding to $30,000 or more, the subaward enters the reporting requirement as of the date the obligation crossed the threshold, and the report should reflect the total subaward amount, not just the incremental modification. Track modifications against the threshold continuously, because a $22,000 subaward that receives an $11,000 increase creates a filing duty most tracking spreadsheets never flag.

Does my subrecipient need a full SAM.gov registration?

No. A subrecipient organization must have a Unique Entity Identifier, but 2 CFR 25.300(a) does not require it to complete a full SAM registration solely to receive a subaward. Individuals receiving subawards are treated differently again. Getting this wrong delays project starts while a subrecipient works through a registration process it did not need.

Is any recipient exempt from subaward reporting in SAM.gov?

Yes, narrowly. The award term exempts a recipient whose gross income in the previous tax year was under $300,000. This is an entity-level exemption based on your own prior-year income, not a judgment about the size of the subaward. If your organization is near that line, document the determination each year rather than assuming last year’s answer still holds.

How far back should we reconcile if we have missed filings?

Reconcile to the start of every open award. Pull every executed subaward and modification, filter for $30,000-plus in federal funds, and match each one against what actually appears in SAM.gov. Late reports still get filed — a late filing is a better position than a missing one when an agency or auditor pulls the record, and self-identified gaps read very differently from discovered ones.

Bottom Line and Next Steps

The recommendation here is narrow and sequenced, and it is not “build a compliance calendar.” Do the role preflight first, this week: confirm in SAM.gov Workspace that at least two named people hold a reporting role on the correct entity UEI. Access is the gating item, and it is the one thing you cannot fix on the twenty-ninth of the month. Second, run the reconciliation back to the start of each open award and file whatever is missing, on the reasoning that a voluntarily corrected gap is a materially different conversation than one an auditor finds. Third, add the threshold-crossing check to your modification workflow, since that is where the misses cluster.

What has changed is not the rule but the leverage attached to it. A reporting record that used to be an administrative artifact is becoming an input into whether an award continues, and the affiliate provisions mean some organizations will discover reportable subawards they never classified as subawards at all. The organizations that come through this cleanly will be the ones that treated a permissions check as urgent while everyone else was reading the preamble.

If your team is carrying more federal awards than its post-award capacity can absorb, that is a staffing question before it is a compliance one. OpenGrants’ managed grant writing and grants management services support recipients through the post-award reporting cycle, and our network of vetted grant professionals includes practitioners who do subrecipient monitoring and SAM.gov reporting as core work.