I'm building a B2B SaaS and need invoicing, taxes, and dunning handled

For a B2B SaaS, you usually want a billing stack that covers:

• Invoicing: generate, send, and store invoices
• Taxes/VAT/GST: calculate correctly based on customer location and tax status
• Dunning: retry failed payments, notify customers, and reduce churn
• Subscriptions: recurring billing, upgrades/downgrades, prorations
• Compliance: receipts, credit notes, audit trail, and revenue records

Common options

1) Stripe Billing + Stripe Tax

Best if you want a strong default and are comfortable building some workflow yourself.

Pros

• Great API and developer experience
• Handles subscriptions, invoices, payment retries
• Stripe Tax supports many jurisdictions
• Easy to integrate with card payments and ACH
• Widely used, lots of tooling

Cons

• Tax/invoice edge cases may need custom handling
• Dunning logic is good but not fully “hands off” for every scenario
• Can get complex as you add entity-level billing, multi-currency, or local compliance

2) Chargebee

Best if you want a more complete billing layer on top of payment processors.

Pros

• Strong for invoicing, subscriptions, dunning, and enterprise billing
• Better out-of-the-box workflows than pure payments platforms
• Supports multiple gateways
• Useful for metered billing, entitlements, and finance ops

Cons

• More expensive
• More abstraction, sometimes less flexible than building directly on Stripe
• Still may require tax engine integration depending on region/needs

3) Paddle

Best if you want them to act as Merchant of Record.

Pros

• They handle sales tax/VAT/GST compliance in many cases
• Less tax burden on your side
• Good for SaaS selling globally

Cons

• Less control over billing/payment stack
• MoR model affects how revenue is recognized and your customer contracts
• Not always ideal for complex B2B procurement or enterprise invoicing needs

4) Recurly / Zuora

Best for larger companies with complex subscription billing and finance requirements.

Pros

• Powerful subscription and invoicing features
• Enterprise-grade workflows
• Good for complex billing rules

Cons

• Heavier implementation
• Usually overkill for early-stage SaaS
• Can be expensive

---

Practical recommendation

If you’re early-stage B2B SaaS:

Stripe Billing + Stripe Tax is often the best starting point.

Add:

• email automation for dunning/collections
• customer portal for payment method updates and invoices
• accounting sync to QuickBooks/Xero if needed

If you want less tax/compliance burden:

Consider Paddle as Merchant of Record.

If you need strong finance operations and invoicing workflows:

Consider Chargebee.

---

What to decide first

To choose the right stack, answer these:

1. Where are your customers located?

   • US only?
   • EU/UK?
   • Global?

2. Do you need to be the merchant of record?

   • If yes, Paddle is a strong candidate.
   • If no, Stripe/Chargebee are common.

3. Do you sell subscriptions only, or also usage-based billing?

   • Usage billing can add complexity.

4. Do you invoice manually for enterprise customers?

   • If yes, you may need PO numbers, net terms, wire/ACH, credit notes.

5. How much tax compliance do you want to own?

   • If you want minimal responsibility, MoR helps a lot.

---

A solid default architecture

For many B2B SaaS products:

• Stripe Billing for subscriptions and invoices
• Stripe Tax for tax calculation
• Stripe Customer Portal for self-service updates
• Webhook-driven dunning with retry logic and email notifications
• Accounting integration for finance records
• Manual invoice flows for enterprise net-30 customers if needed

---

If you want, I can help you pick the right setup based on:

• your target countries,
• subscription vs usage-based pricing,
• whether you need net terms,
• and whether you want to avoid tax compliance yourself.

If you share those, I can recommend a specific stack.