> 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/how-do-i/check-all-jobs-are-invoiced.md).

# Check all jobs are invoiced

To check that no jobs have missed being invoiced:

1. Check that the "To Process" and "Draft" tabs on the [Invoices](/tracking/invoices.md) page are clear and that the "Ready to invoice" tab on the [Jobs](/tracking/jobs-list.md) page is clear. This will catch all the jobs which have been closed off correctly (i.e. by clicking "Create Final Invoice"), or have not been closed off yet but have had their [job status](/eboard/calendar/job-status.md) updated to "Complete" via the eBoard [job status](/eboard/calendar/job-status.md).
2. Set your [eBoard](/eboard.md) calendar to the period you want (e.g. start date June 1st and 30 days), and check that any job you expect to be invoiced has a tick on the very left-hand side (the "C" column). The tick will display when a completed invoice is detected for that day. This will pick up any eBoard jobs that haven't been closed/invoiced. If a job has not been closed, but does have a complete (marked as invoiced) progress invoice for a given day, you will see a check mark.

Note that the above process only picks up scheduled eBoard jobs, and won't detect any un-invoiced TMP Only or Dry Hire jobs. To determine that these have been invoiced, you should check the "Dry hire" and "TMP only" tabs on the [Jobs](/tracking/jobs-list.md) page of the Tracking System. Any jobs on these tabs have not had their final invoice created. Once they do, they will move to the "Complete" tab.


---

# 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/how-do-i/check-all-jobs-are-invoiced.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.