A Contractor of Record (COR) is a model for engaging independent contractors in which the provider, not the client, becomes the contracting party with the contractor. Like an Agent of Record (AOR), a COR handles the administrative layer around the engagement: onboarding, payment facilitation, and compliance support. The decisive difference is who signs and holds the contract.
Under COR, the client contracts with the COR provider, and the COR provider contracts directly with the contractor. Under AOR, the client keeps the direct contract with the contractor, and the AOR provider acts only as an authorized agent for the administrative work.
That single difference — who the contractor's counterparty actually is — is what separates the two models, and it's worth understanding clearly before choosing either one.
How a Contractor of Record Works
A COR typically handles:
Contracting — the COR provider, not your company, signs the agreement with the independent contractor.
Onboarding — setting up the contractor's agreement and administrative details.
Payment facilitation — the contractor invoices the COR provider, who facilitates payment. This isn't payroll: independent contractors aren't employees, so no tax withholding or statutory employer obligations apply the way they would under an Employer of Record (EOR).
Compliance support — ongoing support bundled into the arrangement, since the COR provider is the one who holds the contract.
This is structurally similar to an Agent of Record (AOR) engagement in terms of scope of work. The difference isn't what gets done, but who's legally the contracting party while it's being done.
Who Typically Uses a COR Model?
Companies tend to reach for a COR when they want a single provider to sit between them and a large or fast-growing contractor base. Often these are businesses managing many independent contractors across borders.
They want the contracting relationship handled by someone else entirely, rather than negotiated and signed by their own team. It's a structure you'll commonly see offered alongside, or as an alternative to, contractor payment tools and AOR services.
Does a COR Reduce Misclassification Risk?
It's a reasonable assumption: if a COR provider signs the contract, surely they're also taking on the classification risk. In practice, it doesn't work that way.
Worker classification is judged on the substance of how the relationship actually works day to day — who directs the work, who sets the schedule, who holds control — not on which entity's name appears on the paperwork. Moving the contract to a COR provider doesn't change those underlying facts. At worst, it could obscure a misclassification issue that already exists rather than resolving it.
Under an AOR model, by contrast, the client keeps its direct relationship with the contractor. That doesn't eliminate classification risk, but it does mean that the relationship is fully transparent to the client. That can support a cleaner classification position and keep the client, not an intermediary, in control of the engagement.
The Real Cost of Getting Classification Wrong
Misclassification isn't a hypothetical risk. Studies suggest 10–20% of employers misclassify at least one worker. Organizations worldwide now manage a contractor workforce numbering in the hundreds of millions, and in the EU alone, the European Commission estimates as many as 5 million workers could be wrongly classified as self-employed.
Enforcement is real and rising: the UK's HMRC has recovered over £263m from public-sector IR35 cases since 2017; a single US state assessed Uber roughly $649m in back taxes and penalties; and Spain fined Glovo €79m over rider misclassification.
And the fine is rarely the biggest cost. Misclassification can trigger back taxes, social contributions, wage claims, benefits, and penalties across an entire workforce.
When Contractor Risk Signals a Bigger Problem
Whether an engagement runs through a COR, an AOR, or neither, the same signals tend to mean a contractor relationship is drifting toward employment:
Tenure — the engagement has run long enough to look ongoing rather than project-based.
Exclusivity — the contractor now works solely, or almost solely, for one company.
Scale & permanence — hours, responsibilities, and team integration have grown.
Funding milestones — new investment brings headcount plans and added scrutiny.
Rising misclassification risk — the engagement increasingly resembles employment.
When one or more of these show up, it's usually a sign to revisit whether the person should become an employee. The goal is to engage them compliantly today and convert them to an employee when permanence, risk, or scale changes, without switching providers.
Key Things to Know Before Choosing a COR
A COR becomes the legal contracting party with your contractor, which can simplify certain administrative handoffs.
It does not change how classification is judged — the underlying facts of the engagement still determine worker status, regardless of who signed the contract.
Compliance support is typically bundled into the arrangement, similar to AOR, but responsibility for the contracting relationship sits with the COR provider rather than your own team.
If staying the direct party in the relationship matters to your business, an AOR model is worth considering against a COR before you decide.
Ask any provider, COR or AOR, exactly what's included in "compliance support." The phrase covers very different levels of involvement depending on the vendor, and it's worth getting specifics before you sign.
A COR arrangement is still worth documenting carefully on your end. If the engagement is ever reviewed by a regulator, having your own record of how the working relationship actually functions matters, regardless of who signed the contract.
Frequently Asked Questions
What is a Contractor of Record (COR)?
A Contractor of Record (COR) is a model for engaging independent contractors in which the provider, not the client, becomes the contracting party with the contractor. The COR handles onboarding, payment facilitation, and compliance support around the engagement.
Does using a COR reduce misclassification risk?
Not on its own. Classification is judged on the substance of the working relationship, not on which entity holds the contract. Moving the contract to a COR provider doesn't change the underlying facts of the engagement.
Is a Contractor of Record the same as an Employer of Record (EOR)?
No. A COR contracts with an independent contractor — there's no employment relationship, and no payroll. An EOR becomes the legal, statutory employer of a worker, running payroll and carrying full employment-law compliance.
Which is better for my business, COR or AOR?
It depends on what you're optimizing for. A COR shifts the contracting relationship to a third party; an AOR keeps you as the direct contracting party with expert support around the engagement. Neither structure by itself determines your classification outcome — that depends on the facts of the engagement and applicable law.