How SaaS billing actually works

This is not a tool decision

Billing is usually framed as a product comparison. Which provider has better APIs? Which one is cheaper? Which checkout looks nicer?

None of that is the real question.

The real question is structural: who is the legal seller of your product?

That one decision determines who handles tax, who carries fraud risk, who deals with compliance, and how much operational work lands on your plate every month.

Get it wrong and you don't just have a bad tool — you have a legal and financial structure that's expensive to unwind.

The real decision: responsibility

Every SaaS billing setup answers the same question:

Are you the seller, or is someone else?

If you are the seller:

• You collect payments directly
• You calculate and remit tax in every jurisdiction where you have customers
• You carry the liability for chargebacks and fraud
• You manage compliance with local payment regulations

If someone else is the seller:

• They appear on the invoice and the credit card statement
• They handle tax calculation, collection, and remittance globally
• They absorb chargeback and fraud liability
• You receive payouts, minus their fee

This is not a feature difference. It's a difference in who carries the weight.

Choosing to be the seller gives you control. Choosing to delegate gives you simplicity. Neither is free.

What you are actually signing up for

If you handle it yourself

Tax calculation. You need to charge the correct tax rate for every customer, based on their location, your tax registration status, and what you're selling. In the EU alone, that means tracking VAT rates across 27 countries — and those rates change.

Filing and remittance. Collecting tax is only the first step. You also need to file returns and remit payments to each tax authority on schedule. Miss a deadline and you face penalties.

Ongoing maintenance. Tax rules change. Thresholds shift. New jurisdictions introduce digital services taxes. Someone on your team needs to track this — or you need to pay someone who does.

Audit exposure. If you're the seller, you can be audited by any jurisdiction where you have tax obligations. That means records, documentation, and potentially legal representation in countries where you've never set foot.

The question isn't whether you can handle this. It's whether this is where you want your time and money going.

If you delegate it

Higher fees. The entity handling your compliance charges for it. Typically 5%+ per transaction versus ~3% for processing alone. On low volume, the difference is small. At scale, it compounds.

Less control. You don't own the customer relationship at the payment level. Refund policies, payout timing, and checkout experience are shaped by someone else's rules.

Dependency. Your revenue flows through a third party. If they change terms, raise fees, or have an outage, your business feels it directly.

The question here is whether the operational relief is worth the control you give up.

What actually matters for your decision

Where are your customers? If they're spread across multiple countries — especially in the EU — tax compliance becomes a serious operational burden. If they're concentrated in one country, it's manageable.

Are you selling to businesses or consumers? B2B sales often simplify tax through mechanisms like reverse charge. B2C sales in multiple countries almost always mean you need to handle tax at the point of sale.

How much engineering capacity do you have? Building billing logic yourself — proration, dunning, plan changes, tax integration — takes real engineering time. That's time not spent on your product.

Do you need to move fast, or do you need control? Delegating lets you start selling globally in days. Owning the setup gives you flexibility to build exactly what you need — but it takes weeks or months, and you maintain it forever.

Each of these is a constraint, not a preference. Your answers narrow the decision to one or two viable paths.

A simple decision shortcut

If you want full control over your billing, payment experience, and customer data — and you have the resources to handle tax and compliance — own it.

If you want to sell globally without building tax infrastructure, and you're willing to pay higher fees and accept less control — delegate it.

If you're unsure, ask yourself: do I have someone who will own tax compliance as a recurring responsibility? If the answer is no, you probably shouldn't be the seller.

Why this decision is hard to change

Switching billing models mid-growth is not like switching a SaaS tool. It's a structural change that touches nearly everything.

Active subscriptions need to migrate. Every customer on a recurring plan needs to be moved — with correct proration, no double charges, and no gaps in service. This is error-prone and customer-facing.

Tax obligations don't reset. If you've been the seller and you switch to a delegated model, you may still owe taxes for the period you were the seller. Past obligations follow you.

Integrations break. Webhooks, invoicing flows, accounting integrations, revenue recognition — all of it is wired to your current setup. Rewiring takes engineering time and introduces risk.

Customers notice. The name on the invoice changes. The checkout experience changes. Payment methods may change. For B2B customers especially, this triggers procurement reviews.

None of this means you can never switch. But it means the cost of switching is high enough that getting it roughly right the first time matters.