Key takeaways
- A distributed company runs two separate payment operations at once: payroll for employees under an employment contract, and payouts for contractors under a services agreement. They are two legal relationships, not two variants of one process.
- For employees abroad, the choice sits between opening a local entity, engaging an Employer of Record, or routing through a global payroll aggregator — and the employer’s real cost swings from a few percent of pay to well over a third, depending on the country.
- For contractors abroad, the choice is between paying invoices directly, with tax documentation collected and tracked in-house, or routing them through a dedicated contractor payment platform built for many countries at once.
- The most common failure is procedural: a contractor’s invoice gets paid on the same schedule, through the same system, as salaried staff. That is exactly the fact pattern a tax authority or labor inspector looks for first.
Picture a mid-size distributed company: employees on staff in three countries, contractors doing project work in twenty more, and one finance team responsible for paying both groups every month. The employees have offer letters, fixed salaries and withholding on every paycheck. The contractors have signed a services agreement, invoice for completed work, and get paid once an invoice clears approval. The two relationships are clear on paper. The two payment systems that carry them often are not.
That gap is the actual operating question a distributed company has to solve, and it splits into two decisions. On the employee side, the company chooses how to put someone legally on payroll in a country where it may have no entity at all. On the contractor side, it chooses how to get invoices paid across dozens of countries without an in-house team drowning in tax forms — settling them directly, or routing them through a contractor payment platform built to handle onboarding paperwork and cross-border payment for many contractors at once.
Two populations, two legal relationships
An employee works under a contract of employment: a fixed wage or salary, taxes withheld at source, and a set of statutory obligations — unemployment insurance, the employer’s own share of payroll tax — attached to the relationship itself. A contractor works under a services agreement: they invoice for a deliverable or a period of work, and nothing is withheld unless required documentation is missing.
Every worker-classification test used anywhere, however locally worded, comes back to the same questions: who controls the hours and method of the work, whose equipment and systems are in use, how integrated the person is into the regular business, whether the arrangement is exclusive, and how economically dependent the worker is on this one payer.
Enforcement of that line has been getting sharper across the jurisdictions distributed companies actually operate in. In the Netherlands, the moratorium on enforcing the Wet DBA classification rules ended on 1 January 2025, and penalties for intentional or grossly negligent misclassification became available from 1 January 2026.
There is a second, quieter risk sitting under the same set of facts: permanent establishment. Under Article 5 of the OECD Model Tax Convention, a company can create a taxable presence in a country through a fixed place of business, or through a person there who habitually concludes contracts on its behalf, or who habitually plays the principal role leading to contracts routinely signed without material change.
Paying employees abroad — the global payroll options
Once a company decides to put someone on staff in another country, it chooses among three structural options, and the choice carries a real cost difference, not just a speed difference.
Open a local legal entity.
- Who it fits: companies with enough headcount in one country to justify the setup, or ones planning to stay for years.
- What it involves: local incorporation, a local payroll registration, and either an in-house payroll run or a local payroll provider plugged into the company’s own systems.
- The tradeoff: full control over the employment relationship, at the cost of the time and expense of setting up and maintaining an entity before the first hire.
Engage an Employer of Record.
- Who it fits: a company hiring one or a handful of people in a country where it has no entity and does not plan to build one soon.
- What it involves: a third party becomes the legal employer of record in that country, running local payroll and statutory filings, while the company directs the person’s day-to-day work.
- The tradeoff: speed to hire without an entity. The arrangement does not by itself resolve the classification and permanent-establishment questions above; those turn on the actual working relationship.
Route through a global payroll aggregator.
- Who it fits: companies with employees already spread across several countries, some through their own entities, who want one interface and one reporting line instead of a different local payroll vendor per country.
- What it involves: the aggregator plugs into local payroll infrastructure, or partners with local providers country by country, while the company keeps its own entities where it has them.
- The tradeoff: consolidated reporting and a single point of contact, weighed against dependence on the aggregator’s own coverage and partner network in each new country.
Paying contractors abroad — the payout options
For the contractor population, the structural choice is narrower, but the paperwork load per contractor is real and easy to underestimate at scale.
Pay invoices directly.
- Who it fits: a company with a handful of contractors, or one already set up to collect and track tax documentation in-house.
- For a US payer: collect a W-9 from a US contractor, or a W-8BEN (individual) or W-8BEN-E (entity) from a foreign one, before the first payment, and keep it on file. Without valid documentation, the default is backup withholding — 24% for a US payee, 30% for a foreign one. A foreign contractor performing all services outside the US generally triggers no 1099 and no withholding at all, because compensation for services is sourced to where the work is physically done, provided the payer holds a valid W-8. A W-8BEN expires at the end of the third calendar year after it is signed, so a form valid at onboarding can lapse quietly two contracts later.
- For a non-US payer: cross-border business-to-business services typically fall under the reverse-charge mechanism, where the tax liability shifts to the buyer, plus whatever invoice format the contractor’s own country requires — Brazil’s nota fiscal has no direct English equivalent — and often evidence that the contractor is registered as self-employed under the local scheme (PFA in Romania, paušalac in Serbia, PJ in Brazil).
- The tradeoff: full visibility into every payment, at the cost of tracking dozens of documents by hand, each with its own expiry and its own local format.
Route through a contractor payment platform.
- Who it fits: a company paying contractors across many countries at once, where the paperwork load above stops being manageable in a spreadsheet.
- What it involves: contractors complete their own onboarding and document collection through the platform instead of a finance inbox handling each one manually, with payments and closing documents generated per contractor.
- The tradeoff: less manual document-chasing, weighed against dependence on the platform’s own country coverage and workflow rules.
4dev.com is one example of that second category: a Contractor Platform built for the contractor side, covering onboarding, documentation and payment across 150+ countries under a Contractor of Record engagement model, with contractors handling their own document flow instead of a client team collecting it inbox by inbox.
Where companies get it wrong
The most common mistake is mechanical: a contractor’s invoice gets processed through the same system, the same general-ledger codes and the same approval chain as salaried pay, because it is the path of least resistance for whoever is closing the books that month. The underlying relationship stays the same. The accounting record now tells a different story than the facts do, and a regular, fixed-schedule payment to someone the company calls a contractor is precisely the pattern a classification test weighs first.
A close second is treating an engagement model as a substitute for reviewing the actual relationship. Neither an Employer of Record nor a Contractor of Record arrangement removes permanent-establishment risk or misclassification risk on its own; both turn on what the person is actually doing day to day.
A combined operating model
Once a company has both populations, the fix is not one unified system: clear ownership, split between the two sides, with a point where they meet.
- HR / People team owns how to legally put someone on staff in a new country — entity, Employer of Record, or aggregator — and owns the employment contract itself.
- Payroll owns the pay cycle for employees: withholding, statutory filings, and the payslip and W-2 (or local equivalent) trail that goes with it.
- Finance / accounts payable owns the contractor side: invoice approval, tax-document collection at onboarding, tracking each document’s expiry, and booking contractor spend to its own general-ledger account, separate from salary expense.
- Legal / compliance owns periodic review of the classification factors and permanent-establishment exposure per country, treated as an ongoing check rather than a one-time setup step.
- A joint review, on a set schedule. HR, payroll, finance and legal look at both populations side by side and check for drift: a contractor paid on the same schedule as employees, a document past its expiry, a country where the working pattern has quietly changed.
That last point is what actually keeps the two systems from merging back into one by accident. Payroll and contractor payments can sit on separate rails for years and still end up looking alike on paper, if nobody is checking.
Article received via email
