A foreign employer usually structures the relationship one of three ways: a direct contractor agreement paid by bank transfer, formal employment through…
Key takeaways
- A foreign employer usually structures the relationship one of three ways: a direct contractor agreement paid by bank transfer, formal employment through an Employer of Record, or an engagement run through a contractor platform that sits between both sides.
- Getting paid across a border is rarely free even when the transfer shows no listed fee: most of the real cost sits inside the exchange rate the money is converted at.
- Paperwork depends on who is paying. A US company collects a tax form before the first payment; a company based elsewhere usually needs proof that the developer is registered as self-employed and an invoice that matches the developer’s own country’s rules.
- A contractor agreement on paper and a genuine contracting relationship in practice are two different things — the second is judged by how the work is actually managed day to day.
A backend developer in Skopje or Sarajevo answers a message from a recruiter working for a company hiring in London or Berlin. The interview goes well, an offer follows within days, and then the practical question arrives on both sides at once: how does a company with no legal entity anywhere near the Western Balkans actually pay someone who lives there, and what paperwork is supposed to travel alongside the money.
The finance lead who signs off on that offer usually has three ways to structure it: a direct contractor agreement settled by bank transfer, a formal local employment contract arranged through an Employer of Record, or an engagement run through a contractor platform such as 4dev that sits between the company and the developer and handles the paperwork on both sides. Which one gets chosen shapes almost everything that follows — who the developer’s actual counterparty is, which documents show up and when, and who answers for the arrangement if it is ever questioned.
Why foreign companies hire in emerging markets
Two things usually justify the extra paperwork of hiring across a border: the skill is available at a competitive rate, and it is available now, at a moment when the same skill is scarce at home. Software development sits squarely in that category. Demand for backend, mobile and data engineers has outpaced local supply across most of the US and Western Europe for years, and remote-first hiring norms since the pandemic made a developer’s location far less central to how a project actually runs day to day.
Cost plays into the decision too, although the mechanism is often misunderstood. Salary alone does not make employing someone directly expensive; the statutory cost layered on top of it does. The OECD’s Taxing Wages review puts the average tax wedge on a single earner at close to 35% of total labor costs across its member countries, and the employer’s own share of that wedge varies sharply by country. In Germany, employer social contributions alone add a little over a fifth of gross pay, plus employer-only accident insurance. In Brazil, once the FGTS severance fund is counted, employer contributions run to roughly 35% of pay, and that share is uncapped as salary rises, unlike the employee side. None of this touches what the developer takes home. It sets what it costs the company to run someone through full local payroll, and that gap is a large part of why a first cross-border hire so often starts as a contracting arrangement, long before anyone considers opening local payroll.
The Western Balkans and comparable emerging-market regions fit the same pattern that applies anywhere with a strong technical education base and a lower cost of living than the hiring company’s home market. The developer competes on skill against candidates the company could hire locally; the engagement structure competes against the cost of setting up and running payroll in a country the company has no other presence in.
The contract types a developer will be offered
Most offers arriving from abroad fall into one of a small number of shapes, and it is worth knowing which one is on the table before the details of pay come up at all.
- Direct independent-contractor agreement. The developer invoices the company directly and is paid by bank transfer. This usually means registering locally as self-employed first — the label varies by country (PFA in Romania, paušalac in Serbia, PJ in Brazil), but the underlying requirement is the same: the developer needs a status that lets them issue a valid invoice, and the company needs to be able to show that status on file.
- Employment through an Employer of Record. A local or regional entity formally employs the developer, runs payroll and statutory withholding, and the foreign company directs the work under a services agreement with that entity. The developer gets a payslip and local employment protections, and the foreign company never opens its own entity.
- Engagement through a contractor platform. Both sides sign with a platform that formalizes the engagement, checks the developer’s documents, and handles invoicing and payment, and the relationship remains a contractor relationship. The administration around it — contracts, documents, invoicing — sits in one place on the platform. 4dev.com works this way: it describes itself as a Contractor Platform running a Contractor of Record model, with contractors self-onboarding through a document check and a single agreement covering all of a company’s contractors regardless of where they are based, across more than 150 countries. It stays in the contractor lane specifically — no Employer of Record option and no payroll for staff employees, with an Employer of Record product only planned for 2027.
- Subcontract through an agency or local studio. Less common for an individual hire, but frequent for teams: a local development shop bills the foreign client and pays the developer as its own contractor or employee, one layer removed from the end client.
Which of these options gets used depends on how many people the company is hiring in the region, how long the engagement is expected to run, and how much day-to-day management the company wants to do itself.
How the money arrives and what documents come with it
Bank transfer remains the standard rail for this kind of cross-border business payment, and the documentation around it depends heavily on which country is paying.
On cost: a cross-border business payment is rarely free even when the transfer itself shows no listed fee. The Financial Stability Board’s 2025 review of G20 cross-border payment costs found the average total cost of a business payment running close to 1.6% of the amount sent, and about seven-eighths of that — roughly 1.4 percentage points — sits in the exchange-rate margin baked into the conversion itself. Visible fees tend to shrink as the payment size grows; the FX margin holds steady, staying in a 0.7–1.1% band across most payment sizes. The same review found the regional spread runs from about 1% in Europe to as much as 3.5% in parts of sub-Saharan Africa. Personal remittance apps quote a different figure entirely, measuring a different kind of transfer, and that number does not carry over to business payments.
On documents, the paying company’s own country sets the rules:
- A US company collects a Form W-9 from a US person or a W-8BEN (individual) or W-8BEN-E (entity) from a foreign one, before the first payment goes out. A W-8BEN expires at the end of the third calendar year after it is signed and needs renewing. Since January 1, 2026, a US business only needs to issue Form 1099-NEC once payments to one contractor pass $2,000 in a calendar year, a threshold that replaced the long-standing $600 marker and now also governs when backup withholding kicks in. Compensation is generally sourced to where the work is physically performed, so a developer doing all the work from outside the US typically triggers no 1099 and no withholding at all, provided the company holds a valid W-8 form on file. Without that documentation, the default is withholding: 24% backup withholding, or 30% on a foreign payee.
- A company based outside the US paying a contractor abroad is usually handling cross-border B2B services under the reverse-charge mechanism where EU VAT rules apply: the VAT liability moves to the paying business, and the paperwork exists on both ends either way. The invoice itself has to satisfy the developer’s own country’s requirements, which is one more reason the developer’s local registration status matters to the payer as much as to the developer.
What the developer should check before signing
- Who the actual counterparty is. A direct client, an Employer of Record, and a contractor platform are three different legal relationships, each with a different answer to who to ask if a payment doesn’t arrive.
- How the exchange-rate cost shows up. Since most of the real cost of a cross-border payment is in the exchange rate itself, the number worth asking about is the effective rate on the day of the transfer, not only the fee line.
- Whether local self-employed registration is required, and whether the invoice format the company expects lines up with what is actually valid at home.
- Whether documents are generated automatically or have to be requested by hand — a contract, an invoice for payment, and a record a developer can produce later if a bank or tax office asks for one.
- Who owns the code being written. A services agreement should state clearly whether rights to the work transfer to the client and at what point, something worth confirming before starting rather than after the project ships.
What the company should check before paying
- Whether the relationship, in practice, resembles employment. Classification rules differ by country, but they tend to weigh the same signals: does the company dictate the schedule and the method of work, is the developer using the company’s own tools and systems, is the person folded into the team the way a staff member would be, is the arrangement exclusive to this one client, and has it been running long enough to look like a permanent fixture on the team. Calling the arrangement a contractor agreement carries little weight against that pattern on its own.
- Whether the arrangement creates a taxable presence in the developer’s country. No engagement model removes this risk on its own; it depends on what the person is actually doing there, such as habitually concluding contracts on the company’s behalf, and that has little to do with which paperwork sits on top of the relationship.
- Whether the required paperwork is actually on file, beyond a mention in a contract clause: a signed W-9 or W-8BEN before the first US payment, or evidence of self-employed registration and a compliant invoice where the payer sits outside the US.
- Whether a contractual indemnity is being mistaken for protection against the tax authority itself. An indemnity clause is a claim against whichever party promised it. It settles who pays afterwards between the two parties; it does nothing to stop a tax authority or labor inspector from acting in the first place.
FAQ
Does a developer need to be a registered business to get paid by a foreign company? In most cases, yes. Self-employed registration is usually a precondition for issuing a valid invoice, and the category has a different local name almost everywhere — PFA in Romania, paušalac in Serbia, PJ in Brazil — but the underlying requirement is consistent: without it, there is no document the paying company can rely on.
Why does the exchange rate matter more than the transfer fee? Because it usually is the larger part of the cost. Global data on business cross-border payments puts the FX margin at roughly seven-eighths of the total cost of a typical transfer, baked into the rate itself rather than listed as a separate charge. A transfer advertising no fee at all can still end up costing more than one with a small listed fee that converts at a better rate.
Does signing a contractor agreement automatically protect both sides from misclassification risk? No. What decides that question is how the relationship actually runs day to day — who directs the work, whose systems are used, how exclusive and long-running it is. A well-drafted agreement documents the arrangement; it is evidence for that question, and nothing about a signature turns it into a guarantee.