GitHub Community
GitHub charged $117.98 incorrectly - Metered usage bug when subscribing mid-month (Ticket #4281580) #193046
Replies: 2 comments 1 reply
-
|
Yeah, you diagnosed this correctly. The 1,500 included Copilot Premium credits reset on the calendar month (UTC), not on your individual subscription anniversary. Usage between March 14 and March 31 gets counted against a credit window that technically started March 1, and since you weren't subscribed on March 1 you don't get that allocation at all. Mid month subscribers fall straight into this gap until the first full calendar month rolls over. On the ticket side: reply to #4281580 and ask them to escalate specifically to the Copilot billing team, not general billing. General billing tends to look at the line items and stop there. Copilot billing has access to the credit ledger and the subscription timestamps together, which is what actually needs reviewing. When you reply, include a screenshot of the Mar 1-31 line and explicitly ask for a prorated refund on the portion corresponding to Mar 1-13, since you weren't a subscriber during that window and those credits couldn't have belonged to you in the first place. The $44.64 April debt with "No usage found" is a separate sync bug between the billing service and the usage dashboard. Call it out explicitly in the same reply, otherwise it gets bundled with the main issue and only one part gets fixed. The access cancellation is harder to reverse until the balance clears. If they say the $44.64 has to be paid before reinstatement but the dashboard shows zero usage, push back and ask them to either document the usage source or zero the balance. Billing tickets usually move in 7 to 14 business days when they land in the right queue, so 4 days is still normal. Past day 10 with no progress, a followup on the same ticket with a short summary of both issues (credit window bug and ghost April debt) tends to do more than opening a new one. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for the detailed explanation, this confirms exactly what I suspected about the credit window bug. |
Beta Was this translation helpful? Give feedback.
-
|
I haven’t personally faced this exact issue, but from what you’ve described, this looks like a billing logic mismatch between the usage cycle and your subscription cycle. If your Copilot Pro+ subscription started on March 14, then your included monthly credits should logically reset based on your billing cycle (14th → 14th), not the calendar month (1st → 31st). Charging metered usage for March 14–31 despite included credits should not happen if the system is working correctly. The fact that:
…strongly suggests a backend inconsistency rather than actual overuse. Also, refunding only $39 and removing access doesn’t really address the root issue — it just partially offsets it. A few things you can do (if you haven’t already):
If others have experienced this, it would likely point to a systemic issue with how Copilot usage is tracked vs billed. This definitely deserves a proper review from GitHub staff, especially since billing accuracy and transparency are critical here. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Account Related
Body
I purchased Copilot Pro+ on March 14, 2026. My billing cycle runs from the 14th to the 14th of each month.
GitHub charged me $117.98 on April 14 broken down as:
Copilot Usage Mar 1–31: $78.98
Copilot Pro+ Apr 14 – May 13: $39.00
The $78.98 is incorrect. Usage from March 14–31 should have been covered by my 1,500 included monthly credits. GitHub's system reset credits on March 1st instead of my billing date (March 14), causing my included usage to be billed as metered usage.
GitHub refunded only $39 and cancelled my access, but the core billing bug remains unresolved. I also have a $44.64 debt in April despite my dashboard showing "No usage found".
Ticket #4281580 has been open for 4 days with no real resolution.
Has anyone experienced this same issue? @github-staff please review
Beta Was this translation helpful? Give feedback.
All reactions