GitHub Copilot Reopens Business and Enterprise Sign-Ups With New Billing Terms
GitHub CopilotStarting September 1, 2026, GitHub is reopening Copilot Business and Copilot Enterprise sign-ups for organizations paying by credit card or PayPal. New seat assignments on those payment methods will now require upfront per-seat payment before a user gets Copilot access, and existing customers on card/PayPal billing move to the same upfront model starting October 1, 2026. List prices are unchanged, but GitHub is also removing prorated refunds for revoked seats.
Key Takeaways
- Upfront payment is now mandatory for new Copilot Business and Enterprise seats on credit card or PayPal, starting September 1, 2026.
- Existing customers aren't grandfathered — the same upfront-billing behavior applies to them from October 1, 2026 onward.
- List prices stay the same, so this is a billing-mechanics change, not a price increase, but it does change cash-flow timing for finance teams.
- Prorated refunds are gone for revoked seats, making seat removal timing a real cost consideration for admins.
- Prorated charges for new seats are unaffected — only the refund side of the seat lifecycle changed.
- This shift lands alongside GitHub's broader 2026 move to usage-based billing, part of a pattern of tightening how Copilot spend is tracked and collected.
Sign-Ups Reopen for Card and PayPal Customers
GitHub is lifting a restriction on new Copilot Business and Copilot Enterprise sign-ups. Beginning September 1, 2026, organizations that pay by credit card or PayPal will once again be able to sign up for these plans directly, without going through the alternate onboarding paths GitHub had been steering card and PayPal customers toward.
Upfront Payment Becomes the Norm
The bigger operational change sits underneath the reopening: every new Copilot Business or Copilot Enterprise seat assigned on a card or PayPal account will require payment for that seat to be collected before the user gains access to Copilot. That marks a shift away from a model where a seat could be provisioned first and reconciled on the next invoice. Existing customers already on these payment methods are not exempt — GitHub says the same upfront-charge behavior takes effect for them starting October 1, 2026, so admins managing seats through the fall should expect payment to be collected immediately at the point a seat is assigned rather than batched into a later billing cycle.
No More Prorated Refunds on Revoked Seats
GitHub is also tightening how seat removals are handled financially. Previously, revoking a seat mid-cycle could generate a prorated credit. Going forward, seat revocations will not generate a prorated refund — the seat's cost for that billing cycle is retained regardless of when in the cycle it's removed. Newly added seats still prorate normally from the assignment date through the end of the billing cycle; it is only the refund side of the equation that changes.
Why This Matters
For finance and engineering-management teams that add and remove Copilot seats frequently — onboarding contractors, cycling seats during headcount changes, or trialing access for new hires — this changes the cost calculus of seat churn. Assigning a seat now means committing to that cycle's cost immediately, and removing a seat early no longer recovers any of that spend. Combined with GitHub's broader move to usage-based billing earlier in 2026, this is another step toward tighter, more immediate alignment between seat assignment and payment collection across Copilot's paid tiers.