> 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/filter-invoices-by-aging-or-source.md). # Filter invoices by customer, property, invoice date, aging, or source > **Where to find it:** Invoices page, the filter (funnel) control to the right of the status tabs Open **Filter**, then choose **Customer** or **Property**. Search the options and check as many customers or properties as you need. Within each filter, invoices can match any checked value. Using both filters shows invoices that match a selected customer and a selected property. Selecting customers narrows the property choices to their properties. Removing a customer clears selected properties that no longer belong to any selected customer; clearing all customers leaves your property selections in place. The choices include accounts with invoices across all statuses, including inactive accounts. Customer filtering follows the property's current owner. Both filters combine with the status tabs, search, Aging, and Source. They also update the aging summary and the invoices available for bulk actions. Changing a filter returns you to the first page. Your customer and property selections stay in the page URL, so reloading or sharing the link keeps those selections. Remove an individual selection using its pill below the toolbar, or uncheck it in the filter menu. Use **Invoice date** to choose **is between** (a start and end day), **is on or after**, or **is on or before** a day, picking the days on one calendar (see [Pick a date range](/administration/basics/pick-a-date-range.md)). Both dates are inclusive and use your business's timezone. This filters the invoice date shown on the document, rather than its creation date or payment due date. Invoices without an invoice date are excluded while a date boundary is set. The range combines with the other table filters and applies to bulk selections across all pages. Remove its pill to clear it. The aging summary continues to follow the customer and property filters. Use Aging to show only outstanding invoices in a given past-due bucket (Current, 1-30, 31-60, 61-90, or 90+ days); the Aging filter appears on the Non-Void, Open, and Overdue tabs (it's hidden for Draft, Unpaid, Partially Paid, Paid, Void, Uncollectible, and Payment Processing). Use Source to show only Manual invoices or only those generated from a Subscription; the Source option appears only if you have permission to read invoices. If invoice filters are missing but you need them, contact your business's administrator to review your role. Use **Task folder** to show only invoices with a task still open (not in a Done status) in the folders you pick, such as **Invoices → Overdue** or a folder your business added like **Invoices → Collections**. The list offers the Invoices folders and every folder your business has added, so an invoice task you moved into another folder is still found. Only tasks you can open in Tasks count. These filters combine with whichever status tab is selected. Click a table column heading to sort the results. ## Related guides * [Filter invoices by status](/revenue/invoices/filter-invoices-by-status.md) * [Read the aging report on the Invoices page](/revenue/invoices/read-the-aging-report-on-the-invoices-page.md) * [See and browse all your invoices](/revenue/invoices/see-and-browse-all-your-invoices.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) --- # 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/filter-invoices-by-aging-or-source.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.