GitHub is changing how it bills Copilot Business and Copilot Enterprise seats, and the biggest shift lands October 1, 2026. If your team pays by credit card or PayPal, every assigned seat will start getting charged upfront at the beginning of each billing cycle, according to GitHub's August 28 changelog post. That's a different mechanic from what most teams are used to, and it turns idle Copilot seats into money leaving the account before anyone opens the editor.
Two more changes ride along in the same post, one that already took effect and one landing a few days before the billing change. Here's what each one actually does, who it hits, and what to check before October 1.
What's changing on 1 October 2026
Starting October 1, 2026, existing Copilot Business and Copilot Enterprise customers who pay by credit card or PayPal will be charged upfront, at the start of the next billing cycle, for every seat currently assigned, per that changelog post's billing section. Today, that charge is billed in arrears over the course of the cycle. After October 1, it's billed upfront the moment a seat is assigned, whether or not the person attached to it ever opens Copilot.
Three details soften that, all from the same post. Prices aren't changing, GitHub says so explicitly. Mid-cycle seat additions keep prorating as before, so adding someone halfway through a billing period still costs a partial-period rate, not a full upfront charge. And on usage: if a seat exceeds its included usage, additional payment may be required, with included usage prorated across the month to match the seat-cost proration. None of that is a rate hike. It's a timing change: a stale seat now costs money the moment it's assigned, not the moment it's used.
Who this actually hits
The qualifier matters here: this applies to customers paying by credit card or PayPal. The changelog doesn't say anything about invoiced customers or enterprise-agreement billing, so don't assume either way how those accounts are treated. If your organization pays GitHub through an invoice rather than a card on file, this specific clause simply isn't addressed in the source, and you should confirm directly with your GitHub account team rather than guess.
For everyone on card or PayPal billing, the teams who feel this first are the ones with seat sprawl: a developer who got a seat during a hiring push six months ago and never logged into Copilot, a contractor whose engagement ended but whose seat stayed assigned, a pilot group that grew past its original scope. None of that costs anything extra today, because those assigned seats are billed in arrears over the cycle. After October 1, every one of those seats generates an upfront charge the moment the new billing cycle starts, whether the person behind it writes a single line with Copilot or not.
What to do before 1 October
Pull the seat assignment list now, while there's still time to act before the first upfront charge hits. Cross-reference it against actual usage, GitHub's own admin reporting shows last-active dates per seat, and flag anyone who hasn't touched Copilot in the last billing cycle. Decommission seats you can't justify, and confirm with team leads before removing anyone who might just be between projects.
Timing matters more under the new rule than it used to. The changelog is explicit that revoking a seat doesn't trigger a prorated refund, and the removal only takes effect in the next monthly billing cycle. Once the upfront charge for a cycle has landed, dropping the seat doesn't get that money back, so the cleanup has to happen before the charge hits, not after.
This is also a reasonable moment to ask whether Copilot seats are earning their cost in the first place, separate from the billing mechanic. What the actual research shows about AI coding speedups is a useful gut check: the gains are real on bounded, well-scoped tasks and much thinner on complex work inside a codebase someone already knows cold. If a seat's been idle, it's worth asking whether that's a rollout problem or a fit problem. New hires are a common blind spot here too; how fast AI-assisted engineers actually ramp up affects when a freshly assigned seat starts paying for itself, and a seat sitting unused during someone's first two weeks isn't the same signal as one unused after three months.
New Copilot Business/Enterprise sign-ups reopened 1 September
Sign-ups for new Copilot Business and Copilot Enterprise customers paying by credit card or PayPal reopened on September 1, 2026, with what GitHub describes as strengthened account vetting and updated billing experiences, per GitHub's changelog entry on the reopening. If your organization paused a signup or held off starting a new account, that door is open again as of this writing.
One clause belongs specifically to these new customers, not to existing accounts: all new Copilot Business or Copilot Enterprise seat assignments now require payment for each seat before the user gains Copilot access, according to the same post. That's a new-customer onboarding rule, distinct from the October 1 upfront-charge mechanic that applies to existing accounts. Don't conflate the two: new customers pay before access starts at all; existing customers get billed upfront for seats already assigned once the new cycle begins.
The other change coming 28 September: one Copilot Chat experience
No earlier than September 28, 2026, GitHub plans to merge Copilot's cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile into a single experience, replacing three separate policies with one consolidated policy, per GitHub's changelog entry on the Copilot Chat consolidation. The cloud agent will move to Sandbox as part of the change, which GitHub frames as a faster cloud experience.
The detail worth flagging to anyone who handles security or compliance review: chat data retention is set to change from 28 days to the life of the account, according to the same post. That's a real shift in how long Copilot Chat history sticks around, and it's worth raising with whoever owns your data retention policy before the change lands rather than after.
There's effectively no staying on the old setup either. GitHub says that opting out of the unified Copilot experience means you or your teams lose access to Copilot on github.com and GitHub Mobile once the new experience launches. That makes the consolidation less a choice to evaluate than a deadline to prepare for.
Code review's default effort level changes too
Also effective no earlier than September 28, 2026, Copilot code review's default effort level moves from Lite to Balanced, per that changelog's code review update. Orgs and repos that want to stay on Lite need to explicitly select it in repo or org settings before that date; otherwise the switch happens automatically. If your team picked Lite deliberately for speed or cost reasons, check your settings this week rather than after the default flips.
Tool changes like this raise the same question as seat hygiene: is the setup matched to how the team actually works, or just left on GitHub's default. Why reviewing AI-generated code matters more than typing speed makes the same argument about hiring, and misconfigured Copilot seats are rarely the root problem on their own. The productivity problems no coding tool fixes usually sit upstream of tooling choices, and no billing change forces that conversation the way an unexpected invoice does.
FAQ
Is GitHub Copilot's price going up on 1 October 2026?
No. GitHub's changelog states explicitly that prices aren't changing. What changes is the timing of the charge: assigned seats get billed upfront at the start of the billing cycle instead of over the course of it.
Does the upfront billing change affect all Copilot Business and Enterprise customers?
No, only customers paying by credit card or PayPal, according to the changelog. The post doesn't address invoiced or enterprise-agreement billing at all, so confirm directly with GitHub if that's how your account is set up.
What happens to unused Copilot seats after 1 October?
They still get charged upfront at the start of the billing cycle, whether anyone uses them or not, per GitHub's post. That's the reason to audit assigned-but-unused seats now, before the first cycle under the new rule starts.
What's changing with Copilot Chat on 28 September 2026?
Copilot's cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile are set to merge into one experience under a single consolidated policy, with the cloud agent moving to Sandbox and chat data retention extending from 28 days to the life of the account, according to the changelog.