Contractor of Record

Contractor of Record is a third-party intermediary that engages independent contractors on a buyer's behalf and absorbs a defined tier of audit response.

For global contractor management teams, the CoR is the structural alternative to converting a worker from contractor to employee through an EOR. The CoR keeps the contractor as a contractor while shifting some of the classification audit risk onto the provider.

The CoR contracts with the worker as an independent contractor, not an employee. The provider handles contracting, invoicing, payment processing, statutory filings (1099 in the US, IR35 SDS in the UK), and a defined slice of misclassification audit defence.

The classification-shielding mechanic is partial. Most CoR MSAs cap indemnification at per-invoice fee levels that fall short of multi-year audit-window exposure on reclassified workers. Read the indemnity clause carefully before signing.

What does Contractor of Record mean in payroll?

In contractor management, CoR is the intermediary structure that sits between the buyer and the contractor. Three operational features matter for the buyer.

The legal structure

The CoR contracts with the worker as an independent contractor. The CoR also contracts with the buyer as a service provider. The buyer has no direct contractual relationship with the worker.

The structure aims to insulate the buyer from misclassification claims by shifting the contractor relationship to the CoR. The shielding is structural but not absolute; classification tests look at the lived working relationship.

The operational scope

Standard CoR scope covers contract drafting, invoicing handling, payment processing including FX and rail selection, statutory filings (US 1099-NEC, UK IR35 SDS, EU DAC7 reporting), and a defined tier of audit-defence support.

The provider does not absorb the worker as an employee. The worker stays in contractor status; no employer contributions, statutory benefits, or employee labour-law protections attach. See the EOR compliance entry for the alternative employee-conversion route.

The classification-shield mechanic

The CoR's classification shield depends on three factors. The contract structure between CoR and worker (must be genuine contractor terms). The working relationship between buyer and worker (must not show employer-employee characteristics regardless of CoR intermediation). The indemnification cap in the MSA.

Most CoR providers warrant the classification work they performed but cap indemnification at per-invoice or per-worker fee levels. The shield protects against the provider's own errors; it does not cover audit-window exposure on a relationship that fails the classification test on substance.

How does CoR compare to EOR, contractor management, and direct contracting?

The contractor-engagement spectrum runs from direct buyer contracting to full EOR employment. CoR sits in the middle as a classification-shielded contractor structure.

The CoR fits where the buyer wants contractor flexibility but seeks classification shielding. The cost premium over a contractor management platform reflects the indemnification scope; the cost discount versus EOR reflects the contractor status.

The Agent of Record (AOR) label predates CoR in some US sectors but resolves to the same structure. See the agent of record entry for the terminology distinction and the contractor management entry for the platform tier below CoR.

What does the CoR scope cover operationally?

The operational scope splits between the CoR and the buyer along the contractor-relationship boundary. The CoR holds the contract; the buyer drives the work.

The CoR scope explicitly excludes work direction, performance management, and integration of the worker into the buyer's teams. These activities sit with the buyer and create classification risk regardless of the CoR's intermediation.

The 2024 EU Platform Work Directive (transposition deadline December 2026) introduces a rebuttable presumption of employment for digital-platform workers under algorithmic management. CoR providers face heightened classification scrutiny from late 2026. See the Platform Work Directive entry.

What do buyers consistently get wrong on CoR?

The recurring mistakes cluster into four moves visible across contractor-management procurement reviews that engaged CoR providers.

The first is treating CoR as full classification shielding. The MSA caps indemnification at per-invoice or per-worker fee levels. The cap rarely covers multi-year audit-window back-tax exposure when a relationship fails the classification test on substance.

The second is missing the buyer-controlled relationship activities. Direction over how, when, and where the work is done sits with the buyer regardless of CoR intermediation. Workers attending daily stand-ups, using company laptops, and reporting to a buyer's manager fail the IRS common-law test on behavioural control.

The third is using CoR as a route to keep workers in contractor status when employment classification is the correct outcome. The CoR's commercial value is contractor flexibility; using it to evade an employment classification that the lived relationship supports just shifts risk to a later audit event.

The fourth is missing the IR35 end-client liability. For UK public-sector engagements from April 2017 and medium-large private-sector from April 2021, the end-client carries the IR35 status determination liability. The CoR can prepare the SDS, but the liability for getting it wrong falls on the buyer. See the misclassification audit entry.

What does a CoR provider handle versus what stays with the buyer?

The MSA decides the operational and liability split. Contractor management platforms with CoR tier structure the indemnification carefully to manage the provider's downside exposure.

The most-debated MSA clause is the indemnification cap. Providers typically cap at per-invoice or per-worker fee levels (often 1-3 percent of invoice value or 1-12 months of service fees). A reclassified worker can carry $30,000-$100,000+ of audit-window back-tax in the US. The cap rarely matches that exposure.

For buyers planning to use CoR as primary classification shielding, push for indemnification scope that covers the full audit-window back-tax on workers where the CoR signed off the classification. See the W-2 vs 1099 entry for the US classification cost stack.

Contractor of Record FAQs

What is the difference between CoR and EOR?

CoR is a third-party intermediary that engages workers as independent contractors on the buyer's behalf, retaining contractor status with no employer contributions or statutory benefits.

EOR is a third-party intermediary that employs workers as W-2 or local-statute employees, providing full employer-side compliance. CoR typically costs $49-$199 per worker monthly or 1-3 percent of invoice; EOR costs $199-$750 per worker monthly.

Does CoR fully shield the buyer from misclassification?

No. The CoR's classification shield is structural but not absolute. Classification tests look at the lived working relationship between the buyer and the worker, which can survive CoR intermediation.

CoR MSAs typically cap indemnification at per-invoice or per-worker fee levels that fall short of the multi-year audit-window back-tax exposure when a relationship fails the classification test on substance.

What is the difference between Contractor of Record and Agent of Record?

Agent of Record (AOR) is the older US terminology predating CoR in some sectors, particularly insurance and certain regulated industries. Contractor of Record (CoR) is the dominant modern term in the global contractor management category.

Both refer to the same third-party intermediary structure. Modern providers use the terms interchangeably. See the agent of record entry for the terminology distinction.

Does CoR cover UK IR35 status determination liability?

Partially. The CoR can prepare the IR35 Status Determination Statement on the buyer's behalf, but the liability for getting it wrong falls on the end client under the post-2017 (public) and post-2021 (medium-large private) Chapter 10 rules.

HMRC enquiries on incorrect SDS conclusions land at the end client, not the CoR. Verify the indemnification clause specifically covers IR35 SDS errors.

How does the EU Platform Work Directive affect CoR?

The 2024 EU Platform Work Directive (Directive 2024/2831) with transposition deadline December 2026 introduces a rebuttable presumption of employment for digital-platform workers under algorithmic management.

CoR providers operating EU platform-mediated contractor pools face heightened classification scrutiny from late 2026 onwards. The presumption shifts the classification default; the platform must rebut by showing genuine self-employment.