How does Virginia worker classification actually work?

Priya is a data analyst in McLean, engaged on a 1099. She uses the client's laptop and analytics platform, joins the daily sprint call, bills only this one client, and works the hours the team lead sets. Run those facts through the VEC's 20-factor guide and she's an employee for unemployment tax. Run the same facts through the Department of Taxation's IRS guidelines and you reach the same answer. The 1099 contract changes nothing.

The presumption is the fault line employers miss. In Texas or many other common-law states the auditor starts neutral and weighs the facts. In Virginia, the Department of Taxation starts with the assumption you got it wrong. The burden flips. A worker you've treated as a 1099 for three years is an employee under Virginia law until you prove the IRS factors point the other way. Compare the approach in Maryland, which has a separate statutory presumption for wage-and-hour that adds yet another track.

James is a compliance consultant in Richmond, paid by the project on a 1099. He holds several clients, uses his own credentials and home office, sets his own hours, and bills by deliverable. He passes most of the 20 factors clearly. The role that fails on the first ten, the behavioural-control bucket, is the one Virginia reclassifies first and on which the civil penalty clock starts.

A genuine contractor reads the opposite way on most of these: own hours, own tools, several clients, paid by the project, free to subcontract. The role that fails on the first ten, the behavioural-control bucket, is the one Virginia reclassifies first. Teamed's Contractor Classifier walks the same 20 factors the auditor uses and records the rationale in your file.

The presumption has real procedural bite. In a typical audit in a neutral common-law state, the auditor builds the case that the worker is an employee. In Virginia, under Va. Code 58.1-1900, you come to the table already presumed wrong. Well-documented factor analysis, filed consistently, is your rebuttal.

This is the multi-state trap. A developer engaged clean as a 1099 in Texas keeps the same role after the company opens a Richmond office. In Texas there is no presumption and no prong about usual business. In Virginia the worker starts presumed as your employee the moment they perform services for remuneration, and three separate agencies can open a file. Teamed's Contractor Classifier runs the test that matches each engagement's state, so the Texas answer and the Virginia answer come from the right rulebook every time.

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

Virginia gives no state safe harbour beyond the federal Section 530 shield, which can cap the federal payroll-tax piece if you filed 1099s consistently and had a reasonable basis. It does nothing for the FLSA back wages, the Virginia civil penalty, or a worker's own lawsuit. Compare the route in Texas, where there is no state civil penalty for private engagements and no statutory presumption. In Virginia, the cleanest version of this bill is the one you never trigger, because the role went on W-2 from day one.

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 on the federal payroll-tax track.

The Virginia presumption runs on a different channel. Even where Section 530 protects the federal FICA and FUTA piece, the Dept of Taxation can still impose its civil penalty if the IRS factor analysis, applied under Va. Code 58.1-1900, points to employee. Document the factor analysis at the point of hire. That documentation is your rebuttal to the presumption, not the 1099 itself.

The honest read for most knowledge-work roles is the same on every test: employee. The divergence sits in genuine edge cases: the specialist who works from home on their own kit, sets their own hours, bills by deliverable, and serves several clients. That worker clears the common-law 20-factor test and the FLSA economic-reality test together. The role that fails one usually fails the others, and in Virginia the presumption means that outcome is the starting assumption, not the end of an audit.

Real HR and legal experts handle your Virginia classification calls and know the VEC 20-factor test, the Dept of Taxation's presumption, 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 common-law analysis at the point of hire. For a role that fails it, Teamed US Inc. is your W-2 employer of record from day one, with Virginia unemployment tax, federal FICA and FUTA, and Virginia income-tax withholding all booked at the correct rate. A quarterly review catches any contractor whose role has drifted toward employee before the Department of Taxation does.

Contractor onboarding, EOR payroll, and entity graduation live on one platform. A Virginia 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 Virginia hire, until it isn't.