Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
A purchase order documents authorized intent; it is not a posted expense or vendor liability. Confirm current product and plan support, approve the request before issue, use controlled vendor and item records, acknowledge receipt separately, convert the accepted quantity and value to a bill or expense once, route quantity and price differences, and close only after remaining commitments are fulfilled or formally cancelled.
Best for: purchasing, operations, and finance teams using purchase orders before vendor bills
What this guide covers—and what it does not
The page owns one search intent: operating a controlled purchase-order workflow in QuickBooks. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This page owns purchase intent, authorization, receipt matching, bill conversion, open commitments, and PO closeout.
- The accounts-payable guide owns invoice approval, vendor credits, payment, and AP reconciliation.
- QuickBooks purchase orders do not by themselves enforce requisition, budget, receiving, or three-way approval segregation.
Evidence-first workflow
Move a purchase from request to closed commitment
Keep authorization, receipt, obligation, and payment as distinct evidence even when the product links them.
- 1
Request
Document business need, item or service, quantity, budget, project, timing, and proposed vendor.
Evidence: A responsible owner and approved requirement exist.
- 2
Approve
Apply spending authority, vendor, price, terms, conflict, tax, and change controls before issue.
Evidence: Approval predates the commitment.
- 3
Issue
Create and send one numbered PO using controlled vendor, item, account, class, location, and project data.
Evidence: Vendor acknowledgment agrees with the approved order.
- 4
Receive and bill
Record what was actually received and convert only supported quantities and value to the obligation.
Evidence: PO, receipt, invoice, and exception agree.
- 5
Close
Resolve partials, returns, price differences, credits, cancellations, and stale balances.
Evidence: No open quantity or commitment remains without an owner.
Decision control
Choose from evidence, not a feature list
Use the same four gates for operating a controlled purchase-order workflow in QuickBooks: define the job, surface constraints, choose the smallest workable option, then verify the records.
Decide how to process the order
The vendor document and receipt status determine whether to leave the PO open, create a bill, record an expense, or route an exception.
| Your situation | Direction | Why |
|---|---|---|
| PO approved but nothing received | Leave as an open commitment | No liability should be created merely from the purchase intent unless the accounting policy requires a separate accrual. |
| Partial quantity received and invoiced | Convert only the supported portion | The unreceived balance should remain visible or be formally changed. |
| Invoice price or quantity differs | Route a documented exception | Editing the PO to match the invoice can erase the evidence of what was authorized. |
| Immediate card purchase with no prior PO requirement | Use the approved expense/card workflow | Creating a retrospective PO adds form without restoring prior authorization. |
Configure purchasing roles and master data
Confirm the exact plan or Desktop edition supports the required purchase-order behavior. Define who may request, approve, create, change, receive, convert, cancel, and close. Establish thresholds and required independent approval for vendor-bank, price, quantity, or scope changes.
Govern vendor identities, remit-to information, items, units, purchase accounts, tax, class, location, customer or project, billable status, ship-to locations, terms, and custom fields. A PO built on duplicate or incorrect master data will propagate the error into receiving and AP.
Issue one approved order and preserve changes
Use a unique PO number and attach or reference the approved request, quote, contract, delivery terms, and budget. Send through an approved vendor channel and retain acknowledgment. Do not treat a draft saved in QuickBooks as proof that the vendor received or accepted it.
When scope, price, quantity, delivery, or vendor changes, preserve the original authorization and record the change approval. Avoid silently overwriting the PO after the vendor invoice arrives.
Match approval, receipt, and invoice
Document actual receipt of goods or completion of services independently from the invoice where practical. Compare vendor, PO, item, quantity, price, tax, freight, terms, and project. Convert the supported portion to a bill or expense once and search for an existing transaction before saving.
Route missing receipt, overreceipt, short shipment, damaged goods, price variance, duplicate invoice, split invoice, and unapproved substitution to named owners. A forced match transfers an unresolved operational issue into the ledger.
Review open purchase orders and close deliberately
Review aging open POs by vendor, requester, expected date, project, and amount. Confirm whether the balance is committed, backordered, disputed, cancelled, already billed outside the PO, or simply stale.
Close or change the remaining balance only with evidence. Reconcile material commitments to cash planning, project forecasts, inventory expectations, and period-end accrual decisions. Retain the final PO, receipts, invoices, credits, approvals, and closure reason.
Completion checklist
Do not call the decision or setup complete until someone independent of the initial change can verify these items.
Frequently asked questions
Does a QuickBooks purchase order affect the general ledger?
A purchase order normally records intent rather than a posted expense or liability. The bill, expense, receipt, or approved accrual creates the accounting effect.
Can I convert part of a purchase order to a bill?
Supported products allow linked workflows, but confirm current behavior and convert only quantities and values supported by receipt and vendor documentation.
Should I edit the PO when the invoice price differs?
Preserve what was originally authorized and route the difference for approval. A controlled change may update the order, but it should not erase the variance evidence.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.