Usage-Based SaaS Pricing: Metering, Overage Charges And Billing Disputes

Usage-based pricing can make sense for a growing SaaS business. Instead of charging every customer the same amount, you might charge according to API calls, storage, transactions, tokens or another measure of how much of the service they actually use.

However, once the customer’s bill depends on usage, there is more to agree than simply the price per unit.

Say your SaaS plan costs $100 per month and includes 100,000 API calls. A customer normally stays within that limit, but one month their usage jumps to 500,000 calls and they receive a much larger bill. They say the numbers are wrong and refuse to pay the overage.

Who is responsible? That depends partly on what actually happened, but it also depends on what your customer terms say.

If your customer’s bill depends on what your system says they used, your SaaS Terms of Service, order form or pricing schedule should explain how that usage becomes a charge.

What Is Usage-Based SaaS Pricing?

Usage-based pricing, sometimes called consumption-based pricing, means the amount a customer pays depends at least partly on how much of the product they use.

For example, a SaaS business might charge for each API request, gigabyte of storage, transaction processed or unit of computing or AI usage.

It can also be combined with a normal subscription. You might charge $100 per month, include 100,000 API calls and then apply an additional rate to anything above that limit. The additional charge is usually referred to as an overage.

The model itself is not the difficult part. The legal questions tend to arise when the customer and provider have different ideas about what was included, what was used or how the final charge was calculated.

What Exactly Are You Charging Customers For?

“Usage” can become surprisingly unclear once a customer challenges an invoice.

If you charge for API calls, does every request count? What about failed calls, duplicate requests or activity in a testing environment? If you charge for active users, when does someone become an active user? If you charge for storage, how and when is it calculated?

You do not need to turn your contract into a technical manual, but customers should be able to understand the unit they are paying for.

The pricing might sit in your main terms, an order form or a separate pricing schedule. What matters is that the documents clearly identify what is billable and do not leave an important part of the calculation open to interpretation.

If customers primarily access your product through an API, separate API Terms of Use may also be relevant.

How Is Usage Actually Measured?

This is where “metering” comes in.

Metering is simply how your SaaS records how much of the service a customer has used. Think of it a little like an electricity meter: the amount eventually charged depends on what the system records as consumption.

Your terms can address the billing period, when usage is counted and what records are used to calculate the invoice.

For example, if your own platform records API requests and those records are used to calculate overages, that should not come as a surprise to the customer after an invoice arrives.

At the same time, be cautious about saying your records are always final and can never be challenged. Systems can make mistakes. A better approach is usually to establish which records are used for billing while also providing a process for investigating genuine errors.

What Happens When A Customer Goes Over Their Allowance?

If the customer exceeds their included usage, what happens next should be clear.

Do they continue using the platform and automatically incur overage charges? Does usage stop at the limit? Can they set their own cap? Will they receive a warning before additional charges begin?

There is not one correct approach for every SaaS product. What matters is that the commercial arrangement matches what customers have been told.

For example, if your pricing page says customers will be warned before overages apply, but your platform keeps charging when no warning is sent, you have created a problem that clearer contractual wording alone may not solve.

This is why your pricing page, product interface and legal terms should tell the same story.

What If There Is A Huge Usage Spike?

This is where things can get messy.

Say your customer normally incurs a $300 monthly bill, then suddenly generates $7,000 in usage overnight.

Before asking whether you can charge the full amount, it is worth asking why the spike happened.

It could be genuine customer activity. It could also come from a faulty integration, compromised account credentials, automated activity or an error in your own system.

Your agreement can address responsibility for activity carried out through the customer’s account, account security, usage limits and any safeguards your platform provides. It can also explain whether customers can set caps or receive alerts when usage reaches certain thresholds.

However, not every unexpected spike should necessarily be treated the same way. For products where usage can become expensive very quickly, it may make sense to have a process for investigating unusually high charges.

This is one area where legal advice can be particularly useful. A clause suitable for a low-cost SaaS product may not be appropriate for a platform where a technical issue can generate tens of thousands of dollars in additional usage.

How Should The Customer Know What They Have Been Charged?

A customer should be able to look at their bill and understand how the amount was reached.

If our example customer used 500,000 API calls, the bill might show the monthly platform fee, the 100,000 calls included in the plan, the additional 400,000 calls and the overage rate applied to them.

The contract or related pricing documents can also explain the billing period, when usage is invoiced, when payment is due and whether the customer pays for usage in advance or after it has occurred.

Clarity here is not just good customer service. For consumer-facing businesses, the FTC's general advertising rules require advertising claims to be truthful and non-deceptive, and the FTC identifies price as information that can be material to a consumer's decision.

In practical terms, advertising a low monthly price while making significant usage charges difficult for consumers to identify can create more risk than simply explaining the pricing properly from the outset.

What If Your Pricing Appears In More Than One Document?

SaaS pricing rarely lives in one place.

You might have a public pricing page, SaaS Terms of Service, a proposal, an order form and an enterprise customer agreement all referring to price.

What happens if they do not match?

For example, your website might say overages cost $0.01 per API call, while a customer’s signed order form says $0.008.

For businesses using multiple customer documents, it is worth making clear how those documents work together and which terms take priority if there is an inconsistency.

This becomes particularly important with enterprise customers, who may negotiate an order form containing different commercial terms from your standard online terms.

What If The Customer Disputes The Bill?

That sounds straightforward until the customer says, “We did not use that much.”

Your agreement can establish a process for dealing with the dispute rather than leaving both sides to work it out after the problem arises.

For example, the terms might explain how quickly a customer should raise a billing issue, what information they should provide and how the business will investigate the relevant usage records.

They can also address what happens to undisputed amounts. If the customer disputes $700 of a $5,000 invoice, does the remaining $4,300 still need to be paid while the $700 is investigated?

There should also be a sensible answer if your own metering was wrong. Perhaps a request was counted twice, failed transactions were included or the wrong pricing tier was applied. Depending on the circumstances, that could mean correcting the invoice, applying a credit or refunding an overpayment.

Suspension rights can also form part of this process. A SaaS provider may want the right to suspend a customer that simply stops paying, but a genuine billing dispute is different from straightforward non-payment.

The consequences matter too. Suspending access to a casual consumer app is very different from switching off business-critical software containing a customer's operational data.

Your suspension clause should make sense for the service you actually provide rather than being copied from another SaaS contract.

Can You Change Your Usage Rates Later?

Your pricing model today may not be the pricing model you use in two years.

You might increase the price per unit, reduce the usage included in a plan or introduce new tiers.

Your customer documents should deal with when pricing can change, how customers will be told and whether existing contract periods are protected from those changes.

For example, an enterprise customer might negotiate a fixed price for a 12-month term, while a month-to-month customer could be subject to changes after appropriate notice.

Avoid assuming that a broad clause saying prices can change “at any time” will necessarily deal with every situation, particularly where existing customers have already agreed to specific commercial terms.

Does Your SaaS Sell Directly To Consumers?

Who you sell to matters.

A negotiated SaaS agreement between two businesses is different from an online subscription sold directly to individual consumers.

For online consumer subscriptions that continue or renew unless cancelled, federal rules can add another layer. Under the Restore Online Shoppers’ Confidence Act, businesses using covered online negative-option arrangements must clearly disclose material terms before obtaining billing information, obtain the consumer's express informed consent before charging and provide a simple way to stop recurring charges. The FTC continues to enforce these requirements.

States can impose additional requirements.

For example, California strengthened its Automatic Renewal Law from July 1, 2025. The law includes requirements around consent and cancellation for consumer subscription arrangements, among other obligations.

This does not mean every usage-based SaaS arrangement is subject to the same subscription rules. It does mean a business selling directly to consumers should consider its recurring billing model separately from a negotiated B2B arrangement.

What Changes For Enterprise Customers?

Larger customers often want more certainty about how much they can spend.

Instead of completely open-ended usage charges, an enterprise deal might involve minimum commitments, prepaid usage credits, volume discounts or negotiated overage rates.

You may also come across a “true-up”. This is where the parties compare the amount of usage purchased or committed to against what was actually used and reconcile the difference at an agreed time.

Enterprise customers may also negotiate reporting rights, usage caps or their own billing dispute process.

These commercial terms might sit in an order form alongside the standard SaaS terms or, for a more substantial relationship, in a Master Services Agreement.

Make Sure Your Contract Matches Your Billing System

This is one of the simplest checks a SaaS business can make.

Take your contract, pricing page and actual billing journey and compare them.

If your terms say one thing, your pricing page says another and your software calculates something else, a billing dispute becomes much harder to resolve.

You do not need to put every technical detail into the contract. You do need customers to have a clear picture of what they are buying, what is included and when additional charges can arise.

When Should You Get Legal Help?

Not every SaaS pricing model needs a complicated contract.

However, getting legal advice becomes more useful where customers can incur substantial overages, usage can spike quickly, the business is introducing minimum commitments or unusual pricing mechanics, or enterprise customers are negotiating their own terms.

It is also worth getting advice before materially changing the pricing model for existing customers, particularly if those customers already have contractual rights under their current terms or your SaaS is sold directly to consumers.

A legal expert can review your SaaS Terms of Service, pricing schedules, order forms and related customer documents to make sure the legal terms reflect how customers are actually charged.

Key Takeaways

Usage-based pricing gives SaaS businesses flexibility, but it also creates questions that do not arise with a simple fixed monthly fee.

If a customer's bill depends on what your system records them as using, your terms should explain what counts as usage, how that usage is measured, when overage charges begin and what happens if the figures are disputed.

The goal is not to fill your contract with technical detail. It is to make sure your customers understand how their usage turns into a charge. Getting that right before the first unusually large invoice lands can make billing disputes much easier to manage as your SaaS business grows.

If you would like a consultation on your SaaS pricing terms, you can reach us at (888) 449-8437 or team@sprintlaw.com for a free, no-obligations chat.