What a Contractor of Record actually does
When you engage a COR, you are not hiring the contractor directly. Instead, a three-party arrangement takes shape: your company (the client) contracts with the COR provider, and the COR contracts with the individual contractor. The contractor invoices the COR, the COR invoices you, and the COR manages every compliance and payment obligation in between.
Key responsibilities the COR takes on include:
- Onboarding: Collecting identification, tax registration documents, work permits, and banking details in the contractor's country.
- Localized contracts: Drafting agreements that reflect the contractor classification rules of the specific jurisdiction, not just a generic template.
- Payment processing: Paying the contractor in local currency, handling any required withholding, and issuing the correct tax documentation (1099, self-billing invoice, local equivalent).
- Ongoing compliance monitoring: Tracking regulatory changes that could affect classification status or payment obligations.
- Liability absorption: Assuming responsibility for misclassification claims that arise from the engagement.
Your company keeps day-to-day operational control: you assign work, set deliverables, and evaluate performance. The COR handles everything behind the scenes that keeps the arrangement legal.
Why contractor classification is harder internationally
In the United States, the IRS and the Department of Labor each have their own tests for distinguishing employees from independent contractors. That is already complex enough. Cross a border and the rules change entirely.
A few examples of how classification differs by country:
| Country | Classification framework | Key risk factor |
|---|---|---|
| Germany | "Scheinselbstständigkeit" (false self-employment) rules | Working for a single client over time strongly implies employment |
| Spain | TRADE status for economically dependent contractors | Earning more than 75% of income from one client triggers special protections |
| Australia | Multi-factor common law test plus evolving statutory definitions | Recent High Court decisions have tightened the definition of contractor |
| Canada | Province-by-province common law tests | Quebec applies civil law, creating additional divergence from other provinces |
| Brazil | Consolidation of Labor Laws (CLT); "pejotização" scrutiny | Any sign of subordination or exclusivity risks reclassification |
| UK | Three-tier system: employee, worker, self-employed; IR35 for off-payroll rules | IR35 shifts liability to the end client for medium and large businesses |
A COR with genuine in-country expertise - not just a template contract - knows these distinctions. That is the core value proposition when hiring internationally.
COR vs. EOR vs. AOR vs. PEO
These four service models are often confused because they all involve a third party managing workforce compliance. The difference comes down to who the worker is and what legal status they hold.
| Model | Worker type | Employment relationship | Best used when |
|---|---|---|---|
| Contractor of Record (COR) | Independent contractor | Contractor remains self-employed; COR is contracting entity | Short-to-medium engagements where contractor status is genuinely appropriate |
| Employer of Record (EOR) | Employee | EOR is the legal employer; full employment rights apply | Long-term workers or jurisdictions where contractor classification is not viable |
| Professional Employer Organization (PEO) | Employee | Co-employment; client company must have its own local entity | Domestic HR outsourcing for companies that already have a legal presence |
| Agent of Record (AOR) | Independent contractor | No employment relationship; AOR acts as paying agent | Managing invoices and payments for contractors who are already properly classified |
The critical distinction between a COR and an EOR is not just administrative - it is legal. An EOR converts the worker to an employee, triggering statutory benefits, notice periods, severance obligations, and social contribution requirements. A COR preserves contractor status, which means none of those entitlements apply, but classification must be genuinely defensible. If the work arrangement looks and feels like employment, a COR does not make it legal; it just adds a layer of paperwork to an already risky situation.
Some EOR providers also offer a COR service for clients who have a mix of contractors and employees in the same country. That can simplify vendor management, but verify that the provider has real local legal expertise for contractor classification and is not simply relabeling its EOR product.
Where COR works well internationally - and where it does not
A COR is most effective when the underlying contractor relationship is genuinely independent: the person sets their own hours, works for multiple clients, uses their own tools, and delivers defined outputs rather than ongoing services under supervision.
Situations where a COR adds clear value:
- Engaging a software developer in Poland for a fixed six-month project while they also work for other clients.
- Paying a marketing consultant in Singapore on a retainer for defined deliverables.
- Onboarding a short-term data analyst in Canada without establishing a Canadian entity.
- Scaling a contingent research team across multiple countries for a defined product launch.
Situations where a COR creates more risk than it removes:
- The worker will work exclusively for your company for an extended period - in many countries, exclusivity is one of the clearest markers of employment.
- The work involves ongoing, open-ended tasks rather than defined deliverables.
- You will be directing when and how the work is done, not just what the output should be.
- The country has near-automatic employee status rules for anyone working primarily for one company (Germany and Spain are common examples).
In these cases, the right answer is usually an EOR, not a COR. Using a COR to paper over what is functionally an employment relationship does not eliminate the risk; it may actually concentrate liability because the COR will have assumed legal responsibility for a classification that cannot be defended.
What to look for in a COR agreement
COR agreements govern a three-way relationship, so they are structurally different from a standard services contract. Before signing, review these areas carefully:
- Indemnification scope: The COR should indemnify your company against misclassification claims that arise from how the COR structured the engagement. If the indemnification is narrow or carved out for situations where you directed the work, you retain more liability than you may realize.
- Intellectual property assignment: Since the COR is the contracting entity, the default IP ownership may sit with the COR or the contractor unless the agreement explicitly assigns it to your company. Confirm that work-for-hire provisions are enforceable in the relevant jurisdiction.
- Local law compliance representations: The COR should explicitly warrant that its contractor agreements comply with local classification rules, not just that it will make reasonable efforts to comply.
- Fee structure transparency: Understand whether fees are a percentage of contractor compensation, a flat monthly amount, or a combination. Watch for setup fees, currency conversion margins, and charges for services you assumed were included.
- Geographic coverage: Some COR providers have strong coverage in North America and Western Europe but use subcontractors or partners in other regions. Ask directly whether the provider operates its own legal entities in the countries relevant to you.
- Termination and transition: Confirm the notice period required to end the engagement and what happens to ongoing contractor relationships during a transition to a new provider or to direct contracts.
Who benefits most from a COR arrangement
COR services are not universally useful. They make most sense for specific organizational situations:
- Companies running project-based work across multiple countries who cannot justify the cost and time of establishing legal entities in each market.
- Fast-growing startups that need to engage specialized technical or creative talent globally before their HR infrastructure can handle cross-border compliance.
- Enterprises managing a large contingent workforce who need standardized onboarding, payment, and classification processes rather than managing each engagement ad hoc.
- Companies operating under IR35 in the UK, where the end client bears responsibility for correct off-payroll determination and a COR can provide a documented compliance framework.
Companies with small contractor numbers, stable and local-only operations, or workers who clearly meet the employment test in their jurisdiction will find COR fees add cost without proportionate compliance benefit.
COR and misclassification risk: what the arrangement actually protects
A well-structured COR arrangement shifts legal employer liability to the COR. That is meaningful protection, but it is not unconditional. Most COR providers include clauses stating that their indemnification does not cover situations where your company behaved in a way that created the misclassification - for example, by controlling the contractor's schedule, requiring exclusivity, or integrating them into your organizational structure as if they were an employee.
The practical takeaway: a COR reduces compliance burden and provides a legal buffer, but it does not transform an employment relationship into a contractor relationship by paperwork alone. Before engaging a COR, assess whether your intended working arrangement is genuinely consistent with contractor status in the specific country involved. If there is real doubt, an EOR is the more defensible route.
