How we think about Section 530 relief in an IRS worker audit
An IRS employment tax examiner has just told you the people you pay on 1099s look like employees. Before anyone argues about who controls the work, there's a question that comes first, and it's the one that can end the case: does Section 530 relief apply? Section 530 is a 1978 statute, part of the Revenue Act of 1978, and it sits outside the Internal Revenue Code. It doesn't decide whether your workers are employees. It decides whether you owe federal employment taxes on them anyway.
In our practice, Section 530 is the first thing we look at when a worker classification audit opens, because it can terminate the employment tax liability for the periods under audit and for future periods, so long as its requirements keep being met, without the business ever conceding that anyone is an employee.
One scope note for Oklahoma readers. Everything here is federal. Oklahoma's own agencies apply their own classification tests for their own programs, and those tests are separate from Section 530 and may come out differently.
Why the examiner tests Section 530 relief before anything else
The IRS's own guidance tells examiners to explore Section 530 first, even if the taxpayer never raises it. It isn't necessary for the business to claim relief for it to apply. The examiner is also supposed to hand you Publication 1976, the IRS's short explainer on Section 530, at the start of a worker classification audit, and to provide it whenever Section 530 is considered, even where it turns out not to apply.
So the order of operations in a real audit runs backward from how owners expect it. Owners show up ready to argue control: who sets the hours and who owns the tools. The examiner starts somewhere else, with three requirements tested in sequence, and the sequence matters because failing an early one ends the discussion for that worker or that year before the later ones are reached.
Requirement one: reporting consistency
The first question is paperwork. You must have filed all required federal returns, including information returns such as Forms 1099, before the employment tax examination began, and those filings must be consistent with treating each worker as a non-employee.
Relief isn't available for any year, and for any worker, for whom you didn't file the required information returns. It's not a business-wide pass or fail. It's tested worker by worker and year by year.
In practice, the examiner's opening request is usually a list of every 1099 payee for every year under audit, matched against the forms actually filed. A crew of twelve where eleven got 1099s and one didn't, or a year where the forms never went out, pulls that worker or that year out of relief before anyone discusses how the work was supervised.
One softening point: if no information return requirement existed for a payment, such as one under the filing threshold, relief won't be denied because a return wasn't filed.
The IRS's web page says the returns must have been "timely filed," and the publication says "prior to the commencement" of the examination. Filing a stack of late 1099s after the examiner's letter arrives doesn't repair the prior years.
Requirement two: substantive consistency
Next the examiner asks whether you, or any predecessor business, treated the worker, or any worker holding a substantially similar position, as an employee at any time after December 31, 1977. If you did, relief isn't available for that position.
This is where closely held businesses most often lose. The pattern we see is a crew with one W-2 lead and nine 1099 workers doing the same job, or a shop that put its first two technicians on payroll years ago and then switched to 1099s as it grew. The publication says plainly that if you treated similar workers as employees, the provision isn't available.
The IRS describes "substantially similar position" as a facts and circumstances determination, and it says similar job titles or categories alone aren't enough. That cuts both ways. A business can't escape the rule by retitling the W-2 worker, and it isn't sunk just because two roles share a label on an org chart.
Requirement three: reasonable basis
Only after the two consistency tests are passed does the examiner reach the question most owners thought the audit was about: whether you had a reasonable basis for treating these workers as independent contractors. Without one, you don't meet the relief requirements.
There are three safe havens, and then a catch-all the IRS says is to be liberally construed in favor of the taxpayer. The safe havens each carry conditions that owners tend to assume away.
Safe haven: judicial precedent or an IRS ruling
You may rely on a court case about federal taxes, or on a ruling issued to you by the IRS. The facts in the case must be similar to your situation. One case is enough to establish a precedent that creates a safe haven.
Two limits. The precedent or ruling must have been in existence when you began treating the workers as non-employees. And state court decisions and rulings of agencies other than the IRS don't count as judicial precedent for this purpose. An Oklahoma agency decision that your workers are contractors for its program may help under the catch-all discussed below, but it doesn't fit inside this safe haven.
Safe haven: a prior IRS audit
You may rely on an earlier IRS audit of your business conducted at a time when you treated similar workers as independent contractors and the IRS didn't reclassify them. The date of that audit matters. For an audit commenced after December 31, 1996, you may rely on it only if it included an examination, for employment tax purposes, of whether the individual involved, or any individual in a substantially similar position, should be treated as your employee. For audits before January 1, 1997, the audit didn't need to be an employment tax audit, so long as it produced no assessment attributable to your treatment of substantially similar workers.
This safe haven is narrower than the folklore around it. A prior income tax audit that happened to leave the 1099s alone generally won't do if it falls under the post-1996 rule.
Safe haven: industry practice
You may rely on the fact that you knew, and can substantiate, that a significant segment of your industry treated similar workers as independent contractors. The IRS adds that the practice must be long-standing and recognized, and it defines an industry narrowly: generally, firms in the same geographic or metropolitan area that provide the same product or service and compete for the same customers.
"Substantiate" is doing real work in that sentence. "Everyone in the oilfield does it this way" is a statement of belief; substantiation is evidence of what competitors in your market actually did, in a form the examiner can evaluate. We don't offer a percentage for what counts as a significant segment, because the IRS's published Section 530 materials don't state one.
The catch-all: some other reasonable basis
A business that fails all three safe havens may still get relief if it can show it relied on some other reasonable basis. The IRS's examples include advice of an attorney or accountant who knew the facts about your business; state law, non-tax federal law, and other determinations; a prior audit of a predecessor; a private letter ruling or technical advice to a predecessor; or good faith.
The advice example carries a condition that's easy to miss until an audit: the adviser needs to have known the facts about your business. A CPA's general comment that contractors are fine doesn't carry the weight of advice given with knowledge of how your crews actually work.
The timing rule that runs underneath all of it
Whatever basis you claim, you must have relied on it at the time the employment decisions were being made for the periods at issue. The IRS says the statute doesn't allow ex post facto justification. Finding a favorable court case after the audit letter arrives doesn't supply a reasonable basis for the years already behind you.
Who has to prove what
The burden starts with you, but it moves. You must establish a prima facie case, meaning a showing that on its face supports the position, that it was reasonable not to treat the individual as an employee, and you must cooperate fully with reasonable requests from the examiner. Once you've cooperated fully, the burden of proof shifts to the IRS on the reporting consistency requirement, the substantive consistency requirement and the three safe havens.
That shift is a genuine advantage, and it's conditioned on cooperation. Stonewalling the document request to protect the control argument can cost you the burden shift on the Section 530 argument, which was probably the better argument.
What relief does, and what it doesn't
If the requirements are met, you won't owe federal employment taxes for those workers for the periods under audit, and the relief carries into future periods as long as the requirements continue to be met, which the IRS describes as extending into perpetuity unless there's a material change in the facts surrounding the relationship. Section 530(e), as the IRS paraphrases it, means a worker doesn't have to be an employee of the business for relief to apply, and you don't have to concede or agree that the workers are employees to get it.
Now the limits, which are real.
- It doesn't decide status. Section 530 relief doesn't determine that a worker is an independent contractor. The worker can still be found to be an employee through another route, such as a Form SS-8 determination.
- It doesn't protect the worker. Relief doesn't extend to the worker, who may still be liable for the employee share of FICA. A worker determined to be an employee isn't liable for self-employment tax but owes the employee share of FICA, reported on Form 8919.
- It's only about classification. Section 530 applies to worker classification issues, not wage issues. A dispute over whether a payment to an admitted employee counts as wages is a different fight.
- It excludes certain third-party technical arrangements. The relief doesn't apply to third-party arrangements for engineers, designers, drafters, computer programmers, systems analysts and similarly skilled workers, which matters for staffing and consulting firms.
- It doesn't apply to federal agencies.
Nothing about relief makes the underlying relationship cleaner. A business that holds it can still face a worker's SS-8 request, and the facts can still change once it starts scheduling shifts and supplying equipment. It can also lose relief going forward through its own actions, and that one deserves its own section.
The sequencing decision between Section 530 and the VCSP
The reflex when an owner first hears "your crew looks like employees" is to move everyone to W-2. The IRS's guidance is explicit that a business with relief may continue reporting payments on Forms 1099, and that reporting on Forms W-2 would cause the employer to lose relief for future years. The fix can forfeit the defense.
So the sequencing is a decision, not a reflex. Think of it as two doors. Behind one is Section 530: you keep the 1099 treatment and hold the relief for the open years and going forward, while the status question stays technically open and the facts have to stay consistent. Behind the other is the Voluntary Classification Settlement Program, where you prospectively reclassify the workers as employees under a settlement with the IRS on terms that article walks through, and the relationship becomes a payroll relationship from then on.
Which door makes sense depends on facts that have to be mapped before anything is filed. The first is whether the business passes reporting consistency for every worker and every year, or has a missing 1099 year that takes Section 530 off the table for that period anyway. The second is whether a W-2 lead in the crew fails substantive consistency. Apart from the audit, the owner may also simply want these people as employees for reasons that have nothing to do with the IRS.
Timing interacts with the audit itself. The VCSP has its own eligibility conditions, including conditions about being under examination, which that article walks through. A business that abandons Section 530 by converting to W-2 while the audit is open, and then finds it can't use the VCSP either, has given up the one defense it had for the open years. That's the scenario we most want to prevent.
Underneath all of it sits the employment tax exposure itself. If the audit ends in a reclassification without relief, the assessment lands on the business, and if the business can't pay, the responsible person rules under IRC §6672 can reach individuals for the trust fund portion. Section 530 is attractive precisely because, when it holds, it ends that liability rather than reducing it.
If the file holds together, the audit may end at the Section 530 stage without a control analysis ever being written up. If it has a hole, you want to know which requirement the hole is in, because that tells you whether the defense survives for some workers or some years, and whether the better path is the settlement program.
The Section 530 question tends to get decided in the first records exchange of an audit. If you've received an IRS employment tax examination notice, or you're looking at a 1099 crew and wondering how it would hold up, reach us through our contact page or our Oklahoma City office. Sorting out the defense before a single form changes is almost always less expensive than repairing a choice made in a hurry.
Sources
This article is general information about Oklahoma, Texas, and federal law, not legal advice, and it does not create an attorney-client relationship. Facts matter; talk to a lawyer about yours.