Monthly billing and export 

Monthly billing report 

Monthly billing report, a button below the range switcher, opens a page for one calendar month (ADR-231). It shows the previous complete month by default; the running month and the twelve months before it can be selected. A month runs from its first to its last second in the server timezone, and the page names both. The running month is marked as not complete.

The page has four parts:

Cost

Requests, tokens, the estimated cost of the month, the markup in percent, the markup amount and the total including the markup.

Active editors

Every backend user with at least one request in the month, with cost, requests and tokens. A user counts as active whatever their account state is today; the column Account state today shows when the user is an administrator, disabled or deleted. Requests made without a backend user (command line, scheduler) are listed in a separate row and are not counted as an editor, so the rows add up to the month total. That row includes the usage of core's command-line user _cli_: since TYPO3 14.3.8, console commands such as the scheduler record their usage under it.

Entitled to AI Tasks

Backend users who could use the AI Tasks module, as of today: users, groups and permissions keep no history, so this list shows today's state for every month, and the page says so with the date. A user is counted when all of these hold:

• the account can log in now: not disabled, not deleted, within its start and end time;
• the permission Execute AI tasks (see Backend user permissions) is granted through one of the user's backend groups or a subgroup of one; hidden and deleted groups grant nothing;
• the module AI Tasks is allowed on the user record or on one of those groups.

Administrators are not counted: they can use every AI feature without the permission. The page states how many administrators can log in now, leaving out core's command-line user _cli_, which TYPO3 creates as an administrator with a random password. Extensions that call the AI services with their own permission checks, such as an editor assistant or a chat, grant access their own way; users whose access comes only from such an extension are not counted here, so an active editor is not necessarily entitled to AI Tasks. Do not bill per entitled editor without deciding which of these accesses counts.

Results by kind

Requests, tokens and estimated cost by service type, calling extension (see Per-extension table) and task.