> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/tracking/invoices.md).

# Invoices

The Invoices page lists every invoice created in the [Tracking System](/tracking.md), grouped by where it is in your invoicing workflow. Access to this page, and to financial information, depends on your [access level](/getting-started/user-access-levels.md).

To open it, click **Invoices** in the Tracking navigation bar. Click any invoice to open it in [Beast Mode](/tracking/invoices/beast-mode.md).

## How invoicing works

1. **An invoice is created** for a job, either from the job's [details](/eboard/calendar/job-details.md) (progress or final invoice) or automatically when field staff submit tasks, if that's turned on in [System settings](/tracking/settings/system-settings.md).
2. **You check and adjust it in** [**Beast Mode**](/tracking/invoices/beast-mode.md)**:** labour, vehicle and equipment charges, one-off charges, discounts and rounding.
3. **You preview and export it** with [Preview export](/tracking/invoices/preview-export.md): choose how charges are grouped, check the account codes, then export to Xero, download a spreadsheet, or print.
4. **You mark it complete** with **Workflow** → **Save as complete**.

## Invoice tabs

| Tab            | What's in it                                                                                                                  |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **To process** | New invoices that haven't been worked on yet.                                                                                 |
| **Draft**      | Invoices saved with **Save as Draft** in Beast Mode. What "draft" means is up to you, e.g. adjusted and waiting for approval. |
| **Ready**      | Invoices that are ready to be exported.                                                                                       |
| **Complete**   | Invoices saved with **Workflow** → **Save as complete**, e.g. entered into your accounting system or sent to the client.      |
| **Deleted**    | Invoices deleted from Beast Mode.                                                                                             |

## Finding an invoice

Each row shows the **Job #**, **Invoice #**, **Client**, **Principal**, who to **Bill**, **P/O**, **Your Ref**, **Location**, **Job Type**, who it's **Assigned To**, the **Start** and **End** dates and the **Total**.

* Filter by **Job Type** (Dates Confirmed, Dry Hire, TMP Only, Misc, Dates Not Confirmed or Quote Only) or by **Assigned To** (anyone, unassigned, or a staff member) using the drop-downs in the column headings.
* Use the page numbers at the bottom to move through long lists.

## Related guides

* [Export an invoice](/how-do-i/export-an-invoice.md)
* [Check all jobs are invoiced](/how-do-i/check-all-jobs-are-invoiced.md)
* [eBoard and Tracking notes](/eboard/calendar/eboard-and-tracking-notes.md): the notes invoicing staff see in Beast Mode


---

# 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://wiki.roaddirect.co.nz/tracking/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.