At what point does SaaS billing become an infrastructure problem?

When a SaaS product is small, billing can feel pretty simple.

Customer signs up → payment processor charges them → invoice is generated.

But things change quickly as the product grows.

A customer might:

• Upgrade halfway through a billing period

• Add or remove seats

• Move from a flat plan to usage-based pricing

• Use different payment methods

• Be billed in a different currency

• Trigger a tax calculation

• Have a failed payment that needs to be retried

• Receive credits or refunds

• Have billing data that needs to reach accounting

Now the question isn't just “How do we charge the customer?”

It's:

“How do we make all these billing events work together reliably?”

That's where I think billing orchestration becomes interesting.

The basic idea is to have the different parts of the billing workflow coordinate with each other:

Subscription change → pricing calculation → proration → invoice → tax → payment → recovery → financial records

Instead of treating each step as a separate process, the workflow becomes connected.

I'm curious how other SaaS founders are handling this.

Where does your billing complexity start to become painful?

1. Plan upgrades/downgrades?

2. Usage-based billing?

3. Multiple payment gateways?

4. Failed payment recovery?

5. Taxes and international billing?

6. Keeping billing and accounting data in sync?

7. Something else?

Here's a deeper breakdown of how billing orchestration works, including the difference between billing orchestration, payment orchestration, and subscription management.

[Read the full breakdown → What Is Billing Orchestration? A Guide for Modern SaaS Companies]