What documentation should we maintain to support our contractor versus employee classification decisions?

Your contractor in Germany just got flagged in an internal audit. The contract says "independent contractor," but the reality looks different: fixed hours, company laptop, integrated into the team Slack, and no other clients. Now you're scrambling to find the original classification rationale, and it's scattered across three systems with no clear decision trail.

This scenario plays out constantly in mid-market companies managing international teams. The contract alone won't protect you. Courts and regulators across the UK, EU, and US evaluate the reality of the relationship, not the labels you've applied. A classification decision that relies only on a template contract is routinely undermined in disputes because regulators weigh operational evidence over documentation labels.

Teamed's work with companies across 70+ countries shows that a defensible contractor classification file typically includes at least 12 distinct document types. Most organisations have fewer than half of these, stored in disconnected systems that make audit response slow and error-prone. Here's what you actually need to maintain, and how to structure it so you're ready when questions arise.

The Documents Auditors Actually Come Back For

HMRC can assess underpaid PAYE and National Insurance for up to 6 years in most cases, and up to 20 years where deliberate behaviour is involved, while deemed employers must keep PAYE records for 3 years from the end of the tax year.

UK companies classified as "medium or large" under the Companies Act 2006 must determine IR35 status for contractor engagements, using thresholds of more than 50 employees, more than £15 million turnover, or more than £7.5 million balance sheet total.

The IRS generally recommends keeping employment tax records for at least 4 years after the tax becomes due or is paid.

In Europe, the longer a contractor works for you, the bigger the backdated bill gets. We're talking unpaid social contributions, holiday pay, notice periods, termination protections. It adds up fast, and not in a straight line.

Every time you extend a contractor, they look a bit more like an employee. That's why we insist clients reassess at every extension, or at least every 6-12 months. Because drift happens gradually, then suddenly.

You know how it goes: contracts in HRIS, SOWs in SharePoint, invoices in the finance system. When an auditor gives you 48 hours to produce everything, you'll be chasing screenshots across Slack threads and hoping nothing's missing.

What You Need Ready When Someone Challenges Your Classification

Documentation for contractor versus employee classification is the set of contemporaneous records that show how the engagement was structured and operated in practice. This includes independence indicators, contractual terms, and evidence of actual working arrangements throughout the engagement lifecycle.

The critical distinction here is between what you intended and what actually happened. A beautifully drafted contractor agreement means nothing if the operational reality shows the individual worked like an employee. Your documentation needs to capture both the initial classification decision and ongoing evidence that the relationship continues to operate as designed.

A worker status assessment is a written, role-specific analysis that maps the facts of an engagement to the status tests used by the relevant jurisdiction. In the UK, this means control, substitution, and mutuality of obligation. In Germany, it's scheinselbstständigkeit indicators like integration and dependency. In France, regulators look for subordination. Your documentation must address the specific tests that apply where your contractor works.

What Should Be in One Folder, Ready to Go

The signed contract and statement of work

Every contractor relationship starts with a contract, but the contract alone is insufficient. You need a statement of work (SOW) that defines scope, milestones, acceptance criteria, and change control. An SOW is deliverables-based and time-limited, which distinguishes it from an employment job description that defines ongoing responsibilities performed under managerial direction.

The SOW should specify what success looks like, how deliverables will be accepted, and what happens when scope changes. Open-ended "time and materials" arrangements without clear deliverables are weaker evidence of a genuine contractor relationship than project-defined work with measurable outcomes.

The status determination and rationale

Before engaging any contractor, document why this engagement qualifies as a contractor relationship rather than employment. In the UK, medium and large organisations must issue a Status Determination Statement (SDS) to the worker and relevant parties in the supply chain. This SDS should be retained with supporting evidence as part of your classification records.

Your status determination should address the specific factors relevant to your jurisdiction. For UK IR35 determinations, this means documenting evidence on control, substitution, and mutuality of obligation. The determination should explain how the relationship works in practice, not just reference contract clauses.

Proof of independent business activity

Contractors operate independent businesses. Your file should include evidence that demonstrates this: business registration documents, professional indemnity insurance certificates, evidence of other clients or active marketing, and documentation showing the contractor can realise profit or loss on the engagement.

This evidence matters because it distinguishes a genuine business-to-business relationship from disguised employment. If your contractor has no other clients, no business insurance, and no evidence of operating independently, regulators will question whether the relationship is genuinely commercial.

What to Save While the Engagement Runs (Before It Drifts)

Substitution right evidence

Substitution right evidence is documentation showing whether the contractor can send a substitute and whether substitution occurs in practice. This includes client acceptance criteria for substitutes and records of any substitutions attempted or completed.

The right to substitute is one of the strongest indicators of contractor status, but only if it's genuine. Document your policy on substitution, any instances where substitution was offered or occurred, and the process for approving substitutes. If you've never allowed substitution despite having a contractual right, that weakens your position.

Milestone acceptance and change control

Maintain records of deliverable sign-offs, milestone completions, and any change requests processed through formal change control. These records demonstrate that the relationship operates on a deliverables basis rather than through ongoing direction and control.

A well-governed contractor engagement differs from disguised employment because governance documents show milestone sign-off, change requests, and limited integration. Disguised employment shows line management, embedded team membership, and continuous duties without clear project boundaries.

Communication and integration evidence

Document how the contractor interacts with your organisation. Are they included in all-hands meetings? Do they have access to internal systems beyond what's needed for their deliverables? Are they managed through the same processes as employees?

Evidence of limited integration supports contractor status. This might include separate communication channels, restricted system access, exclusion from employee events and benefits, and clear boundaries around the contractor's involvement in your organisation.

Invoicing and payment records

Contractor invoicing records differ fundamentally from payroll records. Invoices demonstrate business-to-business billing for services, while payroll records evidence employer tax withholding, statutory deductions, and employee remuneration.

Maintain all invoices, payment records, and any correspondence about billing. The invoicing pattern should reflect the commercial nature of the relationship: invoices for completed work or milestones rather than regular salary-like payments.

The File You Can Hand Over Without Scrambling

One folder. One owner. Everything in it: the contract, your classification rationale, proof they're really independent, who approved what and when, plus updates every time you extended them. No hunting, no gaps, no panic.

Most top-cited guidance lists generic documents but fails to specify a dossier structure with version control, approval logs, extension reassessments, and a single source of truth across HR, Finance, and Legal. This gap creates real problems when audits occur.

What We Ask Clients to Pull Together First

Here's what belongs in that folder: the contract and SOW (obviously), proof they could send a substitute, their business registration and insurance, invoices that vary by deliverable, evidence they use their own tools, emails showing clear boundaries, milestone sign-offs, scope change approvals, and your reassessment notes every time you extended them.

You don't need elaborate systems to maintain these records. What matters is having them in one place, with clear version control, and accessible when needed. Many mid-market companies store contractor contracts in HRIS, SOWs in procurement systems, and invoices in finance platforms. This fragmentation increases audit response time and creates omission risk.

Who Signed Off, When, and Based on What

Every significant document should have version control showing when it was created, who approved it, and what changed between versions. This matters particularly for status determinations, which may need updating as the engagement evolves.

Approval trails demonstrate that classification decisions went through appropriate review. Document who made the determination, what evidence they considered, and when the decision was made. This contemporaneous record is far more valuable than reconstructing the rationale after a challenge arises.

Where Teams Get Caught Out: Every Country Has Different Hot Buttons

UK IR35 requirements

UK IR35 off-payroll working rules require medium and large organisations to issue a Status Determination Statement to the worker and relevant party in the supply chain. The SDS should explain the reasons for the determination and be retained with supporting evidence.

UK IR35 determinations are fact-specific and should be supported with evidence on control, substitution, and mutuality of obligation. HMRC and tribunals evaluate how the relationship works in practice rather than contract labels alone. Your documentation must demonstrate the operational reality, not just the contractual intention.

Europe: Where Independence Has to Be Visible

In the Netherlands, contractor status risk increases where there is an authority relationship and embeddedness, and from January 2026 the Dutch Tax Administration can impose culpability penalties and assess up to 5 years back in bad-faith cases. Classification documentation should explicitly evidence autonomy, non-integration, and business independence for Dutch engagements.

In Germany, misclassification risk is closely linked to scheinselbstständigkeit indicators such as integration into the client organisation and dependency. German-facing documentation should emphasise project scope, independence, and client non-control.

In France, regulators and courts can recharacterise contractor relationships when subordination is evidenced. French documentation should capture operational independence, deliverables-based acceptance, and absence of disciplinary control.

US: The Three-Bucket Test

The IRS uses a multi-factor test examining behavioural control, financial control, and relationship type. While the US generally has shorter retention requirements than Europe, maintaining records for at least 4 years after tax becomes due provides a reasonable baseline.

The IRS looks at three things: Do you control how they work or just what they deliver? Do they have real business expenses and other clients? Does the relationship look permanent (ongoing work, benefits, equipment provided)? Document evidence for all three.

GDPR: Your Classification File Is Basically a Mini HR File

Across EU and UK jurisdictions, GDPR applies to classification files that contain personal data, requiring organisations to respond to data-rights requests within 1 month. Worker classification documentation must be stored with defined access controls, a lawful basis for processing, and retention periods aligned to limitation periods and tax record requirements.

Most resources ignore GDPR and information governance for classification files. You need role-based access so only appropriate personnel can view contractor files, documented retention schedules, and clear processes for responding to data subject requests.

When the Risk Changes (Hint: Every Extension)

Extension and renewal triggers

Where a contractor engagement is renewed repeatedly, the probability of employee-like integration typically increases as tenure increases. Teamed recommends a documented reassessment at every extension and at least every 6-12 months for long-running engagements.

Each reassessment should evaluate whether the operational reality still matches the original classification. Has the scope expanded beyond the original SOW? Has the contractor become more integrated into your team? Are they still demonstrating independence through other clients or business activities?

Conversion trigger documentation

Most checklists don't include a conversion trigger pack for contractor-to-employee transitions. This is a frequent mid-market pain point in cross-border hiring. When you convert a contractor to employee status, you need documentation including a new role description, rationale memo, revised security access, revised equipment allocation, and backdated risk assessment.

Choose conversion from contractor to employee when the engagement crosses from deliverables-based work to an open-ended role with ongoing responsibilities and repeated extensions without a fresh SOW and reassessment. Document the decision and the factors that triggered it.

Why This Matters Beyond Compliance

Classification documentation isn't just about compliance defence. It's part of a broader strategy for managing how you engage talent internationally. Teamed's Graduation Model describes the natural progression companies follow as they scale international teams: from contractors to Employer of Record arrangements to owned entities.

At each stage, your documentation requirements shift. Contractor files focus on independence and deliverables. EOR arrangements require different documentation around the employment relationship. Entity employment brings full employment record requirements.

The right structure for where you are means matching your documentation practices to your current employment model while preparing for transitions. When contractor arrangements start looking like employment, you need documentation that supports either defending the classification or converting to a more appropriate structure.

Building your classification documentation system

Start by auditing your current state. Where are contractor contracts stored? Who maintains SOWs? Where do invoices live? Can you produce a complete file for any contractor within 24 hours?

Then establish a single dossier structure. This doesn't require expensive systems. A well-organised folder structure with clear naming conventions and version control can work. What matters is having everything in one place with clear ownership.

Build reassessment into your processes. Calendar reminders for periodic reviews, mandatory reassessment at every extension, and clear criteria for when a relationship needs fresh evaluation. The cost of proactive documentation is far lower than the cost of reconstructing records during an audit.

If you're managing contractors across multiple countries and finding that classification documentation is scattered, incomplete, or inconsistent, that's a signal to consolidate your approach. Book your Situation Room to review your current contractor arrangements and identify documentation gaps before they become compliance problems.