← Blog
#DevOps#GitHub Copilot#IT Procurement#Developer Tooling#Budgeting

GitHub Copilot's Prepaid Seat Reset: A Procurement Playbook for September–October 2026

webhani·

GitHub paused new self-serve signups for Copilot Business and Copilot Enterprise on April 22, 2026, as part of preparing a shift to usage-based billing. On September 1, 2026, signups reopened for customers paying by credit card or PayPal. The change that actually matters for budgeting isn't the reopening itself — it's what comes with it: every new seat assignment now requires payment upfront before the user gets access, and starting October 1, 2026, existing card/PayPal customers move to the same upfront-per-cycle billing model.

For any organization managing more than a handful of Copilot seats, this is a procurement and internal-approval process change, not just a pricing footnote. We've been walking clients through what to actually do about it.

What changes mechanically

Under the old model, an admin could assign a Copilot seat to a new hire or contractor immediately, and billing caught up at the end of the cycle. Under the new model, seat assignment and payment are coupled — the payment has to clear before the seat activates. For teams that provision Copilot access as part of a standard onboarding checklist, this introduces a dependency that wasn't there before: onboarding automation that assigns a seat now needs to account for a payment step that can fail or lag, rather than assuming instant activation.

Old flow:
  Admin assigns seat → User has access immediately →
  Invoice reflects usage at end of billing cycle
 
New flow (from Oct 1, 2026):
  Admin assigns seat → Payment charged upfront →
  Payment clears → User gets access

If your onboarding pipeline includes a script or Terraform-managed process that provisions Copilot seats via the GitHub API, this is worth testing in a sandbox org before your next batch of hires — a silent payment failure now means a blocked developer, not just a billing discrepancy to clean up later.

The budgeting implication: seats become a prepaid commitment

Prepaid-per-cycle billing changes how Copilot shows up in a budget. Instead of a variable monthly line item that scales up and down with actual seat usage mid-cycle, you're committing to a seat count at the start of each cycle. Deprovisioning a departing employee's seat mid-cycle doesn't refund that cycle's charge — the same way most SaaS prepaid-seat models work (this mirrors how Slack, Zoom, and similar per-seat SaaS tools already bill, so the operational muscle to handle it likely already exists in your finance team; the gap is usually IT-to-finance communication, not finance capability itself).

We recommend clients treat Copilot seat count the same way they treat any other prepaid-seat SaaS: reconcile seat count against active headcount monthly, not reactively when someone notices an invoice discrepancy.

# Example: monthly seat reconciliation checklist
copilot_seat_audit:
  frequency: monthly
  steps:
    - compare_active_seats_to: hris_active_employee_list
    - flag: seats_assigned_to_terminated_accounts
    - flag: seats_unused_in_last_30_days  # candidate for reclaim
    - action: deprovision_before_next_billing_cycle_start

The last line matters most: because charges are upfront-per-cycle, deprovisioning before the cycle starts (not mid-cycle) is what actually saves money. A seat removed on day 15 of a 30-day cycle still cost the full cycle.

What this means if you were waiting out the pause

If your organization delayed a Copilot Business/Enterprise rollout because self-serve signup was paused since April, the reopening on September 1 removes that blocker — but we'd recommend deciding on your seat allocation model before onboarding at scale, precisely because seats are no longer a low-friction, adjust-as-you-go resource. Decide up front:

  • Which roles get standing Copilot access vs. which get provisioned per-project
  • Who owns the monthly reconciliation (usually IT, informed by an HRIS feed, not engineering managers)
  • Whether contractor/temporary seats get a shorter internal review cycle than full-time employee seats, given the same prepaid cost applies regardless of tenure

Takeaways

  • From October 1, 2026, GitHub Copilot Business/Enterprise seats are billed upfront per cycle — deprovisioning mid-cycle doesn't refund that cycle, so seat cleanup timing now has a direct cost impact.
  • If seat provisioning is automated, test the payment-then-access dependency in a sandbox before relying on it for real onboarding — a payment failure now blocks a developer, not just a future invoice.
  • Set up monthly seat reconciliation against your active headcount list now; the operational pattern is the same one most teams already use for other prepaid-seat SaaS tools.

Sources: Upcoming changes to GitHub Copilot policies and billing, Pausing new self-serve signups for GitHub Copilot Business

← Back to Blog