Why the two consistency tests deserve their own audit project
Section 530 relief has three requirements, but the two consistency tests are unusually document-driven. Reporting consistency asks what federal returns were filed for each worker and period. Substantive consistency asks how the business and any predecessor treated workers in substantially similar positions. Neither question is answered by a current independent-contractor agreement or by management’s general belief that “we have always used freelancers.”
Because the evidence lives in different systems, run a separate consistency project before writing the relief narrative. Accounts payable can show who was paid. Tax files can show which Forms 1099 were filed and corrected. Payroll can identify people doing similar work as employees. HR and operations can explain whether similar titles actually meant similar functions. Starting with this reconciliation is more valuable than immediately drafting a legal memo because it surfaces gaps that a polished memo cannot cure.
Reporting consistency starts with whether an information return was actually required
The IRS explains that reporting consistency requires all required federal tax returns for the period to be filed on a basis consistent with the taxpayer’s good-faith treatment of the individual as a nonemployee. In many small-business cases, the relevant document is Form 1099-NEC. But the first question is whether a return was required under the rules applicable to that year and payment, not whether the business has a 1099 for every person ever described as a contractor.
Build the population from the general ledger and payment system rather than from the year-end 1099 file alone. Then determine which payments were reportable, whether the return was filed, and whether corrected filings exist. This catches the most dangerous blind spot: a worker omitted from the tax-filing folder because the filing itself was missed. It also prevents overstatement when no information-return obligation existed for a particular payment.
Good-faith filing errors are not the same as never filing the required return
Recent IRS guidance distinguishes certain good-faith mistakes from a complete failure to satisfy the reporting requirement. The guidance indicates that filing the wrong type of information return in good faith, or reporting an inaccurate amount while making a good-faith attempt to report the payment, does not automatically destroy reporting consistency. That is very different from discovering that a required information return was never filed before the examination began.
For each anomaly, preserve the original filing, correction date, correspondence, and reason for the error. Do not rewrite the history as though the corrected document had always existed. A chronology lets the reviewer distinguish an honest reporting mistake from a missing reporting trail. It also helps identify whether the correction occurred before or after the examination started, which can matter when evaluating what returns were filed prior to commencement of the audit.
Substantive consistency turns on “substantially similar,” not identical job titles
The substantive-consistency requirement looks for workers in substantially similar positions who were treated differently. IRS guidance directs a factual comparison of day-to-day services and job functions. A company can therefore have both employees and contractors in the same broad department if the actual positions are materially different, but the distinction must be real. Changing “designer” to “creative consultant” does not create a different position when the person performs the same production work under the same managers and schedule.
Create a matrix of functions rather than titles. Compare responsibility for clients, authority to accept or reject assignments, supervision, required availability, tools, compensation model, business-development expectations, and whether the worker provides the same services to the market. If two roles diverge on meaningful operating facts, document those differences. If they do not, do not invent distinctions. The purpose of the matrix is to expose consistency risk early, not to make every row produce a preferred answer.
Predecessor history can matter even when the current company has a clean record
Section 530 substantive consistency reaches treatment by the taxpayer and predecessor businesses. A company formed after a reorganization, asset transfer, or ownership change should therefore ask whether substantially similar workers were treated as employees by a predecessor. This is especially important when the current organization inherited contracts, managers, customers, or operating units but changed worker labels during the transition.
The diligence file should identify predecessor entities, the date operations moved, and how the relevant class of workers was treated on both sides of the transaction. Pull payroll registers, 1099 files, employee rosters, and acquisition records if available. The point is not that every business purchase creates a predecessor problem; it is that a company cannot safely declare substantive consistency by looking only at the years under its current legal name when the relief rule expressly asks about predecessor treatment.
Mixed W-2 and 1099 treatment can be legitimate only when the underlying work is truly different
Businesses sometimes have a person who performs one role as an employee and later performs separate project work as a nonemployee, or vice versa. The existence of both a W-2 and a 1099 does not automatically prove substantive inconsistency. The real question is whether the services and positions were substantially similar during the relevant periods. A former employee who later forms a separate business and provides a different specialized service may present a different fact pattern from an employee whose payroll status is simply switched to 1099 while the job stays the same.
When dual treatment exists, create a dated service map. Identify the duties, reporting line, compensation, tools, customer responsibility, and contractual basis for each phase. Attach representative records from both phases. If nothing material changed except the tax form, the file should flag that risk rather than trying to explain it away. If the work truly changed, the chronology becomes the evidence for why the two treatments are not necessarily inconsistent.
Finish with an exceptions schedule, not a blanket consistency statement
A useful Section 530 file ends with an exceptions schedule listing every worker or role that does not fit the clean pattern. Common entries include a late or missing information return, a worker who moved from payroll to contractor status, a predecessor employee with similar duties, or a role whose job description overlaps both groups. Each exception should have a factual explanation and a status: resolved, requires professional analysis, or likely prevents relief for a worker or period.
This is more credible than a memo saying the business “has consistently treated all contractors as contractors.” The IRS tests are narrower and more demanding than that slogan. A transparent exceptions schedule lets management understand where relief may be strong, where the classification merits need to carry more weight, and where settlement or prospective correction should be considered. It also reduces the risk of giving an examiner an inaccurate categorical answer during an interview.
RECONCILIATION TOOL
Consistency exception schedule
Create one row for every worker or role that breaks the normal pattern. Empty exception schedules are useful only if they result from a real reconciliation.
| Exception | Documents to inspect | Question to resolve |
|---|---|---|
| Required 1099 may be missing | AP ledger, 1099 transmittal, filing confirmation | Was a return required and filed before examination? |
| Worker received W-2 in another period | Payroll, job duties, engagement chronology | Were the services substantially similar? |
| Similar employee role exists | Org chart, job descriptions, manager interview | Is the similarity only in title or in actual functions? |
| Predecessor used employees | Transaction records, predecessor payroll | Does predecessor treatment affect the same worker class? |
| Corrected information return | Original/corrected forms, correspondence | Was this a good-faith reporting error or a missing filing? |
WORKED EXAMPLE
Example: one “contract analyst” was previously a payroll analyst
A consulting firm treats twelve analysts as contractors and has complete Forms 1099 for all twelve. During the substantive-consistency review, HR finds that one analyst worked on payroll the prior year under a different title. Management initially says the titles prove the roles were different.
The team compares the actual work instead. The payroll role handled internal forecasting under a finance manager; the later contractor role performed a one-time data conversion for a client, set its own project sequence, and used separate tools. The chronology does not guarantee Section 530 relief, but it gives the company a factual basis to explain why the two positions may not be substantially similar. If the duties had been the same, the matrix would have exposed that risk just as clearly.