SaaS compliance in Latin America: a country-by-country guide

A company can close a SaaS contract in six countries and still not have a regional operation. For finance, that means six questions about billing, currency, and settlement. For legal, it means six reviews of data, contract, and liability. For tax, it means six different answers about who withholds, which document proves the sale, and what happens when the supplier is outside the country.

For ISVs (Independent Software Vendors, software companies that sell their product to other businesses), the question before the first contract is not whether Latin America is in the plan. It is another one: in which country can the company sell right now without turning every customer into an exception? This guide defends an operational answer: start with the country where the ISV can prove the operation, classify the others as conditional go or no-go, and only scale after closing the gaps.

Scope and date. This is a COMPARATIVE analysis, aimed at the international ISV selling in Latin America. The Brazilian tax analysis is valid as of August 13, 2026, with the effective-date table of Distribution Counsel consolidated on July 6, 2026. Changes after that snapshot were not independently incorporated into the table. The transitions planned for 2027 and for 2029 to 2033 must be rechecked before any contract, transaction, or assessment position. The Distribution Counsel legislative corpus covers Brazil. Mexico, Argentina, Colombia, Chile, and Peru appear only as preliminary regulatory screening, with general official sources consulted on August 13, 2026. No statement about those five countries establishes a rate, deadline, registration, billing, privacy, consumer, security, penalty, or non-resident supplier obligation. Each point requires a specific, dated, verifiable official instrument, plus validation with local counsel. A general authority page is a starting point for research, not a conclusion applicable to the specific contract.

What SaaS compliance must resolve before entry

SaaS compliance is the ability to sell, bill, deliver, renew, and terminate a software product inside the rules that apply to the customer's country. The term covers taxation, billing, privacy, contract, security, payments, and operations. The company is ready when it can name the person responsible for each obligation, keep the evidence, and explain the flow to a customer, auditor, or authority.

The problem usually appears after the sale. Sales promises a price in local currency, finance discovers a withholding, legal receives a foreign contract, and the product team realizes the data will be processed by an unevaluated subcontractor. None of this is an isolated legal surprise. It is a market entry without an operational design.

The matrix must separate three levels of certainty:

1. Confirmed rule: an obligation supported by a law, a tax authority, a data protection authority, or a current, dated official publication.
2. Operational hypothesis: a procedure that seems compatible with the model but depends on the customer, the sales channel, the contract, the billing, or the processing location.
3. Blocking gap: missing information that prevents the company from demonstrating that it can start, such as the identity of who issues the tax document or the classification of the service.

The operational heuristic created for this guide is direct: a country with eight verifiable answers offers a better base for the first market than a larger country with two commercial promises and six open questions. This is not a legal requirement, an official risk score, or a universal readiness metric.

How to build the per-jurisdiction evaluation matrix

The matrix converts a regional ambition into a per-country decision. For each jurisdiction, the ISV fixes the use case, attaches the source of each claim, names the internal owner, and records what still depends on local opinion. If a material axis has a blocking gap, the country does not receive go, even if the other axes are documented.

The table organizes the work. The figure shows the moment when investigation turns into decision.

The matrix must also stay valid. A new form of billing, a consumer customer, a data subcontractor, or a change to the standard contract reopens the analysis. The calendar alone does not detect those changes.

Brazil: confirmed rule, tax transition, and validation points

Brazil has tax coverage in the Distribution Counsel corpus, but not full compliance coverage. The analysis is valid as of August 13, 2026, with the effective-date table consolidated on July 6, 2026. Privacy, consumer, security, billing, and payments require their own official sources and specialized evaluation.

Mode CLIENT, direct contracting by the Brazilian customer. For a direct contract by the Brazilian customer, IRRF (withholding income tax), CIDE, and the other taxes depend on the legal classification and the contract clauses. This dossier does not carry enough support to apply Solução de Consulta Cosit 191/2017 automatically to that specific fact: the corpus document deals with SaaS purchased from a foreign supplier for resale to users or customers in Brazil. The Cosit SC is administrative guidance that binds the Receita Federal within its scope, not a general court decision. The classification of the direct contract must be validated by Distribution Counsel. [Official source: SC Cosit 191/2017, official Receita Federal document, consulted on August 13, 2026. The document is preserved in the Distribution Counsel corpus at references/legislation/brazil/importacao-software/cide/Importação - CIDE - Cosit 191 2017.pdf; the consultation deals with the facts described in it.]

The CIDE distinction remains decisive, but it does not authorize carrying the distributor consultation over to the customer. In Mode CLIENT, the 10% CIDE and the classification of SaaS as a technical service can only be applied to the direct contract when there is an official instrument that covers the facts. The exemption in art. 2, §1-A, of Lei 10.168/2000 is restricted to the license of use or to the commercialization or distribution rights of a computer program without transfer of the corresponding technology. Pure license and SaaS are not the same category. [Official source: Lei 10.168/2000, art. 2, §1-A and §2, Planalto, consulted on August 13, 2026; regime distinction: references/tax-incidence-modes.md, lines 5 to 19.]

The Solução de Consulta Cosit 99/2018, of August 17, 2018, deals with a different question. It records the administrative position that IRRF composes the CIDE calculation base by addition to the net remuneration, when the facts of the consultation and the current law are applicable. SC Cosit 99/2018 binds the Receita Federal within its scope; it is not a court precedent or a universal rule. The gross-up and the base must be tested against the contract and the legislation in force. It is not the source of the SaaS classification. [Official source: SC Cosit 99/2018, summary and lines 28 to 40, 166 to 224 of the corpus document, consulted on August 13, 2026.]

PIS/COFINS-Import also cannot be reduced to a single generic line. In Mode CLIENT, the effective-date table records 1.65% PIS and 7.6% COFINS, totaling 9.25%, only under the applicable import-of-services hypothesis. The classification of license, SaaS, support, and grouped services controls the framing. The credit depends on the non-cumulative regime, the nature and documentation of the operation, the bookkeeping, and the buyer's legal requirements. A company under Lucro Presumido (presumed profit) does not take that credit. [Official source: Lei 10.865/2004, arts. 7 and 8, and IN RFB 2.121/2022, art. 273, consulted on August 13, 2026; current state: references/legislation/brazil/VIGENCIA.md, lines 7 to 12.]

Mode COMPARATIVE, direct contracting versus the route contracted via Nexforce Marketplace. The domestic invoice in reais from Nexforce can join the documentation analyzed for a possible credit by a company under Lucro Real (actual profit), but the invoice alone neither creates nor guarantees credit. The treatment depends on the buyer's non-cumulative regime, the nature and documentation of the operation, the bookkeeping, the contract, and the tax classification confirmed by Distribution Counsel. For Lucro Presumido, the operational benefit lies in local currency, an invoice in reais, and simplification, not in PIS/COFINS credit. In 2026, PIS/COFINS, including PIS/COFINS-Import, remain under the current regime. From 2027, the transition replaces those contributions with CBS in the form set out in art. 126 of the ADCT and in LC 227/2026. From 2029 to 2032, the ISS and ICMS rates are reduced in the proportions of art. 128 of the ADCT, and those taxes are extinguished from 2033 by art. 129. Do not present a future full CBS or IBS rate as in force. [Official sources: EC 132/2023, ADCT, arts. 126 to 129, Planalto, consulted on August 13, 2026; LC 227/2026, transition provision reproduced at lines 15866 to 15869 of the corpus; current state: references/legislation/brazil/VIGENCIA.md, lines 7 to 14.]

The tax reform requires separating effective date from planning. In 2026, PIS/COFINS and ISS remain under the current regime. From 2027, the transition replaces PIS/COFINS and PIS/COFINS-Import with CBS in the form of art. 126 of the ADCT and LC 227/2026. From 2029 to 2032, ISS and ICMS are reduced in the proportions of art. 128 of the ADCT, and those taxes are extinguished from 2033 by art. 129. A future full CBS or IBS rate must not be presented as in force; any planning number must be identified as a hypothesis. [Official sources: EC 132/2023, ADCT, arts. 126 to 129, Planalto, consulted on August 13, 2026; LC 227/2026, lines 15866 to 15869 of the corpus; current state: references/legislation/brazil/VIGENCIA.md, lines 7 to 14.]

For the ISV's entry, the Brazilian result is conditional go until the classification, the contract, the party responsible for the tax document, and the remittance flow are documented. The direct customer route and the Marketplace route are distinct comparisons. Contract, taxpayer, and tax layer cannot be mixed.

Mexico: confirm the digital VAT and the non-resident role

Mexico, preliminary analysis. The Distribution Counsel corpus does not contain a Mexican legislative folder. The general SAT page, consulted on August 13, 2026, is only a starting point for research. This dossier carries no support to conclude a rate, deadline, registration, billing, privacy, consumer, security, penalty, or non-resident supplier obligation. Each claim needs a specific, dated, verifiable Mexican official instrument, plus validation with local counsel before entry.

The Servicio de Administración Tributaria, SAT, is the official tax authority identified to start research on digital services. The general page consulted is not proof of treatment for the B2B SaaS of the contract analyzed. The ISV must identify who contracts, who pays, who bills, and which document will be delivered, with local validation. [Official research source: SAT, "Servicios digitales", https://www.sat.gob.mx/consultas/38828/servicios-digitales, consulted on August 13, 2026.]

Official source identified: SAT is the authority consulted, but the page does not close the treatment of the contract. Operational hypothesis: the model may work with direct billing or with regional infrastructure, but the responsibility depends on the contract. Blocking gap: this dossier carries no local opinion on registration, filing, tax document, and B2B treatment of the chosen flow. The recommended classification is conditional go, not go.

Privacy, security, and contract must follow the same path. Without a specific official source in the dossier and without local opinion for the operation, the article does not state an additional Mexican obligation.

Argentina: close currency, billing, and contract before promising scale

Argentina, preliminary analysis. The Distribution Counsel corpus covers only Brazil. The general ARCA page, consulted on August 13, 2026, is a starting point for research, not a specific source on B2B SaaS from a non-resident supplier. This dossier carries no support to conclude a rate, deadline, registration, billing, privacy, consumer, security, penalty, or uniform obligation. Each point requires a specific Argentine official instrument and local validation. The currency decides.

ARCA is the official tax authority identified to start tax research, but the institutional page consulted is only a starting point. It does not prove treatment for B2B SaaS from a non-resident supplier. The decision starts with a specific instrument and a local opinion. [Official research source: ARCA, https://www.arca.gob.ar/, consulted on August 13, 2026.]

Official source identified: entry must be investigated with the Argentine tax authority and the exchange rules of the flow. Operational hypothesis: VAT, withholdings, currency, and remittance vary with the customer, the acquirer, the contract, and the intermediary. Blocking gap: a promised price and deadline with no confirmed mechanism for billing, reconciliation, and settlement. The country receives conditional go for a documented pilot, never automatic go for scale.

The official source consulted is not enough to state a rate, a registration deadline, or a uniform obligation for all B2B SaaS. Those points must be closed by Argentine counsel before the contract.

Colombia: document who sells and who invoices

Colombia, preliminary analysis. The Distribution Counsel corpus does not contain Colombian legislation. The general DIAN page, consulted on August 13, 2026, is a starting point for tax and electronic-invoicing research. It does not prove the framing of the chosen SaaS nor define who is responsible for each stage of the contract. This dossier carries no support to conclude a rate, deadline, registration, billing, privacy, consumer, security, penalty, or non-resident supplier obligation. A specific Colombian official source and local validation are required. [Official research source: DIAN, https://www.dian.gov.co/, consulted on August 13, 2026.]

Official source identified: DIAN is the authority to consult for VAT and tax documentation, but the institutional page does not close the case. Operational hypothesis: the treatment of the non-resident supplier, electronic invoicing, and withholdings depends on the concrete sale. Blocking gap: not knowing who sells, who bills, who issues, and who files the document. Without that answer, there is no-go for scale. A pilot can only be conditional go after prior local validation.

B2B and B2C must not be merged into a single conclusion. The same application can have different contractual and documentary flows.

Chile: separate the business customer from the consumer

Chile, preliminary analysis. The Distribution Counsel corpus covers only Brazil. The general SII page, consulted on August 13, 2026, is a starting point for research, not proof of the tax treatment of the analyzed SaaS. It indicates an axis to investigate, not a rate, document, or registration applicable to the contract. This dossier carries no support to conclude a tax, billing, privacy, consumer, security, penalty, or non-resident supplier obligation. A specific Chilean official source and local validation are required. [Official research source: Servicio de Impuestos Internos, "Servicios digitales", https://www.sii.cl/servicios_online/1039-.html, consulted on August 13, 2026.]

Official source identified: digital services and VAT must be researched at the SII, but the general page does not close the contract. Operational hypothesis: the B2B flow may receive treatment different from B2C. Blocking gap: not knowing which rule reaches the customer that actually pays. A B2B operation with validated documentation receives conditional go. Entry into consumers remains no-go until a dedicated analysis.

The contract must separate billing, cancellation, consumer protection, data, and support. The article does not present a Chilean conclusion on those topics without a specific and current source.

Peru: validate service, customer, and remittance

Peru, preliminary analysis. The Distribution Counsel corpus covers only Brazil. The general SUNAT page, consulted on August 13, 2026, is a starting point to research IGV, digital services, and non-domiciled suppliers, but it does not close the ISV's case. This dossier carries no support to conclude a rate, deadline, registration, billing, privacy, consumer, security, penalty, or uniform obligation. A specific Peruvian official source and local validation are required before the decision. [Official research source: SUNAT, https://www.sunat.gob.pe/, consulted on August 13, 2026.]

Official source identified: the treatment of digital services and non-domiciled suppliers must be researched at SUNAT, but the general page does not close the contract. Operational hypothesis: the result depends on the contract, the economic user, the billing, and the remittance abroad. Blocking gap: starting to bill without an opinion on the chosen flow. Without local documentation, Peru is no-go for scale. A pilot only becomes conditional go after closing the tax gap.

There is no base in the available corpus to state a Peruvian rate, deadline, registration, or uniform obligation for B2B SaaS. Peruvian counsel must also validate data, consumer, security, and contract.

How to turn the matrix into go, conditional go, or no-go

The classification measures the distance between the promised sale and the demonstrable operation. It does not measure market size. The same country can be go for a B2B product with an annual contract, tested billing, and documented responsibilities, and no-go for a B2C card subscription with no validated tax flow.

1. Fix the case: country, customer, price, currency, contract, billing, processing, support, and renewal.
2. Attach the source: a dated official rule or publication for each legal claim; local opinion when the corpus does not cover the country or the subject.
3. Name the gap: writing "confirm who issues the tax document" is useful. Writing "check taxes" is not.
4. Give the verdict: go without a material gap; conditional go with documented conditions for a pilot; no-go when the company cannot prove the operation.

The rule avoids a false sense of security: six filled columns do not compensate for two critical empty columns.

When regional infrastructure reduces the operational burden

The matrix comes before the commercial choice because it defines the country, the customer, the currency, the contract, the billing, and the responsibilities the operation must prove. Mode COMPARATIVE, commercial proposal. That order avoids choosing a channel for the promise of scale before knowing which obligations remain the ISV's responsibility and which depend on the contract.

The direct path through a cloud marketplace charges an operational price before the first sale: the ISV faces listing and review cycles, pays fees on each transaction, adapts to the platform's contract and programs, may need a commitment to a cloud to transact, and may need to manage a foreign tax entity, USD settlement, exchange cost, repatriation, and compliance on its own. The friction is not a footnote. It enters the sales cycle.

After that comparison, Nexforce Marketplace can be considered when the international ISV needs to sell in LatAm through Nexforce's local infrastructure, receive in local currency, and offer regional payment methods, according to the solution and the contract. Those commercial attributes can reduce operational tasks, but they do not create legal exemption, automatic registration, or tax relief. The commercial description is based on references/nexforce-products.md, not on a legal conclusion.

Nexforce Marketplace presents two distinct commercial solutions: selling in LatAm through Nexforce's infrastructure or selling through a cloud marketplace with Nexforce leading that path. According to the solution, the country, the payment method, the eligibility, and the contract, the commercial proposal may accept the ISV's contract standard and programs, operate without commitment to a specific cloud, connect a reseller network, receive in local currency in the region, and offer Pix, boleto, local cards, and installments. The possibility of paying the ISV up front while the customer pays in up to 12 installments also depends on those same factors. The absence of the ISV's own local entity is a documented commercial possibility, not a legal exemption. Those attributes do not eliminate permanent establishment, registration, license, or tax obligation analysis. [Commercial source: references/nexforce-products.md, lines 43 to 71.]

The commercial proposal still needs to answer who is the seller, who issues the invoice, who bills, who settles, who answers for taxes, how registration, license, refund, and chargeback work, and which permanent establishment analysis applies. Those points depend on the contract, the country, and the exact operational model. The article does not call Nexforce a MoR, reseller, payment agent, or financial institution without a contract and source that support that label.

The gain for the ISV is reducing the number of flows it must manage alone. The legal decision remains with the concrete case.

Final checklist for the ISV's decision

Before opening sales, the team must prove that the chosen flow works in the defined country, for the defined customer, and in the defined currency. The checklist below turns each promise into evidence: a dated official source for the rule, a document for the billing, an internal owner, and a declared gap when the operation still depends on local counsel.

• Which use case was analyzed and who pays?
• Was SaaS distinguished from pure license and from additional technical services?
• Does each tax claim have a specific official source and a consultation date?
• Who issues the tax document and who files the evidence?
• Does the contract cover applicable law, forum, data, security, support, and cancellation?
• Were subcontractors and international data transfers mapped?
• Was the payment method tested in the customer's currency?
• Who reconciles settlement, withholding, renewal, and chargeback?
• Is there a gap that blocks scale?
• Did the country receive go, conditional go, or no-go with a verifiable justification?

As the operational heuristic created for this guide, three answers that end in "the accountant will sort it out later" indicate that the country is not ready for scale. The criterion is not a legal requirement, an official risk score, or a universal metric. Nor does it replace legal analysis.

FAQ about SaaS compliance in Latin America

The questions below close the decisions that most easily turn into a commercial promise without evidence. The correct answer depends on the country, the customer, the contract, and the billing flow. Where the corpus covers only Brazil or the official source is general, the question remains a gap for local counsel, not an authorization to sell.

Can an ISV use the same contract in the six countries?

A base contract can only serve as a drafting starting point. It does not prove compliance in any of the six countries and must not be used unchanged. Taxation, data, consumer, billing, collection, applicable law, forum, and responsibilities require review according to the country, the customer type, the payment flow, the data processing, and the local law before signature.

Does this guide's analysis replace a local opinion?

No. Brazil has support in the Distribution Counsel corpus, with the validity date indicated in the text. Mexico, Argentina, Colombia, Chile, and Peru have a preliminary analysis, based on official sources consulted on August 13, 2026. Entry and scale require local counsel.

Is SaaS always treated as a software license in Brazil?

No. Mode CLIENT: for the customer that contracts SaaS directly from abroad, this dossier does not carry enough support to apply SC Cosit 191/2017 automatically, whose consultation deals with acquisition for resale. The classification of the direct contract, including the incidence of IRRF and CIDE, must be validated by Distribution Counsel. A pure license without technology transfer belongs to another category and must not be confused with SaaS.

What is the difference between go and conditional go?

Go means the material axes have enough evidence to start the defined sale. Conditional go allows a pilot with clear conditions and a deadline to close pending items. No-go means a gap blocks scale or prevents proving the chosen flow.

Does Nexforce Marketplace eliminate local validation?

No. The infrastructure can reduce the currency, billing, remittance, and operational burden according to the contract, and can offer local currency, regional methods, and up-front payment to the ISV with customer installments of up to 12 times when applicable. Those commercial attributes do not waive local validation, and the legal, tax, contractual, and data classification still depends on the country and the model.

References and Further Reading

• Lei Complementar nº 214/2025, Planalto, tax transition under EC 132/2023, ADCT, arts. 126 to 129, consulted on August 13, 2026.
• Emenda Constitucional nº 132/2023, Planalto, ADCT, arts. 125 to 129, consulted on August 13, 2026.
• Lei nº 10.168/2000, Planalto, art. 2, consulted on August 13, 2026.
• Receita Federal, Cosit consultation search, SC Cosit 191/2017 and 99/2018, consulted on August 13, 2026.
• SAT, Servicios digitales, consulted on August 13, 2026.
• ARCA, Administración Federal de Ingresos Públicos, official source consulted on August 13, 2026.
• DIAN, Dirección de Impuestos y Aduanas Nacionales, official source consulted on August 13, 2026.
• SII, Servicios online, consulted on August 13, 2026.
• SUNAT, Superintendencia Nacional de Aduanas y de Administración Tributaria, official source consulted on August 13, 2026.
• Nexforce Marketplace, commercial attributes consulted on August 13, 2026.

What is the next step toward a documented entry?

The entry decision is only ready when the matrix shows who does what, with which document, and under which source. The first country does not need to be the largest. It needs to be the first in which the ISV can sell without hiding a material gap inside the contract.

For the international ISV that needs to sell in LatAm through Nexforce's local infrastructure, receive in local currency, and offer regional payment methods, Nexforce Marketplace can reduce the number of operational flows the ISV manages alone, subject to the solution and the contract. That reduction does not replace local validation. The legal classification, the tax treatment, the contract, and the data position still depend on the country and the model, so the matrix stays the gate between the commercial promise and the demonstrable operation.