> ## Documentation Index
> Fetch the complete documentation index at: https://docs.airlead.de/llms.txt
> Use this file to discover all available pages before exploring further.
# Plans & settlements
> Understand workspace plan limits, AI usage, and how to review commercial settlements.
# Plans & settlements
## Plans
Your workspace plan determines available capabilities and usage limits. Markets and Company Platform are packaged differently because they support different roles in the lead process.
Check the current plan page for:
* included lead or record volume
* members or seats
* Airlead AI usage
* buyer pools and routing capabilities
* governance and support options
The in-product plan page is the source of truth for your workspace. Contracted enterprise terms can differ from standard plans.
## Two different billing surfaces
Do not confuse:
| Surface | Path | Purpose |
| --------------------- | --------------------- | ---------------------------------------------- |
| **Workspace billing** | Settings → Abrechnung | Your Airlead plan, seats, usage, and invoices |
| **Settlements** | Abrechnungen | Commercial reconciliation between lead parties |
Workspace billing answers “what do we owe Airlead?” Settlements answer “what do we owe or expect from buyers and sources?”
## Settlements
A settlement reconciles billable transaction activity between commercial parties for a defined period.
In Markets, settlements are commonly reviewed as:
* **Kunden (AR)** — amounts related to buyers
* **Quellen (AP)** — amounts related to sources or suppliers
* **Belege** — documents generated for the period
* **Transaktionen** — the underlying delivery records
* **Channels** — activity grouped by distribution setup
Exact labels can vary by workspace configuration.
## Review a settlement period
1. Open **Abrechnungen**.
2. Select the counterparty and period.
3. Confirm whether you are reviewing buyer-side (AR) or source-side (AP) totals.
4. Compare the included transactions with their current states.
5. Review buyer price, supplier cost, margin, and Storno events.
6. Resolve disputed outcomes before finalizing documents.
7. Keep the settlement with the transaction export or audit trail.
Document labels and prefixes can differ by document type.
## Why transaction totals can differ
Common causes include:
* a different settlement period
* transactions not yet in a billable state
* Storno recorded after an earlier review
* commercial values changed before finalization
* filters or counterparties not matching
* exclusive vs multi deliveries counted differently than expected
Start with [Understand transaction states](/guides/transactions/lifecycle) and inspect the affected transaction IDs.
## Practical checklist before closing a period
* [ ] Period start and end are correct
* [ ] Buyer and source counterparties are correct
* [ ] Open confirmations and Storno cases are resolved
* [ ] Test leads are excluded
* [ ] Prices and costs match the agreed terms
* [ ] Document recipients and payment references are correct
## Airlead AI usage
AI-assisted features, including chat and Delivery 1.0 evaluation, can consume **metered AI budget**. If an AI action stops after heavy use, check **AI usage** and billing limits before changing channel or buyer settings.
Next: [Understand transaction states](/guides/transactions/lifecycle) · [Feedback and Storno](/guides/connect/feedback-storno) · [FAQ](/guides/help/faq)