Recurring costs for AI seats
State an AI seat plan such as Claude Team once on a custom provider, and Costfluent writes its cost every billing period, beside the rest of your AI spend.
Planned: uploads to a custom provider
No AI vendor reports what its seat plans cost through an API, so the seats of Claude Team, ChatGPT Business or Cursor Teams never reach Costfluent on their own. A recurring cost closes that gap: on a custom provider you state a seat plan once, with its seats per tier at the net price on your invoice, and Costfluent writes its cost for every billing period from then on, until you end it. The cost lands in the AI and Machine Learning category, so it shows in the AI spend dashboard, reports, budgets, alerts, insights and exports beside your other AI spend.
Before you start
- The Manage integrations capability, which owners and integration owners hold. Only they see the Recurring costs card and can add, change or delete a recurring cost; anyone who can view a workspace that reads the custom provider sees the cost it writes in reports.
- A custom provider to hold the seats, such as one named "AI seats". See Create the provider.
- The vendor's invoice: the billing currency, whether it bills monthly or annually, the day a billing period starts, and the net price of each seat tier, before VAT.
Add a recurring cost
- Open the custom provider: under Integrations, select Custom provider, then the provider's name. See Find a connection.
- On the Recurring costs card, add a recurring cost.
- Choose the product. A preset fills in the name, the service name and, for the Claude and ChatGPT plans, the maker tag; it never fills in a price. Choose "Other" for any other seat plan and enter the name and service yourself.
- Choose the billing currency the invoice is in, monthly or annual billing, and the start date: the first day of a billing period on the invoice, at most 13 months back and at most one month ahead. Add an end date only when the plan already has one.
- Add one to ten seat lines, one per tier, each with a name, the number of seats and the price per seat per billing period: your own net price from the invoice, not a list price. On annual billing that is the price of one seat for the whole year.
- Save the recurring cost.
Costfluent then writes every billing period from the start date through the current one, and each later period as it starts. A start date in the past fills in the periods since then; one in the future writes nothing until that day.
What Costfluent writes
Each billing period's charge is the seats times the price per seat, line by line, spread evenly over the period's days: a monthly plan over the days of its month, an annual plan over the days of its year. A period is written whole on its first day, its later days included, as the vendor bills it in advance. Every day of it is an ordinary cost row of the custom provider with the charge category Usage, the charge frequency Recurring, the service category AI and Machine Learning, and its seats as a quantity in UserMonths.
For example, at Claude Team's list prices on 2026-11-14, $25 a month for a standard seat and $125 for a premium seat, a team with 8 standard and 2 premium seats on monthly billing has two lines: $200 and $250, so $450 a month, or about $14.52 a day in a 31-day month. On annual billing the list prices were $20 and $100 a seat a month, so the lines carry $240 and $1,200 a seat for the year: $4,320 spread over 365 days, about $11.84 a day. Enter the price on your own invoice instead: discounts, taxes and currencies differ.
Presets
| Preset | The maker tag it fills in |
|---|---|
| Claude Team, Claude Enterprise | ai:model_provider with the maker of Claude, as Costfluent's AI tags write it |
| ChatGPT Business, ChatGPT Enterprise | ai:model_provider with the maker of ChatGPT, as Costfluent's AI tags write it |
| Cursor Teams, GitHub Copilot | None |
| Other | None; add your own tags |
The maker tag puts a seat plan beside the spend on its maker's models: grouped by Tag and ai:model_provider, Claude Team seats share a row with the Claude models your cloud bills, such as Claude on Amazon Bedrock.
Never enter seats a connection already collects. GitHub bills Copilot seats on the GitHub organization's own bill, and a connection that reads that bill already brings them in; entering them again counts every seat twice, in every report and in the tracked spend on Plans and billing. Use the GitHub Copilot preset only for seats no connection reads.
Read the seats
- The AI spend dashboard. Let the workspace see the custom provider's cost (Choose which workspaces see the cost). The seats count in the "AI spend" report and stay out of "AI tokens", which counts tokens only. A workspace whose first AI cost is a recurring cost gets the dashboard then. See The AI spend dashboard.
- Seats as usage. With Measure set to Usage, a report shows the seats in
UserMonths, a seat for a month, and prices each row per seat-month.UserMonthsis the unit GitHub bills Copilot seats in, so seats of different products add up in one unit. Group by Usage unit to keep them apart from other usage. See Usage and count. - Everywhere else. Budgets, cost alerts, insights and exports read the seats like any other cost of the custom provider, and they count toward the tracked spend on Plans and billing like every custom provider's cost.
Change seats
- On the Recurring costs card, select "Change seats" on the recurring cost.
- Choose the billing period the change applies from.
- Change the lines: their seats or prices, a new tier, or a tier you no longer pay for.
- Save the change.
The chosen period and every later one take the new lines; earlier periods keep theirs. A change never prorates: when the vendor bills a seat added in the middle of a period as a prorated line, add that line once to the same custom provider as an ordinary row, by upload or through the Public API (Use the Public API).
Reporting dimensions
What each group-by dimension of a cost report holds for a recurring cost's rows.
| Dimension | For a recurring cost |
|---|---|
| Provider name, Billing account | The custom provider's name |
| Service | The service name the preset filled in or you entered |
| Service category | AI and Machine Learning |
| Charge category | Usage |
| SKU, SKU ID, Charge description | The seat line's name, such as the tier |
| Usage unit | UserMonths |
| Tag | The recurring cost's tags, the maker tag ai:model_provider among them |
| Sub-account, Region, Resource | None |
Edit, end or delete
- Edit the name, the service name, the tags or the end date. These apply to every period, past ones included.
- The currency, the billing cadence and the start date are fixed. If one is wrong, delete the recurring cost and add it again.
- End a plan you cancelled by setting its end date, the first day it no longer applies. Periods that started before it stay, each one whole, and nothing is written after it.
- Delete removes the recurring cost and every cost it wrote, past periods included. To keep the history, end it instead.
How it behaves
- Timing. Costfluent writes a new or changed recurring cost within a few minutes, and each new billing period within a few minutes of its first day.
- Insights. A new recurring cost is a step up in daily spend, and may raise a cost anomaly on Insights.
- Uploads and the Public API. CSV uploads and Public API submits to the same custom provider leave the recurring cost's rows alone, even where they cover the same days. A line ID starting with
recurring-cost:is reserved for them, and an upload or submit using one is refused. - A write Costfluent cannot make, such as while the custom provider is paused, shows its reason on the card, and Costfluent writes the period on a later run once the reason is gone.
- Limits. A custom provider holds up to 50 recurring costs, each with up to 10 seat lines and up to 120 seat changes. A line has 0 to 100,000 seats.
- Automation. Recurring costs are managed in the console only; the Public API, the Go SDK and the Terraform provider have no recurring costs yet. A script can still send seat rows as ordinary rows through the batch submit (Use the Public API).
- Removing the custom provider removes its recurring costs with it.
Troubleshooting
- The start date is refused. It must lie at most 13 months before today and at most one month after it. For an older plan, start at the earliest period allowed.
- The currency, the cadence or the start date is wrong. They cannot be changed: delete the recurring cost and add it again.
- The card shows a reason and the cost is not written. Costfluent could not write the period, for example while the custom provider is paused. Once the reason is gone, the next run writes it; nothing needs to be entered again.
- An upload or submit fails with "LineItemId must not start with "recurring-cost:", which recurring costs reserve". Give the line an ID of your own that does not start with
recurring-cost:. - Seats count twice. A connection already collects them, or the same plan was entered twice. Delete the recurring cost that repeats them.