HB7799 adds a new subsection to Internal Revenue Code section 501 that makes organizations exempt under 501(c)(3) liable — including criminally — for activities connected to projects they fiscally sponsor when donor deductions are claimed or represented. The bill defines three categories of ‘‘covered activity’’ (aiding foreign terrorist organizations, violent/intimidatory interference with constitutional rights, and forceful obstruction of commerce), creates a statutory definition of ‘‘fiscal sponsorship,’’ and establishes a presumption that sponsors are responsible for how sponsored funds are used while preserving a due-diligence defense.
This is a structural change to how intermediary nonprofits are treated under tax law and criminal exposure doctrine. The provision will reshape underwriting, contracting, and operational practices for community foundations, fiscal sponsors, donor-advised funds and similar intermediaries, and it raises immediate questions about evidentiary burdens, the scope of criminal liability, and First Amendment-protected activity that may be swept up in the statute’s language.
At a Glance
What It Does
The bill amends Section 501 by adding subsection (s), which triggers criminal and civil liability for 501(c)(3) organizations that expend funds as fiscal sponsors when a donor is allowed a charitable deduction or the sponsor represents that a deduction is available. It defines which activities create exposure, what counts as a fiscal sponsorship, creates a rebuttable presumption of sponsor responsibility, and preserves a defense for due diligence and reasonable oversight.
Who It Affects
Directly affects 501(c)(3) fiscal sponsors (community foundations, fiscal sponsor nonprofits, some donor-advised fund structures), the projects they host, donors who claim deductions based on sponsorship, nonprofit legal and compliance teams, and liability insurers that cover nonprofit directors and organizations.
Why It Matters
By imposing both criminal and civil exposure tied to fiscal sponsorship, the bill alters the risk calculus for intermediaries that currently accept pass-through or project-based funds. That change will influence whether organizations accept fiscal sponsorship arrangements, how they document control over funds, and how they police activities of sponsored projects.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
HB7799 creates a new, standalone liability rule for 501(c)(3) organizations that act as fiscal sponsors. The statute triggers liability only when two conditions are present: the nonprofit expends funds for a fiscal sponsorship, and either a donor actually receives a deduction under section 170 or the sponsor tells a donor the contribution is deductible.
Once those conditions are met, the sponsor becomes potentially liable — criminally ‘‘related to or arising from’’ the sponsorship and civilly for ‘‘covered activity’’ connected to it.
The bill lists three types of covered activity. First, materially assisting or conspiring with a foreign terrorist organization as designated under 8 U.S.C. 1189.
Second, using force, a credible threat of force, or physical obstruction to injure, intimidate, or interfere with someone lawfully exercising a constitutional right. Third, using force or physical blocking to prevent the lawful movement of goods in interstate or intrastate commerce.
The statute defines ‘‘intimidate’’ and supplies plain examples of the conduct it targets, but it does not supply a catalogue of criminal mens rea elements or procedural safeguards.Crucially, the bill defines ‘‘fiscal sponsorship’’ narrowly: the sponsor must both receive and administer funds on behalf of a non‑exempt project and retain discretion and control over those funds to ensure they are used for the sponsor’s charitable purposes. The draft also creates a statutory presumption that the sponsor is responsible for legal compliance in how those funds are used, while explicitly allowing the sponsor to raise defenses based on ‘‘due diligence and reasonable oversight.’'Taken together, those mechanisms encourage sponsors to document control and oversight practices more rigorously, revise agreements with projects to allocate risk, and reassess communications to donors about deductibility.
At the same time, the statute’s phrasing — particularly the broad language in the criminal-liability trigger and the presumption of responsibility — leaves open major interpretive questions about how prosecutors, civil plaintiffs, and courts will apply the new rule.
The Five Things You Need to Know
The liability trigger requires both (A) the sponsor expending funds for a fiscal sponsorship and (B) either a donor is allowed a deduction under section 170 or the sponsor represents that a donation is deductible.
The bill imposes criminal liability for conduct ‘‘related to or arising from’’ a fiscal sponsorship and civil liability for ‘‘covered activity’’; it does not limit liability to specific statutes or to negligent conduct.
Covered activities are defined in three buckets: materially aiding a designated foreign terrorist organization; using force, threats, or physical obstruction to injure/intimidate/interfere with someone exercising constitutional rights; and using force or blocking commerce to stop lawful movement of goods.
The statutory definition of fiscal sponsorship requires the sponsor to receive and administer funds for a non‑exempt project and to retain discretion and control over the funds — meaning pure pass‑through arrangements that lack sponsor control may fall outside the rule.
The statute creates a rebuttable presumption that sponsors are responsible for compliance with laws governing funded activities but preserves a defense for ‘‘due diligence and reasonable oversight’’ without specifying objective standards or safe-harbor procedures.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
States the act’s short name: the ‘‘Stop Proxy Organizations Nurturing Subversive Operations and Riots Act’’ or ‘‘SPONSOR Act.’
Liability trigger and general statement of liability
Establishes the two-part trigger: a 501(c)(3) must have expended funds for a fiscal sponsorship and a donor deduction must be allowed or represented; once both are met the sponsor ‘‘shall bear any criminal liability related to or arising from such fiscal sponsorship, and any civil liability concerning a covered activity’’ tied to that sponsorship. Practically, this elevates intermediary status into a potential basis for prosecution and civil suits rather than merely a tax-administrative issue.
Definition of ‘‘covered activity’’
Specifies three categories that create civil/criminal exposure: (A) materially assisting or conspiring with a designated foreign terrorist organization, (B) force, threats, or physical obstruction causing injury/intimidation/interference with constitutional rights, and (C) force or blocking commerce preventing movement of goods. These categories map to existing criminal and civil norms but broaden who can be sued or charged by making the sponsor a target when conduct is connected to sponsored funds.
Statutory definition of fiscal sponsorship
Defines fiscal sponsorship as a relationship where a 501(c)(3) receives and administers funds for a non‑exempt project and importantly retains discretion and control over those funds to ensure they are used for the sponsor’s charitable purposes. That control element is the linchpin that separates simple pass-through funding from arrangements likely to trigger liability.
Presumption of responsibility and defense available
Creates a statutory presumption that the sponsor is responsible for legal compliance in the use of sponsored funds, shifting initial evidentiary burdens toward the sponsor. Paragraph (5) preserves defenses grounded in ‘‘due diligence and reasonable oversight,’’ but the bill does not define those terms or provide a safe harbor; that omission will create litigation over what documentary practices, monitoring, and contractual terms satisfy the defense.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Victims and private litigants — the statute creates a clearer target for civil suits against organizations whose sponsored projects cause harm or violence, increasing avenues for recovery.
- Federal and state prosecutors — provides a direct statutory hook to pursue intermediaries when sponsored funds are linked to terrorism or violent disruptions, potentially simplifying indictments or forfeiture actions.
- Donors seeking transparency — donors worried about unintended uses of gifts gain an additional lever to press sponsors for stronger oversight and documentation, since donors’ deductions are an express trigger.
Who Bears the Cost
- 501(c)(3) fiscal sponsors (community foundations, fiscal-sponsorship nonprofits, arts incubators) — face heightened criminal and civil exposure, increased compliance and legal costs, and pressure to alter or refuse sponsorships.
- Small projects and start-ups that rely on fiscal sponsorship — may lose access to intermediaries or face added costs and delays when asked to incorporate separately or meet stricter oversight requirements.
- Donors and donor-advised funds — may face decreased access to deductible giving routes if sponsors limit representations about deductibility or decline to sponsor higher-risk projects.
- Directors’ and organizations’ liability insurers — expect higher claims, coverage disputes, and premium increases because the statutory presumption and criminal exposure change underwriting risk.
- State and federal courts and prosecutors — could see increased filings and investigations as plaintiffs and authorities test the scope of the new liability hook.
Key Issues
The Core Tension
The bill is built around a trade-off: increase accountability by making financial intermediaries legally liable for harmful uses of sponsored funds, versus preserving robust fiscal-sponsorship mechanisms and protected expressive activity. Tightening liability responds to real risks of proxy funding for illegal conduct but also shifts legal and financial risk onto nonprofits that facilitate legitimate, often experimental, projects — a shift that is likely to reduce fiscal sponsorship as a tool for new or controversial civic activity.
The statute packs a large change into a short text and leaves several critical interpretive gaps. First, the phrases ‘‘criminal liability related to or arising from such fiscal sponsorship’’ and ‘‘civil liability concerning a covered activity’’ are expansive but unspecified: the bill does not identify which criminal statutes apply, what mental-state elements must be proved against a sponsor, or the causal standard tying sponsor conduct to a third party’s wrongdoing.
That creates uncertainty for counsel trying to advise boards about exposure and for insurers deciding coverage terms.
Second, the presumption of sponsor responsibility plus an undefined ‘‘due diligence and reasonable oversight’’ defense creates a shifting burden structure without safe-harbor metrics. Will routine documentation and contract clauses suffice, or will sponsors need real-time monitoring and intervention?
The statute’s covered-activity definitions also risk sweeping in protected expressive or assembly-related conduct: subsection (B)’s language on intimidation, interference, and physical obstruction could capture nonviolent protests or civil disobedience depending on how ‘‘intimidate’’ and ‘‘physical obstruction’’ are construed. Those First Amendment tensions, plus practical issues about how prosecutors coordinate with the IRS and how civil plaintiffs use the new hook, make implementation and litigation likely and unpredictable.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.