What is a Contractor of Record? And when to use one instead of an Agent of Record or EOR

Key takeaways

• COR and AOR keep contractors independent, but an EOR doesn’t. The line that decides everything else is whether an employment relationship is created. In a nutshell, COR and AOR preserve contractor status, but EOR removes it entirely.
• COR and AOR aren’t interchangeable. AOR covers payment and tax documentation (mainly US 1099 work). COR covers the full contract, classification and compliance lifecycle. It is the stronger fit for the UK, EMEA and multi-country engagements.
• Using the wrong model creates real liabilities, not just admin headaches. Misclassification exposure runs into six and seven figure penalties to be carried by the client organisation, not the contractor.
• The decision should follow the worker’s status, not convenience. Worker classification, jurisdiction and engagement type (in that order) determine the right model, defaulting to EOR “to be safe” or COR “to save cost” both create compliance problems.
• Fragmented providers create fragmented risk. Running COR, AOR and EOR through separate vendors makes consistent governance and audit-readiness harder. A single integrated model gives one compliance standard and one point of accountability across the whole contingent workforce.

Contingent labour is already a core part of how organisations resource work, and regulators know it. Gartner has found that 32% of organisations are actively replacing full-time roles with contingent workers as a deliberate workforce strategy, and tax authorities from HMRC to the IRS have responded with tighter classification enforcement. Having more contractors invites more scrutiny, and this combination is exactly where the confusion between a Contractor of Record, an Agent of Record and an Employer of Record becomes expensive.

A Contractor of Record (COR) is a third-party organisation that manages the contractual compliance and payment relationship between a business and an independent contractor, without employing the contractor or converting their independent status. It sits alongside two related but distinct models: the Agent of Record (AOR), which handles payment and tax documentation for contractors, and the Employer of Record (EOR), which legally employs the worker.

Let’s break down how each model works, who carries compliance responsibility under each, when to use one over another, and a practical framework for making that call. Get it wrong and you’ll experience the consequences of exposure: misclassification penalties, backdated tax liability, unravelled contractor relationships and audit risk that can take months to resolve.

Understanding the three models — Contractor of Record, Agent of Record, and Employer of Record Defined

These three models solve different problems, but the market doesn’t always use the terms consistently. Before comparing them, it helps to know exactly what each one is, who the parties are, and most critically, whether an employment relationship gets created.

What is a Contractor of Record (COR)?

• A Contractor of Record engages an independent contractor on behalf of a client, managing contract execution, classification verification, invoicing and payment. It maintains the documentation needed to defend that classification if challenged. 
• A COR does not employ the contractor, run statutory payroll, or provide employee benefits. The worker remains an independent contractor, self-employed individual, or operator of their own limited company throughout.
• A COR takes on the administrative and compliance burden of the engagement while the contractor keeps their independent status. This is the model organisations reach for when they want to engage an established contractor compliantly, without creating a direct contractual relationship or carrying misclassification risk themselves. 
• In the UK, COR arrangements are particularly relevant to IR35 off-payroll working rules, where the COR can support the status determination process and structure the engagement correctly.

What is an Agent of Record (AOR)?

• An Agent of Record acts as the commercial and administrative agent for a contractor. 
• The AOR is in charge of managing payment processing, issuing tax documentation (Form 1099 in the US), and handling compliance verification tied to that payment relationship. 
• Like a COR, an AOR does not employ the worker, take on employer tax liability, or provide statutory benefits. The worker remains an independent contractor or freelancer.
• AOR arrangements are most common in the US, where businesses use them to simplify 1099 payment and tax reporting without taking on direct contractor management. The overlap with COR exists (both preserve contractor independence) but the scope differs. 
• AOR is narrower and payment-focused, COR extends to contract management, compliance verification, and full engagement governance.

What is an Employer of Record (EOR)?

• An Employer of Record legally employs the worker on the client’s behalf. It runs payroll, withholds and remits employment taxes, provides statutory benefits, and carries the employer’s compliance obligations in that jurisdiction. It does not direct the worker’s day-to-day duties or own the work product as both stay with the client. The worker’s status is unambiguous: they are an employee of the EOR, not an independent contractor.
• Organisations use EOR when they need to engage a worker in a country where they have no legal entity yet, or when the role genuinely doesn’t meet the legal bar for independent contracting.
• This is the fundamental line that separates EOR from COR and AOR as it creates an employment relationship, with everything that implies for cost, entitlements and compliance obligations under frameworks like IR35 in the UK or W-2 reporting in the US.

COR vs AOR vs EOR — a detailed comparison

The three models differ along three dimensions that matter for the decision in front of you: 

1. whether the worker is employed
2. who is accountable if compliance goes wrong
3. what each model is actually built to do. 

Getting these straight is what turns “which one do we need?” into a defensible answer.

The distinction that matters most here is the employment line:

• Under COR and AOR, the worker stays independent. There is no payroll, no statutory benefits, no employer on-costs, but the trade-off is that the client (via the COR or AOR) must be able to prove the classification is correct. 
• Under EOR, the client accepts higher cost and administrative overhead in exchange for full compliance certainty and the ability to hire someone the client couldn’t legally engage as a contractor. 
• Choosing between them isn’t really a preference. It follows from the worker’s actual status and the jurisdiction they’re working in.

COR in practice:A UK professional services firm needs a specialist IT contractor who operates through their own limited company. The COR runs the IR35 status determination, executes the contract, and manages invoicing and payment on the firm’s behalf—keeping the engagement compliant without the firm taking on direct contractual risk.

AOR in practice:A US technology company engages freelance UX designers across a dozen states. The AOR issues 1099s, processes payments, and manages state-level tax compliance, removing that administrative load from the client entirely

EOR in practice:A UK SaaS business wants to hire a full-time sales manager in Germany, where it has no legal entity. The EOR employs the worker locally, runs German payroll, manages social security contributions, and handles employment law compliance the business has no infrastructure to manage itself.

Where COR and AOR overlap — and where they diverge

Both models preserve contractor independence, remove the employment relationship from the client, and manage payment and compliance administration on the client’s behalf. The genuine overlap ends there, though. The divergence is in scope, geography and compliance depth.

Scope:

• AOR focuses on payment processing and tax documentation. 
• COR is broader. It spans contract execution, classification status determination, compliance verification, invoicing governance, and full documentation.

Geography:

• AOR is the most established in the US for 1099 engagements. 
• COR is used more widely across international markets, including the UK, EMEA and APAC, where classification obligations are more complex.

Compliance depth:

• AOR manages the payment-layer relationship. 
• COR manages the full contractual and compliance relationship, including the documentation needed to defend independent status in a regulatory audit.

Risk allocation:

• Both preserve independent status, but COR typically carries stronger compliance infrastructure which is a more defensible position in high-scrutiny jurisdictions such as the UK under IR35.

When EOR is the right choice — and when it is not

EOR is the right choice when:

• The worker’s role doesn’t meet the legal definition of an independent contractor in that jurisdiction. An example would be a role that would fail California’s ABC test or fall inside IR35 in the UK.
• The client wants to hire in a country where it has no legal entity and doesn’t plan to establish one.
• The worker needs statutory benefits and entitlements (paid leave, pension contributions, social security) as part of the engagement.
• The engagement is long-term and full-time, which typically points to employment rather than contracting.

EOR is not the right choice when:

• The worker is a genuine independent contractor operating through their own entity. Converting them to EOR employment raises costs significantly and may not be wanted by the contractor.
• The engagement is project-based, short-term or specialist. These are characteristics that support independent contractor status.
• The organisation wants to preserve the flexibility and commercial terms of a contractor relationship.

Misapplying EOR to a genuine contractor and misapplying COR or AOR to someone who should be employed are both compliance failures, just in opposite directions. The decision has to follow the worker’s actual status, not whichever model is administratively easiest.

The compliance consequences of choosing the wrong model

Misclassifying an employee as a contractor (using COR or AOR when EOR is required) carries jurisdiction-specific consequences:

• UK: Under IR35 off-payroll rules, liability for incorrect status determinations sits with the client organisation, not the contractor. HMRC can pursue unpaid income tax and National Insurance, and where the client hadn’t taken “reasonable care,” add a penalty of around 30% on top of the tax owed, plus interest, with HMRC able to look back several years.
• US: The IRS treats unintentional misclassification under Section 3509 as liability for a reduced but still significant share of unpaid income tax typically 1.5% of unwithheld income tax plus a portion of unremitted FICA contributions, on top of interest. Intentional misclassification removes those reductions entirely. States with stricter tests, such as California’s ABC test, add their own penalty exposure on top.
• Australia: Following the 2024 amendments to the Fair Work Act, the Fair Work Commission applies a “whole-of-relationship” test that looks at the practical reality of the engagement, not just the contract wording. Sham contracting carries civil penalties that can run into the tens of thousands of dollars per contravention, and misclassified workers can claim back-pay of employment entitlements.

Misclassifying a contractor as an employee (using EOR when COR or AOR would do) is less discussed but still costly: unnecessary employer on-costs that a genuine contractor engagement wouldn’t carry, contractor dissatisfaction where the worker values their independent status, and incorrect tax treatment.

Regulatory enforcement of classification rules continues to intensify across jurisdictions. HMRC IR35 enforcement activity has picked up since the off-payroll rules extended to the private sector, and the IRS continues to focus scrutiny on sectors with high contractor usage. Organisations that haven’t reviewed their engagement models recently should treat it as a priority, not a background task.

How to choose the right model — a practical decision framework

The right model must follow three factors in sequence: the worker’s legal status, the jurisdictions they’re working in, and what the engagement actually requires operationally. Working through these in order removes most of the ambiguity from the decision.

Step 1: Determine the worker’s legal status.

• Does this worker meet the legal definition of an independent contractor where they’ll be working? 
• If yes, move to Step 2. 
• If no, or if it’s genuinely uncertain, engage via EOR. Don’t proceed with COR or AOR.

Step 2: Identify the jurisdiction.

• Is the work primarily in the US with straightforward 1099 engagements? AOR may be sufficient. 
• Is it in the UK, spread across multiple markets, or in a jurisdiction with complex classification rules? COR is the more appropriate model for the compliance governance it provides.

Step 3: Assess the compliance support required.

• Does the engagement need full contract management, classification determination and audit-ready documentation, or mainly payment processing and tax documentation? 
• The former points to COR. As for the latter, AOR may cover it.

Step 4: Consider the engagement characteristics.

• Is the role long-term, full-time and integrated into business operations, or project-based and time-limited? 
• Long-term and integrated warrants a second look at EOR regardless of the worker’s stated preference. 
• On the other hand, project-based and specialist supports proceeding with COR or AOR per Steps 2 and 3.

Keep in mind that this framework is only a starting point. Engagements spanning multiple jurisdictions, unusual worker arrangements, or disputed classification status should still involve legal and compliance expertise before a final decision is made.

Scenario #1: UK professional services firm engaging a specialist IT contractor

A UK-headquartered professional services firm needs a cybersecurity consultant, operating through their own limited company, for a six-month project.

Working through the framework:

• The consultant meets the legal definition of an independent contractor (Step 1). 
• The engagement is in the UK, where IR35 off-payroll rules apply, pointing to COR over AOR (Step 2). 
• The engagement needs IR35 status determination, contract execution, invoicing and audit-ready documentation which means full COR scope (Step 3). 
• It’s project-based and time-limited, supporting contractor status (Step 4).

Conclusion: COR is correct. It manages the IR35 determination, executes the contract, processes invoices, and maintains documentation that protects the client in an HMRC audit. AOR wouldn’t cover IR35 determination, and EOR would be the wrong call for a contractor who hasn’t been assessed as inside IR35.

Scenario #2: US technology company engaging freelance designers across multiple states

A US-headquartered technology company regularly engages freelance UX and graphic designers across 12 states for project-based work. The designers are genuinely self-employed, invoice their own clients, and work for multiple businesses simultaneously.

• The designers meet the legal definition of independent contractors in their respective states (Step 1). 
• The engagements are primarily within the US, making AOR viable, though states with stricter tests, notably California’s ABC test, warrant separate verification (Step 2). 
• The primary need is payment processing, 1099 issuance and multi-state tax compliance which belong to the AOR scope (Step 3). 
• Engagements are project-based and time-limited (Step 4).

Conclusion: AOR is correct for the majority of these engagements, subject to state-specific classification checks. For California-based designers, the ABC test needs to be run before confirming AOR is appropriate. A worker who fails any one of its three prongs is legally an employee regardless of contract wording.

Scenario #3: European SaaS business hiring talent in a new market without a local entity

A UK-based SaaS business wants to hire a full-time enterprise sales manager in Singapore, where it has no legal entity and no plans to establish one.

• The role is full-time, integrated into sales operations, reports to a UK-based VP, and involves managing client relationships on the company’s behalf. These are characteristics that point straight to employment rather than contracting (Step 1). 
• The jurisdiction is Singapore, and the client has no local entity (Step 2). 
• Contractor engagement isn’t viable given Step 1 (Step 3 not applicable). 
• The role is full-time and long-term (Step 4).

Conclusion: EOR is the only compliant route. The EOR employs the sales manager locally, manages Singapore payroll and statutory contributions, and handles local employment law compliance, while the client continues directing the worker’s day-to-day activities and retains ownership of their output. Attempting to engage this role via COR or AOR would create real misclassification exposure under Singapore’s employment framework.

How CXC Global delivers COR, AOR, and EOR solutions across 100+ countries

Working through the framework above tells you which model fits. The next question is who can deliver it reliably, at scale, without fragmenting your workforce governance across multiple providers. That’s the gap CXC is built to close.

With over 30 years managing contingent workforces across 100+ countries, CXC provides COR, AOR and EOR solutions within a single, integrated service model.

In practice, that means:

• We manage the full contractor engagement lifecycle (classification verification, contract execution, compliance documentation, invoicing and payment) for clients engaging independent contractors across multiple jurisdictions.
• CXC Comply, the compliance infrastructure behind COR engagements, supports IR35 determination in the UK, independent contractor classification in the US, and local employment status tests across APAC and EMEA.
• We handle employing workers directly on clients’ behalf through EOR where no legal entity exists, managing local payroll, statutory benefits and employment law compliance.
• CXC can run COR, AOR, and EOR within one governance framework, avoiding the fragmentation that comes from using separate providers for different engagement types.
• CXC has in-country compliance teams (not just technology) supporting reliability across complex and shifting regulatory environments.
• A single audit trail and point of accountability across the full contingent workforce, regardless of engagement type or country

Organisations that build their contingent workforce model on a clear, compliant foundation (the right model applied to each worker type) are better placed to scale globally without accumulating misclassification risk or compliance debt as programmes grow.

CXC’s Contractor of Record and Agent of Record services

CXC acts as the Contractor of Record for clients engaging independent contractors across the UK, EMEA, APAC, and the Americas. 

We manage contract execution, IR35 or local classification determination, compliance verification, invoice processing and payment. CXC Comply underpins these engagements with audit-ready classification documentation and risk mitigation for clients operating in high-scrutiny jurisdictions.

This is backed by in-country compliance teams, not just platform technology, which is exactly what makes COR arrangements hold up across genuinely complex regulatory environments. 

CXC’s work with RELX Group is a useful illustration of what compliant, at-scale contractor management delivers in practice: annual cost savings of over £275,000 and average savings of 38% per worker, alongside enhanced compliance and governance controls.

CXC’s Employer of Record services for global talent

Where a worker can’t or shouldn’t be engaged as an independent contractor, CXC provides EOR services across 100+ countries. This means employing workers on clients’ behalf and managing local payroll, statutory benefits, employment tax and compliance with local employment law. 

The model runs on CXC’s own in-country legal entities and local compliance expertise, rather than a network of third-party partners, which supports greater consistency and accountability than aggregator-model EOR providers.

Because CXC delivers both COR and EOR within a single service model, clients can apply the right structure to each worker type without switching providers or fragmenting workforce governance across their programme.

Building a compliant global workforce engagement framework with CXC

Different workers in different jurisdictions need different engagement models, and applying the wrong one creates compliance risk that compounds over time. 

CXC’s integrated COR, AOR and EOR model lets organisations manage their entire contingent workforce (from independent contractors in the UK and US to employed workers in markets without a client entity) within a single governance framework, with consistent compliance standards and one point of accountability.

With over 30 years of experience and operations across 100+ countries, we provide the compliance expertise, in-country infrastructure and service model that global organisations need to engage contractors, freelancers and global talent correctly, regardless of jurisdiction, engagement type or workforce complexity. 

Getting the right model in place for every worker type now is what keeps a growing global workforce clear of misclassification liability, tax exposure and compliance debt later. Reach out to the team at CXC today.

Frequently Asked Questions

Share to:

Wish your contractor management was less… messy?

At CXC, we simplify the way you manage your contingent workforce. From contractors and SOW to EOR/AOR, our flexible solutions handle compliance, payroll, and onboarding, so you can focus on scaling, not red tape.

Speak to our team

Share