Manual purchase-order management becomes difficult when the team loses track of which version was requested, accepted, received or billed. A spreadsheet can work with clear ownership and disciplined updates. The warning sign is recurring re-entry or unresolved differences, not a particular number of suppliers or POs.
Use the failure patterns below to find where a shared living purchase order would help, and where a clearer manual process may be sufficient.
Approval is detached from the request
If approval lives in an email while the draft changes elsewhere, the buyer may send something the approver never reviewed. Give the request a reference, show the proposed items and amount, record the decision, and define which later changes require another review.
LineNow keeps requisitions separate from supplier purchase orders. Requests go directly to the owner or Procurement for item review, sourcing, and ordering. Business-unit access determines who can handle the request.
Supplier status is inferred from sending
An email transmission proves neither acknowledgment nor commercial acceptance. A message saying “shipping Thursday” is a planned ship date, not evidence of dispatch.
Keep the source message, order reference, promised quantity and date together. Assign an owner and follow-up deadline when confirmation is missing. If a portal or phone order is manual, record its reference so another buyer does not place it again.
LineNow can parse messages on configured supported channels into reviewable updates. It cannot know about an inaccessible personal chat or an unrecorded phone conversation.
A supplier change is mistaken for physical stock
A supplier confirming eight cases changes expected incoming stock. It does not put eight cases on the shelf. Receiving must record actual accepted quantities and preserve shortages, rejections and remaining balances.
An illustrative failure, assuming no consumption during the example:
| Event | Recorded on-hand | Physical on-hand |
|---|---|---|
| Before delivery | 12 | 12 |
| 24 units arrive but receipt is not entered | 12 | 36 |
| Buyer reads the stale count | 12 | 36 |
| Receipt is finally entered | 36 | 36 |
The stale record understates stock by 24 and can lead to an unnecessary order. Updating the receipt promptly fixes that gap. Counting waste, transfers, returns and sales still matters; automation cannot observe every physical movement.
The PO is edited to make the invoice match
Suppose the original order is 24 cases at $14.50, or $348. The supplier proposes 22 cases at $14.71 plus $42 freight. The revised total is 22 × 14.71 + 42 = $365.62, if the buyer accepts those terms.
Preserve both versions. If 22 cases arrive and the invoice agrees, finance has a clear basis for review. If only 20 arrive, an invoice for 22 needs investigation; changing the receipt or PO to match the bill would hide the discrepancy.
Upstream reconciliation gives the buyer, receiver and supplier a chance to resolve differences earlier. It complements final invoice controls rather than removing them.
Accounting receives incomplete evidence
Finance may need the original commitment, accepted price changes, receipts, invoice, credits and deposits at different times. “Wait until the whole PO is received” is not a universal posting policy.
Agree what each integration sends, who reviews it and how failures are recovered. A procurement purchase total is not automatically current-period COGS. Financial records, tax treatment, coding and payment authorization remain accounting responsibilities.
Adding automation without fixing ownership
Software can carry the wrong SKU, quantity or supplier mapping through several steps faster. Before connecting systems, decide:
- Which item and location records are authoritative.
- Who can create, change and send an order.
- Which system records the physical receipt.
- Who approves substitutions and commercial changes.
- Where finance reviews unresolved invoices.
- How a failed or duplicated handoff is detected and recovered.
A parallel pilot needs one real sender and receiver. The comparison spreadsheet is reference-only; otherwise the evaluation itself can create duplicate orders or stock.
Measure the handoff that hurts
Record time and exceptions for comparable orders: order preparation, approval waiting, supplier follow-up, receipt correction and invoice investigation. Do not multiply a generic data-entry error percentage across the workflow; these events are not necessarily independent and your baseline may differ.
The Whitmans customer account describes supplier purchasing and the customer’s experience of support and flexibility. Use it as a workflow example, then measure your own order sample.
A useful pilot shows fewer repeated entries and clearer unresolved work without removing necessary checks. The procurement time audit and ROI guide explain how to separate recovered capacity from cash savings.