If you hire freelancers, drivers, or independent contractors, you've probably felt the tension: you'd like to help them get health coverage or save for retirement, but your lawyer has told you not to touch it. Offering benefits has long been treated as a red flag for worker misclassification — the kind of thing that turns a 1099 relationship into a W-2 one in the eyes of a state labor agency or the IRS, with back taxes and penalties attached.
That calculus is starting to change. In the past two years, four states — Utah, Tennessee, Alabama, and Georgia — have passed "portable benefits" laws that let businesses voluntarily contribute to a contractor's health, retirement, or paid-time-off account without that contribution being used as evidence of an employment relationship. West Virginia has since followed, and lawmakers in roughly a dozen more states introduced similar bills in the first half of 2026. A bipartisan federal package is also moving through Congress.
For any small business that relies on independent talent — a marketing agency staffed by freelance designers, a logistics company using owner-operator drivers, a home-services platform matching contractors with customers — this is one of the more consequential changes in worker-classification law in years. Here's what's actually in these laws, what they don't fix, and how to think about using them.
The Problem Portable Benefits Are Trying to Solve
The share of the U.S. workforce doing some form of independent or gig work has grown substantially over the past decade — one widely cited estimate puts it at over a third of workers by the early 2020s. Traditional benefits, though, are built around a single employer: your health insurance, 401(k) match, and paid leave all disappear the moment you leave that job. Independent workers who string together income from multiple clients get none of it, because no single company treats them as an employee.
The "benefits gap" is real, but the legal reason companies avoid closing it is more specific than indifference. Multi-factor tests for employee-versus-contractor status — used by the IRS, the Department of Labor, and every state labor agency — routinely list "provides benefits" as a factor pointing toward employment. A company that pays for a contractor's health insurance has historically handed a misclassification plaintiff (or auditor) a very easy argument. So even well-intentioned businesses have stayed away from it entirely.
Portable benefits laws attack that specific problem: they create a state-law safe harbor saying that a voluntary contribution to a contractor's benefit account, by itself, cannot be used to establish an employment relationship under state law.
How the State Laws Actually Work
The mechanics are similar across the four states that have passed laws so far, though the details vary:
- Utah (S.B. 233, 2023) was first, establishing that companies can fund portable benefit accounts for independent workers without those contributions being treated as evidence of employee status.
- Tennessee and Alabama (2025) followed with their own versions. Alabama's law (S.B. 86) went further than any other state, building in tax advantages on both sides: businesses can deduct 100% of their contributions as an ordinary business expense, and the contractor pays no state income tax on the value received.
- Georgia (H.B. 987, 2026) passed with bipartisan support and extends coverage to an estimated one million-plus independent workers in the state, making Georgia the fourth state with a working framework.
- West Virginia has since enacted its own version, and legislators in roughly a dozen additional states introduced bills in the 2026 session.
In practice, a business sets up (or contracts with a third-party administrator to manage) an account for each participating contractor, contributes a set amount per contract or per hour worked, and the contractor draws on that account for health premiums, retirement contributions, or other approved uses — carrying the balance with them if they stop working for that company. Contribution is voluntary and doesn't change the terms of the underlying contractor relationship: no minimum hours, no exclusivity, no schedule control.
What These Laws Don't Change
This is the part easy to miss, and the part that matters most for compliance.
The safe harbor is state law only. It affects how a state agency evaluates worker status for state purposes — unemployment insurance, workers' comp, state wage-and-hour law. It does not bind the IRS or the U.S. Department of Labor. Federal classification tests (the economic-realities test under the FLSA, the common-law test the IRS uses for employment tax purposes) are unchanged by any of these state statutes. A company operating in Alabama can rely on the state safe harbor for state-law purposes and still face a federal misclassification claim if other facts — control over schedule, exclusivity, integration into the business — point toward employee status.
The safe harbor isn't a blanket shield. Contributing to a benefits account doesn't override every other factor a court or agency will look at. If your contractors are, in substance, functioning like employees — set hours, company equipment, no ability to work for competitors — a benefits contribution alone won't rescue that classification. Portable benefits remove one specific risk factor; they don't launder an otherwise-misclassified relationship.
Coverage is inconsistent across states. A national contractor workforce means dealing with a state-by-state patchwork: what's protected in Georgia may carry no such protection in a state without a law yet. Labor advocates, including the Economic Policy Institute, have also raised a structural concern from the other direction — that portable benefits proposals can function as a pro-employer alternative to full employee reclassification, giving companies a way to offer a partial safety net while continuing to avoid the costs (overtime, unemployment insurance, workers' comp) that come with employee status. Whether that trade-off is good for a given worker depends heavily on what they'd otherwise have access to.
Should Your Business Use One of These Programs?
If you're in a state with a portable benefits law (or your contractors are), a few practical questions are worth working through before setting one up:
- Is your contractor relationship actually defensible on the merits? Run through your state's and the federal economic-realities test first. A portable benefits program is a nice-to-have on top of solid classification — not a substitute for it.
- What's the tax treatment in your state? Alabama's full deductibility is unusually generous; other states' laws don't yet spell out the tax side as clearly. Confirm before you assume a contribution is a clean business deduction.
- Who administers the account? Most companies use a third-party benefits administrator rather than building this in-house — check what happens to unused contributions if a contractor leaves and whether the administrator's platform integrates with your existing bookkeeping.
- How will you record it? These contributions are a real, recurring business expense that needs its own account in your books, separate from contractor payments themselves, so you can see the true cost of your contractor workforce and substantiate the deduction if you're ever audited.
Keep Your Books Ready for What Comes Next
Whether you're funding portable benefit accounts for a fleet of drivers or just paying a handful of freelance contractors, clean separation between contractor payments, benefit contributions, and your own payroll is what keeps you audit-ready if a classification question ever comes up. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — every contractor payment and benefit contribution is a plain-text entry you can trace, diff, and audit, with no black-box software standing between you and your books. Get started for free and see why developers and finance-savvy business owners are switching to plain-text accounting.