> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/platform/analysis.md).
# Analysis
Understand software costs, actual payments, and portfolio usage in one place.
***
The **Analysis** page gives administrators a consolidated view of the organization's software portfolio. Use it to compare subscription cost with payment data, identify where applications are concentrated, and monitor how the portfolio changes over time.
Cost, Payments, and Usage answer different questions and use different data sources.
The page is organized into three tabs:
| Tab | What it covers | Details |
| ------------ | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| **Cost** | Annual run rate, completed-month cost, unused-license cost, app ranking, cost distribution, and renewals | [Cost Analysis →](/docs/platform/analysis/cost.md) |
| **Payments** | Actual monthly payments by vendor from a bank, accounting integration, or import | [Payments →](/docs/platform/analysis/payments.md) |
| **Usage** | User and workflow KPIs, application-count trends, rankings, organizational distribution, and security posture | [Usage Analysis →](/docs/platform/analysis/usage.md) |
## Set the scope
The **Filters** control is available on **Cost** and **Usage**. It lets you scope both pages by:
* **Organization** — one organizational unit.
* **Team** — one team within an organizational unit.
* **Group** — one or more groups synchronized from Google Workspace or Microsoft Entra ID.
* **Custom Field** — the values recorded in your own custom fields on applications.
Selecting a Team also selects its Organization. Clear the values to return to the organization-wide view.
The **Payments** tab does not use these filters. It reports payment records from the connected finance sources or imported file and displays its synchronization state separately.
{% hint style="info" %}
Cost and Payments are related but not interchangeable. Cost is calculated from subscription records and billing periods; Payments comes from approved invoices and imported transactions. An approved invoice may still be unpaid, and subscription cost is an estimate from your saved prices, so the two totals do not have to match.
{% endhint %}
***
## Best Practices
* **Start organization-wide, then narrow the scope.** Compare the whole portfolio before filtering to the Organization or Team responsible for a change.
* **Review Cost and Payments together.** A difference can indicate timing, missing subscription metadata, or a finance source that needs to synchronize.
* **Use the year buttons on each chart.** They change the chart period; there is no page-wide time-range filter.
* **Keep subscription dates current.** Cost projections and Upcoming Renewals depend on accurate billing and renewal information.
* **Verify data coverage.** Usage charts are only as complete as the connected directory, application inventory, and extension or integration signals.
***
## Need Help?
If you have questions about any metric on the Analysis page, contact us at ****.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://boza.gitbook.io/docs/platform/analysis.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
