Merchant of Record (MoR) Explained for SaaS Companies

If you are building a SaaS product and selling to customers across borders, payments are not just about charging a credit card. They are about tax collection, compliance filings, refund handling, chargeback management, and legal responsibility across dozens of jurisdictions simultaneously.

This is where the concept of Merchant of Record becomes critical — and where many SaaS founders make decisions that create significant compliance exposure without realising it.

What Is a Merchant of Record?

A Merchant of Record (MoR) is the company that is legally responsible for a transaction. That legal responsibility includes:

• Collecting payment from the customer
• Charging the correct tax rate (VAT, GST, sales tax) based on the customer's location
• Filing and remitting those taxes to the relevant governments
• Handling refunds in compliance with local consumer protection laws
• Managing payment disputes and chargebacks
• Issuing compliant receipts and invoices that satisfy local tax documentation requirements

When a MoR processes a transaction, they are the entity that governments and payment networks recognise as the seller — even if your company is the one building and delivering the product.

The Problem: Selling Globally Without a MoR

Consider a SaaS company registered in the United States selling to customers in the EU, UK, Australia, India, and Canada.

The moment you charge a customer in Germany, you may be required to collect German VAT at the applicable rate, register for VAT in Germany (or use the EU's One Stop Shop system), file quarterly VAT returns, and issue VAT-compliant invoices with your VAT registration number.

The same applies in the UK (post-Brexit VAT registration), Australia (GST if you exceed the threshold), India (GST with HSN/SAC codes), and so on across every market you enter.

This is not theoretical compliance complexity. These are active enforcement regimes. The EU has been increasing scrutiny of non-EU digital service providers since 2015. Australia introduced its "Netflix Tax" in 2017. India's GST rules for foreign digital service providers are actively enforced.

Without a Merchant of Record, you become the Seller of Record in every country where you have customers. That means:

• Registering for tax in each jurisdiction that requires it
• Filing regular returns in each jurisdiction
• Maintaining compliance with local invoicing requirements
• Handling refunds under local consumer protection laws
• Managing chargebacks under the payment processing rules of each region

For an early-stage or mid-sized SaaS company, this is an enormous operational overhead — and the cost of getting it wrong (penalties, back taxes, forced deregistration) can significantly exceed the cost of the compliance work itself.

How a MoR Solves This

A Merchant of Record acts as a reseller of your SaaS in the jurisdictions where they operate. Instead of you selling directly, the MoR sells to the end customer on your behalf. They handle the tax collection, the filings, the refunds, and the compliance.

Your role in this structure:

• You control pricing, plans, and the product experience
• You own the customer relationship and the underlying service
• You receive payouts from the MoR after their fees
• You are not directly responsible for tax compliance in the customer's jurisdiction

The MoR's role:

• They process the payment and charge the correct local tax
• They file and remit taxes to the relevant government agencies
• They handle refunds and chargebacks under local law
• They issue compliant receipts and invoices
• They take on the legal liability for the transaction

MoR vs Seller of Record: The Distinction

These two terms are often confused. The distinction matters:

Seller of Record (SoR): The entity that is legally recognised as the seller of the product. This is almost always the company that built and delivers the software — you. You set the pricing, you own the customer contract, and you are responsible for delivering the service.

Merchant of Record (MoR): The entity that processes the transaction. When you use a MoR platform, they step between you and the customer at the payment layer. The customer's receipt is issued by the MoR. The tax filing is the MoR's responsibility.

You can be the Seller of Record while using a third party as the Merchant of Record. This is the standard structure when using platforms like Paddle or Lemon Squeezy. You remain the product company and the customer relationship owner. The MoR handles the payment and compliance layer.

Major MoR Platforms and What They Handle

The key distinction with Stripe is important: Stripe is a payment processor, not a Merchant of Record. When you use Stripe, you are the MoR. Stripe handles payment processing and can calculate taxes with their Tax product, but the legal responsibility for filing and remitting those taxes remains with you. Adding Avalara or TaxJar automates the calculation and filing — but the liability is still yours.

If you want to transfer the tax liability to a third party, you need a platform that explicitly operates as MoR: Paddle, Lemon Squeezy, Polar, FastSpring.

When a MoR Makes Sense vs When It Does Not

A MoR makes sense when:

• You sell to consumers or SMBs in multiple countries
• You want to avoid the operational overhead of multi-jurisdiction tax compliance
• You are early-stage and cannot afford a dedicated tax counsel in each market
• Your product is a self-serve, card-based subscription
• You want to accept local payment methods without building integrations for each

A MoR may not be the right model when:

• Your customers are enterprises that require invoices directly from your company
• You need direct bank transfers (ACH, SEPA wire) for large transactions
• Your contracts are complex and customised — MoR platforms are built for standard subscription billing, not custom enterprise contracts
• You are in a regulated industry where the payment layer needs to be your company's legal entity
• You sell in markets where the MoR platform's coverage is limited

For enterprise SaaS, the limitations of MoR platforms become significant. Enterprise procurement teams often require invoices from the vendor company, not from a third-party billing platform. Contracts at enterprise scale tend to involve custom pricing, custom payment terms, and payment by wire transfer — structures that MoR platforms do not accommodate well.

The Tax Complexity MoR Platforms Handle

To understand the value of a MoR, it helps to know specifically what tax obligations they are absorbing:

United States: No federal VAT, but state-level sales tax. After the 2018 Wayfair decision, SaaS companies may owe sales tax in states where they have economic nexus (typically $100K revenue or 200 transactions). Rules differ by state — some tax SaaS, others do not. MoR platforms calculate and remit by state automatically.

European Union: VAT on digital services is charged based on the customer's country. Rates range from 17% to 27% depending on the EU member state. Non-EU companies selling B2C must either register in an EU member state or use the One Stop Shop (OSS) system. MoR platforms handle this entirely.

United Kingdom: Post-Brexit, the UK operates its own VAT system separate from the EU. Non-UK businesses selling B2C digital services above £85,000 must register for UK VAT. MoR platforms handle UK VAT independently.

Australia: GST applies to digital services sold to Australian consumers by foreign businesses above AUD $75,000 in annual Australian sales. MoR platforms calculate and remit.

India: GST applies to B2C digital services. Foreign providers must register under the simplified GST regime. Invoicing requirements include specific format and reference standards. MoR coverage varies — check specific platforms.

What a MoR Does Not Solve

A Merchant of Record handles transaction-level compliance. It does not replace your broader finance and revenue operations infrastructure:

• Revenue recognition under ASC 606 or IFRS 15 remains your company's responsibility. The MoR collects cash; your accounting system must recognize revenue correctly based on when performance obligations are satisfied.
• Financial reporting — your P&L, deferred revenue, ARR calculations, and revenue forecasts require proper accounting infrastructure regardless of how payment is processed.
• Enterprise invoicing — customers who require invoices from your company (common in enterprise sales) cannot be served through a MoR model where the invoice is issued by Paddle or Lemon Squeezy.
• Complex billing structures — milestone billing, usage-based overage structures, custom contract terms — these are outside the scope of most MoR platforms.

For SaaS companies that need to handle all of the above — global consumer payments via MoR, enterprise direct billing, complex pricing structures, and clean revenue recognition — the typical architecture is a MoR platform for self-serve and a direct billing stack for enterprise, with a revenue operations layer that ties them together.

The Bottom Line

For early-stage SaaS companies selling globally via self-serve, a MoR is almost always the right choice. The operational overhead of managing global tax compliance directly is not worthwhile until you have the revenue and internal finance capacity to justify it.

For growth-stage and enterprise SaaS, the decision becomes more nuanced. MoR platforms simplify compliance but add constraints on contract structure, payment methods, and invoicing that matter at enterprise scale. The right model depends on your customer mix and contract complexity.

If you are evaluating your billing and compliance infrastructure and want to understand what you are currently taking on as the effective MoR — and where the risks are — get in touch. We can map out your current exposure and what makes sense to offload versus manage directly.