# Purchase orders

> Order from vendors, itemize with line items, charge the cost to a project or work order, link related records, and receive parts into stock.

Source: https://app.assetlab.ca/docs/cmms/purchase-orders

A purchase order records what you've ordered from a vendor, what it costs, and what has arrived. Open **Purchase Orders** in the sidebar to see every order in your organization, including the ones created from a project's Financial tab - they are the same records.

## The list

Switch between **List** and **Split** view at the right of the toolbar; the choice is remembered in this browser. Split view shows the orders on the left with their status and balance, and the selected order on the right: its line items, status, next-step buttons, balance, vendor contact and receipt history. You can issue, receive, close or cancel from there without opening the order, and **Open** goes to the full page. Small screens always show the list.

Each row shows the PO number, vendor, what it's charged to, status, expected date and amount. Search by number, vendor or description, filter by status, and read the committed total for what's showing. Click a row to open it, or **New purchase order** to start one. New orders get the next number after your highest existing one, keeping your own prefix and padding (`PO-0041` is followed by `PO-0042`); you can type over it.

## Charged to - where the cost lands

A purchase order is charged to **one project, one work order, or both** (a work order that belongs to the project). Once the order is issued, its amount counts toward that project's or work order's committed cost - see [Budgets & financials](/docs/projects/budgets-and-financials). Draft and cancelled orders don't count. Charging to a project requires [Projects](/docs/projects) on your plan.

## The order page

A new or saved order opens as two columns. The left holds what you edit: **Details**, **Line items**, **Related records** (what it's charged to and what it's linked to) and **Notes**, then **Invoices** once it is saved. The right stays in view as you scroll: the status and next-step buttons, the balance, the vendor's contact details, the expected date (in red, marked overdue, once it passes on an order still waiting for delivery) and the receipt history. On a new order it shows the running total with **Create and issue** and **Save as draft**. On small screens the summary sits above the form.

## Status and next steps

An order moves through **Draft → Issued → Partially received → Received → Closed**, and can be **Cancelled**. You don't pick the status from a list: a saved order shows its status with a line saying what it means, and a **Next step** bar with the buttons that make sense now.

| Status | Buttons |
|---|---|
| Draft | **Issue**, **Cancel order** |
| Issued, Partially received | **Receive items** (or **Mark received** for an order without line items), **Close**, and **Cancel order** while nothing has arrived |
| Received | **Close** |
| Closed, Cancelled | **Reopen** - a closed order reopens as its receipts say, a cancelled one as a draft |

Each button saves any other edits on the page at the same time. **Issue** fills in today's issued date if it's empty. On a new order, **Save as draft** and **Create and issue** do the same at creation. Draft and cancelled orders don't count toward committed cost.

## Line items

Line items are a table: an optional **part** from [Parts inventory](/docs/cmms/parts-inventory), a description, quantity, unit cost and line total, one row per thing you're ordering. The part picker shows each part's stock, with parts running low listed first under **Low stock**, then the chosen vendor's parts. Above the table, a **low stock** strip lists parts below half their desired stock that aren't on the order yet - only the chosen vendor's once one is picked. Click a part to add it at the quantity that brings it back to its desired stock after what's already on order, or **Add all** for every one of the vendor's. Picking a part on an order with no vendor yet fills in the part's supplier as the vendor. Picking a part fills in its name and its cost if you haven't entered them. Once an order has lines, **its amount is the sum of its lines** and updates as you edit them. An order without lines keeps the amount you type.

Lines for a part are counted in whole units, because stock is.

## Receiving

**Receive items** opens a list of the order's lines with what was ordered, what has arrived so far, and a **Receive now** quantity that starts at everything still outstanding - for a full delivery, just confirm. For a partial delivery, change the quantities. For a line that names a part, **the received quantity is added to that part's stock** - receive 5 filters and the part's quantity goes up by 5. To correct a mistake, enter a negative number: it takes the difference back out of stock. Save any other edits first.

The status follows what you receive: something received makes the order **Partially received**, everything received makes it **Received**. Each line shows "Received 3 of 5" once anything has arrived.

When the order's unit cost for a part differs from the part's own cost, the dialog offers to update the part's cost to the new price; nothing changes unless you tick it.

Every receipt is recorded under **Receipt history**: the quantity, the line, when, and who received it (receipts made through the API show as API). Corrections appear as negative entries, so the history always adds up to what was received.

Two safeguards keep stock honest: a line with stock received can't be removed, and its part can't be changed. Correct its receipt back to 0 first.

## Invoices and the remaining balance

A saved order has an **Invoices** section that lines up what was ordered, what has arrived and what the vendor has billed:

- **Ordered** - the order's amount.
- **Received** - the value of what has arrived (received quantity times unit cost), shown when the order has line items.
- **Invoiced** - the pre-tax total of every invoice recorded against the order, except voided ones. Pending invoices count, because they still claim the order's money.
These figures sit in the summary on the right of the page.

- **Paid with this order** - work order actual costs and expenses paid with the order, shown once there is one (see below).
- **Remaining** - ordered minus invoiced minus paid with this order. If spending passes the order's amount, the balance turns red and says by how much.

**Record invoice** opens the invoice form already linked to the order, with its vendor and work order filled in. An invoice recorded here is charged where the order is charged, so it lands in that project's or work order's actual cost once approved or paid. Invoices recorded from a project's [Financial tab](/docs/projects/budgets-and-financials) and linked to the order appear here too. The **Remaining** column on the list shows every order's balance at a glance, which is how you track a blanket order that is billed over time.

## Paying a work order's costs with an order

When someone records a work order's actual cost (in Quick Close, or with **Assign** in the work order's Financial section), a **Paid with purchase order** field appears below the cost category. It only shows when there is an open order to pick, and only once a cost is entered.

- Orders that belong to the job are offered as one-tap buttons: orders charged to this work order or its project, and orders linked to this work order or to the PM schedule that generated it. Each shows the vendor and how much is left.
- **Choose another order** searches every other issued or partially received order.
- Under the field you see what the order has left after this cost. Going over shows a note, and the cost is still saved: nothing blocks a technician from finishing a job.

A work order's actual cost paid with an order counts against that order's remaining balance, and the order's page lists those work orders under **Paid with this order**. Labour and parts from stock never count: parts were already bought, often on another order. The cost still goes to the work order's assets as usual.

**Record each purchase once against an order** - as the work order's cost or as the vendor's invoice, not both - or the balance counts it twice. Removing a work order's cost also clears its purchase order.

## Paying an expense with an order

The **PO number** field on **Assign Cost** and **Add Expense** (see [Expenses & costs](/docs/cmms/expenses-and-costs)) searches open orders and shows each one's balance. A cost recorded there counts against the order and is listed under **Paid with this order**, linked to its asset. **New purchase order** in the same list creates an issued order with the cost's amount, for a purchase that had none; add its line items later here. A work order's own costs are counted once, through the work order.

## Sending the order to the vendor

**Download PDF** on a saved order produces a letter-size purchase order with your logo and organization name, the vendor's contact details, your project or work order reference, the line items and the total. The total names your currency code, since a vendor across the border cannot tell which dollar a bare "$" means. The PDF prints what is saved, so save any changes first.

## Linked records

Under **Linked records**, attach the order to any number of other work orders, PM schedules or projects - for example a blanket order that covers every work order a PM schedule generates. Links are for reference and finding things: **they don't add to anyone's committed cost**. Only the charged-to project or work order carries the cost.

## Who can use it

Purchase orders are a **Manager+** surface, the same as [Expenses](/docs/cmms/expenses-and-costs), and available on every plan. Infrastructure-only Managers see the vendors and parts of their own workspace in the pickers.

## Deleting

Deleting an order removes its lines and links. Stock already received stays in inventory, since the goods did arrive.

## Programmatic access

Purchase orders, their line items (`/v1/purchase-order-lines`) and their links (`/v1/purchase-order-links`) are available on the [REST API](/docs/reference/rest-api) and as [MCP tools](/docs/ai/tools-and-scopes), all under `purchase_orders:read/write`, so existing keys with that scope reach them. Setting a line's `quantity_received` through the API receives stock exactly as the screen does. An update that sets a different amount on an order with line items is rejected with a 400, because the amount is the sum of the lines; so is deleting a received line.

To record which order paid for something, set `purchase_order_id` on a work order (`/v1/work-orders`), an expense (`/v1/asset-costs`) or an infrastructure cost (`/v1/infrastructure-asset-costs`), under those resources' own write scopes. It counts against the order's remaining balance just as picking the order on screen does, an order from another organization is refused, and `null` clears it. The free-text `po_number` on costs is unchanged.
