Purchase Order Management: A Filled Ledger for Commitments, Acceptance, and Payments
Published:
Last Updated:
Category: Marketing Budget & KPI, Forecasting & Management Accounting
Authors: Shusaku Yosa
A purchase order record should answer three practical questions: what work has already been committed, which check is holding up processing, and how much budget remains available for new orders? Tracking payments alone cannot answer them. There is no universal vendor-count threshold at which a process fails. Even a small order can become difficult to resolve when its scope, approval, or acceptance conditions are unclear. This guide uses outsourced production work to build a ledger that connects ordering, acceptance, invoicing, and payment.
What a purchase order ledger should help you decide
Start with four kinds of unresolved work: an unapproved start, an unrecorded change, acceptance waiting for review, and an invoice discrepancy. A single “in progress” status hides these differences. Record the pending action and the person who must make the next decision.
Unresolved item | Record to check | Next decision owner |
|---|---|---|
Work started before approval | Request, quote version, approval status | Order approver |
Change missing from the order | Change ID, amount, revised date | Buyer and vendor contacts |
Acceptance pending | Delivered version, criteria, review date | Acceptance reviewer |
Invoice discrepancy | Order, acceptance scope, invoice ID | Payment reviewer |
Use one purchase order ID across the quote, approval, change record, delivery, and invoice references. Several projects with the same vendor still need distinguishable records. The ledger is an index connecting evidence and actions, not a replacement for the underlying documents. Here, purchase order management means the buyer’s handling of approved orders. Vendor selection and sourcing policy happen earlier; sales order management concerns the seller. A management balance also differs from accounting expense recognition.
Agree scope, amount, approval, and acceptance conditions
At ordering, record the deliverable, included work, exclusions, amount, tax basis, delivery date, acceptance method, payment terms, and approver. For a landing page, “one complete website” is insufficient. Specify pages, supplied copy, revision arrangements, file formats, and the agreed form-testing scope. Word count or revision limits alone may not define adequate quality.
Acceptance means comparing the delivered work with agreed conditions. Evidence might be an approved copy version, design files, or test results for the specified environments. If corrections are needed, identify the affected item, the requested correction, and the evidence that will allow a second review to close.
Set approval routes using your organization’s authority rules. An urgent route can be shorter while still recording scope, an amount ceiling, an authorized decision, and a deadline for completing the paperwork. Splitting an engagement merely to avoid a threshold obscures the total commitment. Maintain a vendor reference with the formal name, contact, contract location, and payment terms. Important changes such as bank details require the organization’s verification procedure, rather than an immediate edit based solely on a message.
Read a filled ledger without double-counting amounts
The following two orders and all prices are fictional. Amounts are tax-exclusive JPY, cumulative at one reporting date. The approved budget is JPY 1,000,000; Order A’s JPY 50,000 change is approved. There are no advances or approved cancellations. These inputs are neither market prices nor a real client case.
Order / scope version | Initial amount | Approved change | Current order | Accepted | Invoiced | Paid | Next action |
|---|---|---|---|---|---|---|---|
PO-A / LP v2 | 300,000 | +50,000 | 350,000 | 250,000 | 200,000 | 150,000 | Check evidence for remaining 100,000 / Sato |
PO-B / articles v1 | 200,000 | 0 | 200,000 | 0 | 0 | 0 | Confirm delivery date / Suzuki |
Current committed amount = 300,000 + 50,000 + 200,000 = JPY 550,000. Ordered but unaccepted = 550,000 − 250,000 = JPY 300,000. Accepted but unpaid = 250,000 − 150,000 = JPY 100,000. Available for new orders = 1,000,000 − 550,000 = JPY 450,000.
The accepted JPY 250,000 and paid JPY 150,000 are stages within the JPY 550,000 already committed. Subtracting all three amounts from the budget double-counts the same work. Subtracting only payments misses commitments still outstanding. The accepted-but-unpaid JPY 100,000 comprises JPY 50,000 not yet invoiced and JPY 50,000 invoiced but unpaid. Use that distinction when investigating timing. Advances, foreign currencies, invoice-first arrangements, and cross-period contracts need separately defined rules.
Record changes, partial acceptance, and cancellations
Connect each change ID to the original order and record its reason, affected scope, amount, revised date, approver, and approval date. Replacing JPY 300,000 with JPY 350,000 without history loses the explanation for the increase. Keep both the current approved version and its history available.
For partial acceptance, identify the deliverables, quantities, or service period accepted. If JPY 250,000 of Order A has been accepted, the remaining JPY 100,000 must also correspond to identifiable work. Do not allocate money first and leave the work undefined. Separate undelivered work from delivered work awaiting correction.
A cancellation is not simply an instruction to set an order to zero. Confirm the cancellable portion, completed work, fees, and expected invoices with the vendor, then record the approved reduction. Track any refund separately if money has already been paid. A spreadsheet formula does not settle contractual obligations or determine accounting treatment.
Resolve order, acceptance, and invoice discrepancies
Situation | Evidence | Next action | Decision owner |
|---|---|---|---|
Extra charge appears only on the invoice | Change request and approved quote version | Confirm difference and treatment of unapproved scope | Order approver |
Only part of the work was delivered | Criteria, delivered version, acceptance result | Record partial acceptance and outstanding scope | Acceptance reviewer |
Same invoice number received again | Vendor, invoice ID, payment history | Distinguish resend, correction, and duplicate | Payment approver |
For a reference on the control, Microsoft’s explanation of three-way matching describes comparing order, receipt, and invoice quantities or prices. Goods receipt is not identical to acceptance of creative services; service orders need the evidence agreed for the deliverable or service period.
Matching is one way to identify discrepancies, not a guarantee against every duplicate, overpayment, or unauthorized action. Check invoice-number duplication, due dates, corrected documents, exception approvals, and sensitive supplier-data changes separately. When a discrepancy appears, assign an owner and response date, and handle its effect on the agreed payment terms rather than leaving it indefinitely unresolved.
Review outstanding commitments and hand off actions
At each monthly review, use the same reporting date for budget, current orders, cumulative acceptance, invoices, and payments. An old unaccepted commitment might reflect late delivery, a buyer review delay, or a long service period. Age alone does not establish vendor fault. Compare the agreed plan with the actual next action.
A handover should include the next owner, date, unresolved amount, latest approved version, and payment-term reference for every open order. Distinguish the person entering data from the person accepting work or approving payment. Show unapproved requests separately as potential changes; do not silently treat them as approved commitments.
Review the process when change history cannot be reconstructed, payment checks stall, or balances cannot be reproduced. These observable problems are more useful than a fixed number of vendors. Apply the ledger to several recent orders first and remove fields that do not support an actual decision.
For the next step, use How to Write an RFP: A Filled Example with Mandatory Criteria and a Scoring Sheet; Vendor Management: A Practical Review of Decisions, Quality, and Delivery; Compare Web and Advertising Estimates: Effort, Exclusions, and a Three-Year Cost Example.
