Argentina 
Brazil 
Mexico 
Colombia 
Permanent establishment (PE) risk is the risk that your company becomes taxable in another country because of the work your people do there. For US companies hiring remote developers abroad, it’s one of the questions finance and legal teams ask first, and one of the least understood.
The good news is that writing code from a home office rarely creates a permanent establishment on its own. The risk grows when remote staff sign contracts, manage local operations or work under an arrangement that looks like a local branch of your business.
In this guide, we explain what a permanent establishment is, how remote developers can trigger one, and how each hiring model changes your exposure. We also look closely at Latin America, where many US companies build their engineering teams and where the tax treaty map matters most.
What Is a Permanent Establishment?
A permanent establishment is a taxable presence of a foreign company in another country. Once a company has one, that country can tax the profits connected to the activities carried out there.
Most tax treaties follow the definition in Article 5 of the OECD Model Tax Convention, which describes two main ways to create a PE:
- A fixed place of business: an office, branch or other location at the company’s disposal, used regularly to carry out its business.
- A dependent agent: a person who habitually concludes contracts, or plays the principal role in concluding them, on the company’s behalf.
Countries without a treaty with the US apply their own domestic rules, which can be broader than the OECD definition.
Why Permanent Establishment Matters for US Tech Companies
A permanent establishment turns a remote hire into a local tax issue. If a country decides your company has a PE there, the consequences go well beyond payroll:
- Corporate income tax on the profits attributed to that country.
- Registration, local bookkeeping and annual tax filings.
- Indirect taxes, like VAT, on certain services.
- Penalties and interest if the PE is discovered years later.
- The risk of double taxation when there’s no treaty to resolve it.
For a company that only wanted to add a few engineers, an unplanned PE can cost more than the hires themselves.
How Remote Developers Can Create a Permanent Establishment
Most remote developers create little PE risk, because writing and reviewing code doesn’t involve signing contracts or running a local business. The risk usually comes from four situations:
- A home office at the company’s disposal. The OECD considers that a home office can become a PE when it’s used continuously for the business and the company requires the employee to work from there.
- Authority to sign contracts. A developer who negotiates or signs agreements with local clients can act as a dependent agent.
- Local management roles. Titles like “country manager” or responsibility for local operations make a business presence more visible.
- Long-term services to local clients. Some countries treat services provided locally over long periods as a taxable presence.
During the pandemic, the OECD clarified that temporary remote work from home should not create a permanent establishment, but that a permanent change in working arrangements requires reviewing the facts and circumstances. For long-term remote hires, that review is now the rule, not the exception.
Tax Treaties: Why the Country Matters
Whether a US company has a PE in another country depends heavily on whether the US has an income tax treaty with it. Treaties usually follow the OECD definition and protect business profits unless there’s a clear permanent establishment. Without a treaty, local law decides, and it can be stricter.
For US companies hiring engineers in Latin America, the split is clear. Mexico and Chile have a treaty with the US. Brazil, Argentina and Colombia, three of the most common countries for hiring engineers in the region, don’t.
| Country | US income tax treaty | What it means for PE risk |
|---|---|---|
| Mexico | Yes | The treaty definition applies, based on the OECD model |
| Chile | Yes | The treaty definition applies, based on the OECD model |
| Brazil | No | Local rules apply, so review each arrangement carefully |
| Argentina | No | Local rules apply, so review each arrangement carefully |
| Colombia | No | Local rules apply, so review each arrangement carefully |
The IRS keeps the official list of US income tax treaties, which is the place to confirm the status of any country before you hire there.
How Your Hiring Model Affects PE Risk
The way you hire abroad changes who has the legal and tax presence in each country:
| Hiring model | Who has the local presence | PE exposure for your company |
|---|---|---|
| Your own local entity | Your subsidiary | Intended and managed: the subsidiary pays local taxes |
| Independent contractors | Nobody, they are self-employed | Usually low, but misclassification and dependent-agent risk remain |
| Employer of Record | The EOR employs the worker | Reduced, but what the worker does for you still matters |
| Staff augmentation | The staffing partner employs and manages the engineers | Generally the lowest, because you buy services from a partner |
An EOR solves employment, not every tax question. An Employer of Record becomes the legal employer, but if the person signs contracts for your company or runs local operations, the PE analysis can still point back to you.
What PE Risk Looks Like When You Hire Developers in Latin America
Latin America is where many US companies build remote engineering teams, thanks to time-zone overlap with the US and a deep pool of senior engineers. It’s also where the treaty map matters most. In Brazil, Argentina and Colombia, local rules decide whether your activity creates a taxable presence, and they can reach further than the OECD model.
That is why most US companies avoid direct, informal arrangements in the region. Instead, they work through a structure that is already established in each country:
- Staff augmentation. The partner employs, pays and manages the engineers locally, and your company buys a service. The engineers work on your product and your schedule, but the local presence is the partner’s.
- Employer of Record. The provider employs the engineer for you, while day-to-day management stays with your team.
- Your own entity. It makes sense once a team is large and long-term enough to justify local incorporation, accounting and tax filings.
For a team of developers who write code and report to US managers, staff augmentation keeps your company’s footprint in each country to a minimum. You also avoid managing a different set of local rules in every country where you hire.
How to Reduce Permanent Establishment Risk
A few practices keep PE risk low when you hire developers abroad:
- Keep contract authority in the US. Remote engineers shouldn’t negotiate or sign agreements on your company’s behalf.
- Avoid local management titles unless you plan to have a local presence.
- Don’t rent or provide a local office for your remote team.
- Keep key business decisions in the US, and document where they’re made.
- Hire through a local employer, like an EOR or a staffing partner, instead of setting up informal arrangements. In Latin America, choose one that is already established in each country where you hire.
- Track headcount and roles by country, and review them with a tax advisor as the team grows.
These practices also protect you from the related risk of treating long-term workers as contractors, which can lead to employee misclassification penalties on top of tax exposure.
Do Remote Developers Put Your Company at Tax Risk?
For most US companies, remote developers create low PE risk, as long as they write code and don’t run your business locally. The risk grows with contract authority, local management and informal arrangements, and it’s higher in countries without a US tax treaty.
In Latin America, where Brazil, Argentina and Colombia have no US tax treaty, working through a partner established in each country is the simplest way to keep that exposure low. Every arrangement still depends on its facts, so review yours with a qualified advisor.
Want to build an engineering team in Latin America without taking on local compliance? Learn how IT staff augmentation with BEON.tech lets you add senior engineers while the partner handles employment in each country.
