Finance Index
How do I close a purchase order - and when should a PO be closed vs left open?
Reference guide to closing purchase orders, including request intake, purchasing controls, approval routing, vendor coordination, and finance visibility.
Close a PO when its business is finished: fully received and fully invoiced, or partially fulfilled with no further deliveries expected. Closing releases any remaining committed budget and signals AP that new invoices against it are exceptions. Leave POs open only while genuinely awaiting goods or invoices - an open PO is a claim on budget and an open door for invoices, so stale ones distort both.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Close a purchase order | Close a PO when its business is finished: fully received and fully invoiced, or partially fulfilled with no further deliveries expected. | Keeps spend controlled before the commitment is made. |
| ERP alignment | Run a one-time triage, then install a cadence. | Keeps accounting records aligned with the ERP. |
| Related terms | Fully receiving is an operational fact (everything ordered arrived); closing is the administrative end of the PO's life (no further activity expected, commitment released); cancelling voids unfulfilled quantities before delivery. | Keeps spend controlled before the commitment is made. |
| How often should we review | Monthly for the operational review (anything past expected delivery, anything fully received but uninvoiced), with a deeper quarterly pass tied to accrual review. | Keeps spend controlled before the commitment is made. |
| Close a PO that was | Close the unfulfilled lines (releasing their commitment), confirm with the vendor that the balance is cancelled, and note the reason. | Keeps vendor records and payment decisions reliable. |
We have hundreds of stale open POs cluttering the ERP - how do I clean them up?
Run a one-time triage, then install a cadence. Triage: pull all open POs, age them, and sort into fully-received-awaiting-invoice (chase or accrue), partially-received-never-completing (close remaining lines), duplicates and abandoned orders (cancel), and legitimately open (keep). Get buyer or requester confirmation where ownership is unclear, document closure reasons, and watch the committed-spend number drop to something real. Then prevent recurrence: auto-close on final match where your system supports it, and a monthly open-PO review with aging thresholds that force a decision on anything past its expected life.
What is the difference between closing, cancelling, and fully receiving a PO?
Fully receiving is an operational fact (everything ordered arrived); closing is the administrative end of the PO's life (no further activity expected, commitment released); cancelling voids unfulfilled quantities before delivery. A PO can be fully received but still open awaiting the final invoice.
How often should we review open POs - what should the cadence look like?
Monthly for the operational review (anything past expected delivery, anything fully received but uninvoiced), with a deeper quarterly pass tied to accrual review. The review should end in decisions - chase, accrue, close - not just awareness.
How do I close a PO that was partially received and will never be fulfilled?
Close the unfulfilled lines (releasing their commitment), confirm with the vendor that the balance is cancelled, and note the reason. The received portion stays matched and payable; the phantom remainder stops haunting your committed-spend reports.
How do open POs affect accruals and year-end close - should all POs be closed at fiscal year end?
Don't blanket-close at year end - close the dead ones and accrue properly for the live ones (received-not-invoiced becomes GRNI; ordered-not-received is disclosure context, not an accrual). Mass year-end closure just destroys commitment visibility for orders that are genuinely in flight.
An invoice arrived against a closed PO - how do I handle it?
Treat it as an exception, not a match: verify the goods or services were actually received and the PO was closed in error vs the vendor billing improperly. If legitimate, reopen or document the override with approval; if not, dispute it. Either way the closed status did its job - it surfaced the anomaly.
How do I automatically close POs after final invoice match?
Enable auto-close where the system supports it, triggered when invoiced quantity meets ordered (or received) quantity within tolerance. Keep a human in the loop for blanket POs and partial-delivery patterns where "final" is ambiguous.
How do I report on PO aging - how long POs stay open before receipt and invoice?
Track two intervals per PO: issue-to-receipt and receipt-to-invoice, then distribute by vendor and category. Aging outliers point to specific fixes - late vendors, missing receipts, or invoices stuck in someone's inbox - which is the point of the report.
How do I handle PO rollover at fiscal year end for multi-year projects?
Follow your accounting policy: either carry the open PO forward with its remaining commitment re-encumbered against the new year's budget, or close and reissue for the remaining balance. Pick one treatment, document it, and apply it consistently - auditors care about consistency more than which method.
Stampli perspective
Stampli tracks remaining availability on every PO line as invoices match against it, so it's always visible what's been consumed, what's still open, and which POs are candidates to close. Receiving lines can be marked closed or "won't be received," and the full lifecycle - statuses, revisions, receipts, matches - lives in one record, which makes open-PO review a filter on live data instead of a quarterly spreadsheet hunt.