Merchant of record vs Stripe Tax: which handles compliance?
Last updated: November 16, 2026
SoleOS: One dashboard for revenue, traffic and live signals across every app, game and website you run. Start 7-day trial →
From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.
A merchant of record (MoR) like Paddle, Lemon Squeezy, or Polar becomes the legal seller of your product, which means it collects and remits sales tax and VAT on your behalf and absorbs the liability if something goes wrong. Stripe Tax does the calculation, collection, and reporting plumbing, but you remain the seller of record — you register, file, and remit in every jurisdiction where you owe tax. Neither is "better" in the abstract; they solve different problems, and the right pick depends on how many tax jurisdictions you're exposed to and how much of that work you want to own.
What each one actually does
Merchant of record sits between you and your customer legally. When someone buys through Paddle or Lemon Squeezy, the invoice says Paddle (or whichever MoR you use) is the seller, not you. That company:
- Registers for VAT/GST/sales tax in the jurisdictions it needs to
- Calculates the correct rate at checkout
- Collects it from the customer
- Files and remits the returns
- Handles audits related to that tax
In exchange, they take a cut — typically 5% of transaction value, sometimes more, on top of payment processing fees. You get a single payout, net of their fee and the tax they handled, and you never touch a VAT return.
Stripe Tax is a feature inside Stripe, not a separate legal entity standing between you and the buyer. You're still the merchant of record. Stripe Tax will:
- Determine the right tax rate based on customer location and your registered jurisdictions
- Add it to the invoice or checkout
- Generate reports you can hand to an accountant or file yourself
But you have to register for VAT/sales tax in each jurisdiction yourself once you cross that jurisdiction's threshold, and you (or your accountant) file the actual returns. Stripe Tax saves you from calculating 11,000 different US sales tax rates by hand, but it doesn't make the registration and filing obligation disappear.
The real difference: who owns the liability
This is the part that gets glossed over in comparison posts. An MoR isn't just "tax calculation as a service" — it's a transfer of legal responsibility. If a tax authority comes knocking because a rate was wrong or a filing was late, that's the MoR's problem, not yours, because they were the seller on the invoice. With Stripe Tax, if something is wrong, it's your business's name on the registration and your business that answers to the tax authority. Stripe gives you better data to get it right; it doesn't indemnify you.
For a solo founder with no finance team, that liability transfer is the actual product being sold by an MoR. The 5%+ fee isn't really for "tax calculation" — plain Stripe Tax calculation is far cheaper — it's for making VAT/sales tax someone else's legal exposure.
When an MoR makes sense
- You sell digital products or SaaS to consumers/small businesses across many countries and don't want to register for VAT in the EU, UK, or a growing list of US states
- You don't have an accountant who can file multi-jurisdiction returns, and don't want to hire one yet
- Your margins can absorb the extra percentage without killing the business
- You'd rather pay for certainty than optimize for lowest fees
This is the default recommendation for most solo founders selling internationally, and it's why Paddle, Lemon Squeezy, and Polar exist as a category: the compliance tax (pun intended) of doing it yourself scales faster than most indie revenue does. We've written about Stripe vs Paddle for EU-based founders and the trade-offs show up again here.
When Stripe Tax (and staying your own merchant of record) makes sense
- You're mostly selling in one or two jurisdictions and already know your registration obligations
- You have an accountant or bookkeeper who's comfortable filing VAT/sales tax returns
- You're price-sensitive on fees and the extra 5%+ matters at your volume
- You want direct control over customer relationships, refund policy, and dispute handling rather than routing everything through an MoR's support process
A lot of US-only B2B SaaS founders fall into this bucket: sales tax exposure is limited to a handful of states (often none, below economic nexus thresholds), and Stripe Tax's automatic rate calculation is enough. Don't switch to an MoR "just in case" if your actual exposure is narrow — that's paying for a problem you don't have. When you don't need SoleOS either, for that matter: if you're running a single product with simple, well-understood tax exposure, a spreadsheet and Stripe's own tax reports may be all the reconciliation you need, and you can see what that looks like in SoleOS vs a spreadsheet.
How this connects to reconciliation
Whichever path you pick, the numbers in your payment processor stop being a clean 1:1 match with what you actually earned, and that's where founders get tripped up during reconciliation:
- With an MoR, your payout is net of their fee and the tax they collected and remitted. The "revenue" Paddle or Lemon Squeezy shows you in their dashboard already has tax stripped out — good, because you don't need to track it, but it means comparing that number directly to a Stripe-only product's gross revenue is comparing apples to oranges.
- With Stripe Tax, your Stripe balance includes tax you collected but don't yet own — it's sitting there until you remit it. If you're eyeballing Stripe balance as "cash I have," you're overstating it by whatever tax is pending remittance.
If you run some products through an MoR and others on raw Stripe (a common setup as a portfolio grows — maybe your early apps are Stripe-direct and newer international ones went MoR from day one), you now have two different revenue definitions living side by side. One already excludes tax by design; the other includes tax you haven't remitted yet unless you subtract it manually.
This is exactly the kind of inconsistency that tracking Stripe and RevenueCat together runs into with subscription revenue, just on the tax side instead of the platform-fee side. The fix is the same: decide on one definition of "revenue" for your own dashboards — ideally net of tax and processor fees across the board — and normalize every connector to it before you compare products.
Disclosure: SoleOS wrote this post about its own space — we build portfolio intelligence for multi-product founders, and reconciliation across payment and tax setups is a problem our own users hit. SoleOS pulls in revenue metrics from Stripe and RevenueCat and normalizes them for cross-product comparison, but it doesn't calculate tax, file returns, or replace Stripe Tax or an MoR — it sits downstream of whichever one you choose. Exact formulas and what's excluded are in the metrics dictionary.
Frequently asked questions
Can I use Stripe Tax and a merchant of record for different products in the same portfolio?
Yes, and it's common as a portfolio grows — older or domestic-only products stay on raw Stripe with Stripe Tax, while newer or more internationally exposed products launch through an MoR. The tradeoff is that your per-product revenue numbers now have different tax treatment baked in, so any dashboard comparing them needs to normalize for that rather than taking each payout number at face value.
Does switching to a merchant of record change my MRR numbers?
It can, depending on how you were calculating MRR before. If you were treating gross Stripe charges (including tax) as revenue, moving to an MoR will show a drop simply because tax is now excluded by design — not because your actual subscription revenue fell. Always check whether a number is gross or net of tax before comparing it across a switch like this.
How do I know if I've crossed a VAT or sales tax threshold that requires registration?
This depends on jurisdiction-specific rules (EU VAT has no de minimis for digital services sold to consumers; US economic nexus thresholds vary by state) that change periodically, so check current rules with a tax professional or the relevant tax authority rather than relying on a blog post. Stripe Tax's dashboard will flag when you're approaching thresholds in jurisdictions it's tracking, which is a useful early warning even if you ultimately need a professional to confirm the filing requirement.
Is an MoR more expensive than Stripe Tax long-term?
The MoR's percentage fee is usually higher than Stripe's base processing plus Stripe Tax add-on, but that comparison ignores the cost of registering and filing in each jurisdiction yourself — accountant fees, your own time, and the risk of a missed filing. Model both: processor fees plus accountant cost for the DIY route, versus the MoR's all-in percentage, at your actual sales volume and jurisdiction spread, before assuming either is cheaper.
Can SoleOS tell me which tax setup I should use?
No — SoleOS isn't a tax tool and doesn't give tax or legal advice. It can show you revenue trends and let you compare products side by side once you've normalized for tax treatment, which helps you see the dollar impact of a switch after the fact, but the decision itself belongs with a tax professional who knows your specific jurisdictions and volume.