Form 5500
Form 5500 is the primary annual return/report used by employee benefit plans subject to the applicable ERISA and Internal Revenue Code reporting rules. Depending on the plan, it can require multiple schedules and attachments.
Form 5500-SF
Form 5500-SF is the Short Form Annual Return/Report of Small Employee Benefit Plan. It is intended for eligible small plans that satisfy the conditions in the current instructions. Size alone does not answer every eligibility question, so the filer should verify all requirements for the plan year.
Why the Choice Matters
Using the wrong form can create filing problems. The return format affects the data elements, schedules and validation rules that apply. Preparers should determine eligibility before building the filing.
Both Are Filed Electronically
The DOL states that Form 5500 and Form 5500-SF must be filed electronically through EFAST2 using approved third-party software or IFILE.
Questions to Ask Before Choosing the Form
- What type of employee benefit plan is being reported?
- How many participants are covered under the applicable rules?
- Does the plan satisfy all small-plan short-form eligibility conditions?
- Are there plan investments, schedules or circumstances that require the full Form 5500?
- Is the filing an original, amended or delinquent return?
Software Should Support the Decision, Not Make It Blindly
Software can present the correct data-entry workflow after the preparer selects a filing type, but the plan's facts and current DOL instructions determine which form is appropriate.
Official DOL reference: Form 5500 Series.
Do Not Rely on Last Year's Form Without Rechecking
A plan that qualified for Form 5500-SF in a prior year may not automatically qualify in the current year. Participant counts, investments, plan characteristics and filing rules can change. Reconfirm eligibility each year before carrying forward the prior return type.
What Software Should Do After You Choose
Once the correct filing type is determined, software should present the appropriate fields and validation rules, reuse recurring plan information when appropriate, and help produce EFAST2-compatible filing data. It should also make the selected form obvious so the preparer does not accidentally build the wrong return.