What is SaaS Billing?
Written by Arnon Shimoni
✓ Expert
Last updated on:
SaaS billing is everything between a customer agreeing to pay for software and the money arriving: pricing the plan, tracking what they're entitled to and what they use, rating that into charges, producing a compliant invoice, collecting payment, and handling every change in between. For a flat monthly plan it's a scheduled charge. For a modern SaaS business with seats, usage, tiers, commitments, multiple currencies and several legal entities, it's a system.
The reason it has its own name is that software is sold differently from almost anything else. The customer buys continuously, changes what they buy mid-period, and often doesn't know in advance how much they'll consume. The billing has to follow all of that without a human in the loop.
At a glance | SaaS billing |
|---|---|
Covers | Pricing, subscriptions, entitlements, metering, rating, invoicing, payments, dunning, revenue recognition |
Pricing models it has to support | Flat rate, per seat, usage-based, tiered, hybrid, credits, minimum commits, outcome-based |
Hard parts | Mid-period changes, usage at scale, multi-entity tax and compliance, e-invoicing, revenue recognition |
Typical architecture | Product catalog → pricing plans → subscriptions → metering → invoices → payments → ERP |
Build or buy | Most teams that build their own regret it by the second pricing change |
What a SaaS billing system does
Product catalog and pricing plans. The definition of what you sell and at what price: products, items, tiers, rates, currencies, tax categories. Pricing changes should be a configuration, not a deployment.
Subscriptions and entitlements. Which customer is on which plan from when to when, with what overrides, discounts, included volume and commitments. Entitlements tell the product what the customer may use; the subscription tells billing what to charge.
Metering. Ingesting usage events from the product (API calls, GB, tokens, seats, transactions) reliably and idempotently, at whatever volume the product generates.
Rating. Turning usage into money by applying the plan: tiers, volume discounts, minimums, overages, credits. This is where revenue leakage happens when it's done in spreadsheets.
Invoicing. Producing a legally valid invoice per customer per period from the right legal entity, with the right tax treatment, numbering and date, in the format each country requires. The EU invoice requirements page covers what that means in Europe.
Payments and collection. Charging stored payment methods, presenting payment links, handling bank transfers, retries and dunning, and reconciling what came in against what was invoiced.
Changes. Upgrades, downgrades, pauses, cancellations and proration, all mid-period, all without breaking the invoice.
Accounting. Posting invoices, credit notes and payments to the ERP and feeding revenue recognition under ASC 606 or IFRS 15.
Pricing models and what they demand of billing
Model | What billing has to do |
|---|---|
Recurring charge, proration on change. The easy case | |
Track seat counts over time, prorate additions, decide whether removals are refunded | |
Meter events at scale, rate them, show them on the invoice line by line | |
Apply the right rate to the right band, graduated or whole-volume, per period | |
Combine a platform fee, included volume and overage on one invoice | |
Hold a balance, draw it down, top it up, expire it, and recognise revenue on consumption | |
Compare usage to a floor per period or per term, true up | |
Meter results rather than activity, often with a verification step before billing |
Most SaaS companies move down this table over their life. A billing system that only handles the first two rows forces a rebuild when pricing evolves, which is why the choice is strategic rather than operational.
Why SaaS billing is harder than it looks
Time. Every charge has a period, every change happens mid-period, and every period has to close cleanly. Proration, ramp-ups, pauses and backdated changes all produce edge cases.
Volume. Usage-based pricing means billing ingests events at product scale, not finance scale. Late, duplicated and out-of-order events have to be handled without producing wrong invoices.
Geography. Each country adds a VAT regime, mandatory invoice fields, deadlines and, increasingly, structured e-invoicing. Each legal entity adds a number series, bank account and currency. The multi-entity billing page covers the combination.
Immutability. Once an invoice is issued it can't change. Every correction is a credit note, which the system has to produce and link.
Two audiences. The customer's finance team wants a clear, PO-matched invoice. Your finance team wants a clean ledger and a defensible revenue schedule. The same data has to satisfy both.
Build or buy
Engineering teams build billing because the first version looks easy: a cron job, a Stripe charge, a PDF. It stops being easy at the first pricing change, the first country with a reverse charge, the first customer who wants a credit note, and the first auditor who asks about the gap in invoice numbers. The home-built billing page goes through the cost in detail. The short version is that billing is a product in its own right, and unless billing is your product, building it diverts the team from the one that is.
Where Solvimon fits
Solvimon is a billing platform built for exactly the table above. Product catalog, pricing plans and subscriptions are configuration, not code. Metering ingests events in real time and rates them against tiers, commitments, included volume and discounts on the subscription schedule. Invoices are generated per billing entity with per-invoice tax, their own number series, rule-based dates and structured e-invoicing where mandated. Payments are collected through your own PSP with payment links, retries and workflow-driven dunning, and everything posts to your ERP. Solvimon powers billing for some of Europe's largest fintechs and a growing number of US companies, which is a reasonable test of whether it handles the hard parts. If you're deciding between extending what you've built and replacing it, talk to one of our experts.
FAQ
What's the difference between SaaS billing and subscription billing?
Subscription billing is the recurring-charge subset. SaaS billing today also covers usage, credits, commitments and hybrid models that aren't simple subscriptions.
Is a payment processor a billing system?
No. A processor moves money. A billing system decides how much to charge, produces the invoice, and reconciles the payment to it. Most billing systems work with several processors.
Do I need a billing system before I have usage-based pricing?
You need one before the first pricing change you can't make without an engineer, which for most companies is within the first two years.
How does billing connect to revenue recognition?
Invoices and credit notes are the inputs. Revenue recognition schedules when the invoiced amounts count as revenue, which for subscriptions is over the service period and for usage is as consumed.
Can billing live in the ERP?
The ledger can. Metering, rating, subscriptions and invoice generation at product scale are not what ERPs are built for, which is why billing platforms feed ERPs rather than replace them.
This page was last reviewed in October 2026.
Related
Billing engine. The rating and invoicing core.
Usage-based pricing. The model that makes billing hard.
Subscription management. Plans, changes and lifecycle.
EU invoice requirements. What the invoice must contain.
Quote to cash. The wider process billing sits in.
Automated invoicing. The invoicing stage in detail.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
