Reporting ARR When SaaS Pricing Combines Subscriptions and AI Usage

SaaS contracts increasingly combine fixed fees, minimum usage commitments, and variable consumption in a single agreement. This presents all kinds of challenges from both an accounting and a leadership perspective.

The most relevant reporting question is revenue durability: what is contractually committed versus what depends on continued consumption. Getting that distinction right shapes everything from board reporting to how a business holds up under investor diligence.

The Building Blocks of ARR in a Hybrid Pricing Model

Not all revenue that flows into an ARR figure behaves the same way. A fixed annual subscription fee and a variable consumption charge can sit inside the same contract, but they carry very different levels of certainty about what next month looks like. The subscription continues regardless of usage; the consumption charge depends entirely on what the customer does.

That distinction matters more than which product generated the revenue. An AI product can carry a flat monthly fee with no usage component. A conventional software product can charge by transaction volume or seat-plus-overage. The product category tells you what the software does; the contract structure tells you how durable the revenue is. In a hybrid pricing environment, those two things rarely line up neatly, which is why reporting that conflates them produces a less useful picture of the business.

Evaluating ARR Through Two Key Lenses: Durability & Product Mix

Finance teams running hybrid pricing models benefit from tracking two distinct dimensions of their revenue.

The first is durability: how dependent is a given revenue stream on future consumption? Fixed recurring fees and minimum commitments behave differently from variable usage, and treating them the same obscures how stable the business actually is.

The second is product mix: how much revenue comes from AI products versus non-AI products? This is a genuinely useful strategic question, but it is a separate one from durability. An AI product can generate highly committed revenue; a non-AI product can generate highly variable revenue. Collapsing both dimensions into one metric answers neither question well.

ARR Is a Company-Defined Metric, Not an Accounting Standard

ARR is a management metric that companies define and disclose for themselves, not a line item governed by a single accounting standard, and treating it as inherently "contractually locked in" overstates what it represents.

A company combining annualized subscription contract value with annualized on-demand billings is making a reasonable choice, provided its disclosures are explicit that the metric is a point-in-time calculation that does not predict future renewals, cancellations, or usage. Clear definitions and consistent disclosure are what make a figure like this defensible. How a company defines and stress-tests its ARR matters as much as the number itself, and the gap between contracted ARR and recognized revenue is where that definition gets tested.

Report Commitments and Variable Usage Clearly

When annualizing a period of usage for reporting purposes, the measurement window matters and the figure should be clearly labeled as an estimate rather than a committed amount. A quarter of heavy consumption says little about the next one. Any combined metric that includes a usage run rate alongside committed fees should make that distinction visible, so a reader can assess the two components on their own terms.

A more useful approach reports usage separately as an annualized usage revenue run rate, discloses the measurement window it is based on, and presents it alongside fixed recurring fees rather than summed into them by default.

Minimum usage commitments need their own careful handling here: a commitment is contractual, but that alone does not make it recurring, since a minimum could just as easily represent a one-time credit purchase as an ongoing fee. Keep minimum commitments separately identified, and disclose the policy under which they are reported alongside fixed revenue. The annualized usage run rate should then reflect only consumption above that minimum. Counting the commitment once as committed revenue and then adding an annualized usage figure that already includes it double counts the same dollars.

Keeping ARR Separate From Revenue Recognition

ARR itself is never recognized as revenue. Revenue from the underlying arrangement is recognized under the applicable accounting guidance, and a point-in-time annualized metric will not simply equal revenue earned during a reporting period. The gap between the two includes timing differences, new contracts signed mid-period, churn, variable consumption that came in above or below the annualized assumption, and one-time items excluded from the recurring figure. A documented bridge explaining these differences, refreshed each period, is what keeps an ARR metric traceable and explainable during diligence.

Tagging billing lines for ARR reporting is a management-reporting exercise, and it does not itself determine performance obligations or revenue allocation under SaaS revenue recognition guidance. Keeping the two processes separate, rather than assuming one settles the other, is what a well-built SaaS P&L depends on when subscription and usage-based revenue carry different margin profiles.

A Hybrid Contract Example

Consider a hypothetical customer under one noncancelable annual agreement: a $24,000 annual platform subscription, and four quarterly AI consumption commitments of $3,000 each (totaling $12,000 for the year), with no rollover of unused commitment and overage billed each quarter above that quarter's $3,000 commitment. In the first quarter, the customer consumes $5,000 of AI credits: $3,000 draws down that quarter's commitment, and $2,000 bills as overage.

The report should separate three components rather than blend them:

• Platform subscription commitment: $24,000 for the year.
• Minimum consumption commitments: $12,000 for the year (four $3,000 quarterly commitments, contractual regardless of usage).
• Overage run rate: the $2,000 first-quarter overage, annualized at four times the quarter, for an $8,000 usage revenue run rate, clearly labeled as an estimate rather than a committed figure.

Combining the subscription, the minimum commitments, and the overage run rate gives $44,000, a defensible combined view as long as the $8,000 stays labeled as an estimate. The error to avoid is annualizing the customer's total quarterly consumption, $5,000 times four, or $20,000, and adding that on top of the $24,000 subscription and $12,000 minimum already counted as committed. That calculation, $24,000 plus $12,000 plus $20,000, or $56,000, double counts the $12,000 minimum, since it is already included inside the $20,000 annualized consumption figure as well as in the committed total.

Credit purchases, credit consumption, and recognized revenue can also occur at different times. A customer might prepay for a block of credits, consume them on a different schedule than the prepayment assumed, and unused credits, expiration terms, or rollover rights can affect when revenue is recognized under the applicable breakage guidance.

The Impact on Additional SaaS Metrics

Consumption pricing changes how some familiar metrics get measured, but not always what they mean.

Gross and net retention still work for consumption businesses when measured against comparable customer cohorts over comparable revenue periods rather than fixed contract values.

CAC payback periods keep their underlying concept, recovering acquisition cost through customer contribution or gross profit, regardless of pricing model. Usage-based pricing changes the timing and the assumptions behind the calculation, since the revenue backing the payback period is less certain period to period, but it does not require a different formula. Shared acquisition costs across product lines add a separate complication: splitting payback calculations by product gets harder when the same sales motion sells both subscription and usage-based components together.

Building the Internal Systems to Support This Reporting

Separating revenue by durability, and separately by product line, is not just a reporting exercise. It requires billing systems, contract management, and revenue recognition processes that can tag revenue at the line-item level, distinguishing fixed fees, minimum commitments, and usage above those minimums, rather than at the contract level alone. Many finance teams built their systems around single-price subscription models and now find that they need to retrofit them to handle usage meters, consumption tiers, and minimum-commitment true-ups.

Get Your ARR Reporting Ready for Hybrid Pricing

Hybrid pricing is not a temporary trend, and the durability question, what is committed versus what depends on continued usage, will only become more important as more contracts combine the two revenue models. A defined measurement window, consistent treatment of credits and minimum commitments, and a documented bridge back to recognized revenue matter more here than which label sits on which line.

G-Squared Partners helps growing SaaS and AI companies build this kind of reporting infrastructure. If hybrid pricing has outgrown a single ARR line, schedule a free consultation to discuss how to structure ARR reporting for your business.