> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/inventory/software-assets/view-software-assets.md).

# View software assets

The **Software Assets** page provides an overview of your active software subscriptions, current spending, and total spending.

To view software assets: 

1. Go to **Inventory** > **Software Assets**.
2. Use the search options to view your software asset inventory list. You can search using a purchase order number or reference number. You can search by purchase order number or reference number. Additionally, you can apply available filters or expand **Show more options** to access advanced filters.
3. Review details on two tabs: Software Assets and Financial Transactions.
   * The **Software Assets** tab allows you to view only your active software subscriptions and current spending. Please note that it does not show past payments.
   * The **Financial Transactions** tab provides a comprehensive view of your total spending on all software, including both subscriptions and past transactions.


---

# 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://docs.platform.softwareone.com/modules-and-features/inventory/software-assets/view-software-assets.md?ask=<question>&goal=<user_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.