Plan, quotas and the format gate

The Plan and usage page (/en/account/plan).

The quotas

As of 5 October 2026:

Plan	Members	Invoices/month	API keys	API calls/month	Templates	Batch (files)	Tool calls/month	Creation formats	Mail dispatch
Free	1	10	1	10	1	5	50	2 selectable	–
Startup	1	10	0	–	1	10	250	2 selectable	–
Team	5	50	0	–	2	25	1,000	all	yes
Business	10	250	5	2,500	5	50	5,000	all	yes
Enterprise	unlimited	unlimited	unlimited	unlimited	unlimited	unlimited	unlimited	all	yes

In addition:

• The mail quota is twice the invoice quota per month.
• Bulk import is not a plan dimension: on all cloud plans it runs over 10 rows per run.
• All monthly counters run on the UTC calendar month and reset at the turn of the month.
• Anonymous use is not counted. The invoice quota and the tool counters only run with a tenant signed in.
• A creation attempt that fails a pre-check or the format gate consumes no unit; a run that fails after the booking is refunded.

Why the start page shows a sum and the plan page the highest single value

Tool calls are counted per tool — validate, view, convert, extract, combine, capture. A sum against six times the limit would suggest headroom while an individual tool is already exhausted. The plan page therefore names the highest single value.

Format gate

Free and Startup may create in at most two target formats. All nine are selectable: xrechnung, zugferd, peppol, fatturapa, finvoice, ebinterface, austrofix, favat, facturae.

Rule	Behaviour
Automatic claiming	while slots are free nothing blocks: the first creation in a format claims a slot — and consumes no monthly change
A hybrid PDF counts as ZUGFeRD	both share one slot
Changing	an explicit change on the plan page, once per calendar month
When the gate applies	the create form and the API reject the request and name the permitted formats

A rejected form claims no slot — the gate runs only after all pre-checks have passed.

Payment

Upgrades go through a hosted checkout, and subscription management through a customer portal — plain redirects, with no third-party payment code on the portal’s own pages. Both are owner rights. If the payment connection is not configured on the installation, the buttons do not appear; the page remains usable as a pure usage overview.

This page does not exist in an Enterprise installation

Every tenant there is unlimited, there is nothing to purchase, and /{language}/account/plan answers with 404; the menu entry is absent. The counters keep running — an administrator wants to see what was consumed; they simply no longer limit anything.