Key Takeaways

• After a five year pause, the IRS is again accepting group exemption applications, and it has issued a new roadmap for how central organizations can obtain and maintain a group exemption letter.
• The new revenue procedure replaces the decades old procedures and modernizes the program with clearer supervision standards, updated eligibility rules, and more structured annual reporting.
• In response to public comments, the IRS eliminated several requirements that drew the most pushback, including a foundation classification requirement, a similar purpose requirement tied to NTEE codes, and a uniform governing instrument requirement.
• New group applications must be submitted electronically on Form 8940 via Pay.gov, and the annual supplemental group ruling information submission is designed to move to electronic submission as well.
• Certain new rules apply to preexisting group exemption letters and preexisting subordinates only after a transition period that ends January 22, 2027.
  
  

Introduction

The IRS has finally released long awaited guidance updating the group exemption letter program, which, if you missed it, had been paused since June 2020. Revenue Procedure 2026-8 modifies and supersedes the legacy framework in Rev. Proc. 80-27 and sets out the current requirements to obtain and maintain a group exemption letter for subordinate organizations affiliated with, and under the general supervision or control of, a central organization.

For 501(c)(3) networks, including national nonprofits with local chapters, faith based structures, and other federated models, this matters because a group exemption letter can relieve each subordinate organization from filing its own separate application for recognition of exemption. At the same time, the new procedure makes clear that the administrative convenience comes with more explicit oversight expectations for the central organization.

You can download and read the full text of the new procedure here. The companion explanation of public comments and the IRS’s revisions is also worth reviewing.

Rev. Proc. 2026-8 Key Developments

At a high level, Rev. Proc. 2026-8 sets the updated requirements for a central organization to obtain and maintain a group exemption letter and defines what it means for subordinates to be affiliated with, and under the general supervision or control of, the central organization. It also updates how a central organization submits a new group application and how it maintains the group ruling through annual Supplemental Group Ruling Information, or SGRI.

While many people assume group exemptions are specific to 501(c)(3) status, the procedure is far broader. It applies to group exemption letters for organizations described in section 501(c) generally, with certain special eligibility rules for 501(c)(3) subordinates, such as exclusions for private foundations and Type III supporting organizations.

The IRS modernized submission and reporting

One of the clearest modernization moves is electronic submission. Applications must be submitted electronically on Form 8940 at Pay.gov, along with the required documentation and user fee of $3,500. This is consistent with the IRS’s stated goal of improving efficiency and strengthening the integrity of data collected for oversight.

On the maintenance side, the central organization generally must submit annual SGRI at least 30 days, but no more than 90 days, before the close of its annual accounting period, and the procedure contemplates electronic submission of that information as well.

Clearer standards for affiliation, supervision, and control

A major theme in the comment process was ambiguity. Commenters asked for more clarity on what counts as affiliation and what level of information gathering satisfies “general supervision.” In response, the IRS revised the final procedure to use a facts and circumstances standard focused on whether the subordinate is a chapter, local, post, or unit of the central organization and added examples of how affiliation can be demonstrated.

On general supervision, Rev. Proc. 2026-8 explains that a central organization can satisfy its obligation to obtain, review, and retain information by obtaining a copy of a subordinate’s Form 990 or Form 990 EZ. But the procedure explicitly says a Form 990 N is not sufficient, so central organizations will need another way to collect meaningful annual information from those very small subordinates. The IRS made this revision after comments requested more specificity, especially for Form 990 N filers.

The final procedure also includes an important accommodation for subordinate organizations not required to file an annual information return or notice, which often includes churches and certain church affiliated entities. In that situation, the central organization may satisfy general supervision without annually collecting financial and activity information, so long as it annually transmits written information or otherwise educates the subordinate about the requirements to maintain exempt status, including filing obligations if applicable. The IRS explains in Notice 2026-8 that this revision was responsive to concerns raised by religious organizations about local autonomy and religious governance.

On control, commenters also argued that the proposed standard was too rigid and did not fit alternative governance structures, including union democracy models. The IRS responded by tightening the voting power concept for boards and also adding an additional pathway: a written agreement that evidences the central organization’s control over the subordinate’s activities and operations. The IRS intentionally did not prescribe a single required level of control in that agreement, stating instead that sufficiency depends on facts and circumstances.

Requirements that carried over from the proposed rule

Not every commenter request was adopted. A good example is the minimum number of subordinates. The final revenue procedure retains the rule that a central organization must have at least five subordinate organizations to obtain a group exemption letter. Notice 2026-8 explains the rationale in practical terms: the IRS views the administrative burden of processing one group application as comparable to processing roughly four individual exemption applications, so the minimum threshold is meant to preserve program efficiency.

The IRS also continues to prohibit a central organization from maintaining more than one group exemption letter, subject to transition relief for existing structures. The notice explains that historically IRS electronic systems have not systematically tracked more than one group exemption letter per central organization, and that multiple letters can also undermine the central organization’s ability to exercise meaningful supervision or control.

Requirements the IRS removed

Some of the biggest changes in the final procedure are best understood as the IRS choosing a more workable compromise after receiving comments.

The proposed “foundation classification requirement” would have required 501(c)(3) subordinates in a group to share the same public charity classification under section 509(a), subject to exceptions. Commenters noted it added burden while accomplishing little given the exceptions, and the IRS agreed, so the final procedure does not include that requirement.

The proposed “similar purpose requirement” would have pushed groups to align on a single NTEE code. The IRS concluded it would not actually facilitate supervision because many legitimate group exemptions include subordinates with different purposes, and the rule could incentivize overly broad code selection just to comply. The IRS therefore removed that requirement in the final procedure.

The proposed “uniform governing instrument requirement” drew heavy criticism, including concerns about differences in state law and the reality that local chapters often need tailored provisions for non tax reasons. The IRS agreed that complete uniformity would impose burdens outweighing its benefits and removed the uniform governing instrument requirement. In its place, the final procedure uses a narrower “uniform purpose statement requirement,” which requires subordinates that share the same purpose to include the same general purpose statement in their governing instruments. This approach is designed to give the IRS and the central organization confidence that each subordinate has a valid exempt purpose, while avoiding the practical impossibility of one size fits all governing documents.

The matching requirement was softened in a meaningful way

The proposed guidance would have required subordinate organizations to match not only each other’s 501(c) paragraph but also the central organization’s paragraph, with limited exceptions. In the final revenue procedure, subordinate organizations still must be described in the same paragraph of section 501(c) as one another, but they do not have to match the central organization’s paragraph. The IRS states that, in light of other revisions in the final procedure, requiring subordinates to match the central organization’s paragraph was no longer necessary to achieve the oversight objectives.

For some federated 501(c)(3) structures, this may be a practical relief when the central organization is structured differently from its subordinates, while still preserving a baseline of consistency among the subordinates covered by a single group letter.

Additions, removals, and effective dates now have clearer consequences

Rev. Proc. 2026-8 strengthens and clarifies the mechanics of removing a subordinate organization from a group exemption letter. A central organization may remove a subordinate with or without cause, but it must give the subordinate at least 30 days’ notice before removal and then notify the subordinate after the removal is submitted to the IRS. The authorization a subordinate signs for inclusion must acknowledge this removal power, at least for newly added subordinates.

The procedure also updates effective date rules in a way that responds to real world timing issues. In particular, for a subordinate added via SGRI that was not previously recognized as exempt, the effective date can be the subordinate’s date of formation if the organization is added within 27 months of formation. Notice 2026-8 explains that commenters viewed the proposed rule as unduly burdensome because it effectively pushed immediate SGRI submissions for every new subordinate to avoid a gap in exempt status, and the IRS agreed and revised the rule accordingly.

Transition rules for existing group exemptions

If your organization already operates under a group exemption letter, the transition period is critical. Rev. Proc. 2026-8 provides that certain provisions do not apply to preexisting group exemption letters and preexisting subordinates during the period beginning on the publication date and ending January 22, 2027. Among other things, this transition window covers the one subordinate minimum to maintain a group letter, the one group exemption letter limit, certain affiliation and supervision requirements for preexisting subordinate relationships, and the matching requirement for subordinates to be in the same 501(c) paragraph.

The IRS explains in Notice 2026-8 that it calibrated the transition period to avoid running two fully separate group exemption programs for an extended period, which would reduce efficiency and increase administrative burden for the IRS. At the same time, the transition period gives central organizations time to align relationships and records with the new standards, including confirming affiliation, supervision or control, and cleaning up mismatches in 501(c) classification among subordinates.

Practical implications for 501(c)(3) central organizations and their subordinates

For 501(c)(3) systems, the bottom line is that the IRS is signaling a more formalized oversight posture. Central organizations should expect to document how each subordinate is affiliated and how general supervision is exercised annually, especially when subordinates file Form 990 N and the central organization must collect additional written information beyond the e postcard.

Central organizations considering a new group exemption letter should plan early for the information gathering required in a group application, including the uniform purpose statement text for each purpose category among subordinates, the representations about public charity status and disqualifying classifications, and the practical reality that the application must be submitted electronically through Pay.gov on Form 8940.

Existing group exemption holders should calendar the transition period endpoint and use the runway to address structural issues, including whether multiple group exemption letters exist under one central organization and whether any subordinates do not cleanly fit the matching requirement or affiliation and supervision standards under the new definitions.

Final Thoughts

Rev. Proc. 2026-8 brings the group exemption program into a more modern compliance framework. For many 501(c) networks, the practical tradeoff is straightforward by reducing the need for each subordinate to file its own exemption application, but the central organization must be prepared to document affiliation and exercise ongoing supervision in a more deliberate way. That means building repeatable annual processes, maintaining clear records, and planning ahead for transition deadlines if you already operate under a preexisting group exemption letter.

If your organization is considering a new group exemption application, evaluating whether an existing group exemption remains a good fit, or working through the transition requirements, legal counsel can help align your governance documents and operational realities with the IRS’s updated expectations.

This post is for general informational purposes only and does not constitute legal advice.