Review 403(b) sponsor eligibility, employee access, provider coordination and oversight before comparing proposals or changing your nonprofit’s plan.
April 1, 2024 · Financial Forte Staff
Historical article: prepared retrospectively using information available as of April 1, 2024.
A nonprofit leader may hear that a 403(b) is the natural retirement plan for an organization with a public-service mission. The mission matters to the business, but it does not by itself establish eligibility for this type of plan. The employer's legal and tax status comes first.
Before comparing providers or investment menus, confirm that the organization can sponsor the arrangement and identify the rules that apply to its employees. That foundation helps the board, finance team and HR staff make a benefits decision they can administer consistently.
Verify the employer category before selecting the plan
403(b) arrangements are available to specified eligible groups, including employees of qualifying section 501(c)(3) organizations, public schools and certain ministers. An ordinary for-profit business cannot choose a 403(b) simply because it prefers the pricing or wants a similar benefit.[1]
Not every tax-exempt organization is a 501(c)(3). Obtain the relevant status information and have the provider or counsel confirm eligibility. If the organization is not eligible, the next question is which other arrangement fits its circumstances, not how to work around the sponsor requirement.
Public schools, private charitable organizations and church-related employers may also operate under different legal frameworks. A proposal prepared for one category shouldn't be copied without checking those differences.
Keep the eligibility conclusion with the plan records. If the organization's structure changes, that record gives the next reviewer a starting point rather than leaving the original assumption unexplained.
Separate access to salary deferrals from employer funding
An eligible employer offering salary deferrals generally needs to consider the 403(b) universal-availability rule: if some employees can defer, the opportunity generally must be available to other employees, subject to permitted exceptions. Those exceptions need specific review; job titles or informal labels are not enough.[1]
An employer contribution is a separate design question. The rules for who can make salary deferrals should not be assumed to match every condition governing an employer contribution. Ask the administrator to explain each group and the basis for any exclusion.
Consider a hypothetical charitable organization with twenty employees. It offers the program to salaried staff but has not evaluated the hourly employees because the original announcement described the benefit as being for “professional employees.” That wording doesn't establish a permitted exclusion. The first operational decision is to stop relying on that label and have the administrator review the complete census against documented eligibility rules.
Suppose eight of the twenty employees were left out solely because they were hourly. The administrator confirms that all eight should have received the deferral opportunity. For one employee earning an assumed $24,000 who wanted to defer 3%, that opportunity would have been $720 annually, or $60 monthly. This does not establish a correction amount or an employer match: actual elections, compensation and the applicable correction method require their own review. The immediate action is to correct the enrollment process for the eight affected people and have the administrator evaluate the prior omission. The practical improvement is an eligibility review based on the actual rules, rather than an enrollment list inherited from an old memo.
That review can improve access and employee understanding while reducing the chance that the same omission continues. It does not require promising that every employee will choose to contribute.
Make the written plan and operating process agree
The plan's governing documents and contracts should describe the arrangement being administered. Identify who maintains them, who approves changes and how payroll and providers learn about those changes. Having several vendors does not remove the need for a coordinated process.[2] Ask who combines information across vendors before a transaction that requires a plan-level check.
For example, an employee may interact with a vendor about an account while HR tracks eligibility and payroll transmits contributions. The organization still needs a way to reconcile those pieces. Otherwise each party may correctly perform its own narrow task while an error falls between them.
Ask how contribution limits, transfers, distributions and other relevant activity are coordinated across the arrangement. Don't assume that one provider can see every transaction occurring with another provider.
A written responsibility chart can be short. It should identify who supplies data, who checks it, who resolves an exception and who confirms the task is complete.
Assess the benefit from the employee's point of view
Provider comparisons should include more than an employer invoice. Review the services, investment expenses and any product or contract restrictions that affect participants. An annuity contract and a mutual-fund custodial account can have different features and costs; compare the actual terms rather than relying on the plan label.[1]
Ask what help employees receive when enrolling or changing contributions. A confusing benefit may have limited practical value even if its formal design is sound. Clear explanations can support participation and make the employer's benefit easier to understand during recruiting.
Use appropriate measures: participation, recurring questions, unresolved service issues and total cost. If participation is low, ask whether the obstacle is affordability, communication, eligibility or the enrollment process before assuming employees simply aren't interested.
Those measures can guide improvement. They do not establish that the plan caused a change in retention or that a lower-priced provider will necessarily deliver better value.
Identify the oversight duties that actually apply
Some 403(b) plans are subject to ERISA fiduciary requirements; other arrangements may fall outside that framework under applicable exceptions. Determine the plan's status specifically. Where fiduciary responsibilities apply, selecting and monitoring providers and evaluating reasonable costs require an appropriate process.[3]
Where ERISA does not apply, tax rules, contracts, state law and other duties can still matter. The organization should identify those responsibilities rather than treating an exemption as permission to stop reviewing the benefit.
Begin with three documents: the employer-status confirmation, the current plan documents and a complete employee census. Review those before requesting a redesign. A well-chosen 403(b) starts with a qualified sponsor and an operating process that gives the right employees a clear, usable opportunity to save. Track employees who should have received enrollment materials and confirm delivery, then review any gap with the administrator.
Related reading
- 403(b) Universal Availability: Where Exclusions Go Wrong
- 403(b) or 401(k) for a Nonprofit: Compare the Operating Model
Have more questions about 403(b) eligibility, administration or provider oversight? Email Dave at dave@financialforte.com to discuss your questions and next steps.
The contact invitation is current; it does not imply this contact path existed on the historical reference date.
Educational information, not personalized investment, tax, legal or benefits advice. Examples use hypothetical assumptions. Verify current rules and your circumstances before acting.
