> For the complete documentation index, see [llms.txt](https://cee-systems.gitbook.io/tcp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cee-systems.gitbook.io/tcp/tcp-billing/key-points-summary.md).

# Key Points Summary

* Only **organization administrators** can manage billing, invoices, wallets, PCC settings, and subscriptions
* **Billing verification is required** before creating invoices - allow 1-2 business days for CEE Travel Systems finance department approval
* **PCC configuration is required** before accessing billing and subscription features
* The **root administrator** can assign custom expiry dates to marketing wallet credits. Default expiration: **1 month**
* **Credit transfers** are instant with no approval or limits required
* **Subscriptions auto-renew** if sufficient credit exists (Marketing Wallet used first, then Organization Wallet)
* **Free trials** are available once per organization per application (one month + USD 100 deposit)
* **Paid subscriptions** cost USD 290/month and auto-renew
* **VAT may be added** to invoices based on your organization's country and tax status


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cee-systems.gitbook.io/tcp/tcp-billing/key-points-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.