Purchase Orders, Requisitions & Receiving
The full procurement path in one place — requesting, converting to a PO, approving, and receiving — plus the exact statuses and a few real footguns along the way.
On this page
The three stages, at a glance
Procurement moves through three separate record types, each in Purchasing in the sidebar: Requisitions (an internal request), Purchase Orders (the formal order sent to a vendor), and Receiving (a read-only ledger of what's actually arrived — there is no “+ New Receipt” button; every receipt starts from a PO).
A Requisition and the PO it produces are two separate records, and the new PO always starts at Requested. When you submit a PO made from an approved requisition, it is approved straight away if the requisition already covers it (see How approval actually works); otherwise it goes through the PO approval chain like any other PO.
Creating a Requisition
Go to Purchasing > Requisitions and click + New Requisition. Fields: Title (required), Vendor (optional unless your org's Required Fields settings make it mandatory), Notes, and a line-items table. Each line picks an item from the Products/Parts catalog — quantity, unit cost (pre-filled from the catalog using your org's costing method, editable), an optional Project (only offered on Stocked Material / Project Material lines — never on a Maintenance Part line), and a computed line total. Tax Rate, Shipping, and Discount apply to the whole requisition.
Save as Draft to keep working on it later, or Submit for Approval to route it to the first approver in your org's chain.
Requisition status
| Status | Meaning |
|---|---|
| Draft | Being built. Not visible to approvers yet. |
| Pending Approval | Submitted. Routed through the org's configured approval chain. |
| Approved | Chain resolved with no rejection. Can now be converted to a PO. |
| Rejected | An approver rejected it. Reset to Draft to fix and resubmit, or Close it. |
| Ordered | A PO has been created from it (see Converting, below). Goes back to Approved if every PO made from it is deleted or canceled. |
| Closed | Done — set with Close Requisition. No more POs can be made from it and its lines are locked. |
From Rejected, click Reset to Draft, make your changes, and submit again. A resubmitted requisition starts the whole approval chain over: approvals given before the rejection don't carry over, so every step is asked again.
Close Requisition (shown on Approved, Ordered and Rejected requisitions) marks it finished: no more purchase orders can be made from it and its lines can't be edited. Purchase orders already made from it aren't affected.
Editing after creation
Converting to a Purchase Order
Open an Approved requisition and click Convert to Purchase Order. This opens the New PO form pre-filled with the requisition's vendor and line items — nothing is created until you actually submit that form. Submitting creates a brand-new, fully independent Purchase Order (its own PO number, starting at status Requested), and the requisition's status jumps straight to Ordered the instant the PO is created, not when the PO is later actually ordered or received.
If line items span multiple vendors, use Split by Vendor instead — it groups the requisition's lines by each item's catalog vendor and creates one PO per vendor group in one action.
If a split fails partway (say the first vendor's PO was created but the second wasn't), you can close the dialog and reopen it, then retry — it recognizes the POs already created for that requisition and only creates the missing ones instead of duplicating the first.
Its own line items are never modified by converting. If every PO made from a requisition is later deleted or canceled, the requisition goes back to Approved (with the same approved total) so you can make a new PO from it; reopening one of those POs with Reset to Requested moves the requisition back to Ordered. A Closed requisition is never reopened this way.
Purchase Order fields
A PO can be created directly (Purchasing > Purchase Orders > + New Purchase Order) or arrive pre-filled from a requisition conversion — either way it's the same form and starts at the same status. Fields: Vendor, PO Date (defaults today), Payment Type (Check / ACH / Credit Card), Invoice Number, Notes, and line items — same pattern as a requisition, plus one addition: each line has a Taxable toggle (on by default), letting you exempt a specific line — a delivery fee, for example — from sales tax. Requisition lines don't have this toggle; if a requisition is converted, every resulting PO line defaults to taxable regardless.
Discount reduces tax. When this box is ticked the discount comes off before tax, spread across the taxable and non-taxable lines by their share of the subtotal — only the taxable lines' share lowers the amount taxed. Example: a $1,000 PO with $800 of taxable lines and a $100 discount taxes $800 − $80 = $720. With the box unticked, the full taxable amount is taxed and the discount comes off the total afterward. The PO screen, the PDF and the saved totals all use this same rule.
The New Purchase Order form also shows a read-only Part # column beside each line's item, filled in from the catalog entry (a dash if it has none), so you can check the part number without leaving the form. The New PO and Receive Goods dialogs are wider than they used to be so every column fits.
Purchase Order status
| Status | Meaning |
|---|---|
| Requested | Just created. Not yet submitted for approval. |
| Pending | Submitted. Routed through the approval chain. |
| Approved | Chain resolved with no rejection. Ready to mark as ordered. |
| Rejected | An approver rejected it. |
| Ordered | Manually flagged as sent to the vendor — a status label only, no email or PDF is sent. |
| Partially Fulfilled | At least one line item has been received, but not all of it yet. |
| Completed | Fully received — or forced complete anyway (see the Mark Complete callout). |
| Canceled | Called off with Cancel PO before anything was received. Reset to Requested reopens it. |
How approval actually works
- Requisitions and POs each go through your org's configured Approval Flow independently — see the Approval Flows guide for how a chain is built. If no flow is configured for that record type (or the flow has zero steps), the record auto-approves immediately.
- A step with no specific person assigned resolves to every user holding the required role — any one of them approving satisfies that step for everyone else at it. If nobody in the org holds that role, it silently falls back to the first admin as a catch-all.
- An admin submitting their own requisition/PO automatically clears any manager-level step in the chain (the step still shows in history, just marked skipped) — admins outrank managers in this flow.
- Managers can stand in for another approver on a step, but only on non-admin steps. A step whose Required Role is admin can only be decided by an admin (or the admin it was assigned to) — a manager doesn't see the override option there, and the server rejects it if attempted.
- Only the approver whose turn it currently is can act — trying to approve or reject out of turn is rejected server-side with “It's not your turn to approve this yet — an earlier step is still pending.”
- A PO made from an approved requisition approves itself when the requisition covers it. On submit, the PO is approved without a chain when every line is a line of that requisition (same catalog item and project, at a unit cost no higher than requested), the quantities across all open POs made from the requisition stay within the requisition's, and those POs together don't cost more than the requisition's approved total. Anything else — an extra item, a higher price, more than was requested — goes through the normal PO approval chain.
- Each approval covers what the approver saw. If the lines or vendor change while a record is still going through its chain, the last approval doesn't finish it: earlier approvals that no longer match are asked again, and if the total now crosses a higher threshold, that step's approver is added. The record stays Pending until the rebuilt chain is done.
- A rejection restarts the chain. When a rejected record is submitted again, every step is asked again — approvals from before the rejection don't carry over.
- Approving a record you submitted yourself is allowed when you hold the step's role.
- Approval thresholds use the total the system calculates. A requisition's or PO's subtotal, sales tax and grand total are always worked out from its line items, tax rate, shipping and discount — whenever a line or one of those fields changes, and again at the moment it's submitted. A total typed or sent from anywhere else is replaced, so a record can't slip under a threshold its lines are actually over.
Receiving
There's no standalone “New Receipt” screen — Receiving is a read-only ledger you search by receipt #, vendor, or PO #. Every receipt starts from a PO: open one with status Ordered or Partially Fulfilled and click Send to Receiving.
Each line pre-fills with whatever's still outstanding — ordered minus everything already received across any earlier partial receipts on the same PO — so partial receiving across multiple deliveries works correctly out of the box. Maintenance Part quantities round to whole units; material quantities allow two decimal places. Tax and any PO-level discount are prorated onto each partial receipt proportionally, so a discount isn't double-counted across multiple receipts. You must pick a Received By person before recording.
A PO line can never be received past what was ordered in total. Clicking Record twice, or receiving the same PO in two tabs, is refused with “… would be received in total but only … was ordered — check for a duplicate submission” instead of creating a second receipt. A Maintenance Part with a Parts record is always received into that part (the product's count follows it); the system refuses to add the units to the product alone.
Recording a receipt does two things, in order: first, inventory updates — quantity on hand increases and a new cost layer is appended (see the Inventory Costing Methods guide for how that cost is computed) — and only after that succeeds is the receipt itself saved. If a line can't be matched to a catalog product, the whole receipt is rejected with an error and never saved.
If a Work Order already used some of that part before the stock was received (so the Work Order could only take what was on hand, and the Parts list shows a “used before received” badge), recording the receipt settles it: those units come off the incoming quantity automatically. A receipt of 3 for a part that two Work Orders had already used 3 of leaves quantity on hand at 0, not 3.
The status changes the moment the receipt is recorded — you don't have to click Done or keep the page open. Once every line on a PO is fully received, its status automatically moves to Completed; if only some lines are fully received, it moves to Partially Fulfilled instead. You can correct a receipt you already recorded by editing its quantities — the system applies the difference to inventory rather than re-receiving from scratch, so lowering a quantity by mistake correctly pulls the stock back down too. The PO's status is worked out from its receipts, so it follows a correction as well: lowering a receipt on a Completed PO moves it back to Partially Fulfilled (or to Ordered if nothing is left received). That includes a PO you marked complete by hand — any later receipt change re-checks it against what was received.
The “Mark Complete Anyway” override
On a PO that hasn't been submitted, Submit for Approval sits in the same button row as Cancel PO. Cancel PO is for calling off an order before anything arrives. It shows on Requested, Pending, Approved, Ordered and Rejected POs that have nothing received yet, and asks you to confirm. Once any goods are received the PO can't be canceled — use Mark Complete to close it short. A canceled PO can be reopened with Reset to Requested.
Spend and repair cost reports
Reports in the Equipt sidebar opens a tabbed page. Two tabs cover money spent:
- Parts Spend — spend on catalog items categorized as maintenance parts, with a date range picker (Last 6 months, Last 12 months, or All time; default is 12 months). Canceled and rejected POs are excluded, and each PO is placed in a month by its PO Date. The cards show Total Parts Spend, Avg Parts PO Value, Total POs, and Open POs, followed by a monthly trend and the top 5 vendors. The four cards are clickable — each opens the list of line items or POs behind that number (for Avg Parts PO Value, the parts-only amounts it's averaged from).
- Repair Cost — what maintenance actually cost, taken from the lines on each work order's Costs tab: Parts, Labor, and Vendors / Subs, with the same date range picker, a Preventive vs. Reactive split, a monthly breakdown, and the top 5 assets by repair spend. Total Repair Spend, Parts, Labor, and Vendors / Subs are clickable and open the individual cost lines behind them.
The Equipt Dashboard's Parts Spend MTD card also shows a smaller repairs MTD figure beneath it — the same repair-cost definition as the Repair Cost report, for the current month.
Gotchas
- No GL code field exists on Requisition or PO line items today — if you're looking for GL coding on a purchasing line, it isn't there yet.
- PO/Requisition/Receipt numbers aren't strictly sequential. They're generated client-side from a timestamp, not a gapless counter — fine for day-to-day use, but don't treat them as audit-grade sequential IDs.
- Requisitions have no per-line taxable flag; POs do. If you need a tax-exempt line, that only becomes possible once it's a PO line.
- A discount can't make a total negative. A discount larger than the lines' subtotal is capped at the subtotal, so the most it can do is bring the lines to $0 — tax on any taxable amount left and shipping still apply.