Usage, budgets and billing

Usage metering is always active. It shows what the usage actually costs and is the basis for budgets, limits and receipts.

What is measured

The basis is the tokens of every single request, separated into input and output. From that comes an amount per request, which the panel adds up by person, model, day and month. Model prices are held in the configuration and can be taken over from the provider’s catalog; billing is in euros at an exchange rate that is frozen per billing month. Closed months and their receipts therefore stay as they were.

Maintaining prices pays off

Maintain the price and the context size for every model in use. If these figures are missing, the analysis works with assumptions: it then looks plausible and is wrong all the same, and long conversations are truncated earlier than necessary.

Monthly budget and personal limits

A shared monthly budget in euros can be set for the organization. It is a shared monthly tank, not an amount per person. Without an entry there is no budget. On the overview the status is set against real usage, with a warning and a projection before it gets tight.

You decide with a switch whether the budget is merely displayed or also enforced:

Setting	Effect
off	The budget is display only. Nobody gets locked out.
on	Once the budget is used up, new requests are rejected, for all accounts including the administrators. A notice bar appears in the chat. The panel itself stays operable.

Raising the budget, switching the toggle off and the change of month all lift the block again.

In addition a monthly limit can be set per person.

The pool beats the personal limit

If the shared pot is empty, everyone is at zero, including anyone who is nowhere near exhausting their own limit. The personal limit is an additional brake, not a reservation.

Credit balance: two meanings

The word “credit balance” appears in two places in the panel and means two different things:

	Credit balance of a person	Credit balance of the organization
What it is	the individual limit account in euros	the account balance from recorded deposits
What it is for	technical enforcement of blocks per account	commercial overview of deposits and usage
When it is relevant	only when enforcement is active	as soon as you record deposits

Put briefly: the credit balance per person is a valve, the credit balance of the organization is bookkeeping. The token credit itself is deliberately pooled across the organization, so that individual people do not stand at an artificial limit while budget is left over elsewhere.

Billing and receipts

The billing page shows the selected month with two line items: a platform fee per user and the measured token usage. Both can be issued as CSV and as PDF. Deposits are recorded in a ledger that is only ever added to: a correction happens as a counter entry, the original entry stays in place. Past months sit in an archive.

Better blocked than wrong

If a basis for the calculation is missing, the panel blocks the receipts instead of silently calculating with zero. A receipt that shows too small a figure without an error message would be worse than no receipt at all.

Receipts are not tax invoices

CSV and PDF are receipts, not tax invoices, and there is no payment integration. Invoicing and incoming payments continue to run through your accounting.

The analyses

Two views show the same figures from different angles: a monthly view of the calendar month with key figures, a daily trend and the tables per user and per model, and a rolling view over the last weeks with a comparison to the previous period.

Neither of the two is responsible for the question about a single request; the logs are there for that.