What Is a Merchant of Record? Guide for SaaS Companies Going Global

The CFO of a Brazilian SaaS company closing a customer in Germany finds out on the first remittance that the money does not arrive whole. The payment processor withheld 3%. The bank applied a 4% spread on the FX. The tax authority wants withholding tax, social contributions, and financial transaction tax on the remittance. The municipal service tax depends on the city. The accountant, three months later, asks whether the transaction was a service or a license.

The Merchant of Record solves the second half of this problem. The first half, the sale, the SaaS company already owns. The second half, the transaction, is where the invisible cost accumulates.

What is a Merchant of Record?

A Merchant of Record is the legal entity that assumes responsibility for the sale toward the buyer and the tax authorities. The SaaS company closes the deal. The MoR processes the payment, calculates and remits all taxes, issues the fiscal documentation, and assumes chargeback and compliance risk.

The essential distinction: the MoR is the legal seller. The contract with the end customer is in the MoR's name. The invoice comes from the MoR's legal entity. A billing dispute is against the MoR. The SaaS company receives the net amount from the MoR, with taxes and the service fee already deducted. The commercial relationship with the customer belongs to the SaaS company. The transaction belongs to the MoR.

How does the Merchant of Record model work?

A transaction through a MoR operates in two distinct legal stages, with four participants.

Stage 1: the sale to the end customer. The MoR enters into the contract with the buyer in its own name. It processes the payment through the buyer's local method (credit card, bank transfer, local payment rails). It calculates, withholds, and remits all taxes due in the buyer's jurisdiction. It issues the invoice or tax document under the MoR's legal entity.

Stage 2: the payout to the SaaS company. The MoR transfers the net amount to the SaaS company that provided the software. The transfer occurs in local currency or foreign currency, per the agreement between MoR and SaaS. The SaaS company receives a consolidated amount, already net of taxes, service fees, and any chargebacks.

The four participants: the end customer, who pays in local currency; the MoR, which legally assumes the transaction; the SaaS company, which delivers the software and receives the payout; and the tax authorities in each jurisdiction reached, which receive the taxes from the MoR.

The MoR charges for the service in two typical ways: a percentage of transaction volume (4% to 7%, varying by industry, geography, and chargeback risk) or a fixed fee per transaction plus a reduced percentage. The percentage covers compliance costs, assumed risk, and the provider's margin.

Merchant of Record, payment processor, and PayFac: what is the difference?

The three models are frequently confused, but the legal distinction is definitive. Who appears on the end customer's invoice determines the model.

A payment processor (Stripe, Adyen, PagSeguro) connects the SaaS company to acquirers and card networks. The SaaS company retains the legal relationship with the customer and is responsible for taxes. A PayFac (Stripe Connect, Pagar.me) goes one step further: onboards the SaaS company as a sub-merchant and simplifies registration, but the SaaS company remains the legal seller.

The MoR is a different category. The SaaS company transfers the transaction to the MoR. The legal relationship with the buyer shifts to being between buyer and MoR. The SaaS company appears as the software provider, not as the seller on the invoice.

Why do SaaS companies in Latin America need a Merchant of Record?

Selling SaaS internationally without a MoR means incorporating in every jurisdiction reached. Every country where the SaaS company has customers requires tax registration, indirect tax calculation, local document issuance, and ongoing compliance.

Complexity scales fast. Five European countries mean five VAT regimes. Three U.S. states already configure distinct sales tax rules after Wayfair (2018). India applies an 18% GST on cross-border digital services. Australia, 10% GST.

For a Latin American SaaS company, the MoR solves two fronts simultaneously:

Front 1: selling abroad. A MoR with global presence processes the German customer's payment, calculates German VAT (19%), issues the invoice per local requirements, and remits the net amount to the LatAm SaaS company. The SaaS company does not need a legal entity in Germany.

Front 2: buying from abroad. Companies in Latin America that consume international software face the other side of the same coin. In Brazil, this means: 15% withholding tax (IRRF) on the remittance (25% if the beneficiary is in a tax haven), 1.65% PIS and 7.6% COFINS social contributions, IOF-FX, and an FX spread of 1% to 4%. The IOF on foreign exchange for outbound funds is 3.5%, in effect under the injunction in ADC 96 (Brazilian Supreme Court, published July 16, 2025), with Decree 12,499/2025 (art. 15-B, XXIV of Decree 6,306/2007). Litigation is pending before the Supreme Court's full bench, but the current rate is 3.5%. A MoR with a local entity in the country processes the transaction domestically and issues an invoice in local currency.

The Nexforce Marketplace operates on this second front as an international software distribution platform. The transaction is invoiced in Brazilian reais, taxes are calculated and withheld automatically, and the domestic invoice allows companies in the non-cumulative Lucro Real regime to recover 9.25% in PIS/COFINS credits. Companies in the Lucro Presumido regime, which do not take PIS/COFINS credits, benefit from the locked FX rate, the BRL-denominated invoice, and the operational simplification of consolidating payment and import into a single process.

The tax equation of selling SaaS from Latin America

The MoR simplifies tax compliance, but simplification has limits. For the LatAm CFO, three cost layers remain relevant even with a MoR.

FX spread and IOF. The MoR pays the SaaS company in USD or local currency. If the payout is in USD and the SaaS company converts to BRL, the FX spread (1% to 4%, depending on volume and FX partner) and IOF (0.38%, Decree 6,306/2007, art. 15-B, XXV) apply on every conversion. A MoR that settles directly in BRL eliminates this additional conversion.

Taxation of the payout. The amount the MoR transfers to a Brazilian SaaS company is service export revenue. For SaaS, the export is exempt from ISS (municipal service tax, Complementary Law 116/2003, art. 2, I), PIS, and COFINS (Law 10,637/2002, art. 5, II, and Law 10,833/2003, art. 6, II), provided the funds enter the country. IRPJ and CSLL apply according to the company's tax regime. Other Latin American countries have their own export service exemptions and thresholds.

Ancillary obligations. Even with a MoR, the Brazilian SaaS company retains reporting obligations: Siscoserv (registration of cross-border transactions), ECF (fiscal accounting records), and, depending on volume, transfer pricing documentation. The MoR eliminates the tax obligation in the buyer's jurisdictions. It does not eliminate the SaaS company's obligations at home.

What the MoR simplifies and what it does not solve

The MoR is a delegation tool. It is not an elimination tool.

What the MoR simplifies:

• Tax registration in multiple countries. The MoR has the entities. The SaaS company does not need to open any.
• Calculation and remittance of indirect taxes (VAT, GST, sales tax) in each jurisdiction.
• Issuance of local invoices or tax documents for each buyer.

Chargeback management and billing disputes also migrate to the MoR, offloading one of the most operationally expensive processes in international sales.

What the MoR does not solve:

• The taxation of the SaaS company's revenue at home. IRPJ, CSLL, PIS, and COFINS on the payout follow the Brazilian service export rules. Other LatAm countries have their own domestic tax frameworks.
• Domestic ancillary obligations (Siscoserv, ECF in Brazil; equivalent regimes in other countries).
• The commercial relationship with the customer. The MoR is the legal seller, not the owner of the relationship. Customer experience (support, onboarding, renewal) remains with the SaaS company.

There is also concentration risk: if the MoR suspends operations in a jurisdiction, the SaaS company loses the ability to sell in that territory until it finds an alternative.

The choice of MoR is, in practice, a compliance outsourcing decision. The CFO outsources the legal complexity of the transaction. They retain the tax complexity of their own company.

How the MoR fits into software import operations

Companies in Latin America buying international software face a problem that global MoRs like Paddle and FastSpring solve for selling, not for buying. These providers are designed for the SaaS company that wants to sell. When a Latin American company is on the buying end, the traditional MoR does not act.

The Nexforce Marketplace operates as a MoR on the import side. A Brazilian company buying HubSpot, OpenAI, Datadog, or any of the more than 150 international solutions available on the platform closes the transaction in Brazilian reais. The Marketplace processes payment via PIX or boleto, locks the exchange rate at the moment of the transaction, calculates and withholds import taxes, and issues the invoice in BRL.

The tax benefit depends on the regime. Companies in the non-cumulative Lucro Real regime recover 9.25% in PIS/COFINS credits: the domestic invoice issued by Nexforce enables the credit, eliminating the tax classification and withholding complexity that direct import demands on every remittance. Traditional payment orchestration solves transaction routing but does not reach the tax layer; the MoR on the import side covers exactly that gap. Companies in the Lucro Presumido regime do not take PIS/COFINS credits: the 9.25% in domestic PIS/COFINS embedded in the invoice represents a non-recoverable cost for this regime. The benefit for them lies in the locked FX rate, the BRL invoice, the elimination of IRRF, CIDE, PIS/COFINS-Importação, and IOF from the import layer, and the simplification of consolidating payment and compliance into a single platform.

The 10% CIDE (Contribution for Intervention in the Economic Domain) applies to SaaS and technical services, per the Brazilian Federal Revenue classification (SC Cosit 191/2017, 99/2018). The exemption under §1-A of art. 2 of Law 10,168/2000 applies exclusively to pure software licenses without technology transfer, a category distinct from SaaS. A MoR operating the import must apply this distinction correctly.

Brazil's Tax Reform and the future of the MoR

Complementary Law 214/2025, which introduces the IBS and CBS to replace ISS, PIS, and COFINS, establishes a phased transition: 2026 as a test year (CBS at 0.9% and IBS at 0.1%), CBS at full rate starting in 2027, and 2029 to 2032 for the transition from ISS and ICMS to the subnational IBS. PIS and COFINS are extinguished in 2027 with the entry of CBS at full rate.

For the MoR, the reform brings two implications. The first is positive: the unification of indirect taxes under IBS/CBS tends to simplify the tax calculation a MoR must perform on each transaction. A single unified tax is more predictable than the current overlap of municipal ISS and federal PIS/COFINS.

The second is uncertain: the reference rate for IBS/CBS has not yet been set by Senate resolution, as provided for in art. 14 of LC 214/2025. Current Senate estimates place the combined rate between 26.5% and 28%, but this number is a planning assumption, not a normative value. For software imports, CBS (federal) applies to the transaction, and IBS (subnational) follows the destination rule. A MoR operating in Brazil starting in 2027 will need to calculate and remit CBS and IBS on every transaction.

Until 2027, while PIS and COFINS remain in force, credit recovery of 9.25% via domestic invoice remains the primary mechanism for reducing tax burden for companies in the Lucro Real regime that import software. With the extinction of PIS and COFINS and the entry of CBS, the crediting mechanism will migrate to the full non-cumulativity of the new system.

Frequently asked questions about Merchant of Record

What is the difference between a MoR and a payment intermediary?

A payment intermediary (Stripe, Pagar.me) processes the transaction in the SaaS company's name. A MoR processes the transaction in its own name. The difference is who appears as the legal seller on the customer's invoice. The intermediary is a technical facilitator. The MoR is the legal counterparty.

Do small companies need a MoR?

It depends on the sales destination. A Latin American SaaS company with three customers in the United States does not need a MoR if the customers pay via international credit card and the SaaS company issues export documentation at home. The moment the SaaS company reaches customers in jurisdictions that require local tax registration (European Union, United Kingdom, Australia, India, several U.S. states), the MoR becomes cheaper than opening entities in each country.

Does a MoR replace an accountant or tax consultant?

No. The MoR calculates and remits taxes on the sales transaction. It does not replace the SaaS company's domestic accounting, does not file local tax returns, does not fill out Siscoserv, and does not advise on the company's tax regime. The MoR covers the transaction. The company covers its own corporate compliance.

What does a MoR cost?

The typical fee ranges from 4% to 7% of transaction volume, varying by industry, average ticket size, buyer geography, and chargeback risk. For a SaaS company with an average annual ticket of USD 500 and volume of USD 500,000 per year, the MoR fee represents USD 20,000 to USD 35,000 annually. The relevant comparison is not against processing payments directly (which is cheaper per transaction). It is against the cost of opening and maintaining tax entities in the countries where the SaaS company has customers.

Does the MoR withhold tax at source in Brazil?

It depends on where the MoR is incorporated. If the MoR is an entity abroad and remits funds to a Brazilian SaaS company, the remittance is service export revenue and is subject to Brazilian taxation on the inflow. If the MoR has an entity in Brazil and settles in BRL via a local invoice, the transaction is domestic for tax purposes and there is no withholding tax on the remittance. The Nexforce Marketplace operates under this second model.

The decision to outsource the transaction

The Merchant of Record solves a scaling problem. For a Latin American SaaS company selling in one or two markets, opening a local entity may be cheaper than paying 5% of volume to a MoR. For a SaaS company with customers in ten countries, ten entities are unworkable and the MoR is the correct decision.

The math is compliance cost versus service cost. The MoR charges for the compliance it executes. Opening an entity charges upfront, in legal fees, registrations, and maintenance, regardless of sales volume in the country. The inflection point depends on average ticket size and the geographic concentration of the customer base.

On the import side, the logic inverts: the Latin American company is the buyer, and a MoR operating locally assumes the international software purchase transaction. The gain is not in delegating sales abroad. It is in transforming a complex import, with multiple taxes and FX exposure, into a local transaction with a domestic invoice and recoverable tax credits.

For the CFO managing international software, the question is not whether the MoR works. It works. The question is whether the company's cross-border transaction volume has already crossed the point where doing it manually costs more than delegating.

---

References and Further Reading

• LC 116/2003 - ISS on services
• Law 10,168/2000 - CIDE, §1-A of art. 2
• Law 10,637/2002 - PIS
• Law 10,833/2003 - COFINS
• Decree 6,306/2007 - IOF/FX, art. 15-B (XXIV: outflow 3.5%; XXV: inflow 0.38%)
• LC 214/2025 - Tax Reform (IBS/CBS)