When SaaS founders should start caring about sales tax

Executive overview

Global sales tax compliance sounds urgent but is mostly irrelevant until you reach meaningful scale. You are legally responsible for collecting and remitting taxes your customers owe — across every jurisdiction where you have a buyer — but enforcement against small bootstrapped SaaS companies is effectively nonexistent today.

The practical threshold: don't worry about it until you're doing $500K–$1M ARR. At that point, turn on Stripe Tax to track obligations, then remit incrementally starting with your home country.

The core insight: there is no clean solution — it's pick your poison between acting as your own merchant of record (lower fees, more complexity) or using a third-party MoR (convenience, but high fees and platform risk).

What a merchant of record is and why it matters

• A merchant of record (MoR) is the entity legally liable for a transaction — the name that appears on the customer's bank statement.
• Most SaaS companies use Stripe and are their own MoR, making them responsible for tax collection and remittance in every jurisdiction.
• Third-party MoRs (Paddle, Lemon Squeezy, Gumroad) process payments on your behalf and handle tax remittance — but charge significantly higher fees.
• Being your own MoR via Stripe gives you lower processing costs but full tax compliance responsibility.

When to start paying attention

• Below $500K ARR: ignore it; the risk is negligible and your time is better spent elsewhere.
• $500K–$1M ARR: start tracking obligations with Stripe Tax; begin remitting in your home jurisdiction.
• $1M+ ARR: remit in major markets (home country first, then Europe); expand gradually as volume warrants.
• Creator businesses selling one-time digital products: a third-party MoR makes sense — a 5% fee once is tolerable; on recurring SaaS revenue it compounds painfully.

Third-party merchant of record: the trade-offs

Pros:

• Convenience — they handle all tax collection, remittance, and filings across every jurisdiction.

Cons:

• Customer confusion — customers see Paddle or Lemon Squeezy on their bank statement, not your company name.
• Platform risk — if the MoR goes under, your billing infrastructure collapses.
• High fees — typically 5–10% on every transaction, indefinitely.
• You usually must use their checkout UI, creating two separate implementation paths if you also support Stripe.

Acting as your own merchant of record with Stripe Tax

• Turn on Stripe Tax first — it tracks tax owed by jurisdiction and alerts you when you cross local thresholds.
• Stripe Tax integrates with TaxJar (US), and has recommended partners for Europe and Asia for actual filing.
• Remit taxes incrementally: home country → Europe → other markets as volume grows.
• The cost of remittance doesn't scale linearly with revenue — optimising for lower processing fees and remitting manually is usually cheaper than paying MoR fees permanently.

Why enforcement risk is low (for now)

• No evidence of foreign governments successfully pursuing small bootstrapped companies for unpaid sales tax.
• Governments outsource collection to businesses precisely because they lack scalable enforcement mechanisms.
• Risk may increase over time — particularly if you raise funding or sell the company, where undisclosed tax obligations may appear in due diligence.
• One founder sold a company for $500M–$1B having never paid global sales tax; the acquirer essentially shrugged.
• Acquisition holdbacks are a more realistic risk than direct government enforcement today.

The complexity of the problem

• In the US alone, there were 600+ tax rate changes in 2021 — keeping up within one country is already unrealistic.
• Taxes being remitted are technically owed by your customers, not your business — you're just the required collector.
• No software product achieves full compliance; even purpose-built tax platforms acknowledge this.
• The conclusion after 18 months of evaluation: there is no great solution — pick the least-bad option for your situation.