Software Bills Just Became Utility Bills

A finance lead I work with at a $9M services firm pulled three software invoices side by side last week. Same three vendors as 2024. Last year each one was a flat monthly charge that matched the renewal letter to the penny. This year, every invoice carried a different number. The lowest was 8% under accrual. The highest was 41% over. None of the line items reconciled to what her ERP had budgeted.

Two of the three vendors had moved to usage-based billing in Q1. The third was still on a seat-based contract but had quietly added a metered AI add-on. Her variance wasn't bad pricing. It was a different billing model wearing the same vendor name.

What the new invoice looks like

Software vendors are repricing AI as consumption, not access. GitHub Copilot moves to usage-based billing on June 1. OpenAI's enterprise tier already bills per token class. HubSpot, Atlassian, and Salesforce have each introduced AI add-ons priced by event volume or model calls. The shift accelerated in Q1 when several large vendors amended renewal letters to add metered components without renegotiating the underlying contract.

The invoice tells the story. A 2023 SaaS invoice had a seat count, a unit price, and a total. A 2026 invoice carries token tiers, model class, throughput overages, premium feature flags, and a base subscription. It reads like an AWS bill. Most accounting systems read it like a vendor PDF and post the total to a single GL line.

Where the budget breaks

A vendor that used to be a fixed-cost line item is now a utility meter. Finance teams that haven't redrawn the budget are accruing the wrong number every month.

Three things compound. The accrual no longer ties to a contract amount, so close week starts with an unknown. The variance against budget is structural, not exceptional, so the explanation lands on the CFO every month. And the spend isn't capped, so a product team running a model against a customer dataset can move the bill by 30% without anyone touching procurement.

For a $10M revenue company, software is typically 8 to 12% of opex. Half of that line going variable changes the shape of the operating budget. It also changes the FP&A skill required to defend it.

What to do this quarter

Tag every vendor with metered billing as a separate GL subaccount. Anything with a token, call, event, or run-rate component lives outside the fixed software bucket. Treat it like cloud spend. Track unit economics by vendor: dollars per active user, dollars per model call, dollars per transaction. The board metric is no longer ARR exposure. It's cost per usage event.

Then build a usage signal. Pull the vendor's metering dashboard once a week. If the vendor doesn't expose one, that's the negotiation. A vendor that meters you and refuses to show the meter is asking to be replaced.

Cap the spend. Every metered contract needs a monthly ceiling above which the vendor pauses or alerts. Most vendors will agree because their commercial team doesn't want a chargeback fight in Q3. Procurement teams that don't ask are absorbing the variance for them.

Your software vendors changed their billing model. Your budget didn't notice.