← FinOpsAid blog

Why did our Copilot bill change? Usage-based billing, explained for finance — FinOpsAid blog

Why did our Copilot bill change? Usage-based billing, explained for finance

Copilot moved to usage-based billing on 1 June 2026. Prices didn't change, but what you get for them did — and promotional credits mean most orgs see the real bill in September.

For most organizations the Copilot line has looked the same for years: a number of seats, a published price, multiply and done. If your finance partner has started asking why that number moved — or why it suddenly has a component nobody recognises — the answer is that the product changed underneath the invoice on 1 June 2026.

GitHub moved Copilot to usage-based billing. The headline prices did not change, which is why it's easy to miss. What changed is what those prices buy, and whether they're now a floor rather than the whole bill.

What actually changed

The subscription survives. Copilot Business is still $19 per user per month and Enterprise still $39, charged per assigned user whether or not that user opens their editor.

What's new is that each subscription now carries an allowance of AI credits equal to its price — $19 of credits on a $19 seat. Credits are consumed by token usage, input, output and cached alike, at the published API rate for whichever model served the request. Spend within your allowance and the bill looks exactly as it always did. Spend past it and the overage is a real, variable charge.

So the mental model shifts from a subscription to a subscription with a meter attached. That's a different kind of line item, and it needs a different kind of attention.

The exclusion that decides your exposure

One detail does more work than everything else in this post: code completions and Next Edit suggestions consume no credits. They're included, unlimited, on every plan.

Credits are burned by the agentic surfaces — Copilot chat, the coding agent, code review. That single boundary determines whether your bill moves at all. An organization whose developers mostly accept inline completions while they type may never touch its allowance. An organization that has enthusiastically adopted the coding agent is metering every run.

It also inverts the usual adoption story. For years the cost question was "are people using this enough to justify the seats?" Now there are two failure modes: seats nobody uses, and seats someone uses very expensively. Those want opposite responses, and a single adoption percentage hides both.

Why your bill probably hasn't moved yet

Here's the timing detail worth putting in front of finance before they find it themselves.

Business and Enterprise accounts received promotional credits running into August 2026. That means the first months of usage-based billing were substantially cushioned — consumption happened, the ledger moved, and the invoice didn't. Plenty of organizations have concluded from a flat June and July bill that the change didn't affect them.

The first genuinely unsubsidised bill for many will be the one that arrives in September. If you want to know what it holds, the answer is already sitting in your credit consumption for this month — you just have to look at it before the invoice does the telling.

What a Copilot subscription buys before and after June 2026 Before June 2026 a Copilot subscription was a flat per-user charge with unlimited use. Since June it is a per-user charge that includes an allowance of AI credits equal to its price; consumption beyond that allowance is billed at published per-model token rates. Code completions and Next Edit suggestions consume no credits under either model. BEFORE — UNTIL MAY 2026 Subscription — the whole bill nothing else to meter AFTER — FROM 1 JUNE 2026 Same subscription, same price now includes an equal allowance of AI credits + overage token rates, per model CONSUMES NO CREDITS, EITHER WAY Code completions · Next Edit suggestions CONSUMES CREDITS Chat · coding agent · code review Promotional credits ran into August 2026 — for many orgs the first unsubsidised invoice lands in September.
The price didn't change; the shape of the charge did. A flat subscription became a floor with a meter on top, and which of your surfaces developers actually use now determines whether that meter moves at all.

What to do before September

Look at credit consumption per user against allowance. Not total credits — the ratio. A team at 20% of allowance is a different conversation from one at 180%, and only one of them is a budget problem.

Separate the two kinds of waste. Dormant seats still burn a full subscription and consume nothing, so reclaiming them is still the cheapest win available. Heavy agent users are the new variable, and they're often your most productive people — that's a conversation about model choice and workflow, not about taking access away.

Use the native controls. GitHub shipped budgets at enterprise, cost-center and per-user level alongside this change, and cost centers now support pooled AI credits. A cap enforced at the source beats one enforced by a dashboard, and this is one of the few GitHub surfaces where you get that natively.

Re-baseline your ROI story. The cost half of Copilot ROI used to be trivial — seats times price. It has two terms now, and any business case still quoting the old arithmetic is out of date.

Expect the credit ledger to disagree with the invoice. Allowances, promotional credits and the credit-free surfaces all sit between them, which is the ordinary signal-versus-billed reconciliation in a new costume. The gap is explainable; it just has to be explained.

The organizations that will handle September well are the ones looking at consumption now, while it's still a number on a dashboard rather than a line on an invoice.

FinOpsAid tracks both halves: Copilot shows seat assignment and adoption alongside credit consumption against allowance per user and per team, and Budgets tracks the result in credits or dollars — with every modeled figure flagged and reconciled back to the billed invoice.

Frequently asked questions

What changed with GitHub Copilot billing on 1 June 2026?

Copilot moved to usage-based billing. The headline prices did not change — Business is still $19 per user per month and Enterprise $39 — but each subscription now carries an allowance of AI credits equal to its price, and usage beyond that allowance is a real variable charge. A flat subscription became a floor with a meter on top.

Why hasn't our Copilot bill gone up yet?

Business and Enterprise accounts received promotional credits running into August 2026, so early consumption was substantially cushioned — the ledger moved while the invoice did not. For many organizations the first genuinely unsubsidised bill is the one arriving in September.

Which Copilot features consume AI credits?

Copilot chat, the coding agent and code review consume credits. Code completions and Next Edit suggestions do not — they are included and unlimited on every plan. That single boundary decides whether your bill moves at all, because the highest-volume surface is the free one.

How do I estimate my Copilot bill before the invoice arrives?

Look at credit consumption per user against allowance, as a ratio rather than a total. A team at 20% of allowance is a different conversation from one at 180%, and only the second is a budget problem. The answer for next month's invoice is already in this month's consumption.

Want to know what your September Copilot bill looks like before it arrives? Connect your GitHub org — read-only and free during beta — or explore the demo dashboard first.