Agent of Record (AOR), Contractor of Record (COR) and Contractor Pay are three of the main ways to engage and pay an independent contractor, so they are easy to conflate.
All three move money to the contractor, and all three take administrative work off the client. They are not equal on risk, however, and choosing the wrong one can leave a company carrying exposure that it assumed it had dealt with.
All three models apply to independent contractors, so they only come into play once a worker has been correctly classified as one.
The Three Models, Defined
Agent of Record (AOR) — the client keeps the direct contract with the contractor, while the provider acts as the client's authorized agent for the layer around it: classification guidance, onboarding, payment facilitation and ongoing compliance support. The relationship stays between the company and the contractor.
Contractor of Record (COR) — the provider, not the client, becomes the contracting party. The client contracts with the COR provider, and the COR provider contracts with the contractor. An intermediary now sits between the company and the person doing the work.
Contractor Pay — simply a payment mechanism. The tool collects from the client and pays the contractor, but does nothing about classification, compliance or ongoing risk. The client contracts directly and carries the full compliance burden alone.
AOR vs COR vs Contractor Pay at a Glance
Question | AOR | COR | Contractor Pay |
Who contracts with the contractor? | The client, directly | The COR provider | The client, directly |
Your relationship with the contractor | Direct | Indirect — routed through the provider | Direct, but unmanaged |
Runs payroll? | No — the contractor invoices; the provider facilitates payment | No — same as AOR | No — moves money only |
Classification and compliance support | Yes — guidance, onboarding and ongoing support | Yes — but bundled with taking over the contract | None — it only moves money |
Effect on classification | Reflects the real, direct relationship | Adds a contracting layer that does not change the underlying facts | Leaves classification unaddressed |
Who controls the engagement? | The client | Provider-mediated | The client, unsupported |
Where does the compliance risk sit? | Actively managed within the engagement — the AOR provider assesses the misclassification risk so the client can decide whether to proceed | Unchanged — moving the contract to the COR does not remove misclassification risk, because it is the facts of the working relationship that are examined, not what is in the contract | Entirely with the client |
Does the Model Chosen Change Classification Risk?
No — not on its own. Misclassification is judged on the details of the working relationship — the actual facts of how the work is done — and not on how the contractor is paid or on whose name is on the paperwork. None of the three models changes those facts.
What does differ is how much visibility and support the client gets. Contractor Pay leaves classification unaddressed, so the entire exposure stays with the client. COR changes who holds the contract, but not the underlying facts that a regulator would examine; at worst, an intermediary contract could mask a live misclassification rather than resolve it.
Both AOR and COR assess the risk within the engagement, so the client can decide whether to proceed on an informed basis. The difference is that under an AOR the client contracts directly with the contractor, so the arrangement could be considered more direct and transparent rather than routing it through an intermediary.
When to Use Each Model
AOR is appropriate when the work is genuinely independent, the client wants to keep a direct relationship with the contractor, and classification and compliance support is needed around the engagement.
COR is appropriate when a third party is meant to hold the contracting relationship itself — a matter of administrative convenience, not risk transfer.
Contractor Pay is appropriate when classification has already been confirmed, no compliance support is required, and the only remaining need is to move payment to a contractor the company is managing directly.
Frequently Asked Questions
What is the difference between AOR, COR and Contractor Pay?
All three are mechanisms to pay an independent contractor. Under AOR, the client keeps the direct contract and the provider supports classification and compliance around it. Under COR, the provider becomes the contracting party in the client's place. Contractor Pay is a payment tool only: the client contracts directly and carries the compliance burden alone.
Does using a COR remove contractor misclassification risk?
No. Misclassification is assessed on the details of the working relationship, not on which entity holds the contract. Moving the contract to a COR changes who signs and adds an intermediary, but it leaves the underlying facts — and the exposure — where they were.
Is Contractor Pay enough on its own?
Only where classification has already been settled and no ongoing compliance support is needed. A contractor pay tool collects from the client and pays the contractor; it does nothing about classification, compliance or ongoing risk, so the full misclassification exposure stays with the client.
Legal Disclaimer
The information provided in this article is for general informational purposes only. Accuracy, completeness, or reliability is not guaranteed. This content does not constitute legal, professional, or other advice, including with respect to worker classification, and should not be relied upon as such.