How does Alabama’s state worker classification test work in 2026?

Marcus is a Birmingham-based software developer. A 35-person SaaS startup hires him on 1099 in March 2026 at $7,500 a month. He works from home, uses his own laptop, but joins the daily Slack standup, follows the sprint board, and bills only this one client. By December the Alabama Department of Labor audit is open. Marcus passes 4 of 20 factors as contractor. He is an employee for unemployment. He is also an employee for workers’ comp under the right-of-control test, because the startup’s engineering lead reviews his pull requests.

Three tests, three findings, three separate bills. Plan classification on day zero with all three tests in mind.

Latoya is a sales rep based in Huntsville. A 90-employee industrial-equipment dealer pays her on a 30% commission as a 1099 contractor. She uses the company CRM, attends the Monday sales meeting, follows the territory map the VP of Sales redrew last quarter, and earns no income from any other source. She passes 5 of 20 factors. The first 10 (behavioural control) lean almost entirely toward employee. Calling her a contractor cost the dealer roughly $24,000 in back FICA, SUTA, and workers’ comp premium for one year of audit lookback, before penalties.

Teamed’s Contractor Classifier walks the 20 factors and returns a confidence score with the auditable rationale. The same checklist the auditor uses. The output goes in your file.

Jamal handles gig-style ops contracts for a Mobile logistics broker. He drops by the warehouse two mornings a week, works the rest from coffee shops, sets his own routes, but takes daily routing instructions from the dispatcher and only takes work from this one client. Pass the 20-factor test? Borderline. Pass the right-of-control test? No. The dispatcher’s daily instructions are the marker of employment.

Jamal slips and breaks his wrist unloading a pallet six months in. There is no workers’ comp policy. The broker now pays the medical bill, the wage replacement, and loses the statutory immunity that would have capped the claim. A single uncovered injury can blow past six figures.

What this costs an employer who gets it wrong

• Missed premium, plus penalty and interest, back to the start of the engagement.
• Personal liability for the injury itself, if the worker was hurt on the job during the look-back and was never on a policy.
• Loss of statutory immunity from civil suit, because the workers’ comp bargain (premium for tort immunity) was never paid.

Teamed’s US payroll books workers’ comp on every Alabama hire automatically, with the right risk class and the right premium. The classification answer is the same across all three Alabama tests because the worker is on W-2 from day one.

Three conditions, all required:

1. Reasonable basis for the contractor treatment. Reliance on a prior IRS or Alabama Department of Labor audit, a court precedent, industry practice, or written advice from a qualified tax adviser. Any of the four qualifies.
2. Consistent 1099 reporting every year, with no W-2 issued to the same worker for the same role.
3. Consistent treatment of similar workers as contractors. No mixing of W-2 and 1099 for the same job description.

A Birmingham marketing agency relied on its CPA’s written advice that copywriters were contractors. The agency paid Marcus and three other writers on 1099 for two years. The IRS audit opens. Section 530 covers the federal payroll tax bill. The agency keeps the $18,000 in back FICA the auditor wanted.

What the safe harbor does not cover

Section 530 protects federal payroll tax. It does not protect FLSA back wages, it does not protect workers’ comp claims, and it does not bind a private misclassification lawsuit brought by Marcus himself. The IRS audit goes away. The FLSA double-damages action filed three months later does not. The workers’ comp claim for the wrist injury does not.

Before SB86, the honest answer to "can we offer this contractor health benefits without re-classifying them" was no, not really. Paying for health cover or retirement risked tipping the 20-factor analysis toward employee under the integration and continuing-relationship factors. SB86 severs that link.

Take Jamal again. The Mobile broker wants to keep him as a genuine 1099 contractor but wants to fund a basic disability policy after the wrist incident. From 31 December 2025 they can route the contribution through a Portable Benefit Account in Jamal’s name. The broker deducts the contribution. Jamal owns the account and can take it to the next client. The Alabama Department of Labor cannot point to the contribution as evidence of employment.

How the accounts work

Voluntary on both sides. The hiring party may offer, the contractor may opt in or out, and payroll-style withholding from invoices into the account works under a written agreement the contractor can revoke at any time.

Walk through Marcus, the Birmingham developer, three years in. The 35-person startup paid him $60,000 a year as a 1099. Audit lands on 1 March 2029, looking back to 2026. Marcus worked roughly 8 hours of overtime every week.

The audit is one story. The litigation is the next. Marcus joins a private FLSA suit a year after the audit. He recovers back wages, overtime, liquidated damages, and his attorney fees, which the statute makes the employer pay. Plaintiff-side firms in Alabama track the audit pattern and follow with civil action.

Why "reasonable basis" does not cap the downside

Section 530 kills the federal payroll tax bill. It leaves the other four columns standing. The FLSA back wages and double damages survive, the workers’ comp injury claim survives, and Marcus’s private right of action survives. Plan classification on day zero with the test the auditor will use, not with optimistic adviser language.

Teamed’s payroll books every Alabama hire correctly from day one. Statutory employer cost (FICA, FUTA, SUTA, workers’ comp premium) passes through at cost, itemised on the invoice. No markup on statutory cost. You see every line. Auditable from month one.

The federal proposal matters because FLSA exposure is one of the five stacked liability columns on the previous page. If the proposed rule lands, the federal threshold for finding a worker is an "employee" for FLSA overtime tightens slightly compared to the 2024 rule.

The state Alabama test runs on its own track. A worker who is an employee for Alabama unemployment compensation can still be analysed under the federal economic-reality test for FLSA and reach a different conclusion at the edges.

What this means for an Alabama hire

For most full-time-equivalent roles, the answer is the same on every test: employee. The divergence sits in the edge cases. A highly-specialised consultant who works from home, uses their own tools, sets their own hours, and bills by deliverable passes 20-factor and passes economic-reality. The role that fails one test usually fails the others too.

Where the tests diverge, the conservative answer is the one with the broader coverage. Usually "employee".

If the federal rule lands later in 2026, Teamed’s in-house payroll specialists reprice the federal FLSA exposure on every Alabama hire and surface the change to clients with affected workers. No new contract. The analysis updates in the platform.

What an Alabama engagement through Teamed looks like, day to day:

• Day 0. The role goes through the Contractor Classifier. The tool walks all 20 factors, returns a confidence score, and flags any factor that pushes the role toward employee. High-confidence contractor passes engage on 1099. Anything else engages through Teamed’s US entity (Teamed US Inc., Delaware) as W-2 from day one.
• Day 1, EOR path. Teamed’s US entity is the legal employer of record. We onboard the worker with Form A-4 (Alabama withholding), federal W-4, Form I-9, and the local occupational-tax certificate if relevant. Workers’ comp premium gets booked automatically at the right Alabama risk class.
• Day 1, contractor path. The engagement runs on a Teamed contractor agreement that documents the 20-factor analysis at the point of hire. If the contractor wants to join Alabama’s Portable Benefits Act programme from 31 December 2025, the hiring party can contribute through the same platform without affecting classification.
• Ongoing. All federal and state filings run on cadence. Multi-state day ledger maintained for any worker who travels. Quarterly classification review surfaces any role that has drifted toward employee since hire, before the auditor finds it.
• If a role changes. A contractor who needs to convert to W-2 keeps their record. Their Portable Benefit Account stays in their name. The same platform onboards them as an EOR employee. One continuous record for the worker. A clean classification reset for the hiring party.

Behind the platform sits a named country specialist for the United States and an in-house legal specialist for state-level employment matters who tracks Alabama case law and audit patterns. When something looks borderline on the 20-factor test, you message the same person. No support tickets. No chatbot triage.

Contractor onboarding, EOR payroll, and entity graduation all live on one platform. A US contractor who converts to employment in Alabama keeps their record. The same worker can graduate from EOR to your own Delaware C-corp without changing system.

Pricing is one number per employee per month, in any currency you pay us in. No FX mark-up. Statutory employer cost (FICA, FUTA, Alabama SUTA, workers’ comp premium) passes through at cost, itemised on every invoice. No setup fees. No exit fees.

When EOR is the right call (and when it isn’t)

EOR works while you’re testing the Alabama market, ramping a small remote team, or running a handful of W-2 hires alongside contractor relationships you want to preserve.

Once you have 6 or more Alabama employees and predictable hiring ahead, the maths of your own US entity starts to win. Teamed’s Crossover Calculator tells you the month the model stops being right. We graduate clients to their own entity when the spreadsheet says it’s time. EOR is the right hiring model, until it isn’t.