# What purpose does the job field READY\_TO\_INVOICE serve?

**URL:** <https://community.servicem8.com/t/what-purpose-does-the-job-field-ready-to-invoice-serve/487>\
**Category:** API & SDK\
**Created:** [August 19, 2023, 4:33am UTC](https://community.servicem8.com/t/what-purpose-does-the-job-field-ready-to-invoice-serve/487 "2023-08-19T04:33:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![developer](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@developer](https://community.servicem8.com/u/developer)\
**Post date:** [August 19, 2023, 4:33am UTC](https://community.servicem8.com/t/what-purpose-does-the-job-field-ready-to-invoice-serve/487/1 "2023-08-19T04:33:34Z")

</div>

**Originally posted by Dan**

Hi Everyone,

I’m trying to pull together a list via API of jobs which are completed but not yet invoiced.

The trouble is choosing which field to filter my API call by

STATUS = “Completed” - returns too many positives  
INVOICE\_SENT = “false” - returns too many positives

I had the idea to filter by jobs READY\_TO\_INVOICE however by default the jobs keep a value of “1” even after they have been invoiced.

My next thought was perhaps once the jobs are invoiced to change READY\_TO\_INVOICE from “1” back to “0” so these jobs don’t reappear when I filter by READY\_TO\_INVOICE

Can anyone share any insight on whether this will have adverse effects on other things?