> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/invoices/see-and-browse-all-your-invoices.md).

# See and browse all your invoices

The Invoices page lists your business's invoices, with voided invoices hidden from the default Non-Void view. Each row shows the external ID, status, amount, invoice date, due date, customer, property, who created it, and when it was created; an Aging column also appears for outstanding-relevant statuses (it's hidden for Draft, Paid, Void, Uncollectible, and Payment Processing). To review canceled invoices, select the Void status tab above the table.

The **Invoice Date** column shows the actual invoice date. Click its heading to sort invoices by that date across every page. Invoices without a date appear last when sorting newest first, and first when sorting oldest first.

Click any row to open that invoice. The back arrow on the invoice returns you to the list you came from — including a list filtered to one customer, or the customer's own page when you opened the invoice from there — so you can keep working through one customer's invoices without finding them again. For invoices generated from a subscription, the Created By cell is a link to that subscription instead of a person. A summary aging report sits at the top of the page, the status tabs and the filter control narrow the list, and the New Invoice button in the top right starts a new one.

For an exact customer or property, open **Filter** and choose **Customer** or **Property**. These selections also narrow the aging summary and stay in the URL when you reload.

A search box ("Filter by ID, customer, or property") narrows the list by invoice ID, customer name, or property, and you can also ask Essential to find an invoice by customer name, property, description, or line item.

![Invoices list with aging report](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-2c92d1188fe3cc611e07534cd10844779bca3989%2Finvoices-list.png?alt=media)

> **Where to find it:** Invoices page (main navigation, Invoices)

## Related guides

* [Bulk actions on invoices](/revenue/invoices/bulk-actions-on-invoices.md)
* [Filter invoices by customer, property, aging, or source](/revenue/invoices/filter-invoices-by-aging-or-source.md)
* [Filter invoices by status](/revenue/invoices/filter-invoices-by-status.md)
* [Add a line item to an invoice](/revenue/invoices/add-a-line-item-to-an-invoice.md)
* [Apply a discount to an invoice](/revenue/invoices/apply-a-discount-to-an-invoice.md)
* [Attach files or reports to an invoice](/revenue/invoices/attach-files-or-reports-to-an-invoice.md)


---

# 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://learn.withessential.com/revenue/invoices/see-and-browse-all-your-invoices.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.