Starting 1 October 2026, every seat on GitHub Copilot Business and Enterprise plans is charged upfront at the start of the billing cycle, rather than billed after the fact based on usage. GitHub announced the change on 28 August 2026, and reopened Business and Enterprise signups on 1 September 2026 ahead of it taking effect.
The other half of the change matters just as much: usage that exceeds your plan's included allowances may require a payment method on file to keep working. If you're currently on Copilot Business or Enterprise, or evaluating it, the billing mechanics you sign up under from 1 October are materially different from what they've been, and it's worth understanding exactly what changes before your next renewal, not after.
What "upfront" billing actually changes
GitHub's own changelog frames this as a policy and billing update rather than a price change. There are no new dollar figures disclosed in GitHub's notice beyond the shift in billing mechanism itself. But the mechanism shift is real. Paying upfront at the start of a billing cycle means committing to that cycle's seat cost before you know how it will be used, rather than being billed afterwards based on what happened. For a team that adds or removes Copilot seats mid-cycle, or that has historically waited to see actual usage before deciding how many seats to renew, this changes the cash-flow and procurement timing, not just the invoicing paperwork.
The added-payment-method requirement for over-allowance usage is the piece that can actually interrupt someone's work if it's missed. If your organisation's Copilot usage runs close to or over its included allowance in a given month, and there's no payment method on file to cover the overage, GitHub's notice implies that usage could be affected. That's not something worth discovering when a developer's Copilot access stops working mid-sprint.
Who needs to act before 1 October
Anyone who currently administers a Copilot Business or Enterprise subscription should check three things directly in GitHub's billing settings before the change takes effect: whether a valid payment method is already on file at the organisation level, whether your current usage pattern runs close to your plan's included allowance in any given month, and who on your team has the admin access needed to update billing details quickly if something needs to change.
If your organisation paused or never got around to a Copilot Business or Enterprise signup, note that access reopened on 1 September 2026, so if you'd been waiting, there's no procedural blocker left, only the billing terms changing under you a month later.
Procurement and finance teams should also flag this internally. Upfront billing at the start of a cycle is a different budgeting motion than billing in arrears: the cost hits your books before the month's engineering work happens, not after. For a team managing cash flow tightly, or one whose finance process expects invoices to reflect consumed usage, this is worth a short conversation with whoever owns the GitHub relationship, well before the first upfront invoice lands.
How this fits the wider AI-tooling billing picture
It's a useful contrast to notice: plenty of AI tooling is moving toward metered, usage-based billing that charges after the fact for exactly what was consumed. GitHub is moving Copilot's business tiers the other way on timing: pay upfront for the seat, then have a payment method ready to cover anything beyond the included allowance. Neither approach is inherently better, but if your team is used to reasoning about AI tool costs in arrears, Copilot's shift to upfront seat billing is the kind of change that's easy to miss until an invoice or a declined payment surfaces it.
The practical takeaway is to stop treating your Copilot subscription as a background line item that renews itself without review. Put a recurring check on the calendar, once a quarter is enough, where whoever owns the GitHub account confirms the payment method is current, the seat count still matches who's actually using it, and usage isn't creeping toward the included allowance without anyone noticing. That same review is also the moment to remove seats for people who've left the team or stopped using Copilot, since upfront billing means you're paying for every provisioned seat at the start of the cycle regardless of whether it gets used.
The bottom line
From 1 October 2026, GitHub Copilot Business and Enterprise seats are billed upfront at the start of each cycle, and usage beyond your included allowance may need a payment method on file to keep working. Check your organisation's GitHub billing settings for a valid payment method before that date, so a missed administrative detail doesn't turn into an interrupted developer workflow.