Plans, entitlements, usage and billing
How ENT-1.0 and BILL-1.0 separate technical capability, limits, price, subscription, usage and reconciliation.
How to interpret this document
This content describes technical and methodological behavior that is implemented or explicitly planned in the product. When a control depends on configuration, a provider, a secret, a contract or legal approval, that dependency must remain visible.
Pricing states
BillingPrice distinguishes configured, custom and unconfigured states. The public UI does not invent a price when the commercial catalog does not have one configured.
Usage
Usage and snapshots can derive from canonical operations such as runs. Reconciliation looks for divergence between the SaaS ledger and operational facts.
Plan change
Requesting a change and applying it are separate steps. A change may depend on the contractual cycle and must not create fabricated billing.
Tax document
Commercial SaaS billing is not the same as a tax invoice. Tax-document issuance depends on the legal and finance process of the contracting entity.