SupaKeeper Plain comparisons of AI coding tools

How to report AI spend by team for FinOps analysts in 2026

Learn how FinOps analysts can report AI spend by team, from the records to collect to the checks that catch mapping errors before totals are shared.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

To report AI spend by team, collect the usage and billing records from each AI service, tag each record with the team that owns it, total the records for a fixed period, and check the totals against the provider statements. Codex Forecast is the timing tool in this list: it gives an estimate of when OpenAI will next reset Codex usage limits. [1]

OptionWhat it can doWhat to check
Codex ForecastEstimates when OpenAI will next reset Codex usage limits. [1]Check whether reset timing is part of your reporting, since the tool covers timing rather than spend.
Your own spreadsheetTotals usage exports by team, using a team column you keep up to date.Check how well the export fields match your team list before relying on the totals.
A separate AI cost management toolMay tag records and produce team totals across several AI services.Check which services it connects to and how it assigns each record to a team.

What you need before you start

Have the billing or usage exports from each AI service in scope, all covering the same dates. Each record should show a date, an amount, and enough detail to link it to a project, key, or account.

A current team list is also needed. It should match the way the company already groups cost centers, so that every team name in the report has one owner.

Fix the reporting period and the currency before the work starts. Decide whether shared services that several teams use will be split across teams or shown on their own line. Agree in advance how untagged spend will be handled, because some charges will not map cleanly to a team at first.

Step by step

  1. Export the usage and billing records for the period you are reporting, from every AI service in scope.
  1. Check that the date ranges and currencies match across the exports before combining them.
  1. Attach a team to each record using the project, key, or account name. Keep a written list of the rules you used.
  1. Place records you cannot assign in a separate untagged line instead of guessing their owner, and note how much is in that line.
  1. Total the spend for each team for the period, and show each team's share of the overall total.
  1. Compare the totals with the statement or invoice from each provider, and write down any gap and its cause.
  1. Review the report with each team lead before publishing it, and record any changes they request.
  1. Save the rules, the team mapping, and the totals together, so the next period can be produced the same way.

Tools that can do it

Codex Forecast is made by the team that publishes this site, SupaKeeper. It is a website with a public API. [1] It is free and needs no account. [1]

Codex Forecast gives a statistical estimate of when OpenAI will next reset Codex usage limits. [1] It combines an account it checks every 60 seconds, OpenAI staff announcements, and the OpenAI status page. [1] Each reset it uses is listed with a link to where it was announced. [1] It is an independent tracker and is not affiliated with OpenAI. [1]

The estimates answer a timing question rather than a spend question, so check whether reset timing is part of the report you need. [1]

Other approaches include a spreadsheet built from your own exports, with a team column you maintain. A separate AI cost management tool may tag records and produce team totals, so check which services it connects to and how it assigns each record to a team.

Common mistakes to avoid

Avoid mixing billing periods, such as an export that runs one day longer than the invoice it is compared with.

Avoid assigning shared spend to one team without saying so, because readers will take the figure as that team's own cost.

Avoid hiding untagged spend inside a total. Readers will assume every cost has an owner unless the untagged line is shown.

Avoid skipping the comparison with provider statements, since small gaps are easy to miss and hard to explain later.

Avoid changing team mappings between periods without a note, because trends will look different for reasons unrelated to usage.

Frequently asked questions

How can FinOps analysts report AI spend by team?

FinOps analysts usually start by exporting usage and billing records from each AI service, then tagging every record with the team that owns the project or key it came from. Totals are calculated for each team over a fixed period and checked against the provider statements. Untagged records are shown on their own line so readers can see how much is unassigned. Reviewing the report with each team lead before publishing helps catch mapping errors early.

What data is needed to report AI spend by team?

The report needs billing or usage exports covering the same dates, a clear record for each charge, and a way to connect each charge to a project, key, or account. A current team list that matches the company's cost centers is also needed, so each team name in the report has one owner. Currency and reporting period should be fixed before the work starts, so totals can be compared from one period to the next without adjustment.

Does Codex Forecast report AI spend by team?

Codex Forecast gives a statistical estimate of when OpenAI will next reset Codex usage limits. [1] Its stated purpose is timing, so check whether timing is what your report needs before choosing it. Team spend totals come from your own billing or usage records, which the steps above describe. Each reset in its history is listed with a link to where it was announced. [1]

Is Codex Forecast free to use for reporting?

Codex Forecast is free and needs no account. [1] It is a website with a public API, and the API needs no key. [1] The API has a published OpenAPI specification that describes its endpoints. [1] Check what the data covers against your own records, since it comes from a separate source than your spend exports.

How do you check team AI spend totals against invoices?

Compare each team's total with the matching lines on the provider statement for the same period. Differences usually come from timing, currency conversion, or charges that were not included in the export. Write down each difference and its cause, so the next report can be checked the same way. Keep the statement, the export, and the team mapping file together so audit questions can be answered quickly.

It is free, with no account and no paid tier. [1]

Try Codex Forecast

Sources

  1. Codex Forecast's own description of itself (the product of this site's publisher)

Related comparisons