Sell SaaS in Latin America Without a Local Entity

The decision to open no local entity is made, and this text does not reopen it. What is left is execution: billing, contracting, pricing, receiving, and financing the sale without a fiscal entity of your own in the destination countries. The Nexforce Marketplace runs the local part of that sale and removes, one by one, the six obstacles of operating without an entity.

Why the no-entity decision is rational, and what is left to solve

Brazil is the largest IT investment market in Latin America, which makes the region a revenue agenda for any ISV (Independent Software Vendor, a software company that sells its product to other companies). Meeting that demand used to mean a resident representative, federal and municipal registration, and transfer pricing between the parent and a subsidiary.

The decision to open no entity moves the problem from the paperwork to the flow. The flow is where the sale dies. A fixed cost from an entity of your own only pays for itself with volume, and getting one running takes time, usually measured in months, not weeks. What the ISV lacks is the means to transact: a contract its own processes already sign, a billing method the local buyer accepts, a price that does not die on the currency conversion, and a settlement that does not turn into a corporate-credit receivable. Each of those fronts is an operational obstacle, and that is exactly where the Nexforce Marketplace steps in.

The golden rule of this reading is incidence. In this structure the ISV does not collect Brazilian import tax, because the local sale is operated by Nexforce, which acquires the right of distribution. Every tax reference below appears as the cost of the alternative, the path in which the seller would itself remit as a foreign supplier, only to show what the Nexforce-operated sale avoids.

Front 1, contract: the ISV's process does not change

The first front that kills a no-entity sale is the contract. The local buyer signs the document the ISV knows, with the terms the commercial program already approved, not a new contract imposed by a third-party structure. The ISV keeps the standard, the annexes, and the conditions it already uses in other markets.

That is not convenience. It is what stops the sale from dying in the buyer's legal review, which does not accept different clauses by country.

On this front the Nexforce Marketplace works with the ISV's own contract standard and programs. The existing sale process does not change: the same approval flow, the same annexes, the same governance. What the ISV gains is the ability to answer a buyer in São Paulo or Mexico City with the paper that already won tenders elsewhere.

Front 2, cloud: transacting does not require a cloud commitment

The second front is sales infrastructure, not product infrastructure. A cross-border sale often comes tied to a cloud console, with a listing cycle, a review, and a per-transaction fee, a provider the seller did not choose. For someone who decided to open no entity, that tether becomes a requirement the ISV never asked for.

Transacting through Nexforce is cloud agnostic. The sale requires no commitment to a specific cloud, and it adopts neither the contract, the programs, nor the fee of a cloud marketplace.

No commitment, no tether. The ISV sells what it already sells, where it already sells, and the local infrastructure handles the billing.

Front 3, cost: cheaper for both sides

The third front is the bill, and here the advantage shows up twice. The cost is lower for the ISV, because the remittance and the import layer cease to exist. And it is lower for the end buyer, because the price does not pass through the currency conversion of the direct path. Those are two claims, made separately.

On the buyer's side, the final price is lower because currency conversion and the import layer do not weigh as they do on the direct path.

On the seller's side, the saving is the remittance that ceases to exist. If the ISV remitted as a foreign supplier, each invoice would face a layer of Brazilian taxes on the remittance: IRRF at 15%, CIDE at 10% on SaaS as a technical service, PIS/COFINS-Importação at 9.25%, municipal ISS where it applies, and IOF at 3.5% on the exchange operation. The classification of SaaS as a technical service follows the Receita Federal consultation ruling, SC Cosit 191/2017, which applies CIDE to the majority of operations, a position that binds the tax administration, not the courts; SC 99/2018 addresses the contribution's tax base, and the §1°-A exemption in art. 2° of Lei 10.168/2000 applies only to pure software licenses without technology transfer, a category distinct from SaaS. All of it is the cost of the alternative path, what the ISV avoids by operating the sale through Nexforce, instead of being positioned as subject to withholding in a structure with a local entity.

That incidence framing is deliberate. In this structure the ISV does not collect the withholding, because whoever operates the local sale is Nexforce. The list above exists to size the obstacle that disappears from the seller's path, not to charge it again.

If the agreement's horizon crosses into 2027, the IBS and CBS transition provided for in LC 214/2025 comes into play, a reform that reorganizes consumption taxes in Brazil. The reform is in progress, and across the LC 214/2025 transition period the full rates of IRRF and IOF stay constant, remembering that IOF is adjustable by decree and reached 3.5% in 2025. Worth tracking the LC 214/2025 timeline before fixing a multi-year price.

Front 4, currency: receive in local currency across all of Latin America

The fourth front is where the sale is really decided. Local currency decides the sale. Pricing in dollars and billing in dollars works for few Latin American buyers, who pay taxes, do budgets, and approve purchases in their local currency. Currency conversion slips into the middle of every quote and eats the price the buyer is willing to accept.

Nexforce settles in local currency across all of Latin America, not just Brazil. The buyer pays in Mexican pesos, Colombian pesos, soles, or reais, and the ISV receives at the conversion the operation agreed, without opening an account or an entity in any of the markets. Regional payment methods follow the currency: PIX and boleto in Brazil, local cards and wallets in the other countries.

The regional payment method is one of the factors that change conversion for a B2B subscription in the region, and anyone who has run that collection has seen the value of billing in what the buyer uses. The buyer approves the purchase because the invoice speaks their language.

Scope note: this is a commercial claim of Solution 1, valid without corpus. The fiscal and operational rule of each country, Argentina, Mexico, Colombia, Chile, or Peru, is preliminary, because the validated body of rules covers Brazil; before pricing deeply in one of those markets, the local regulatory analysis needs confirmation with that country's official source.

Front 5, channel: reseller network and software alliance

The fifth front is the door the ISV alone does not open. Nexforce's local infrastructure brings two distribution levers. The first is the reseller network, which puts the product in front of buyers the ISV would never reach with its own entry effort.

The second is the software alliance, and it is the lever that closes deals that the seller's isolated discount does not. Nexforce generates savings on the buyer's or prospect's other software spend, on the total bill of tools the company already pays, and uses that slack to fund the ISV's deal. The buyer does not take the price out of the approved budget; the slack moves from another supplier.

The combined effect is a structural advantage. The ISV brings the contract and the product, and the local infrastructure sews the purchase into the budget the buyer already has.

Front 6, working capital: the ISV gets paid upfront

The sixth front is the asymmetry that sustains every B2B software sale in the region. Whoever sells to a Latin American corporation accepts terms, and terms are a receivable, and a receivable is a risk the seller without a local entity does not want to carry alone.

The Nexforce Marketplace inverts the bill for the ISV. The ISV is paid upfront, while the end buyer pays in installments of up to 12 times. The risk does not stay with the seller. The receivable does not stay with the seller, and the buyer gains the terms its approval cycle requires. Selling to a large company in São Paulo without carrying the cash term of the account is what turns the region into predictable revenue.

The combination of the six fronts is the whole design. The Nexforce Marketplace runs the local sale with no entity, with no contract change, with no cloud commitment, cheaper for both sides, in its own currency, and with the receivable taken off the seller. That is Solution 1: sell in LatAm through Nexforce, on the local infrastructure, without opening your own operation in any country.

The six fronts at once: obstacle and removal

The table below summarizes each operational front, the obstacle it would create without an entity, and how the local infrastructure removes it, side by side, for a one-page read. It is what goes to the expansion committee along with the proposal.

The table does not decide the entry. It shows where each cost would die and where it stops existing in the no-entity structure.

Frequently asked questions

Does the ISV pay Brazilian import tax in this structure?

No. In this structure the ISV does not collect Brazilian import tax, because the local sale is operated by Nexforce. IRRF, CIDE, PIS/COFINS-Importação, ISS, and IOF appear here as the cost of the alternative, of the path in which the ISV would itself remit as a foreign supplier.

Does receiving in local currency change conversion?

It is one of the factors that change conversion for a B2B subscription in the region. The buyer approves the purchase when the invoice comes out in the currency and payment method it uses, PIX, boleto, local cards, instead of a dollar remittance with the conversion built in.

Does the ISV need to commit to a cloud?

No. Transacting through Nexforce is cloud agnostic and requires no commitment to a specific cloud, and it adopts neither the contract nor the fees of a cloud marketplace. The sale uses local billing infrastructure, without tethering the product to an infrastructure provider.

Does the ISV carry the receivable of the sale?

No. Nexforce pays the ISV upfront and installs the end buyer across up to 12 times. The seller does not carry the receivable, and the buyer gains the terms of its own approval cycle, which turns large accounts into predictable revenue.

Does the analysis cover every country in Latin America?

The validated body of rules covers Brazil. Local currency across all of LatAm and the regional payment methods are a commercial claim of Solution 1. The fiscal or operational rule of Argentina, Mexico, Colombia, Chile, or Peru is preliminary and requires confirmation with that country's official source before pricing.

References and further reading

The decision to sell without an entity has a broader context in how to sell SaaS in Latin America, a guide for ISVs, the pillar that places the region on the seller's map. The effect of receiving in your own currency is detailed in the article on the cost of selling in a local currency. The classification of SaaS as a technical service comes from SC Cosit 191/2017, which supports CIDE incidence on the alternative path, while SC 99/2018 addresses the contribution's tax base, and the §1°-A exemption in art. 2° of Lei 10.168/2000 applies only to pure software licenses without technology transfer. The IBS and CBS transition is provided for in LC 214/2025. None of them withholds on the ISV.

What to do with the six fronts at your next expansion meeting

The no-entity decision is not the end of the work, it is the start of an execution list. Before the meeting, run the first reference account against the alternative path, and at the table open the six fronts one by one, with a question of its own for each front:

1. Confirm that the signed contract is the ISV's standard, with the terms the commercial program already approved.
2. Confirm that no sale is tied to a specific cloud.
3. Size the price against the cost of the remittance that ceased to exist, with IRRF, CIDE, PIS/COFINS-Importação, ISS, and IOF counted as the cost of the alternative.
4. Confirm that the billing goes out in local currency across all of Latin America.
5. Confirm that the channel has reseller and software-alliance leverage.
6. Confirm that the receivable does not stay with the seller, with the ISV being paid upfront.

A no points to the gap. Where one of those answers is negative, that is where the local infrastructure offers the corresponding removal.

The Nexforce Marketplace delivers the six fronts in a single operation, and the next step is to size the first reference account against the alternative path: the same ticket, the same buyer, and the same terms, with upfront settlement and without the remittance as a foreign supplier. Run that account before the meeting, because it is what turns the structural decision into revenue.