Software Marketplaces: The Complete Guide for Brazilian ISVs Selling on Cloud Marketplaces

Brazilian ISVs selling on cloud marketplaces lose between 8% and 15% of revenue before the money reaches the bank account. Not because of product failure. Because of tax structure failure.

AWS processes the charge in USD. Azure invoices in foreign currency. Google Cloud Marketplace settles in dollars. The platform handles technical distribution. Currency conversion, taxes, and invoice issuance in Brazil are the ISV's responsibility. Most discover the real cost of this architecture in their first quarter of operation.

This guide covers the full path: choosing the right marketplace to tax reconciliation. In five steps, the ISV structures international SaaS sales with control over currency spread and tax burden. Estimated implementation time: 4 to 8 weeks.

The method:

1. Choose the cloud marketplace based on commission, buyer profile, and contract model
2. Structure international payment collection: account, FX, and settlement terms
3. Configure Brazilian tax compliance: tax regime, invoicing, and export exemptions
4. List and price accounting for every layer of cost in the chain
5. Automate financial and tax reconciliation

Prerequisites

Before the first step, the ISV needs four operational elements:

• Active CNPJ with a CNAE code compatible with software exports. CNAEs such as 6201-5/00 (custom software development) or 6203-1/00 (development and licensing of non-customizable software), both under Division 62 (Information and Communication) of CNAE 2.0, cover the activity. Correct tax classification is a precondition for issuing export invoices.
• An account for international payments. Brazilian banks accept international wire transfers, but FX costs are high (3% to 6% spread over commercial rates). Fintech FX accounts (Wise Business, Payoneer, Husky) reduce the spread to 1% to 2%. The choice directly affects margin.
• An active cloud marketplace contract. AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace require publisher registration, tax verification (W-8BEN-E, an entity form that certifies Brazilian tax residency with the IRS), and acceptance of listing terms.
• A defined tax regime. Lucro Real (Actual Profit), Lucro Presumido (Presumed Profit), or Simples Nacional. The choice determines whether export revenue is taxed on actual profit or a presumed base, and whether tax credits are recoverable on the ISV's own software imports.

Step 1: Choose the cloud marketplace based on data, not inertia

The decision of which marketplace to list on does not start with the platform. It starts with the buyer.

The ISV needs to answer: do my target customers use AWS, Azure, or Google Cloud? The marketplace is a distribution channel that mirrors the buyer's infrastructure commitment. Companies with AWS environments buy on AWS Marketplace because the invoice consolidates cloud spend. The same holds for Azure and GCP.

The table below compares the three marketplaces on dimensions that directly affect the Brazilian ISV's financial and tax operations:

AWS Marketplace has the highest transaction volume of the three. Azure attracts ISVs selling to companies with a consolidated Microsoft stack (Dynamics, Power Platform, Office 365). GCP grows among ISVs in data, machine learning, and infrastructure. The choice follows the buyer, not the other way around.

The full registration, verification, and publishing process follows the official AWS Marketplace Seller Guide, with specific requirements for international publishers.

Step 2: Structure international payments so the currency spread does not consume the margin

The payment flow from a cloud marketplace follows three stages: the customer pays the marketplace in their local currency; the marketplace deducts its commission; the marketplace remits the net amount to the ISV, always in USD.

The Brazilian ISV receives USD and must convert to BRL. This process carries three costs most underestimate:

Currency spread. The difference between the commercial exchange rate and the rate applied at conversion. Brazilian banks operate with spreads of 3% to 6%. Fintech FX platforms reduce this to 1% to 2%. On monthly revenue of USD 50,000, the difference between a 1.5% and 5% spread means USD 1,750 per month lost at conversion.

IOF on foreign exchange. The rate is 0.38% on the converted amount, fixed and non-negotiable, under Decree 6.306/2007, art. 15-B, caput. It applies to each FX transaction, not the monthly total. If the ISV converts in weekly batches, IOF is applied four times, slightly reducing the total net base.

Settlement timing. AWS Marketplace pays on a 30-day cycle. The ISV receives the net amount (commission already deducted) approximately 30 days after the customer pays. This cash flow mismatch requires working capital or an FX hedge at the moment of sale, not at the moment of receipt.

The FX hedge is the tool that eliminates dollar fluctuation risk between the sale and the payout. Without it, the ISV prices at USD 100 and receives the BRL equivalent of USD 92 because the exchange rate moved. With a hedge, the real-denominated amount is locked at the transaction date.

Step 3: Configure Brazilian tax compliance, the layer most ISVs neglect

A Brazilian ISV selling SaaS through an international cloud marketplace is, legally, exporting services. This defines the tax treatment: rates differ from domestic sales, and specific ancillary obligations apply.

ISS (Municipal Service Tax). Lei Complementar 116/2003 (art. 2, I) establishes that ISS does not apply to service exports. There is a relevant exception: the Sole Paragraph of the same article excludes from the exemption services developed in Brazil whose result materializes in Brazil, even if the payer resides abroad. In practice, ISVs with local development and local consumption may be subject to municipal tax regardless of where the payment originates. Issuing the export invoice with the correct CFOP code and maintaining the marketplace contract documentation is the documentary defense against this contingency.

PIS and COFINS (Federal Social Contributions). Revenue from service exports falls outside the scope of COFINS (Lei 10.833/2003, art. 6, II) and PIS (Lei 10.637/2002, art. 5, II), provided the payment represents an inflow of foreign currency into the country. The ISV must archive marketplace payment reports as supporting documentation.

Tax reform transition notice. LC 214/2025 (Tax Reform) establishes the gradual replacement of ISS and PIS/COFINS with IBS (Imposto sobre Bens e Servicos) and CBS (Contribuicao sobre Bens e Servicos), with a transition phase from 2029 to 2032. Export exemptions are maintained in the new system, but tax procedures, document issuance, and calculation methods will change. ISVs operating international sales must track secondary regulation and prepare their systems for the transition.

IRPJ and CSLL (Corporate Income Tax and Social Contribution on Net Profit). Taxation on profit follows the company's regime. Lucro Real taxes actual profit. Lucro Presumido applies a 32% presumption on gross revenue (as the IRPJ base) and 32% for CSLL. Simples Nacional uses a progressive table, with limitations for higher-volume exports. ISVs under Lucro Presumido with profits exceeding BRL 20,000 per month pay an additional 10% IRPJ surcharge on the excess (BRL 240,000 annually).

Export invoice (NFS-e). Each marketplace payout to the ISV requires a municipal service export invoice (NFS-e), following the rules of the provider's municipality. The invoiced amount is the net amount received (marketplace commission already deducted). The ISV does not invoice the gross amount the marketplace charged the end customer, because the marketplace is the primary counterparty to the transaction and the ISV receives the net payout.

Domestic versus international sales. If the ISV also sells SaaS to Brazilian customers, the tax treatment is entirely different. Domestic sales have ISS (2% to 5%), cumulative or non-cumulative PIS/COFINS, and distinct ancillary obligations. Mixing both operations in the same accounting structure creates audit risk. Separate accounting by channel (domestic vs. international marketplace) is mandatory.

Step 4: List and price accounting for every cost layer in the chain

Pricing on a cloud marketplace must cover five cost layers that do not appear in the simplistic "price minus commission" calculation:

1. Marketplace commission (3%, per the Step 1 table)
2. Currency spread (1% to 6%, depending on bank or fintech)
3. IOF on FX (0.38%)
4. IRPJ/CSLL (per the tax regime)
5. Operational compliance cost (invoice issuance, international accounting)

Real calculation example for an ISV under Lucro Presumido selling an annual subscription of USD 12,000 through AWS Marketplace (standard 3% commission):

• Gross revenue: USD 12,000
• AWS commission: USD 360 (3%)
• Payout to ISV: USD 11,640
• Currency spread (2%): USD 233 (loss at conversion)
• IOF (0.38%): USD 44
• Net amount in USD: USD 11,363
• IRPJ/CSLL base (32% presumption): USD 3,636
• IRPJ (15%): USD 545; CSLL (9%): USD 327
• Total tax cost: USD 872
• Final net amount: USD 10,491

Out of USD 12,000 billed, the ISV retains USD 10,491. The effective combined rate (commission + spread + taxes) is 12.6%. Pricing without factoring in this layer destroys margin in the first billing cycle.

For ISVs distributing SaaS internationally while also consuming software and AI for their own operations, Nexforce Marketplace handles imports with BRL-denominated invoicing and FX hedging, unifying technology consumption costs with the distribution operation.

Step 5: Automate reconciliation to prevent invisible tax liability from accumulating

The most expensive mistake in cloud marketplaces does not happen at listing. It happens during monthly reconciliation, six months later, when the ISV realizes the marketplace reports do not match the bank statements and the invoices issued.

The monthly reconciliation cycle requires three aligned sources:

• Marketplace payment report (AWS Marketplace Report, Azure Payout Report, GCP Payment Report) with the gross amount billed by the marketplace, the retained commission, and the net amount remitted.
• Bank statement confirming the receipt of the net amount in USD and the conversion to BRL.
• Export invoices issued with amounts matching the net amount received.

A discrepancy between these three documents is the tax liability that grows silently. The ISV declares one amount on IRPJ, the marketplace reports another, the bank records a third. If the Brazilian Federal Revenue cross-checks the data, the audit arrives with penalties, interest, and inflation adjustment.

Manual reconciliation works for five transactions per month. For fifty, automation is mandatory. ERP tools with foreign trade modules or international revenue management platforms consolidate the three streams into a single dashboard and issue invoices automatically at the close of the marketplace payment cycle.

How to verify the structure is working

The real test is the first complete sales cycle: a customer closes a subscription on the marketplace, the marketplace processes the payment, deducts its commission, and remits to the ISV, who converts USD to BRL, issues the export invoice, and books the revenue. If the amounts on the payment report, the converted bank statement, and the issued invoice match within a 1% tolerance, the structure is operational.

If the discrepancy exceeds 1%, the problem lies in one of three layers: either the currency spread was higher than projected, or the marketplace commission was applied at a different tier than expected, or the invoice was issued with an incorrect amount.

Common errors and how to fix them

Error 1: treating the marketplace sale as domestic revenue. The ISV issues a service invoice with ISS, PIS, and COFINS as if it were a local sale. The fix is to reclassify the transaction as a service export, cancel the incorrectly issued invoices, and reissue them as export invoices.

Error 2: failing to submit the W-8BEN-E. Without the form, the marketplace applies a 30% withholding tax in the US. The ISV receives 30% less. The W-8BEN-E (an entity-specific form) declares that the ISV is a Brazilian tax resident and therefore not subject to US taxation on revenue from services provided outside US territory. The absence of a double taxation treaty between Brazil and the US makes the form even more critical: without it, the marketplace classifies the payments as US-source income and applies withholding. The fix is to submit the W-8BEN-E immediately, with guidance from an accountant experienced in international taxation.

Error 3: pricing without the currency spread. The ISV sets the USD price looking only at the marketplace commission. The 2% to 6% conversion spread does not appear on the payment report but erodes the BRL net. The fix is to recalculate the list price including the spread as a fixed operational cost.

Error 4: not separating domestic and international accounting. Mixed operations generate inconsistency in the tax books. The fix is to create distinct cost centers: one for marketplace export revenue, another for domestic revenue.

Error 5: invoicing the gross transaction amount. The ISV invoices the amount the customer paid the marketplace, without deducting the commission. The fix is to issue the invoice for the net amount the marketplace actually remitted, which is the ISV's real revenue.

Frequently Asked Questions (FAQ)

Which cloud marketplace should a Brazilian ISV start with?

AWS Marketplace, for three objective reasons. First, it has the highest transaction volume and the largest base of active enterprise buyers. Second, it has the most documented listing process and the lowest technical barrier for SaaS API integration. Third, the ISV Accelerate program reduces commissions for publishers that reach certain volume thresholds. Azure Marketplace is the correct choice for ISVs whose customers primarily operate on the Microsoft stack. Google Cloud Marketplace is the best option for ISVs in data, analytics, and machine learning.

How does the ISV receive payment from cloud marketplace sales?

The marketplace processes the customer's payment and remits the net amount (commission already deducted) to the ISV in USD, via ACH or wire transfer. The ISV needs an account capable of receiving international dollar transfers. The funds arrive in USD. Conversion to BRL happens either in the international account (if a fintech converts automatically) or through an FX contract at the Brazilian bank.

What taxes does a Brazilian ISV pay on international cloud marketplace sales?

ISS does not apply (service exports, LC 116/2003, with limitations from the Sole Paragraph). COFINS does not apply to export revenue (Lei 10.833/2003, art. 6, II) and PIS does not apply (Lei 10.637/2002, art. 5, II), contingent on foreign currency inflow. IOF on FX applies at 0.38% on conversion (Decree 6.306/2007, art. 15-B). IRPJ and CSLL apply to profit according to the tax regime (Lucro Real, Lucro Presumido, or Simples Nacional). Under Lucro Presumido, the effective IRPJ/CSLL burden on gross revenue is approximately 7.7%, plus the 0.38% IOF on FX. With the additional 10% IRPJ surcharge on profits exceeding BRL 20,000 per month, the combined rate can reach approximately 10.9% for ISVs with higher revenue volume. LC 214/2025 (Tax Reform) provides for the gradual replacement of ISS and PIS/COFINS by IBS/CBS between 2029 and 2032.

Does the ISV need to issue an invoice for every individual marketplace sale?

No. The ISV issues an export invoice for each marketplace payout cycle, typically monthly. The invoice amount is the total net amount remitted by the marketplace in that cycle, consolidating all customer transactions for the period. The marketplace payment report serves as supporting documentation for the invoice.

Does the cloud marketplace handle taxes automatically?

No. The cloud marketplace is a distribution and billing channel. It processes payments, calculates and retains its own commission, and issues reports. Tax responsibility in the ISV's country of residence (Brazil) is entirely the ISV's: invoice issuance, tax calculation, export documentation, and tax record filing. The marketplace does not replace accounting or compliance.

From listing to continuous operation

Listing SaaS on a cloud marketplace is the visible step. The operation that sustains margin and compliance is invisible, and that is where Brazilian ISVs encounter real friction: FX, taxes, and reconciliation.

Nexforce Marketplace offers an alternative and superior distribution and payment infrastructure compared to global cloud marketplaces, eliminating manual work on currency conversion, invoice issuance, and report reconciliation. For the international software the ISV itself consumes in its own operations, Nexforce handles imports with BRL-denominated invoicing and FX hedging, allowing companies under Lucro Real to recover PIS/COFINS credits through domestic invoices.

The cloud marketplace solves distribution. The financial operation that turns foreign revenue into net profit in Brazil requires an additional layer. It exists. The question is whether the ISV builds that layer before or after losing margin in the first quarter.

References and Further Reading

• AWS Marketplace Seller Guide
• Azure Marketplace Publisher Guide
• Google Cloud Marketplace Documentation
• Lei Complementar 116/2003 - ISS on service exports
• Lei 10.637/2002 - Non-cumulative PIS and export exemption
• Lei 10.833/2003 - Non-cumulative COFINS and export exemption
• Decree 6.306/2007 - IOF/FX, art. 15-B
• Lei Complementar 214/2025 - Tax Reform (IBS/CBS)
• IRS Form W-8BEN-E