How does Kentucky classify workers as employees or contractors?

The structure matters because Kentucky's ABC test is more demanding than a pure common-law analysis. Under the common-law approach, an employer who doesn't direct the manner and means of work typically wins the classification question. Under KRS 341, that's not enough. You also need to show the work is outside the company's usual course of business and that the individual maintains an independent enterprise.

The Kentucky Education and Development Cabinet (KEDC) administers UI classification audits and can issue retroactive employee determinations. A KEDC determination is not conclusive evidence of employment in other contexts (workers' comp, IRS), but it triggers the UI liability stack immediately and typically precedes a broader review.

Workers' compensation classification in Kentucky turns on the employer's right to control the manner and means of the work performed. Courts look at factors including who supplies the tools, the skill required, whether the worker can subcontract, and how payment is structured. This tracks the IRS common-law analysis closely, which means a relationship that is defensible under IRS Publication 15-A is typically also defensible for Kentucky workers' comp purposes.

The practical exposure is asymmetric. You can pass the workers' comp test (common-law control) and still fail the UI test (ABC). Prong B of KRS 341 has no analogue in the common-law framework. A skilled developer who works independently, supplies their own equipment, and has multiple clients can satisfy the common-law control test easily. If the work they do is inside your company's core product development function, Prong B fails regardless.

Running all four analyses before any contractor engagement is the only reliable way to know where you stand. A Teamed compliance specialist can work through each framework against the specific facts of the engagement before you issue an offer letter or statement of work.

The financial exposure from a Kentucky reclassification compounds across four separate tax and benefit tracks. Each one accrues independently:

The local occupational licence fee exposure is a Kentucky-specific multiplier that most out-of-state employers miss. 87 of 120 Kentucky counties plus hundreds of cities levy an occupational licence fee on wages earned within their jurisdiction. Employers must withhold for every jurisdiction where the reclassified worker earned wages. There is no unified state portal: each jurisdiction administers independently. A reclassified contractor who worked across multiple Kentucky counties triggers separate back-filing obligations in each.

Under KRS 341.330(3), responsible corporate officers, members, and managers can face personal liability for unpaid UI contributions in certain circumstances. This is not a theoretical risk: KEDC has pursued personal liability in cases where the company lacked the assets to satisfy the back-contribution bill. Founders and CFOs of early-stage companies carrying large contractor workforces should treat this as a material personal exposure, not a corporate one.

A named compliance specialist on the Teamed platform monitors your contractor roster and flags any relationship that drifts toward KRS 341 Prong B exposure. That's the conversation you want to have before the KEDC audit, not after.

The IRS applies three categories of evidence: behavioural control, financial control, and type of relationship (IRS Publication 15-A). Kentucky's Prong A (direction and control) maps cleanly onto the IRS behavioural control analysis. A contractor who is genuinely independent in how they work, uses their own tools, and isn't subject to day-to-day supervision typically satisfies both Prong A and the IRS behavioural test.

Prong B has no IRS equivalent. The IRS doesn't ask whether the services are outside the hiring entity's usual course of business. A software company hiring a software developer who works remotely, sets their own hours, and bills by the project can look clean under the IRS analysis and fail Prong B immediately. The work is inside the company's core function by definition.

Prong C overlaps with the IRS "type of relationship" category but is more stringent. The IRS looks at whether the worker has made a significant investment in their own business. KRS 341 requires that the worker be "customarily engaged" in an established independent business. A contractor who has only ever worked for one or two clients, has no business registration, and carries no business insurance is unlikely to satisfy this prong even if the IRS analysis comes back clean.

The practical result: an IRS-defensible classification is a necessary but not sufficient condition for Kentucky UI safety. If the contractor's work falls inside your company's standard product or service, Prong B is the risk that survives the IRS analysis. Run the KRS 341 analysis separately.

For Prong A (direction and control): the statement of work should specify outcomes and deliverables, not methods or working hours. The contractor should have discretion in how the work is performed. Document that you don't direct their daily schedule, don't require them to use company systems exclusively, and don't integrate them into your management hierarchy.

For Prong B (outside usual course of business or premises): this is the hardest prong to document after the fact. Before you engage, ask directly whether the services you're buying are within your company's standard product or service delivery. If the answer is yes, Prong B is likely to fail, and the documentation task is to convert the engagement rather than defend it. If the services are genuinely ancillary (legal counsel, specialist audit, one-off infrastructure work), document the scope and the distinction clearly in the contract.

For Prong C (independently established business): collect evidence of the contractor's independent business at engagement: business registration documents or EIN, evidence of other clients (even a general statement on the contract), professional liability insurance, their own business email address and invoicing infrastructure. A contractor who can't produce any of this should prompt a classification review, not just a contract signature.

Maintain this documentation file for the life of the engagement plus at least four years (the standard limitation period for KEDC back-assessment). Teamed's in-house compliance team holds classification documentation for every EOR engagement as a standard part of the file, so there's no scramble if an audit arrives.