> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/controlling/invoices.md). # Invoices Viewing invoices in equipme, downloading them as PDF and exporting invoice items. **Path:** sidebar → **"Controlling" → "Invoices"** {% hint style="info" %} This area only appears if the **billing module** is active for the company and your role is allowed to read invoices. Hosted customers contact their provider to have it enabled. {% endhint %} ## The invoice list Columns: "Invoice number", "Billing date", "Supplier", "Total cost", "One-time costs", "Recurring" and **"Invoice"** (PDF icon for downloading in the current language). ## The invoice details Clicking an invoice opens **"Invoice #*****number*****"** with date, reference and the totals of recurring and one-time costs. The **items table** shows for each item: "Instance ID", "Service name", "Type" ("Fee" or "Refund"), "Cost", "Billing interval", "Start date", "End date", "Location", employee, "Employee cost center" and "Group". With the export, you download the items as an Excel file, e.g. for allocating costs to cost centers. Clicking an item opens the service. ## Invoices by email With the **"Invoice"** notification (see [Email notifications](/dokumentation/settings/email-notifications.md)), invoices are automatically sent to the desired recipients, e.g. accounting. The billing address is derived from the cost center (see [Cost centers and billing addresses](/dokumentation/organization/cost-centers-and-billing-addresses.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://hub.equipme.io/dokumentation/controlling/invoices.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.