How do you hire contractors in Arizona in 2026?

David is a software developer in Phoenix. He has three clients, sets his own hours, works from a co-working space he pays for himself, and bills by deliverable. He invoices a startup as a 1099 contractor. The startup pays no employer tax and no benefits. That is the deal a contractor relationship is meant to be. The risk is that Arizona reads the working arrangement, not the invoice, across the 20 common-law factors.

The classification is a tax-status call, and in Arizona four tracks can reach it: the Department of Economic Security for unemployment, the Department of Revenue for income-tax withholding, the IRS for federal payroll, and the US Department of Labor for FLSA overtime. Workers' comp adds a fifth track via the Industrial Commission of Arizona. Run the Contractor Classifier on every engagement before you sign. Compare the W-2 route on the Arizona worker-classification page, the Arizona wage and overtime rules, and the US hiring overview.

The 20 factors are documented in IRS Publication 15-A and reflect a balance: a worker who scores most factors toward independence is usually a contractor, and one who scores toward control is usually an employee. Arizona's Department of Economic Security applies the same test for unemployment, and the Department of Revenue follows the federal employee definition for withholding.

That alignment cuts both ways. A genuine contractor who clears the IRS common-law test and carries a valid DIBS typically clears Arizona DES too. A relabelled employee who fails the IRS test fails on every track at once: back unemployment tax, back withholding, back FICA, and IRC 3509 together. Arizona has no separate state civil per-worker-per-day misclassification penalty, but wilful misrepresentation in unemployment matters is a Class VI Felony under ARS 23-785, a different category of exposure entirely. See how a strict-ABC state reaches the opposite result on the California worker-classification page.

Walk a $60,000 Arizona contractor through a three-year audit and the tracks stack:

The audit usually opens itself: the contractor files for unemployment after the engagement ends, the Department of Economic Security finds no wage record, and the reclassification reaches back over the period. Because Arizona uses the IRS test, a federal finding tends to carry the state one with it. The full state cost picture is on the Arizona worker-classification page and the Arizona hiring overview.

Section 530 of the Revenue Act of 1978 needs three things, all of them: a reasonable basis for the contractor call, consistent treatment of every worker in the role, and timely 1099 filing every year. Miss one and the shield drops. For an Arizona employer, Section 530 is more useful than in California, because Arizona does not run a separate ABC test that overrides it. But the DIBS declaration and Section 530 each have their own requirements; satisfying one does not automatically satisfy the other.

The state-level DIBS shifts the burden to Arizona DES for unemployment and withholding only. It has no effect on a federal Section 530 analysis or on an FLSA challenge. And it does not cover workers' comp at all. Both defences need consistent practice, not just signed paper.

The EOR point is the one that catches people mid-fix. If you move a contractor who looks like an employee onto an employer of record on 1 June, you have not cured the prior period of 1099 treatment. You have made the employment explicit, and the federal lookback on the earlier period stays open. An EOR is the right answer when the engagement is honestly employment from day one, not a retroactive patch.

1. Run the 20-factor test first. Weigh behavioural control, financial control, and the relationship before you sign. The Contractor Classifier walks the factors and records the rationale in your file.
2. Execute the DIBS declaration. If the contractor meets at least 6 of the 10 DIBS factors under ARS 23-1601, sign it. The burden of proof at a DES audit flips to the auditor. Run the engagement consistent with the declaration or the presumption is voided.
3. Collect Form W-9 before the first payment. No W-9, no first payment, or you fall into 24 percent backup withholding.
4. Sign the workers' comp written agreement. If there is any risk of on-the-job injury, sign the separate written agreement under ARS 23-902. The required disclosure that the contractor is not entitled to workers' comp benefits must appear verbatim or the presumption does not trigger.
5. Pay against invoices, through accounts payable, not payroll. Keep the audit trail clean.
6. File Form 1099-NEC by 31 January for any contractor paid $2,000 or more in the year. The One Big Beautiful Bill Act raised that threshold from $600 for payments made in 2026 onward.

For a genuine Arizona contractor this is the whole job. For a role that fails the 20-factor test, onboarding it as a 1099 is the start of the liability, not the end of it. The DIBS is not a substitute for substance; it is a tool for documenting substance that already exists.

Real HR and legal experts run your Arizona classification calls and know the 20-factor test, the DIBS declaration, the workers' comp written agreement, and the federal stack by heart. An actual person, not a chatbot or a pooled queue. The Guard review, the Protect engagement, the W-2 onboarding, and the audit-ready file all run on one platform.

When the engagement is employment in substance, Teamed US Inc. is the W-2 employer of record at $599 per employee per month flat, with zero FX mark-up and statutory employer cost passes through at cost, itemised. There is no setup fee and no exit fee. An Arizona contractor who converts to W-2 keeps their record, and that same worker can graduate from EOR to your own US entity once the volume crossover lands, without switching systems. Use the Crossover Calculator to find the month it flips, or read the Graduation Model. EOR is the right model for a first Arizona hire, until it isn't.