> 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/field-operations/inventory/purchase-order-statuses-billed-paid-and-void.md).

# Purchase order statuses and marking orders billed, paid, or void

A purchase order's status tells you where it is between "we're thinking about ordering this" and "it arrived and we paid for it". The status also decides what you're still allowed to change.

## The statuses

| Status                 | What it means                                                                                                                                                                      |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Draft**              | Created but not placed with the supplier. Fully editable. Doesn't count as incoming stock and can't be received against.                                                           |
| **Submitted**          | Placed with the supplier, either by emailing it or by marking it submitted yourself. Line items and costs are locked; the supplier can still be corrected. Counts toward Incoming. |
| **Partially Received** | Some of the ordered quantity has arrived. Set automatically as you receive.                                                                                                        |
| **Fully Received**     | Everything ordered has arrived. Set automatically as you receive.                                                                                                                  |
| **Fully Billed**       | The supplier has invoiced you for the order.                                                                                                                                       |
| **Paid**               | You've paid the supplier.                                                                                                                                                          |
| **Void**               | Cancelled. Terminal — nothing further happens to it.                                                                                                                               |

Receiving is what drives Partially Received and Fully Received; you never set those by hand.

Billing and payment don't have to wait for delivery. A supplier may bill you before the goods arrive, so you can mark an order Fully Billed or Paid at any point after it's Submitted.

## Mark an order fully billed

When the supplier's invoice arrives, open the purchase order and choose **Mark Fully Billed**. You can record the supplier's invoice or reference number, and attach the bill itself to the purchase order's files so it's stored alongside the order.

Marking an order Fully Billed doesn't stop deliveries. If stock is still outstanding you can keep receiving against it; the quantities update and the status stays Fully Billed.

## Mark an order paid

Choose **Mark Paid** once you've paid the supplier. You can record the date you paid and a payment reference, such as a cheque or transfer number.

Paid is the end of the normal lifecycle. A paid purchase order can't be voided or have its items, quantities, costs, or supplier changed, so mark it paid once the money side is genuinely settled. Outstanding deliveries can still be received against it — paying early doesn't stop the goods — and its notes, estimated delivery date, and attachments stay editable, so you can still file the paperwork against it afterwards.

Essential doesn't track supplier balances or payments beyond this — Fully Billed and Paid are marks you set to keep your team informed, not an accounts-payable ledger.

## Void an order

If an order is cancelled, duplicated, or was raised by mistake, open it and choose **Void**. You'll be asked for a reason, which is stored on the order so anyone looking at it later knows why it stopped.

Voiding is available from any status except Paid, and it's permanent — there's no way to bring a voided order back, so void one only when you're sure. A voided order stops counting toward Incoming and can't be received against.

Voiding is how you get rid of a purchase order. Purchase orders are never deleted, so the record and its history stay available.

> **Where to find it:** Open a purchase order under Inventory -> Purchase Orders. **Mark Fully Billed**, **Mark Paid**, and **Void** are on the purchase order's menu.

## Related guides

* [Creating and receiving purchase orders](/field-operations/inventory/creating-and-receiving-purchase-orders.md)
* [Emailing a purchase order to a supplier](/field-operations/inventory/emailing-a-purchase-order-to-a-supplier.md)
* [Inventory quantity terms: on-hand, reserved, available, incoming](/field-operations/inventory/inventory-quantity-terms-on-hand-reserved-available-incoming.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/field-operations/inventory/purchase-order-statuses-billed-paid-and-void.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.
