How does South Dakota worker classification actually work?

Ravi consults for a Sioux Falls fintech firm on a 1099. He sets his own hours and works remotely, but he attends the weekly product meeting, follows the sprint process, and bills only this one client. Run those facts through the DLR's two-prong test and he fails the second prong, he's not independently established in a business. Run the same facts through the IRS 20-factor test and the behavioural bucket points to employee. There was never just one question to get right.

The fault line most out-of-state employers miss is the two-prong structure. South Dakota does not presume contractor status the way Texas does informally. SDCL 61-1-11 creates an explicit presumption of employment, and the employer carries the burden to prove both prongs. No income tax means there's no withholding discrepancy to surface a bad classification early. The reemployment assistance track is typically the one that opens the file, usually when the worker files for benefits after the engagement ends.

Maria is a social media manager in Rapid City, paid monthly on a 1099. She uses the company content calendar, joins the Monday strategy call, works the territory the marketing director set, and earns nothing from any other client. She clears almost none of the 20 factors on the behavioural side, and she has no independently established business. The contract calling her a contractor changes none of that under SDCL 61-1-11.

A genuine contractor reads the opposite way on most of these: own hours, own tools, several clients, paid by the project, free to subcontract. Under SDCL 61-1-11 the second prong adds an extra bar: even a worker who passes the control test is still an employee if they don't run an independently established trade or business. That double gate is what makes South Dakota's test tighter than it looks on the surface. Teamed's Contractor Classifier walks both the SDCL 61-1-11 prongs and the IRS 20-factor test and records the rationale in your file.

The control test reflects a balance. A contractor who scores most of the 20 factors toward independence and who genuinely runs their own business is probably a contractor. Add facts that point to control or exclusivity and the answer shifts. There is no single fact that ends the conversation, but there are two prongs, both of which must be cleared.

This is the conversion trap multi-state employers walk into. A developer engaged as a clean 1099 in South Dakota keeps the same role after the company opens a small office in California or New Jersey and re-engages them at that address. In a strict ABC state the prong that asks about your usual business fails from day one, no matter how the South Dakota engagement looked. The test changed because the worker's location changed. Teamed's Contractor Classifier runs the test that matches each engagement's state, so the South Dakota answer and the California answer come from the right rulebook each time. Compare the common-law arc in Nebraska, another Plains state where the same federal tracks apply on top of the state test.

Walk a $90,000 contractor through a three-year audit. The tracks stack.

South Dakota gives no state safe harbour of its own, because there's no state income-tax track and the reemployment assistance track carries no reasonable-basis shield. The federal Section 530 safe harbour can still cap the federal payroll-tax piece if you filed 1099s consistently and had a reasonable basis. It does nothing for the FLSA back wages or for a worker's own lawsuit.

Three conditions carry Section 530, all required: a reasonable basis for the contractor treatment (a prior audit, a court ruling, industry practice, or written advice from a qualified adviser), consistent 1099 filing every year, and consistent treatment of every worker in the same role. Miss one and the shield drops.

South Dakota also has a digital-platform carve-out. Under SDCL 61-1-11.1, a worker who connects to clients through a delivery facilitation platform is not that platform's employee for reemployment assistance when a set of statutory conditions is met: the worker controls their schedule, bears their own operating costs, and is paid per transaction rather than by time. Rideshare and on-demand delivery are the clear cases. It answers only the South Dakota reemployment assistance question and does nothing to the IRS or FLSA tracks running in parallel.

The honest read for most knowledge-work roles is the same on every test: employee. The genuine edge case is the specialist who works on their own kit, sets their own hours, bills by deliverable, and serves several clients across several states. That worker clears both prongs of SDCL 61-1-11 and the FLSA economic-reality test together. The role that fails one usually fails the others. Teamed's Contractor Classifier runs the full analysis and records why the call was made.

Real HR and legal experts handle your South Dakota classification calls and know the SDCL 61-1-11 two-prong test, the DLR presumption of employment, and the FLSA economic-reality line by heart. An actual person, not a chatbot or a pooled queue. There is no setup fee and no exit fee, and statutory employer cost passes through at cost, itemised on every invoice.

For a genuine contractor, the engagement runs on a Teamed agreement that records the SDCL 61-1-11 analysis at the point of hire. For a role that fails either prong, Teamed US Inc. is your W-2 employer of record from day one, with South Dakota reemployment assistance tax, federal FICA and FUTA all booked at the correct rate. A quarterly review catches any contractor whose role has drifted toward employee before the DLR does.

Contractor onboarding, EOR payroll and entity graduation live on one platform. A South Dakota contractor who converts to W-2 keeps their record, and that same employee can graduate from EOR to your own US entity without switching systems. Use the Crossover Calculator to see the month the model flips. EOR is the right model for a first South Dakota hire, until it isn't.