Do you need a local entity to pay people in Brazil or Mexico? Local entity vs cross-border payout provider

You don't need a local entity in Brazil or Mexico to pay suppliers or contractors there. A cross-border payout provider can deliver reais over Pix or pesos over SPEI from abroad, in minutes. You need a local entity when local activity demands it: hiring employees, invoicing local customers, holding licenses, or keeping large local revenue in local currency.

Teams often open a subsidiary just to get a local bank account for payments, then spend months on setup and years on upkeep. This guide separates the two jobs. For how a cross-border payout converts and lands, see what a stablecoin sandwich is.

Key takeaways

• Paying people in a country and operating in that country are different problems. Only the second needs an entity.
• A local entity brings fixed costs from day one: incorporation, registrations, accounting, tax filings, a local bank, and a funded balance.
• A payout provider has no fixed setup per country and scales with volume, but each payment carries an FX spread and a fee.
• Switch triggers are local hiring, local invoicing, local licenses, and large local revenue, not payment count.
• Many companies run both: an entity where they operate, a payout provider everywhere else.

Why do companies open a local entity just to pay people?

Because a local bank account looked like the only way to pay in local currency.

Before instant payout APIs, paying 200 contractors in Brazil meant either 200 international wires or a Brazilian account funded in reais. The account won on per-payment cost, so companies opened a subsidiary to get one. That logic still shows up in planning decks.

The Federal Reserve describes the same fixed-cost problem at bank scale. A March 30, 2026 FEDS Note says cross-border payments involve "high fixed costs," including "the cost of setting up a foreign branch," and that small banks route through large correspondents because they can't spread those costs. A company opening a subsidiary to pay suppliers is taking on the same fixed cost for the same reason.

What does running a local entity actually involve?

More than a bank account. A rough list for Brazil or Mexico:

1. Incorporation. Choose a company type, appoint local administrators or representatives, register with the commercial registry.
2. Tax registration. A CNPJ in Brazil, an RFC in Mexico, plus state or municipal registrations depending on activity.
3. Foreign investment registration. In Mexico, the Secretaría de Economía's foreign investment registry form says companies must register within 40 business days of the foreign investment entering, with late filing penalized. In Brazil, foreign direct investment is reported to the Central Bank through the SCE-IED system under Resolution BCB 278.
4. A local bank account. Banks run their own KYB on the new entity and its foreign owners.
5. Ongoing compliance. Local bookkeeping, monthly and annual tax filings, payroll filings if you hire, and annual corporate obligations.
6. Funding. The account has to be filled from abroad before it can pay anyone, which is pre-funding by another name.

Each step needs local lawyers or accountants. None of it is hard, but all of it is recurring. Ask your advisers for a quote on year-one setup and yearly upkeep before you decide.

How does a local entity compare with a cross-border payout provider?

On five dimensions, side by side.

The pattern: the entity wins on marginal cost and loses on fixed cost, time, and capital. The provider is the reverse.

When does a payout provider fit better?

When your activity in the country is paying people, not operating there.

• Paying suppliers and service providers in Brazil or Mexico from a US or European company.
• Paying independent contractors who invoice you. Stablecoin payroll for LATAM contractors covers that flow.
• Testing a market before committing to an entity.
• Paying across many countries with uneven volume, where an entity in each is out of proportion.
• Irregular or seasonal payments, where a funded local balance would sit idle.

A US company can also fund these payouts straight from its US bank account. How a US company pays suppliers in Brazil and Mexico walks through it.

When do you need a local entity anyway?

When the law or your customers require a local presence.

• Hiring employees. Employing people in Brazil or Mexico generally requires a local employer: your own entity or an employer of record.
• Selling and invoicing locally. Local customers may require tax invoices, such as Brazil's nota fiscal or Mexico's CFDI, which are issued by locally registered taxpayers.
• Local licenses. Regulated activities, including payments, need a local license and usually a local company to hold it.
• Large local revenue. If you collect a lot of revenue in reais or pesos and spend it locally, keeping it in a local account avoids converting it twice. What is a natural FX hedge? covers that case.

If none of these apply, the entity is overhead for a payments problem.

How do you decide? A five-question test

Answer these in order. The first "yes" points to an entity.

1. Will you hire employees in the country in the next 12 months?
2. Do local customers need a local tax invoice from you?
3. Does your activity need a local license?
4. Will you collect large, steady local-currency revenue that you will also spend locally?
5. Has your tax adviser flagged a permanent establishment or similar risk from your current activity?

All "no": pay cross-border through a provider and revisit the test every six months. Any "yes": plan the entity, and keep the provider for countries where you don't have one.

Can you run both at the same time?

Yes, and it's the most common end state.

The local entity runs payroll, invoicing, and taxes in its country. The payout provider handles everything that crosses a border: funding the subsidiary from headquarters, paying suppliers in countries where you have no entity, and moving money between your own accounts. One detail trips teams up. Sending to an account in your own company's name is a first-party payout, but your subsidiary is a different legal entity, so paying it is third party, with the documents that go with it. First-party vs third-party payouts explains the difference.

How does BlindPay handle this?

BlindPay pays out in local currency from USDC or USDT without a local entity on your side: Pix, PIX Safe, and TED in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, ACH, wire, and RTP in the US, SEPA in Europe, and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations for other countries. Adding a country is a new bank account type in the same API. Each quote locks the rate and fees for 5 minutes, and KYC and KYB run in the same integration. BlindPay combines a monthly plan with per-transaction fees that vary by rail and network, disclosed in the live quote before execute.

What to do next

Run the five-question test for your next market. If every answer is no, price your first month of payments through a payout quote and compare it with your advisers' year-one estimate for an entity. The payout quotes docs show the request on a development instance.