> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/financial-statements/using-statements/view-transactions-financial-statements.md).
# View transactions
You can view the underlying transactions that make up each value in the financial statement. The transaction level is the most granular detail you can see in the underlying database. If you identify any anomalies in the financial information, you can analyze the transactions to identify the root cause.
The ability to view all transactions is limited by your access to financial data. If you have permission to manage custom statements, you can restrict users from accessing transactions in specific accounts.
Right-click a value and click on the statement under **Transactions for**. The statement grid converts into the Analytics grid > [Transaction mode](/analytics/customize-your-view-analytics/change-the-mode/transaction-mode.md), where you can see the list of underlying transactions. You can then use the Analytics tools to analyze the data further.
You can then:
* Click a column header to sort the transactions in that order.
* Add or remove detail (properties) columns.
* Search for specific transactions.
* Export the transactions.
To return to the financial statement, click the **Summary** button above the dimension list.
{% embed url="" %}
View transactions
{% endembed %}
{% hint style="success" %}
Watch this Phocas Demo video: [Spot opportunities & risks](https://www.phocassoftware.com/watch-demo/spot-opportunities-and-risks?autoplay=true)
{% endhint %}
---
# 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.phocassoftware.com/financial-statements/using-statements/view-transactions-financial-statements.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.
