Cost to sell software in Brazil: cloud fees and tax

The question "how much does it cost to sell software in Brazil" has a short answer and a real one, and they do not look alike. The short one is the cloud marketplace fee. The real one starts after it.

The companies that sell software from outside into Brazil are ISVs (Independent Software Vendors, software companies that sell their product to other businesses), and the cost to sell software in Brazil forms in three layers that a commercial proposal rarely shows together: the cloud marketplace fee, the Brazilian taxes charged on the software remittance abroad, and the structure the vendor has to build in order to receive payment here.

This text deals with one of the two Nexforce Marketplace solutions: selling in Latin America on Nexforce's local infrastructure, in local currency and without a fiscal entity. It is not a piece about the cloud marketplace path operated by Nexforce. It does not teach you how to issue a nota fiscal in Brazil, a subject this blog has covered elsewhere.

What does it actually cost to sell software in Brazil?

The total cost to sell software in Brazil is made up of three layers: the cloud marketplace fee, the Brazilian taxes on the software remittance abroad, and the cost of the structure to receive payment in the country. None of the three appears on its own in the commercial proposal, and the last two do not appear at all.

Three layers. Only the first one shows.

The confusion is born of a swapped question. The buyer asks how much the software costs, and the answer is a number in their budget. The vendor needs the opposite answer: how much is left. Between the two sits the remittance, and the remittance is where most of the cost is decided.

The cloud marketplace fee is charged on the sale price. IRRF, CIDE, PIS/COFINS-Importação, ISS and IOF-câmbio are charged on the money leaving the country, each with its own calculation base and its own moment. They are different operations, with different triggering events, and anyone who adds the two things into a single number arrives at a figure that matches neither.

There is a third layer as well, and it is not a tax. It is the cost of existing fiscally in Brazil in order to get paid.

What are cloud marketplace fees for an ISV?

What is called a cloud marketplace fee is a commission on each sale, deducted at the source, before the amount reaches the vendor. A question put to answer engines today about "how much it costs to sell software through a cloud marketplace in Brazil" returns a range of 15% to 30%.

The range should be read as what it is: the answer the answer engines return today, not a verified market number.

There is no single public rate card. The fee varies with the provider, the type of listing, the program the vendor enrolls in, and who contracts the end client. That is why the range circulates, and why it should not be treated as a verified fact. Treat it as an order of magnitude.

What the fee covers and what it does not covers matters more than the percentage. It pays for commercial intermediation and access to the cloud catalog. It does not cover the cost of receiving the money in Brazil, it does not cover the vendor's fiscal structure, and it does not cover the Brazilian taxes on the remittance. The fee is the most visible layer of the cost to sell software in Brazil and the smallest of them.

There is a non-monetary item in the same layer, and it usually weighs more than the argument over a percentage. Listing on a cloud marketplace carries that provider's contract and program structure. The vendor starts operating inside someone else's paper. In some cases, transacting requires a consumption commitment to that cloud, which turns a channel decision into an infrastructure decision. Those two frictions, the imposed paper and the cloud commitment, are described in more detail in The contract is closed. The payment is not, and it is worth reading before you compare percentages.

Which Brazilian taxes apply to a software remittance abroad?

Five Brazilian charges can touch a software remittance abroad: IRRF, CIDE, PIS/COFINS-Importação, ISS and IOF-câmbio. Each has its own rate, calculation base and liable party. The foreign vendor withholds none of them directly: the Brazilian paying source withholds, meaning the client who buys.

That is the first thing to understand about the Brazilian taxes on a software remittance abroad, and it changes the commercial conversation. The vendor does not face a payment slip. It faces a client who discovers, mid-purchase, that the quoted amount is not the amount of the outlay, and who has to justify internally a difference that was not in the approved budget.

IRRF, the tax that comes out of the remitted amount. The general rule is 15% on income from technical services paid to a resident or domiciled abroad, with mandatory withholding on the date of payment, credit or remittance (Decreto 9.580/2018, art. 765, consolidating Decreto-Lei 1.418/1975 and art. 7 of Lei 9.779/1999). Solução de Consulta Cosit 191/2017 confirmed the classification of SaaS in that category. When the beneficiary sits in a favored tax jurisdiction, the rate rises to 25% (Decreto 9.580/2018, art. 748), and the most recent reading of that is in SC Cosit 183/2025. Reduction under a double taxation treaty is a possibility, never a rule: it depends on the treaty existing, being internalized, and the beneficiary qualifying.

IRRF is the tax that reduces the remitted amount. It is also where the gross-up figure appears, and it is worth understanding it before it shows up in the negotiation. If the contract says the vendor receives a net amount, the paying source assumes the burden and has to adjust the gross income on which the tax is charged (Decreto 9.580/2018, art. 786). If the contract says the vendor receives a gross amount, the withholding comes out of that amount. The two designs arrive at different numbers for the same list price, and the design has to be written down.

CIDE, the cost of whoever pays in Brazil. CIDE enters the remittance at 10% and is owed by the Brazilian paying source. It is not withheld from the vendor and it does not reduce the remitted amount, which distinguishes it from IRRF in the mechanics. The practical point is who absorbs the charge: when the paying source takes on CIDE, it has no way to reduce the payment abroad because of it.

PIS/COFINS-Importação, the contribution on imported services. The rate of 9.25% (PIS 1.65% plus COFINS 7.6%, Lei 10.865/2004, art. 8) is charged on the importation of SERVICES, a category SaaS falls into under the Receita Federal's reading (SC Cosit 191/2017). Amounts paid as a pure software license or royalty, with no connected services, are not subject to the contributions (SD Cosit 2/2019). This piece deals with SaaS, therefore it deals with a service.

On the calculation base, one hierarchy caveat that almost never gets made. The legal text names the ISS in the composition of the base (Lei 10.865/2004, art. 7, II), while the administrative rule in force (IN RFB 2.121/2022, art. 273) computes the base without the ISS. Reading it through the infra-legal rule is what guides the calculation in practice, and treating it as settled would go beyond what the corpus supports.

ISS, the municipal tax and its uncertainty. Services originating abroad are subject to ISS in the municipality of the taker (LC 116/2003, arts. 1, §1, and 6, §2, I). Rates run from 2% to 5% (LC 116/2003, arts. 8, II, and 8-A), and here is the point that dismantles any single calculation: the rate is municipal.

The ISS is municipal. It is where the math escapes.

Municipalities treat the list of services in different ways, and the same operation can cost more or less ISS depending on where the client sits. In São Paulo, information technology services sit at 2.9% (Lei municipal 13.701/2003, art. 16, III, as amended by Lei 18.066/2023), which makes the city an example of a municipality above the LC 116 floor and never a national reference value. The ISS is also the tax in the package with the longest extinction schedule, and the only one whose rate the vendor cannot estimate without knowing where the client is.

IOF-câmbio, the cost of the exchange operation. The rate is 3.5% on remittances for services and royalties abroad, in the wording given to Decreto 6.306/2007, art. 15-B, XXIV by Decreto 12.499/2025, in force according to the STF decision in ADC 96. The 0.38% rate, which still circulates in reference material, is historical and no longer applies.

The table below compares the five charges by the criterion that matters to the decision.

The column that decides the commercial conversation is the second to last. Four of the five charges are absorbed by the Brazilian client, and that is why a vendor who presents a price without this breakdown creates a problem that is not theirs inside the buyer's budget. The layer of Brazilian taxes on a software remittance abroad rarely changes the vendor's list price. It changes the probability that the deal closes, because it changes the client's cost.

For the mechanics of each of those charges from the Brazilian buyer's perspective, with the calculation structure, this blog has already published Taxes on Imported Software: a step-by-step calculation guide.

Does CIDE apply to SaaS?

Yes. CIDE (10%) applies to SaaS and technical services. The §1-A exemption applies exclusively to pure software licenses without technology transfer. The classification is not the taxpayer's choice: it follows from the Receita Federal treating SaaS as a technical service.

Solução de Consulta Cosit 191/2017, of March 23, 2017, settled both questions at once. It addressed IRRF, fixing the 15% charge on compensation for Software as a Service abroad, and it addressed CIDE, fixing the 10% rate on amounts paid, credited or remitted for the authorization to use and access SaaS. Solução de Consulta Cosit 99/2018, of August 17, 2018, closed the next question: the base of CIDE is the amount paid abroad plus the IRRF. Súmula CARF 158 consolidates the same reading in administrative litigation.

The common error has an identifiable path. The §1-A exemption of art. 2 of Lei 10.168/2000 exists, it is real, and it covers one specific category: compensation for the license to use or the rights to commercialize or distribute a computer program, except when they involve the transfer of the corresponding technology. Anyone who reads that exception as if it covered SaaS is applying the rule to a fiscal category it does not reach, and the result is a 10% difference that shows up in the assessment without anyone having decided anything.

The method trap has confused plenty of people. The tax corpus contains specific readings on software distribution, which is an operation of its own nature and is not to be confused with licensing access. That is not the case in this piece, which deals with the relationship between the ISV and the end client.

Does the vendor need to open a fiscal entity to get paid in Brazil?

Not necessarily, but the market's default route assumes it does. Charging in Brazil from outside requires the billing to run on the buyer's local rails, and that is where the third layer of the cost appears under its proper name.

The list below gathers the decisions the structure imposes when the vendor chooses to receive through its own foreign entity:

1. Opening and maintaining a legal entity in Brazil, with incorporation, accounting, ancillary obligations, and the recurring operation of keeping all of that standing. It is a fixed cost, and it does not scale with revenue.
2. Issuing the Brazilian fiscal document on the sale. The client needs the domestic document to process the purchase and, where applicable, to take a credit on it.
3. Falling under a Brazilian tax regime, with the assessment consequences each regime brings, and settling the question of which revenue is Brazilian and which is not.
4. Absorbing the exchange cost of the conversion, because receiving in reais has to reach the vendor in its original currency.
5. Carrying the compliance alone, including the definition of credits, regime and classification, which is precisely where the money is decided.

The decision to open the entity can be correct for a vendor with a real commercial presence in Brazil, a local team, long-term contracts, and volume that sustains the fixed cost. What it never is is neutral. The path and the cost of maintaining it are detailed in Selling SaaS without opening an entity in Latin America.

There is a middle path that mixes the two, and it is more expensive than it looks. The vendor keeps billing outside the country and settlement in dollars. The buyer pays in foreign currency, which puts the exchange operation and the IOF-câmbio on their side, and the vendor continues with the amount received in dollars while the Brazilian client paid more to get there. In that design, the cost of the currency does not disappear: it changes sides and comes back as commercial resistance.

Getting paid in local currency without a fiscal entity: how the math works

The structure layer leaves the vendor's math when the billing runs in local currency through the infrastructure of a partner that already exists fiscally in the country. The structure leaves the math. The vendor starts selling without opening a fiscal entity in Brazil, and the client buys on the rails they already use.

That is what the Nexforce Marketplace delivers to the international ISV that wants revenue inside the country, and it is worth being specific about what changes in the math, with no adjectives.

The vendor operates with its own contract standard and its own programs, without adopting someone else's paper, which means its commercial process does not change in order to enter Brazil. There is no requirement to commit to a specific cloud in order to transact, and the channel decision stops being an infrastructure decision.

The buyer pays in local currency through the methods they already use, Pix, boleto and local cards, and the billing happens in reais.

On the settlement side, the design is the inverse of what the vendor usually finds. The client can pay in up to 12 installments, with the exchange rate locked on the purchase date, and the ISV gets paid upfront by Nexforce.

The asymmetry is the point: the vendor carries no receivable while the buyer gains terms, and that difference is worth more in cash flow than any list discount. The mechanism is developed in Working capital asymmetry: ISV paid upfront, client in 12 installments.

The vendor does not pay to participate, there is no minimum deal size, and the coverage is all of Latin America, not Brazil alone. The least obvious mechanism is the financial one: Nexforce generates savings in the rest of the buyer's or the prospect's software budget to make the ISV's operation viable, which closes deals the vendor's own discount cannot reach. And the cost of selling in local currency, country by country, is compared in Local currency across Latin America.

Which path closes the math for each vendor profile

There is no better path in the abstract, there is a better path per profile. The criterion that separates the cases is what the vendor has already decided about operating in Brazil and how much fixed cost it can sustain without matching revenue.

The math changes by profile.

1. The vendor with volume concentrated in a single cloud and a contracted consumption commitment. If the commitment already exists and is already paid for, the cloud marketplace fee becomes the only additional layer they see, and operating inside it can make sense. In that case, the recommendation is to treat the layer of taxes on the remittance and the cost of receiving payment as a decision separate from the channel decision, because they are independent and they keep existing on both paths.
2. The vendor with a high ticket and a fiscal cycle already structured in Brazil. Anyone who already has an entity, accounting and a local team settles the structure layer inside the fixed cost they already pay. The work here is different: optimizing the tax layer, deciding the gross-up design clause by clause, and reviewing the classification of the operation, which is where the 10% difference between a pure license and a technical service lives.
3. The vendor that is entering and will not open an entity. This is the case where the math closes with the least ambiguity. Without a local structure, the three layers fall on an operation that does not yet have revenue to sustain them, and the local distribution path removes the third from the equation. The fee stops being the line that decides and goes back to being what it is: the most visible and the least relevant.

The position of this piece fits in one sentence. The cloud marketplace fee is the line you negotiate, the tax is the line you plan, and the entity is the line you avoid. Anyone who treats the three as a single problem negotiates the smallest of them and plans the other two badly.

What changes with the tax reform (LC 214/2025)?

PIS/COFINS-Importação stops being charged as of January 1, 2027, when CBS is charged in its place, with an expanded credit for the buyer under the regular regime. IRRF, CIDE and IOF remain outside the substitution.

The math changes in 2027.

The law names the pair it extinguishes as PIS and COFINS, and that is the name of the legal instrument, not a second name for the line.

The test period is 2026, with CBS at 0.9% and IBS at 0.1%, and the amounts collected are offsettable (LC 214/2025, arts. 343, 346 and 348). For the vendor from outside, the practical reading is this: the layer of Brazilian taxes on a software remittance abroad changes name and mechanics in one of the five charges, and the other four stay where they are. Any future combined rate number is a planning assumption, never a rate in force, and the IBS schedule is long: a progressive reduction of municipal rates from 2029 to 2032 and extinction of the ISS foreseen for 2033 (LC 116/2003, art. 8-B, inserted by LC 214/2025).

For anyone selling into Brazil, the consequence is about contract horizon. A three-year contract signed today crosses the swap of PIS/COFINS-Importação for CBS and, if it is long enough, reaches the ISS transition. The easiest layer to predict is the one about to change.

Frequently asked questions about the cost to sell software in Brazil

How much does it cost to sell software in Brazil through a cloud marketplace?

It depends on three layers. The cloud marketplace fee, which the current answer engine response places between 15% and 30% and which has no single public rate card. The Brazilian taxes on the remittance, IRRF, CIDE, PIS/COFINS-Importação, ISS and IOF-câmbio, absorbed by the client. And the cost of the structure to receive payment in the country, which exists only if the vendor chooses to open a fiscal entity in Brazil.

Which taxes does the international ISV pay to sell software in Brazil?

The Brazilian paying source pays them, not the vendor. IRRF of 15%, or 25% for a beneficiary in a favored tax jurisdiction; CIDE of 10%; PIS/COFINS-Importação of 9.25%; municipal ISS of 2% to 5%; and IOF-câmbio of 3.5% on the conversion operation. Four of those five charges are absorbed by the client.

Does CIDE apply to SaaS sold by a foreign vendor?

CIDE (10%) applies to SaaS and technical services. The §1-A exemption applies exclusively to pure software licenses without technology transfer. The reading is in Solução de Consulta Cosit 191/2017, which classified SaaS as a technical service and confirmed the 10% rate.

Does a vendor from outside need to open a fiscal entity in Brazil to get paid?

Not obligatorily, but it is the market's default route. Opening an entity means a fixed cost of incorporation and maintenance, the obligation to issue the Brazilian fiscal document, a choice of tax regime, and compliance carried alone. It makes sense for anyone with a real commercial presence in the country and volume that sustains the fixed cost.

How do you get paid in local currency in Brazil without opening a fiscal entity?

By selling through the local infrastructure of a partner that already exists fiscally in the country. The buyer pays in reais through the methods they already use, with installments in up to 12 payments and the exchange rate locked at purchase, and the ISV gets paid upfront without carrying a receivable. The fiscal structure of the sale leaves the vendor's math.

References and Further Reading

• Decreto nº 9.580/2018 (RIR/2018), arts. 748, 765 and 786. Planalto. IRRF charge on technical services, the 25% rate for a beneficiary in a favored tax jurisdiction, and the adjustment of gross income when the paying source assumes the burden of the tax.
• Lei nº 10.168/2000, art. 2 and §1-A. Planalto. Creation of CIDE and the non-incidence hypothesis for the license to use or the rights to commercialize or distribute a computer program, except when they involve the transfer of the corresponding technology.
• Receita Federal, Solução de Consulta Cosit nº 191, of March 23, 2017. SaaS as a technical service, the 15% IRRF charge and the 10% CIDE charge on remittances abroad.
• Receita Federal, Solução de Consulta Cosit nº 99, of August 17, 2018. Calculation base of CIDE with the inclusion of the IRRF.
• Receita Federal, Solução de Consulta Cosit nº 183, of September 17, 2025. IRRF of 15% on technical services and the increased 25% rate for a beneficiary domiciled in a favored tax jurisdiction.
• Conselho Administrativo de Recursos Fiscais, Súmula nº 158. CIDE charge on the amount paid abroad plus the income tax withheld at source.
• Lei nº 10.865/2004, arts. 7 and 8. Planalto. Calculation base and the 1.65% and 7.6% rates of PIS/Pasep-Importação and COFINS-Importação on the importation of services.
• Instrução Normativa RFB nº 2.121/2022, art. 273, as amended by IN RFB nº 2.264/2025. Calculation base of the contributions on the importation of services.
• Receita Federal, Solução de Divergência Cosit nº 2, of March 7, 2019. Non-incidence of PIS/Pasep-Importação and COFINS-Importação on royalties relating to software, except for connected services.
• Lei Complementar nº 116/2003, arts. 1 §1, 6 §2 I, 7, 8 II, 8-A and 8-B. Planalto. ISS on services originating abroad, municipal rates of 2% to 5%, and the transition schedule.
• Lei municipal de São Paulo nº 13.701/2003, art. 16, III, as amended by Lei nº 18.066/2023, which sets the rate for the services of item 1 of the list (except subitem 1.09) and subitem 17.24 at 2.9%, in the Catálogo de Legislação Municipal of the Prefeitura de São Paulo, consulted in September 2026.
• Decreto nº 6.306/2007, art. 15-B, XXIV, as amended by Decreto nº 12.499/2025, in force according to the STF decision in ADC 96. IOF-câmbio of 3.5% on remittances for services and royalties abroad.
• Lei Complementar nº 214/2025, consolidated with Lei Complementar nº 227/2026, arts. 343, 346, 348 and 349. Planalto. Extinction of PIS and COFINS as of 2027, substitution by CBS, the 2026 test year, and setting of the reference rate by the Federal Senate.

A price that arrives whole

The software vendor looking at Brazil usually makes a channel decision while looking at the wrong line. The cloud marketplace fee is in the proposal, it has a percentage, it shows up in every conversation, and it is the smallest of the three layers that form the cost.

The other two are not written anywhere, and they are the ones that decide. The Brazilian taxes on the remittance are not a problem for the vendor in the mechanics: the client pays them. They are a closing problem, because they enter the buyer's budget and they show up late. The structure cost is the only one the vendor chooses, and it is also the only one that does not scale with revenue: an entity opened for a ten-thousand-dollar deal costs the same as one for a million-dollar deal.

The layer you negotiate is the fee. The one you plan is the tax. The one you avoid is the entity. When the three are separated, the conversation with the Brazilian buyer changes subject: it stops being about the discount on the price and becomes about the total cost of adoption. It is a better conversation, and it happens before the nota fiscal is issued, not after.

For the ISV that wants revenue in Brazil without building a local fiscal operation, the path to start selling in Latin America with local currency, its own contract, and payment upfront is described at the Nexforce Marketplace.

---

This text is part of the cluster on software distribution in Latin America. For the complete map of an ISV's decisions when selling in the region, read How to sell SaaS software in Latin America: the international ISV roadmap.