Employee Benefits
HR & Compliance
Technology
Wellness
PEO Solutions
An HR manager at a growing company may add a flexible spending account during benefits planning because it looks like a simple checkbox. Employees elect an amount, payroll deducts it, and the company offers a useful tax-advantaged benefit.
The complexity appears later. A claim arrives with an incomplete receipt, an employee asks whether a debit card purchase is eligible, payroll carries forward an outdated limit, and several workers reach year-end with unused balances. At that point, FSA administration is no longer an enrollment feature. It's a regulated operating process involving payroll, claims, documentation, deadlines, plan design, and employee behavior.
Table of Contents
- Why FSA Administration Matters More Than You Think
- Understanding How Flexible Spending Accounts Work
- IRS Rules and 2026 Contribution Limits You Need to Know
- Setting Up Your FSA Program and Choosing a Vendor
- The Surprising Truth About Substantiation and Forfeitures
- Common FSA Administration Pitfalls and How to Avoid Them
- Best Practices for Smooth FSA Administration
- How Benely Simplifies FSA Administration for Growing Companies
Why FSA Administration Matters More Than You Think
FSA programs were created in the United States in 1978, while a major IRS ruling in 1984 established the basic structure still associated with these accounts. Employees generally elect an annual amount in advance, and unused balances are generally forfeited at year-end unless the plan includes an applicable exception. The history and structure of FSAs help explain why administration requires disciplined annual planning rather than casual reimbursement handling.
A benefits manager who treats the account as a payroll deduction alone will miss the operational risks. The employer must coordinate elections, deductions, claims, substantiation, account balances, annual limits, eligible expenses, plan documents, and employee notices. A mistake in one area can create confusion elsewhere. For example, an employee may believe a balance is available because the payroll deduction worked, while the administrator still needs documentation before reimbursing a claim.
The employee experience is part of compliance
Compliance controls matter, but employee communication determines whether workers understand and use the benefit. A technically correct plan can still frustrate employees if they don't know which expenses qualify, when claims must be submitted, or whether the employer selected a grace period or carryover.
The same principle applies to year-end balances. Reminders that arrive only during open enrollment won't help an employee who has already forgotten the account or can't tell whether a claim was approved. Effective administration keeps the balance, claim status, documentation request, and relevant deadline visible throughout the plan year.
Practical rule: Treat an FSA like a small financial program with a customer experience, not like a checkbox inside the benefits menu.
This guide focuses on the work that makes a difference in practice: translating rules into payroll controls, selecting plan features deliberately, designing substantiation workflows, communicating at useful moments, and using technology without allowing automation to hide balances or deadlines.
Understanding How Flexible Spending Accounts Work
An FSA lets an employee choose an annual contribution during open enrollment. The employer then deducts that amount from paychecks on a pre-tax basis, subject to the rules of the specific account. The employee uses the funds for eligible expenses and submits a claim, or uses an approved debit card transaction that still may require supporting documentation.
Consider a worker who elects $2,000 for a health FSA. Payroll spreads the election across the applicable pay periods, and the worker can seek reimbursement for eligible medical expenses, such as qualified out-of-pocket care. The tax effect depends on the employee's compensation, tax status, and payroll treatment, so an employer shouldn't promise a specific savings amount. The important operational point is that the election affects payroll before claims activity begins.
Health and dependent care accounts are different
A health FSA generally helps pay eligible medical, dental, and vision expenses. A dependent care FSA addresses eligible care expenses that allow the employee, and generally the employee's spouse where applicable, to work or seek work. The accounts shouldn't be combined in employee instructions because their limits, testing requirements, and timing rules differ.
The use-or-lose concept is central. An employee who elects more than they ultimately use may forfeit the unused amount unless the plan provides an available exception. A plan may offer a grace period, which can allow new expenses for up to 2 months and 15 days after the plan year ends, or a carryover feature. An employer may choose a carryover instead of a grace period, but it can't offer both under the same applicable arrangement. A run-out period is different. It gives employees time to submit claims for expenses already incurred during the plan year, rather than creating extra time to incur new expenses. These distinctions are outlined in guidance on the IRS use-or-lose rule.
Employees need this explained in plain language. “You have a balance” isn't enough. The message should identify what the balance can pay for, what documentation may be needed, and the actual date by which the expense must be incurred or the claim submitted.
IRS Rules and 2026 Contribution Limits You Need to Know
The most important 2026 update for health FSA administration is the employee salary-reduction limit. For plan years beginning in 2026, the health FSA limit is $3,400, up from $3,300 in 2025, and the maximum carryover is $680, according to Mercer's summary of the 2026 health FSA limits.
Dependent care rules require separate treatment. The 2026 dependent care FSA limit is $7,500 for most eligible filers, while the long-standing household ceiling remains $5,000 for married couples filing jointly or single filers, and $2,500 for married individuals filing separately. Employers should reconcile the plan design, payroll configuration, tax treatment, and employee materials before enrollment opens. The dependent care FSA limit reference also reinforces why administrators must not treat the dependent care account as just another health FSA.
| FSA Type | 2026 Limit | Key Administrative Notes |
|---|---|---|
| Health FSA | $3,400 | Employee salary-reduction limit for plan years beginning in 2026 |
| Health FSA carryover | $680 | Available only when the plan includes a carryover feature |
| Dependent care FSA | $7,500 | Separate dependent care rules apply |
| Dependent care household ceiling | $5,000 for joint or single filers, $2,500 for married filing separately | Coordinate household and tax filing rules |
Timing features require precise plan language
A grace period allows eligible new expenses after the plan year ends, for up to 2 months and 15 days. A run-out period only extends the time for submitting claims for expenses already incurred during the plan year. A carryover moves an allowed balance into the next plan year, subject to the plan's stated limit. These are different mechanics, and employee communications should label them clearly.
Dependent care FSAs also require annual nondiscrimination testing. Common tests address eligibility, contributions and benefits, owner concentration, and the 55% average benefits test. Proposed IRS guidance describes a safe harbor in which eligible non-highly compensated employee participation reaches at least 90% of the highly compensated employee rate, as discussed in Lockton's analysis of dependent care FSA discrimination testing.
Operationally, the 2026 changes mean more than replacing a number in a brochure. Update plan documents, payroll limits, enrollment forms, deduction logic, employee portals, onboarding materials, and manager talking points. Employers considering whether they can contribute to an FSA should also review the relevant employer FSA contribution considerations.
Setting Up Your FSA Program and Choosing a Vendor
A successful launch starts with plan design, not vendor shopping. Decide whether the company will offer a health FSA, a dependent care FSA, or both. Then define eligibility, the plan year, claim procedures, and whether the health FSA will use a grace period or carryover.
Build the design before comparing platforms
A practical setup sequence looks like this:
- Define the account scope. Separate medical reimbursement from dependent care reimbursement in every document and system.
- Choose the timing feature. Select a grace period or carryover after considering employee behavior, administrative preferences, and the company's risk tolerance.
- Document eligibility and elections. Make sure onboarding and qualifying life event processes match the plan terms.
- Map payroll deductions. Confirm how elections begin, stop, change, and reconcile.
- Set claim controls. Require the documentation and review steps needed before reimbursement.
Vendor evaluation should focus on operating capability rather than a polished demo. Ask how the administrator handles substantiation exceptions, missing documentation, debit card follow-up, rejected claims, balance visibility, employee support, plan amendments, reporting, and year-end reconciliation. A platform that processes routine claims quickly but leaves HR staff to resolve every exception may not reduce workload.
Compare the real cost of administration
Outsourced administration is often priced at about $5 per employee per month, or $60 per employee per year, while one industry estimate says employers avoid 7.65% in payroll taxes on employee FSA contributions. These figures should be evaluated together, not separately, using the Tax Policy Center's FSA overview as context. The net result depends on participation, payroll volume, contribution patterns, service fees, and the internal time required to manage the program.
Self-administration may appear cheaper, but it transfers the work to payroll and HR. Small employers should outsource when they lack dedicated benefits expertise, consistent claims controls, or reliable payroll and HRIS integration. A specialist third-party administrator can provide structured claims handling, while the employer still owns plan decisions and employee communication.
Before signing, test the integration with sample elections, payroll changes, terminations, and qualifying life events. Ask who owns each handoff. Ambiguous ownership is a bigger operational problem than a missing feature list.
The Surprising Truth About Substantiation and Forfeitures
An employee may have a fully automated FSA claim process and still forfeit money. Automation reduces uploads and manual reviews, but it can also remove the reminders that prompt employees to check balances, resolve claims, and use available funds.
An analysis of 3.2 million accounts found that workers who manually submitted at least one FSA expense were 13 percentage points less likely to forfeit funds and lost an average of $114 less than workers whose claims were auto-substantiated only, according to EBRI's analysis of manual FSA submissions and forfeitures.
Convenience can hide the account
Manual submission creates a useful check-in. Employees review the expense, locate documentation, see the remaining balance, and become aware of deadlines. An automated process can remove those prompts, leaving the account unnoticed until a transaction fails or the plan year ends.
Keep automated substantiation for transactions supported by reliable data. Pair it with balance reminders, claim-status notifications, eligible-expense guidance, and timely year-end messages. Employee communication timing is part of plan design, not an afterthought.
Behavioral insight: The easiest process isn't always the process that produces the best employee outcome.
Substantiation also serves a strict compliance purpose. A debit card swipe or receipt alone isn't necessarily enough. Reimbursement must have independent third-party documentation identifying the participant or dependent, service date, service or product description, provider or merchant, and amount. IRS guidance rejects shortcuts such as self-substantiation, sampling, or dollar-threshold exceptions, as detailed in FSA debit card substantiation rules.
A practical workflow combines both approaches. Automate routine claims when the available data supports substantiation, then give employees clear prompts when information is missing. Display balances and unresolved claims together, and explain how the FSA carryover limit works under the plan. The goal is accurate payment plus enough visibility to help employees use the benefit before funds are forfeited. EBRI's analysis also found that about one-third of accounts in its database were effectively use-it-or-lose-it, keeping forfeiture an active administration issue.
Common FSA Administration Pitfalls and How to Avoid Them
FSA problems usually start with an assigned task that no one owns clearly. A sound administration process connects plan rules, payroll, claims review, and employee behavior. The table below matches common failures with controls that work in daily operations.
| Pitfall | What goes wrong | Operational fix |
|---|---|---|
| Insufficient substantiation | The employer pays a claim based only on a swipe, vague receipt, or employee statement | Require documentation identifying the participant or dependent, service date, product or service, provider or merchant, and amount |
| Outdated annual limits | Payroll or enrollment materials use an old contribution cap | Review current rules before configuration and open enrollment |
| Unclear deadlines | Employees confuse the plan year, grace period, run-out period, and carryover | Publish a date-based calendar with separate labels for incurring and submitting expenses |
| Dependent care testing gaps | Census or eligibility data does not support nondiscrimination testing | Assign an owner and verify payroll census data before testing |
| Poor employee education | Workers learn an expense is ineligible only after purchase | Explain eligible categories, documentation rules, claim status, and balance use throughout the year |
A claim can sound medical while falling outside the plan's eligible expenses. Approving it without adequate review may require the employer to reverse the reimbursement and recover the amount. Rejecting it without an explanation makes the benefit feel arbitrary. Use a clear reason code, identify the missing information, and provide a defined resubmission path.
Substantiation is both an operational and compliance control. A debit card swipe or receipt may not provide enough support. Reimbursement documentation must identify the participant or dependent, service date, service or product description, provider or merchant, and amount. IRS guidance does not permit shortcuts such as self-substantiation, sampling, or dollar-threshold exceptions, as explained in FSA debit card substantiation rules.
Timing errors create another avoidable problem. A run-out period permits submission of an earlier expense, not incurring a new one. A carryover applies only if the plan includes it. Keep the plan document, portal, enrollment guide, payroll notices, and HR responses aligned. Explain the FSA carryover limit works under the plan in the same language employees see elsewhere.
A shared calendar reduces dependence on year-end intervention. Assign owners and completion dates for regulatory review, payroll testing, nondiscrimination testing, employee reminders, claim deadlines, and reconciliation checkpoints.
Best Practices for Smooth FSA Administration
Smooth administration comes from treating the plan as a recurring cycle. Each phase has a different purpose, and the communication that works during enrollment won't necessarily work at year-end.
Plan design
Start by writing the operational rules in plain language before the vendor configures the system. Decide which accounts to offer, who can participate, how elections change, and which timing feature applies. Keep health FSA and dependent care FSA rules visibly separate so employees don't transfer assumptions from one account to the other.
Enrollment
Open enrollment materials should show more than a contribution field. Explain the election decision, payroll deduction, eligible expense categories, documentation requirements, claim process, and relevant deadlines. Use a benefits meeting, written guide, portal prompts, and manager-ready answers rather than relying on one announcement.
Employees often need help estimating an election. The safest guidance encourages them to review predictable expenses without suggesting that every dollar should be committed. A cautious election can reduce forfeiture risk, while a low election may leave the employee paying eligible expenses outside the account.
Ongoing administration
Give employees a live view of balances, claim status, documentation requests, and available actions. Send reminders when a claim needs attention and at useful points before the plan deadline. The EBRI findings on manual submissions support a practical design principle: automated processing should still create opportunities for employees to notice and manage their accounts.
Build monthly or quarterly checks into the HR calendar. Compare payroll deductions with administrator records, review unresolved claims, confirm terminated employee handling, and monitor dependent care eligibility data. For qualifying life events, document the event, apply the plan's election-change rules, and verify that the change reaches payroll and the administrator consistently.
Year-end
Year-end communication should state what employees must do, by which date, and where to find their balance. Separate the deadline to incur an expense from the deadline to submit a claim. If the plan uses a carryover, explain what happens to the allowed balance. If it uses a grace period, explain the extra spending window and its limits.
Vendor support matters most when an exception appears. Require service-level expectations for claim questions, payroll discrepancies, documentation appeals, and year-end reconciliation. Technology reduces repetitive work, but accountable people resolve ambiguous cases.
How Benely Simplifies FSA Administration for Growing Companies
Growing companies often have enough employees to create meaningful FSA demand but not enough benefits staff to manage every exception internally. The practical need is coordination. Elections, payroll deductions, claims, substantiation, employee education, deadlines, and year-end reconciliation must follow the same plan rules.
Benely provides a centralized benefits platform that can connect FSA management with health plan enrollment, payroll connectivity, onboarding, and compliance tools. The platform supports automated enrollment, claims and substantiation workflows, reporting, and open enrollment tracking. Certified HR specialists add human guidance when a plan question doesn't fit a standard help article.
That combination addresses the operational gaps discussed above. A company can compare health plans, set benefits budgets, manage enrollment progress, and coordinate FSA processes in one environment rather than forcing HR to maintain disconnected spreadsheets and portals. Benely also helps employers benchmark benefits programs and offers access to thousands of health plans from major carriers, including Aetna, Kaiser, Anthem, Blue Shield, and UnitedHealthcare.
The value isn't automation for its own sake. A useful partner helps keep plan documents, payroll settings, employee communications, and compliance checkpoints aligned. It should also preserve employee visibility into balances and unresolved claims, because a frictionless claim process that hides forfeiture risk isn't a complete solution.
If your team is reviewing FSA plan design, updating systems for 2026, or dealing with recurring substantiation and deadline questions, a benefits specialist can help map the process before enrollment begins.
Benely connects benefits administration, payroll, onboarding, compliance tools, and FSA workflows for growing companies that need more control without adding unnecessary manual work. Visit Benely to review your benefits process, compare plan options, and request guidance for a more reliable FSA administration program.
