Decide which PO balances can be released without hiding an unbilled delivery or blocking a late invoice. Use a line-level close decision, named approvals and a before-and-after financial check.
The last invoice has been paid, yet the purchase order still shows money committed. Closing it may be the right action—but not until someone establishes whether the balance is unused scope, an outstanding delivery, or a real cost that has not been invoiced.
This purchase order closure checklist is for finance reviewers working with buyers, requesters and accounts payable. It covers ordinary goods and service orders, from closure request through verified release of the unused balance. It does not replace your purchasing system’s instructions, accounting policy or supplier agreement.
Separate three questions before closing a PO
A closure review should answer three different questions:
- Is the work finished? The requester confirms what was delivered, accepted, returned or cancelled, and whether anything else is expected.
- Is the financial position understood? AP identifies invoices, credits, payments and received-but-unbilled amounts. Finance determines the accounting treatment and what commitment, if any, is genuinely unused.
- What will this system action do? The buyer confirms the exact line or header action, its transaction restrictions and the supported recovery path.
A PO’s operational status, its budget reservation and its recorded liability are not interchangeable evidence. Closing an order is not, by itself, proof that no supplier amount remains payable or that the supplier has agreed to stop performance. This is the final control handoff after the broader procure-to-pay process, not another payment approval.
Do not assume “closed” means permanently blocked
For example, Oracle Fusion’s close-status guidance says that Closed for Receiving does not itself prevent further receipts, and Closed for Invoicing does not prevent matching an invoice. Its control-action matrix distinguishes those statuses from Finally Close, which blocks receiving and invoicing against the controlled entity.
Recovery also varies. NetSuite’s line-closing documentation describes reopening by clearing the Closed box, while Stanford’s Oracle procedure treats its Finally Close action as permanent. Neither is a universal instruction for your implementation. Record the behavior your own system owner has verified before authorizing the action.
Build one closure packet for each affected line
Start a review when the requester says performance is complete, unused scope is being cancelled, or a periodic open-order review flags a stale balance. Age is a reason to investigate, not sufficient authority to close. The controls below are recommended company practices; set review frequency, approval thresholds and retention rules under your own policy.
Capture these fields in the request:
- Entity, supplier, PO number, line/schedule, currency, requester and buyer.
- Approved order value and amendments; accepted quantity or service value; invoiced value and credits; payment status.
- Open delivery, unbilled receipt, disputed amount and unused scope, shown separately with their evidence references.
- Pending invoices, receipts, returns, credits and change orders, including items still in draft or approval queues.
- Supplier confirmation of remaining delivery and billing expectations, or an assigned exception when confirmation is missing.
- Proposed system action, reason, financial effect, approvers, executor and verification owner.
Use the same reporting cutoff and entity/currency filters for the supporting extracts. A requester saying “finished” is not a substitute for AP checking its intake queues. As an institutional example, MIT’s PO closeout guidance checks pending change orders, receipt documentation, invoice approval and whether future invoices are expected. Your local checklist should cover those facts without assuming MIT’s forms or permissions apply.
Use a close-or-hold decision matrix
Review at line level before deciding the header outcome. One finished line should not conceal another line’s outstanding work. The authorized buyer chooses the actual system action; this matrix identifies the decision evidence, not an ERP command.
| Finding | Owner and evidence | Decision and financial check |
|---|---|---|
| All expected goods/services accepted; invoices and credits resolved; unused balance remains | Requester confirms completion; AP supplies billing/payment check; finance explains residual | Approve eligible closure. Verify unused commitment release and confirm no unexplained liability adjustment. |
| Some scope will never be delivered | Buyer retains agreed cancellation/change evidence; requester identifies exact unused quantity/value | Cancel or close only the eligible unused portion under local rules. Keep accepted-but-unbilled amounts in accounting review. |
| Goods/services received, invoice missing or unposted | AP and receiving owner provide acceptance, supplier follow-up and invoice status | Hold final closure pending resolution. Controller assesses the unbilled obligation; do not release it merely to clear an open-order report. |
| Receipt, invoice or change order still processing | Buyer/AP identify the transaction, amount, owner and next completion date | Resolve the in-flight work, refresh reports and obtain approval again if the close amount or scope changes. |
| Return, price dispute, credit or payment exception remains | AP and buyer link the claim, return evidence, expected credit and settlement status | Keep an exception open. Confirm how the chosen action affects later credit/invoice processing before proceeding. |
| Requester departed or supplier response is missing | Department owner appoints a reviewer; buyer gathers alternative delivery/contract evidence | Do not treat silence as proof of completion. Escalate uncertainty to the policy-authorized decision maker. |
UAMS’s pre-closing procedure illustrates why draft/in-progress transactions and received-not-invoiced lines need explicit attention. Its restrictions are implementation-specific; the broader control lesson is to inspect those populations before making them harder to process.
Worked example: an $8,000 open balance is not all unused
This is an illustrative transaction, not a customer result. Assume a single-currency $20,000 service PO with no tax, fees or price differences. The company has accepted $15,000 of work. AP has posted and paid $12,000 of invoices. The supplier and buyer agree that the remaining $5,000 of unperformed scope will not proceed.
- $12,000: accepted, invoiced and paid; retain the matched records.
- $3,000: accepted but not yet invoiced; AP must chase the invoice and finance must assess its existing or required accounting treatment.
- $5,000: unperformed scope no longer required; the buyer documents the agreed reduction and the authorized system action.
The arithmetic is $20,000 − $12,000 = $8,000 not yet invoiced, but $8,000 = $3,000 unbilled work + $5,000 unused scope. It would be wrong to label all $8,000 a saving. These are a review bridge, not a prediction of your ERP’s encumbrance report: receipt-based and invoice-based configurations can display different balances.
The team first resolves the unused scope at the appropriate line level, retaining the $3,000 accepted-work evidence. Finance follows its AP accrual process without duplicating any liability already recorded by the system. The PO stays eligible for the expected invoice under verified local rules; final closure waits until that invoice and other required checks are resolved.
After the last invoice is processed, the reviewer checks the resulting PO status, the commitment report and the accounting support. The packet should explain where the $5,000 went and how the $3,000 was recognized and cleared—not merely attach a screenshot saying Closed.
Authorize, execute and verify as separate steps
Approve a specific action, not a vague cleanup
Use the state path Requested → Evidence complete → Approved → Executed → Financial effect verified → Closed. An unresolved item follows Exception → Assigned → Resolved → Re-reviewed. The requester confirms business completion; AP confirms financial transaction status; the authorized finance reviewer approves the financial assessment; the buyer or permitted operator executes. Separate preparation and review where practical.
Approval should identify the exact PO/lines, expected released amount, remaining liability or exception, and permissible action. Changed amounts, new invoices or altered scope return the case for review. Supplier cancellation or contract changes remain a separate commercial step; a system status is not evidence that this communication happened.
Prove the result with fresh reports
- Retain the execution reference, user, timestamp and resulting line/header status.
- Rerun the relevant open-commitment report after the system’s normal update cycle. Compare the affected lines with the approved before-state.
- Inspect related requisition or budget balances where your configuration can leave a separate reservation. Assign any unexpected residual rather than claiming the entire commitment cleared.
- Confirm that outstanding AP, receipt accruals and credit claims still have a valid record and owner. Any posting or correction requires the normal accounting approval.
- Have the reviewer sign off the amount bridge and exceptions. Archive the request, source reports, supplier correspondence and decision together.
If the expected release does not appear, keep the case at Executed—verification exception. Ask the purchasing/finance system owner to investigate the report timing or configuration; do not run another close action or post a balancing journal just to force the numbers to agree.
Keep a recovery path for late activity
A late invoice should reopen the review case, not disappear because the PO is closed. AP checks whether it is a duplicate, a valid previously unbilled delivery, or a new/disputed charge. Link the invoice to the original PO and closure packet, then have the buyer confirm the system-supported route.
If reopening is supported, obtain the required authorization before changing status and preserve the original decision history. If the action was permanent, use the documented purchasing exception process rather than assuming a new PO or non-PO payment is automatically acceptable. Recheck budget authority, accounting treatment and duplicate-payment risk before processing. A late credit or return needs the same traceable handoff.
Where Workhint fits
Workhint can support the coordination layer around the closure request. Its Workflow Engine supports routing approvals to defined roles and requiring details or files before work progresses. For this use case, the team could configure a request with PO references, requester confirmation, AP evidence and finance review.
The Workflow Automation Software solution describes structured forms, review stages, assigned approvers and tracking of owners and next actions. Those elements fit the cross-team handoff from proposed closure to verified completion. Validate the exact fields, access and exception paths against your process before implementation.
The purchasing system remains responsible for the PO action, and the accounting system remains the financial record. This proposed workflow does not establish that Workhint natively imports your PO data, releases encumbrances, posts journals or closes an order in your ERP.
Frequently asked questions
Should finance close every old PO at year-end?
No. Review old orders, but determine whether delivery, invoicing or credits remain before choosing an action. Age or a reporting deadline is not evidence that an obligation disappeared. Follow your own rollover and close policies.
Does paying the final invoice automatically release the balance?
Not necessarily. Check the order’s remaining lines and your system’s commitment report. A final invoice can leave unused ordered value or another reservation requiring a separate authorized action.
Can a PO close while there is received-but-unbilled work?
Do not assume it is safe. Confirm the effect of the proposed action on later invoicing, preserve the acceptance evidence and have finance assess the liability. Under this checklist, unresolved expected invoices block final closure unless an authorized, documented exception establishes a safe processing and accounting route.
Who signs off completion?
The designated reviewer confirms both the authorized system outcome and its financial effect. A buyer’s execution confirmation alone does not prove the commitment release or resolve an accounting exception.
Leave a Reply