Many governmental entities use standard form 401(a) plan documents (volume submitter or otherwise) that were developed for nongovernmental entities. There are, however, a couple of problems with this approach. One is that governmental 401(a) plans are exempt from all of ERISA other than the Internal Revenue Code rules, and are even exempted from many of the Code 401(a) rules that would apply to private plans. (
You can click here for a chart describing the differences.) Thus, if a governmental entity adopts a 401(a) plan intended for private employers, it is probably taking on obligations from which it would otherwise be exempt. In some instances, it can be difficult to figure out later how these obligations could be fulfilled. For example, because governmental plans are not subject to prohibited transaction rules administered by the Department of Labor, they cannot get exemptions from such rules. If a plan document obligates a governmental entity to comply with ERISA prohibited transaction rules unless it obtains an exemption, the governmental entity may actually end up
more restricted in its investments than a private plan would be, because it has subjected itself to the ERISA prohibited transaction restrictions without being able to get an ERISA exemption from those restrictions.
Second, state and local law are not preempted by ERISA in the case of governmental plans. Thus, a plan intended for adoption by private plans may fail to comply with applicable state and local law rules.
It's a tough choice for many smaller governments. For a small governmental unit, adopting a standard form document may in some instances be the only way to have a plan at any reasonable cost. However, there are obvious risks associated with this approach.