Verified decision guide
Copilot Organization Charges: Trace AI Credit Usage
Trace Copilot AI Credit consumption to the documented billing report fields, distinguish included drawdown from paid charges, and identify attribution limits.
Direct answer · current usage-based Business / Enterprise
Start with the billing entity and the AI usage export
Current Copilot Business/Enterprise: AI usage exports aggregate by date, model, username over at most 31 days. Organization owners download per-user reports; enterprise owners and billing managers can filter by user directly. Prompt-level causality is not documented.
Which organization pays for the seat? Request the Detailed usage report from Metered usage and inspect the user's license line and its organization column. When several organizations grant the same user a Copilot license, GitHub selects one at random each billing cycle; last month's payer is not a reliable default.
A pool drawdown is not automatically an extra charge. Reconcile gross usage with discounts and the net billable amount before allocating money to a team. The pooling guide explains where included credits come from; budget controls explains how to stop further paid usage.
Follow the charge
- Confirm the organization or enterprise that bills the seat. Open that entity's Billing & Licensing → Usage / Metered usage → AI usage. Use the same UTC date range throughout. Personal usage views are not substitutes for an organization bill.
- Enterprise owners and billing managers can filter by user. Organization owners must download a usage report to inspect per-user consumption. Broader company-spending guidance does not remove this role restriction.
- Choose Get usage report on AI usage, select at most 31 days, then request the download. The AI report aggregates by
date / model / username. Inspectinput, output, cache_read, cache_writeto understand a model's token composition. - From Metered usage, request the Detailed usage report for up to 31 days. Match
username, licensesku,organizationandcost_center_nameto the same billing cycle. Use the documented billing fields for amounts. Group only populated dimensions; a blank repository or cost center is missing attribution, not proof that no work happened. - For enterprise departmental chargeback, inspect cost-center membership and its effective assignment. Explicit user or enterprise-team assignment can support financial grouping. A GitHub team name is not automatically a billing cost center.
- When totals disagree, check account, report type, date range, units and discounts first. Preserve the export and ask the billing administrator or GitHub support about unresolved differences; do not fill missing fields from guessed prompt activity.
What each report can establish
| Evidence | Supported attribution | Boundary |
|---|---|---|
| AI usage export | Date, model, username, credit consumption and token fields. | Aggregated billing evidence; no documented prompt, retry, tool-call or individual agent-step causality. |
| Detailed metered report | Product/SKU and applicable user, organization, repository or cost-center fields. | workflow_path concerns GitHub Actions where applicable. It is not a Copilot agent activity trace. |
| Multiple-organization seat | The detailed report identifies the charged organization for the user's license. | GitHub chooses an organization each billing cycle. Do not apply the oldest-organization rule used by other GitHub licenses to Copilot. |
| Cost center | A configured financial group for enterprise reporting. | Use recorded assignments; do not retroactively infer a department from the repository owner. |
| Usage amount | gross_amount − discount_amount = net_amount. | Included-use discounts can reduce the bill. Quantity and money are separate fields; inspect unit_type. |
Derived arithmetic example, not an observed invoice: a line with $12 gross and $10 discount has $2 net. It does not prove all of a user's 1,200 consumed AI Credits were paid continuation. License fees and separately billed products still require their own report lines.
For predictable attribution, GitHub recommends a single licensing organization per user or cost-center budgets with direct user assignment. Coordinate a licensing change with the administrator. New cost-center assignments affect future usage; they do not justify rewriting historical report rows. See the allocation reference and multiple-license budget rule. The personal-to-organization guide owns cancellation/refund consequences of seat assignment.
Unknowns that matter
Unknown — unresearched: these reviewed sources do not establish a Copilot-specific maximum reporting delay. The two-hour delay documented for GitHub security products is not a Copilot guarantee. Report generation and observed usage can differ; a missing row is not proof of zero consumption.
Unknown — account_dependent: billing role, populated export dimensions, actual team membership and negotiated billing terms. This procedure does not inspect your account or promise exact per-prompt attribution.
Sources and freshness
- GitHub billing reports reference
- GitHub role-specific usage views and exports
- Managing company Copilot spending
- GitHub cost-center allocation
- Copilot organization and enterprise usage billing
Review weekly and before chargeback. Reverify report columns, role permissions, billing entity, cost-center assignment and included/paid accounting whenever an export or bill disagrees.
For current plans and allowances, see the product guide.