> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/how-to/how-to-view-invoice-history.md).

# How to View Invoice History

This guide covers how to access and review past billing records, track payment statuses, and retrieve details for previously issued invoices within the EKR.

1. In the **EKR** **Finance** section, go to the **Invoice History** screen.

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/6a96da59-cb0d-4721-ae8f-9e82dde4dd80/ascreenshot_5c4b4c9539df48fab700120d9027073e_text_export.jpeg)

2. The **Invoice History** will be shown in this screen. Navigate through the pages by using the arrows in the footer. In this example, we navigated to Page 2.

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/6a96da59-cb0d-4721-ae8f-9e82dde4dd80/ascreenshot_a9ce7e26299443b88c63e53415a2b424_text_export.jpeg)

3. Click on the back arrow in the footer to go back to Page 1.

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/33766e7f-3825-4c57-aaba-0a9f36b6f1e6/ascreenshot_6a640f6839c948ab982fb4323585fd25_text_export.jpeg)

4. Filter through and organise the list using the navigation on the headers of the **Invoice History** list.

{% hint style="info" %}
In this example, we organised the **Created Date** header.
{% endhint %}

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/86ebb390-6af6-4ae1-b344-f903eafbf7e5/ascreenshot_859dcd54fbe44fd0a667c57672513647_text_export.jpeg)

5. &#x20;You can also view the agreement associated with the invoices listed by clicking on the link in the **Agreement** header.

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/194d4b3c-6d50-4db6-aa5d-8960d75629ba/ascreenshot_0e2f02cc5c374460b23bf47f856005bb_text_export.jpeg)

6. &#x20;The Invoice History can be seen by clicking on the Invoice History section in the Agreement.

![](https://colony-recorder.s3.amazonaws.com/files/2026-01-07/3362b0d1-b05b-4c30-81e5-966be6c0361e/ascreenshot_83ada3c0f09a4f0db52522b286463348_text_export.jpeg)

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2F3itzhSJxrc4I0of1ouLG%2Fimage.png?alt=media&amp;token=22e8ccb2-2a8e-4fb4-b5cc-e7c803bbef54" alt=""><figcaption></figcaption></figure>


---

# 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.biscit.com/ekr-user-guide/how-to/how-to-view-invoice-history.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.
