How to Pay International Contractors: Workflow, Tax Forms, and Common Mistakes

In This Guide

Overview

The mechanics are easy. The compliance isn’t.

The mechanics of sending money to a contractor in another country are easy. Wise, Payoneer, Deel, Stripe Connect, even a wire from your bank — pick one and the money moves. The mechanics are not the problem.

The problem is everything around the payment: whether the worker should legally be a contractor at all, what tax documents you needed before the first dollar moved, what your reporting obligations are at year-end, and whether the workflow you’ve cobbled together holds up when you scale from two contractors to twelve.

Most companies don’t get any of this right on the first try. The penalties for getting it wrong are mostly latent — they don’t show up at the time of the mistake, they show up two years later when a contractor files for unemployment in their home country, or when the IRS sends a notice about un-reported foreign payments, or when a sharp acquirer’s diligence team flags 14 misclassified workers across 8 countries.

This is the workflow for not being one of those companies.

The Core Problem

The four risks, in the order they actually bite

Most contractor-payments content treats this as a payments problem. It isn’t. It’s four problems, and the payment is the last and easiest one.

Classification Risk

Is this person legally a contractor in their home country, or have you accidentally hired an employee? Most countries have stricter classification tests than the US. This is the highest-stakes risk and the one most companies skip past.

Tax Documentation Risk

Did you collect a W-8BEN before the first payment? Do you have a system for re-collecting it every three years? Missing documentation is a common audit trigger — either you have the form or you don’t.

Reporting Risk

US companies must file 1099-NEC for US contractors paid $600+ annually. Foreign contractors paid through a US entity may trigger 1042-S reporting if any work was performed in the US. Most companies don’t realize the second rule exists.

Payments Risk

Currency conversion costs, FX spread fees, payment delays, lost wires, and the operational mess of paying twelve contractors in eight currencies. This is the one most companies focus on first — and the least important — but it creates the most friction at scale.

These are sequential. You can have a flawless payment workflow and still get destroyed by a misclassification claim. The order matters.

Highest-Stakes Risk

Classification: the part everyone underdoes

The single most expensive mistake in international contractor relationships is treating someone as a contractor when their home country considers them an employee. Most countries — Germany, France, Brazil, Spain, the UK, the Netherlands, India, Japan — have classification tests stricter than the US, with sharper teeth on the employer.

The general principle is the same everywhere: if the worker has set hours, uses your equipment, works exclusively or near-exclusively for you, takes direction on how the work gets done (not just what gets done), and has been engaged for an extended period, they are probably an employee under local law regardless of what the contract says.

The penalties when this gets caught typically include:

Back-payment of social contributions and payroll taxes for the entire period of misclassification (often 3–7 years retroactive depending on country)
Employer-side penalties (often 50–200% of the unpaid amount)
Severance the worker would have been entitled to as an employee
Interest — and in some jurisdictions, criminal liability for company directors

The practical rule: if you’ve been paying someone in another country for more than six months, they work for you full-time or near-full-time, and you’re treating them as a contractor — you almost certainly have a problem. The fix is to convert them to an employee, which in a country where you don’t have an entity means using an EOR.

The harder version: if you’re about to engage a new international contractor and the relationship will look like employment from day one, you should be using an EOR from day one. Hiring them as a contractor first to “see how it goes” creates the exact problem you’re trying to avoid.

Tax Forms

Tax documentation: collect before you pay, not after

Two forms cover most of the workflow.

Form

When to Use

W-9

US-based contractors, including US citizens and permanent residents living abroad. Collect before the first payment. Required to issue 1099-NEC at year-end when the contractor is paid $600 or more in a calendar year.

W-8BEN

Non-US contractors who are individuals. Collect before the first payment. Certifies the contractor is a foreign person and claims treaty benefits. Valid for three years after the year signed — re-collect after that.

W-8BEN-E

Non-US entities (the contractor’s company, if they’re invoicing through an LLC equivalent). Same logic as W-8BEN but for entities. If the contractor refuses to provide the form, the default rule is 30% withholding on US-source payments.

The mistake most companies make is treating these forms as paperwork instead of as part of the onboarding workflow. The form should be collected at the same time you’re agreeing on rates and payment cadence — not three months in when finance asks “wait, do we have a W-8 for this person?”

The clean version of this workflow: no first invoice gets paid until the form is on file. Treat it like a contract signature.

Year-End Reporting

Reporting: 1099-NEC for US, mostly nothing for foreign

For US contractors, 1099-NEC reporting is straightforward: any contractor paid $600 or more in a calendar year, file 1099-NEC by January 31 of the following year, send a copy to the contractor and the IRS.

For foreign contractors paid for work performed entirely outside the US, you generally do not need to file anything with the IRS. The W-8BEN you collected is the documentation that supports treating these as non-reportable foreign-source payments. Keep the form on file.

The exception: if any of the work was performed inside the US (the contractor came to a conference you paid them for, or did a stint in your office), the portion of the payment attributable to US-source work may require 1042-S reporting and possibly withholding. This is rare for genuinely remote contractors but worth flagging for finance teams that have contractors who travel to the US for work.

State-level 1099 obligations vary. A handful of states (California, New York, others) have separate filing requirements. Your accounting platform usually handles this if it’s set up correctly; worth confirming once and forgetting about.

Operational Risk

Payment rails: where the money actually leaks

This is where the operational pain is, even though it’s the lowest-stakes of the four risks. The standard options:

Rail

Notes

ACH / Wire

Cheap for US contractors; slow and expensive internationally ($25–45/wire + 2–4% FX spread baked into the bank rate). Fine for one or two payments. Meaningful spread costs at volume.

Wise / Payoneer

Better FX rates (0.4–1% spread). Fine for under five contractors. Manual per-payment workflow becomes painful past ten.

Stablecoin

USDC/USDT — near-zero fees, same-day settlement. Popular in LatAm, Southeast Asia, parts of Africa. Tax treatment varies by local jurisdiction; contractors need to understand the implications.

Contractor Platforms

Deel, Remote, Niural — bundle payment rails with documentation, classification, and reporting. More expensive per payment ($49–79/contractor/month) but cheaper than running the workflow yourself past ~five contractors.

The wrong answer is to keep running everything through manual wires past the point where the operational overhead exceeds the cost of using a platform.

Step by Step

The actual workflow

For a company paying anywhere from one to fifty international contractors, the workflow that holds up looks like this:

Onboarding (per contractor, one time)

Determine classification before drafting the contract. If the relationship will look like employment, use an EOR instead of a contractor agreement. Don’t kick the can.
Sign the contract. Specify scope, payment terms, currency, and payment cadence. Avoid language that implies employment (set hours, exclusivity, equipment provided by you).
Collect tax documentation. W-9 for US, W-8BEN for individuals abroad, W-8BEN-E for entities abroad. No payment until the form is on file.
Add the contractor to your payments system. If using a platform, this is one workflow. If running rails directly, this is the contractor’s banking details, Wise account, or wallet address.

Recurring (per payment)

Receive invoice. Verify it matches the contract scope and rate. Verify currency.
Run the payment through your platform or directly through the rails you’ve chosen.
Reconcile in your accounting system. The expense should hit the right cost center, project, or department — not just “contractor payments.”

Annual

Issue 1099-NEC for US contractors paid $600+ during the year, by January 31.
Re-collect W-8BEN forms that have aged past three years.
Audit the contractor list. For each one: is this still a contractor relationship by local-country standards, or has it drifted into employment? If drift, convert.

The annual audit is the step most companies skip. It’s also the step that prevents misclassification claims from compounding for years before anyone notices.

Long-Term Thinking

When contractors should become employees

The trigger is rarely a single event. It’s an accumulation of facts: the contractor has been engaged for over a year, works exclusively for you, has set hours, uses your tools, has direct reports or reports to a manager, attends company meetings, takes vacation that you approve. Past a certain threshold — which varies by country but is usually crossed faster than companies realize — the legal status flips even if the contract still says “contractor.”

When that happens, the conversion is to an employment relationship. In a country where you don’t have an entity, that means an EOR. In a country where you do, that means moving them to your direct payroll.

The architectural advantage of running contractor payments and EOR through the same system is that this conversion stops being a migration. The contractor’s record, payment history, and tax documentation already live in the system; flipping them to an employed status is a workflow change, not a vendor change. For companies handling these on different systems, the same conversion involves exporting data, re-onboarding the worker on the new vendor, and reconciling the transition month manually.

A contractor base that will eventually convert to employees should sit on infrastructure that supports that conversion. A contractor base that’s genuinely transactional (project-based, multiple-client, short-engagement) doesn’t need this and can run on simpler tooling.

For most growth-stage companies hiring distributed talent, it’s the first situation. Plan accordingly.

FAQs

What tax form do I need from a foreign contractor?

Do I need to file a 1099 for a foreign contractor?

What's the cheapest way to pay an international contractor?

Can I pay an international contractor in cryptocurrency?

When should an international contractor become an employee?

What happens if I misclassify an international contractor?

Disclaimer

This article is for informational purposes only and does not constitute legal, tax, or compliance advice. Companies should consult qualified advisors for guidance specific to their business and contractor relationships.

How to Pay International Contractors Without Creating a Compliance Mess