ERP billing for usage-based pricing puts a default to the test, because most finance teams never choose where billing lives. It ends up somewhere.
Often that’s the ERP, because invoices and cash already live there. Sometimes it’s the CRM, because orders start there and someone switched on the billing module. Either one works well enough while pricing is simple: a seat count, an annual fee, an invoice. Then pricing starts to move.
This guide is for controllers, VPs of finance, and finance systems leads. It covers when ERP and CRM billing stop working, how to split the work without replacing the ERP, what changes for finance, and a three-question test for your stack.
Key Takeaways
- Usage, minimums, ramps, and credits turn billing into a configuration project inside a system built for something else.
- You don’t need a new ERP. The CRM stops at the order, a billing platform handles charges and invoices, and the ERP starts at the journal.
- With billing in its own home, new pricing is configuration, the close gets cleaner, and the ERP gets simpler.
- Three questions show whether billing has outgrown where it lives.
The moment ERP billing stops working
A usage product launches. A big customer negotiates a quarterly minimum. Sales wants ramps, and product wants credits. Each change is small on its own. Together, they turn billing into a configuration project inside a system built for something else.
Those changes also reach the books. Deloitte’s accounting alert on hosted software with variable consideration says the invoice-based approach to recognizing usage revenue may not be appropriate when there are fixed fees on top of usage, substantive minimum usage requirements, or a rate that varies during the contract. For the pricing models themselves, see this guide to usage-based pricing.
The signs are familiar:
- Invoices go out late, and some quarters never fully close.
- Usage lives in one place, contracts in another, and someone joins them in a spreadsheet.
- The CRM “does billing,” but the real invoice is rebuilt in the ERP.
- Every new pricing idea starts with “we’d need IT for that.”
Finance leaders often tell us the ERP’s billing module doesn’t go far enough.
Don't replace the ERP. Stop at the order
The instinct is to look for a bigger system, often a new ERP. That is a large project to solve a billing problem. There is a simpler design, often called decoupled order-to-cash: let each system do what it was built for.
- The CRM captures the deal and the order.
- A billing platform turns that order into charges: rating usage, applying minimums and tiers, handling upgrades and renewals mid-term, and producing the invoice.
- The ERP stays the system of record for the ledger, receiving clean summary journals.
The CRM stops at the order. The ERP starts at the journal. Billing lives in between, in a system built for pricing change.
What changes for finance
When billing has its own home, three things get easier.
New pricing becomes configuration
A tiered usage plan or a prepaid drawdown is set up in the product catalog, not built.
The close gets cleaner
If billing and revenue recognition run on the same transaction record, there is no reconciliation step between them.
The ERP gets simpler, not replaced
Your general ledger keeps doing its job. It just stops being asked to rate usage.
A quick test for your stack
Ask three questions:
- How many systems touch an invoice before it reaches the customer?
- When pricing changes, who has to change code or configuration, and in which system?
- At quarter-end, how long does it take to tie billing to recognized revenue?
If the answers involve more than two systems, an IT ticket, and a spreadsheet, billing has outgrown where it lives.
How Zuora keeps billing between the CRM and the ERP
Zuora is the connected monetization layer between your CRM and your ERP. It connects quoting, orders, billing, collections, usage, and revenue in one place, and it sends clean summary entries to the ERP, which stays your general ledger.
Asana shows what that looks like. After moving to Zuora Billing and Zuora Revenue, Asana went from launching about 10 to 15 new rate plans a year to 30+, and cut time to market from 2 to 3 months to weeks. If ERP billing for usage-based pricing has become a workaround on your team, the same split can give finance a billing home that follows your pricing.
Next step: read our guide to modernizing order-to-revenue beyond ERP systems.
FAQs
1.
What is a revenue subledger, and does it replace the general ledger?
A revenue subledger is an accounting layer between the billing system and the ERP. It processes high-volume usage data and contract changes, applies revenue recognition rules, calculates deferred revenue, and sends summarized journal entries to the general ledger. It does not replace the ledger. The ERP stays the book of record for financial reporting.
2.
What counts as hybrid pricing in a SaaS business?
Hybrid pricing mixes charge types in one contract. Common mixes are a seat-based subscription with usage overages, a prepaid credit balance that drains as customers consume, or a committed minimum with usage billed above it. Each charge type follows its own rules, so the billing system has to rate and invoice them together on one bill.
3.
Does moving billing out of the ERP add integration risk?
It adds an integration to plan, and it takes customization out of the ERP. Teams usually connect the billing layer to the ERP with pre-built connectors and send summary journals on a schedule, so the ledger receives clean entries instead of transaction detail. Before go-live, confirm the chart-of-accounts mapping and who owns each hand-off.