You found the Developer. Someone strong, based in Sao Paulo, at a rate well under the US equivalent, and they’ve accepted the offer. Then your Finance Lead asks the question no one on your team can answer: how do we actually pay this person?

It’s a fair question, and harder than it sounds. Paying a Developer in Brazil means paying in reais, on the schedule Brazilian law sets, with the right taxes withheld, inside currency rules nobody on your team has read. A wire from a US bank account doesn’t cover it, and usually isn’t even legal.

Companies plan for recruiting, but this is another matter entirely. Payroll, tax, and the legal machinery behind a foreign hire tend to surface only after the offer’s signed, and by then they’re yours.

So, when you hire across a border, you’re not just adding an Engineer. You’re taking on seven compliance obligations at once. A staffing partner that handles payroll and compliance carries those seven for you, so you can hire the remote LATAM developer you want, fully compliant and under US law.

This guide walks through all of them, flags the three that can actually hurt you, and gives you the questions worth asking before picking a remote hiring partner.

Why Hiring Remote Developers Creates a Compliance Problem You Did Not Plan For

Compliance is a trap, and it’ll catch a sharp team napping as easily as it’ll catch a lazy one. Hire someone in the US, and payroll and compliance are invisible, because the scaffolding is already there. You’ve got an HR function, a payroll provider, and US employment law all running underneath the hire, and the manager doing the hiring never has to look at any of it.

Cross a border, and that scaffolding is gone. Now you’re the one expected to run local payroll, withhold the right taxes on the local calendar, and stay on the right side of a labor code written in another language and enforced by another country’s courts.

The reason this blindsides people is simple. The recruiting tools are everywhere and easy to find. The obligations behind the hire aren’t, so most teams don’t meet them until the offer’s already out.

Faced with all that, the simplest move is to not bother. Hire stateside, keep the scaffolding, and none of this lands on you. Plenty of teams stop right there, and for some of them it’s the right call. But that exit has a price. The same Senior Engineer costs 30 to 40% less in Latin America, works your hours, and can be on the team in a couple of weeks instead of the couple of months a US search tends to take.

The reason you started looking abroad hasn’t gone anywhere. The compliance is just part of the cost, and one you can manage if you’re smart. So, once you decide to hire abroad, you’ve got three options:

• Build the capability yourself.
• Hand it to an Employer of Record (EOR).
• Bring in a staff augmentation partner.

For a sense of scale, the global EOR market was worth about $5.6 billion in 2025 and is on track for roughly $10.5 billion by 2035. The demand is real, and a lot of the industry built to meet it is selling the most expensive answer.

Nelso Villamizar, Acendeo’s VP of Operations, puts the build-it-yourself option like this:

What if we need a computer monitor at the office, and I persuade the organization that I can build the monitor on my own, better, cheaper, and faster than buying it at Amazon? How ridiculous is that in today’s global economy?

Building a compliance operation to support one hire is the same bet. You pull the company off the work that pays the bills to rebuild something you could have rented.

The 7 Main Compliance Requirements Remote Hiring Creates for US Companies

Hiring a Developer in another country creates seven compliance obligations beyond the recruiting itself. Four of these you set up once and mostly manage in the background. The other three, worker classification, labor law, and permanent establishment, are the ones that compound, surface late, and land in a court that isn’t yours.

Here is a quick breakdown of each:

1. Payroll Processing: Pay accurately, on time, in local currency, through a legal in-country channel. Most US companies have no legal way to pay the person at all without a local entity or a partner that already runs one.
2. Tax withholding and Filing: Withhold and remit local income tax and social contributions on local schedules. Miss them, and you’re looking at penalties, interest stacking up, and in several countries, personal liability.
3. Worker Classification: Confirm whether each engagement is a contractor or employee under local law. A Developer you control day-to-day is almost certainly an employee under local tests, regardless of what the contract says.
4. Labor Law Compliance: Honor mandatory employment terms, including minimum wage, hours, leave, termination rules, and severance. Latin American labor codes lean hard toward protecting the employee, and disputes are decided in their courts.
5. Benefits Administration: Provide statutory benefits, including 13th-month pay, paid vacation, and social security contributions. Unpaid statutory benefits don’t disappear. They sit as a debt-gathering interest.
6. Onboarding Documentation: Execute local contracts, identity and right-to-work checks, enforceable IP assignment, and residency verification. Without this, you can’t prove compliance when a dispute opens.
7. Permanent Establishment Risk: Avoid creating a taxable corporate presence by directing employees abroad. This is the obligation that surfaces years after the fact, often after whoever made the hire has left.

The table below shows each obligation in full, with the specific risk of leaving any one unmanaged:

1. Payroll Processing

Paying a Developer abroad legally takes more than sending money. You need an in-country payment channel, payment in the local currency, the right statutory deductions, the local pay schedule, and compliance with that country’s currency-control rules.

Most US companies have no legal way to pay the person at all without either a local entity or a partner that already runs one. The money has to move through a channel the local government recognizes, and a transfer from your US bank doesn’t.

2. Tax Withholding and Filing

Local income tax and social contributions have to come out at source and get remitted on local filing calendars, and those calendars don’t care that you’re a foreign employer. Miss them, and you’re looking at penalties, interest stacking up, and in several countries, personal liability for your hires.

This isn’t a one-time setup, either. It runs every month, and it’s the piece teams most often assume their payroll software covers, even when it doesn’t.

3. Worker Classification

Worker classification is where most direct hires go wrong. Engage a Developer abroad as a “contractor” while you control their hours and their day-to-day work, and under most local tests, and under US common law, you’re employing them.

The IRS spells it out: if you control what gets done and how, the worker is your employee under common-law rules, even when they’re the ones who chose to work remotely. Mexico and Brazil read it the same way, looking at the substance over the label, and they’ll reclassify after the fact, hanging back taxes and back benefits on a relationship you thought was contract work.

What decides it is the degree of control, and Software Development is control-heavy by nature. You’re setting the priorities and running the standups. To a local court, that’s an employer, whatever the paperwork says.

4. Labor Law Compliance

Wherever the Developer sits, the local labor code outranks the contract you signed, and Latin American codes are strong in employee protections. Mexico is the clearest example. There’s no at-will termination.

In any dismissal case, the employer carries the full burden of proof, and an unjustified dismissal means reinstatement with back pay or a full statutory severance of roughly three months’ integrated salary plus a seniority premium.

A lot of it comes down to procedure: miss the deadline on a proper written notice and a dismissal you had every right to make becomes an unjustified one, with full severance owed. Mexico is one country, but the shape repeats across the region: mandatory terms you can’t contract around, decided in the worker’s home court instead of yours.

5. Benefits Administration

Statutory benefits in the region are law, not perks, and they pile up. Most of Latin America mandates a 13th-month salary outright: Mexico under the Ley Federal del Trabajo, Colombia under prima de servicios regulation, Argentina under Law 23,041, and Brazil through the decimo terceiro requirement.

On top of that you’ve got mandatory paid vacation, a vacation bonus in several countries, and employer-side social security and health contributions. The number that surprises people is the load in Brazil, where employer social-security contributions run around 27% of salary per PwC’s Worldwide Tax Summaries, before you add the FGTS severance fund at 8% of salary deposited every month, the 13th salary, and the constitutional one-third vacation bonus.

None of it is optional, and unpaid statutory benefits don’t just disappear. They sit there as a debt, gathering interest, ready to surface the moment there’s a dispute.

6. Onboarding Documentation

You collect a signed local contract, identity and work-authorization checks, background checks, an enforceable IP assignment, and proof the Developer lives where they say. Most of the time, all of it just sits in a folder. Then an audit opens, or a terminated Developer files a claim, and those records become the only thing standing between you and a finding against you.

The burden is on you to prove the engagement was clean, and the records are how you do it. Skip them, and a labor court treats the hire as undocumented from the start, which, in a system where the employer carries the burden of proof, is most sure the way to compliance penalties.

7. Permanent Establishment Risk

Permanent establishment is the obligation that surfaces years after the fact. It entails having direct employees in a country where you have no legal entity, and that country’s tax authority can decide you’re effectively operating there. Once they do, you’re looking at corporate registration, filing requirements, and tax on the profits they attribute to that local presence, which in some places means your global revenue, not just what you earned locally.

The current reference point is the OECD’s November 2025 update to its Model Tax Convention. It introduced a 50% working-time benchmark and confirmed that someone working remotely from another country doesn’t automatically create a permanent establishment, but it left the call to facts and circumstances rather than a clean rule, so the risk is real and depends on the specifics.

The part that gets a CTO’s attention is the timing: this can pop up years after the hiring decision, often after whoever made it has left.

Want to know which of these 7 obligations your current setup actually covers? Talk to our experts for a free remote hiring compliance gap check.

EOR vs. Staff Augmentation vs. DIY Hire: Same Obligations, Different Jurisdiction

Employer of Record, Nearshore Staff Augmentation, and direct hiring are the most common models companies use to engage remote talent from Latin America. All three models face the same 7 compliance obligations.

What changes is who carries each one, and whose legal system you’re standing in when something goes wrong. The whole decision comes down to that, and it’s worth seeing side by side.

Hire directly and you carry all 7 obligations yourself, in the Developer’s country, with nothing between you and the local system. The most critical exposure you face is:

• Permanent establishment: Direct a Developer in a country where you have no entity creates a taxable presence there, the risk that shows up years after the hire.

An EOR looks like the safe middle path, and in the right situation it is. If you’re selling into a local market and need employees who are genuinely part of that country, it’s built for exactly that.

For a US company hiring Developers to build US products, though, it leaves you inside the local labor system without removing your exposure. The EOR becomes the Developer’s on-paper employer, but you still direct the work, and the local courts can still reach you.

Brazil makes this concrete: under a long-standing rule of its labor courts (TST Sumula 331), a company that benefits from outsourced labor can be held liable for the provider’s unpaid wages, taxes, and benefits when the provider doesn’t cover them, and a setup where you direct the worker day to day can be challenged as disguised employment.

What this means is the EOR takes the paperwork off your plate. It doesn’t take you out of the jurisdiction.

Staff augmentation changes the structure. The developer contracts with the staffing partner, the partner is incorporated in the US, and you never enter a foreign jurisdiction.

Since the only employment relationship is between the Developer and a US company, there’s no foreign employment to reclassify, and disputes are resolved in US courts. Consequently, staff augmentation handled all the 7 seven obligations under US law, which you’re familiar with, inside one flat monthly fee per seat filled, by the vendor instead of you.

The Questions to Ask Before Deciding Between EOR vs Staff Augmentation vs DIY For Remote Hiring

If you’re evaluating partners, the 7 questions below are worth putting on the call. Each question is numbered to map back to the obligation it protects against. For each one, there’s an answer that tells you the partner really takes the obligation on, and what to look out for to avoid compliance exposure.

The Partner That Closes All Seven

By now, you’ve got the whole picture: the 7 obligations, the three models that handle them differently, and the questions that reveal which model a partner is really offering. The only setup that covers all seven without dropping you into a foreign legal system is a US-incorporated staff augmentation partner that handles payroll and compliance inside one flat monthly fee.

In practice, that means the partner writes the locally compliant contracts, runs payroll, withholds and files the local taxes, administers the mandatory benefits, ships and supports the equipment, verifies in person that the Developer lives where they say, and screens out disguised applicants before any of it starts. You grant system access and manage the work, the same way you would with anyone on your team. Everything underneath the hire belongs to the partner.

The right partner doesn’t just find the Developer. It makes it possible to employ the Developer legally, without you ever having to leave US jurisdiction.

Acendeo handles payroll, tax, benefits, and compliance, giving you access to an extensive pool of pre-vetted LATAM Developers ready to integrate into your team in 10 days.

Frequently Asked Questions