Cloud Marketplace Procurement Guide for Latin America

---

A company in Sao Paulo approves the purchase of five American SaaS tools. The vendors invoice a combined USD 50,000. What lands on the finance department's books, after FX, taxes, and five separate international remittances, lands between BRL 310,000 and BRL 330,000. Nobody in the chain lied, and the number still doubled. The difference lives in four line items that almost never appear on a commercial proposal, and this article is about those four line items.

73% of corporate software running in Brazil originates abroad, according to ABES, the Brazilian software association. Most of those companies operate separate contracts per vendor, in foreign currency, with payment processes that consume finance team hours and expose the company to FX and tax risk. The cloud marketplace changes that. It consolidates dozens of software purchases into a single invoice, reduces the tax burden on cross-border payments, and simplifies compliance. But it does not solve everything. Understanding where each procurement model applies is what separates an efficient purchase from one that leaves money on the table.

The hidden cost of direct procurement

Every international software contract bought directly from the vendor requires a separate cross-border remittance in foreign currency, with an FX spread, IOF (Brazil's financial operations tax) at 3.5%, IRRF (withholding income tax) at 15%, and CIDE (contribution for intervention in economic domain) at 10% when the software is classified as a technical service. The sum of these layers adds 50% to 70% to the dollar price of the software. The cost is not on the vendor's invoice. It is in everything that happens between the invoice and the payment.

A USD 50,000 remittance never costs USD 50,000. The real number starts with the bank's FX spread, 5% to 8% above the commercial rate. Add IOF of 3.5% on the FX operation. Then comes IRRF of 15%, withheld at source on the gross remittance value, and CIDE of 10% when the software is classified as a technical service. SaaS subscription contracts fall under this classification, as confirmed by Receita Federal's normative interpretation SC Cosit 191/2017, reinforced by SC Cosit 99/2018. CIDE applies to SaaS and technical services. The exemption under §1°-A of art. 2°, Lei 10.168/2000 applies exclusively to pure software licenses without technology transfer, a fiscal category distinct from SaaS.

When the Brazilian contracting party absorbs the tax (gross-up), the IRRF tax base exceeds the invoice value, per RIR/2018 art. 786. PIS/COFINS-Importação, at 9.25% (Lei 10.865/2004), applies to the total transaction value including the taxes already mentioned and compounds the final bill.

Each remittance takes days to process and requires specific tax documentation per operation. The contract may need a sworn translation. The foreign invoice must be registered in SISCOMEX for goods or in the services system for software classified as a service. IRRF, ISS, and CIDE payments follow different deadlines for each tax. By year's end, a company with eight international contracts has spent weeks of finance department labor, paid bank spreads on eight separate operations, and likely missed a tax deadline because each levy has its own calendar.

What the cloud marketplace changes in software procurement

The cloud marketplace works as a storefront where a company buys third-party software and pays through its cloud provider's invoice. The purchase comes out of the buyer's cloud account, the vendor receives in dollars from the platform, and the buyer receives a single consolidated invoice covering everything consumed in the period.

Three things change in procurement. Instead of five separate remittances, the company handles one FX transaction for the marketplace invoice. Instead of classifying each software purchase individually for tax purposes, the platform applies a standardized treatment. Instead of tracking each contract's renewal date, the buyer sees all software in one console and receives centralized expiration alerts.

The marketplace does not eliminate every cost. The invoice is still in dollars in most Latin American countries. The FX spread and IOF still apply to the consolidated invoice because a cross-border remittance still exists, and the IRRF and CIDE burden on SaaS does not disappear just because the purchase went through a marketplace. What changes is the operational simplification and the reduction in spread from one remittance instead of many.

The buyer also becomes tied to a single cloud ecosystem. Software purchased on AWS Marketplace does not migrate to an Azure account. A company operating two or three cloud providers must maintain two or three independent procurement processes, each with its own dollar invoice, its own FX transaction, and its own tax classification.

How cloud marketplace procurement works in practice

Buying software through a cloud marketplace is not like contracting a vendor directly. The process is coordinated by the cloud provider, which acts as an intermediary between the vendor and the buyer. The contract is with the platform, payment goes into the provider's invoice, and tax classification follows the marketplace rules rather than each individual software's.

First, the buyer identifies the software needed and checks whether it is available on their cloud provider's marketplace. AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace each have their own catalogs, and the same software may be available on more than one. The buyer selects the plan (monthly, annual, or usage-based) and accepts the terms directly in the console.

Second, the purchase is linked to the company's existing cloud account. There is no separate contract with the vendor. Payment enters the monthly cloud provider invoice. The vendor receives payment from the platform, not from the buyer. The company no longer has a direct contractual and FX relationship with each software developer.

Third, the consolidated cloud provider invoice includes both infrastructure spending and third-party software spending, which means the finance department receives one document, still in dollars for most Latin American countries, and processes one international remittance per month instead of processing dozens of individual vendor invoices.

The practical limitation appears when a company uses more than one cloud provider. Software purchased on AWS Marketplace cannot be paid through an Azure account. A company running AWS for production and Google Cloud for analytics needs two independent procurement processes. At this point, a multi-marketplace consolidation layer becomes an alternative.

Three procurement paths: the comparison

Three paths exist for buying international software in Latin America: direct contracting from the vendor, purchasing through a cloud marketplace, or using a multi-marketplace consolidation layer. Not all serve the same buyer. Each solves a part of the FX, tax, and bureaucracy problem. The difference lies in how many cost layers it eliminates and what operational complexity remains for the buyer.

The PIS/COFINS credit line requires a domestic invoice that supports the recovery. In direct procurement and standard cloud marketplace procurement, the buyer does not receive a Brazilian invoice from an international vendor. Nexforce Marketplace issues a domestic invoice, allowing Lucro Real companies (the non-cumulative tax regime in Brazil) to recover the 9.25% in PIS/COFINS. For Lucro Presumido companies (Brazil's presumed-profit tax regime), the benefit lies in the FX rate lock, invoicing in BRL, and operational simplification. The PIS/COFINS credit does not apply to the Lucro Presumido regime.

How much it costs: USD 50,000 in SaaS, three paths

The cost difference between direct procurement, cloud marketplace purchasing, and using a consolidation layer is not marginal. On a USD 50,000 SaaS basket, it can exceed USD 20,000 per year. The example below traces the same purchase, five tools, three procurement routes.

Direct procurement. Five separate remittances of USD 10,000 each. Each remittance pays a bank spread of 6% over the commercial FX rate, IOF at 3.5% on the operation, IRRF at 15%, and CIDE at 10% on each remitted amount. USD 50,000 becomes roughly USD 76,000 equivalent in total cost. In BRL at a rate of 5.70/USD, that is approximately BRL 433,000. The finance department processed five FX operations, five IRRF payments, five CIDE filings, and issued five declarations to the Central Bank of Brazil.

Cloud marketplace. The five tools are purchased inside a single AWS or Azure account, which generates one consolidated monthly invoice of roughly USD 4,170 (USD 50,000 per year divided by 12). Instead of five sporadic remittances, one international remittance per month with predictable volume, which reduces the bank spread. Tax classification is standardized by the marketplace. USD 50,000 becomes roughly USD 67,000 equivalent, approximately BRL 382,000. The operational gain is real, but the invoice stays in dollars, and IRRF and CIDE still apply to it.

Nexforce Marketplace. The five tools are consolidated regardless of each one's cloud provider. Payment is monthly, in BRL, with an FX rate lock at the time of contracting. USD 50,000 becomes roughly USD 62,000 equivalent in gross cost. Nexforce's domestic invoice allows Lucro Real companies to recover 9.25% in PIS/COFINS, reducing the net cost to approximately USD 56,000. In BRL, that is roughly BRL 353,000 in gross cost or BRL 319,000 net with the credit. For Lucro Presumido companies, the gross cost is the same, and the benefit comes from the FX rate lock, the BRL invoice, and the complete elimination of the FX operation.

The difference between the most expensive path and the cheapest path is USD 20,000 per year.

Over two years, the extra cost of direct procurement equals 80% of the software value. The example uses a commercial FX rate of BRL 5.70/USD with a 6% spread on the rate for the direct procurement calculation, and IRRF rates of 15% and CIDE of 10% on SaaS as classified by the Receita Federal.

Frequently asked questions about cloud marketplace procurement

Which cloud marketplace should I choose?

It depends on the cloud provider the company already uses. AWS Marketplace is the natural path for companies concentrating infrastructure on AWS, while Azure Marketplace serves the Microsoft ecosystem and Google Cloud Marketplace serves GCP-native organizations. Nexforce Marketplace functions as an independent layer that crosses all three, consolidating purchases from multiple marketplaces and direct vendors into a single contractual relationship with invoicing in BRL.

Does the cloud marketplace eliminate IRRF and CIDE?

No, but it reorganizes the tax base. The taxation on cross-border remittances still exists. The marketplace standardizes the tax classification and consolidates the value on which IRRF and CIDE apply. Instead of five tax events on five smaller remittances, one tax event on the consolidated invoice. The rate does not change. What changes is the operational complexity and the cost of processing each remittance separately.

My company is under the Lucro Presumido regime. Is a marketplace worthwhile?

Yes. The benefit for Lucro Presumido companies lies in operational simplification: one invoice in BRL, an FX rate lock that eliminates the risk of dollar fluctuation between approval and payment, and a procurement process that requires neither international remittance nor per-software tax classification. The 9.25% PIS/COFINS credit is exclusive to Lucro Real companies in the non-cumulative regime.

Does the marketplace work for any type of software?

For SaaS, yes. For perpetual software licenses and consulting services, the tax classification may differ. CIDE at 10% applies to SaaS and technical services. The exemption under §1°-A of art. 2°, Lei 10.168/2000 applies to pure software licenses without technology transfer. Each type of software needs to be evaluated individually before structuring the procurement.

When each path makes sense

Different companies have different purchasing profiles. A five-person tech startup does not buy software the same way a Lucro Real company with five hundred employees does. The criterion that separates the paths is not company size but the number of vendors, the FX exposure, and the tax regime under which it operates.

1. Direct procurement works when the company buys one or two high-value software licenses per year, has an established FX and international tax structure in its finance team, and can absorb the complexity of each remittance. Above five vendors or USD 100,000 annually, the operational cost stops being worth it.

2. Cloud marketplace (AWS, Azure, or Google Cloud) works when the company already concentrates its cloud infrastructure on one provider, buys software complementary to that ecosystem, and wants to consolidate payment without giving up a dollar invoice. The limitation is ecosystem lock-in: leaving AWS Marketplace means restarting the procurement process elsewhere.

3. Nexforce Marketplace works when the company operates two or more cloud providers, buys software from vendors on different marketplaces, and also buys from vendors not on any marketplace. Nexforce consolidates everything, regardless of cloud provider, into a single contractual relationship with invoicing in BRL, an FX rate lock, a domestic invoice that enables the PIS/COFINS credit for Lucro Real companies, and centralized renewal and budget management.

International software procurement in Latin America is not a choice between right and wrong. It is a choice between how much complexity the company absorbs internally and how much it transfers to a specialized layer. The cost is not on the software invoice. It is in everything that comes after it.

References and Further Reading

• Software Import Taxes: Complete Guide (nexforce.ai)
• Taxes on Imported Software: Calculation Guide (nexforce.ai)
• ABES. Mercado Brasileiro de Software: Panorama e Tendências 2025. Available at: abes.org.br
• SC Cosit 191/2017 and SC Cosit 99/2018. Receita Federal do Brasil. Classification of SaaS as a technical service for CIDE purposes.
• Lei 10.168/2000, art. 2°, §1°-A. Establishes CIDE on cross-border remittances.
• Lei 10.865/2004. Establishes PIS/COFINS-Importação.