Streamline Purchase Order Processing
On a Tuesday, two different people ordered the same rebar for the same job. One phoned the supplier from the site trailer. The other sent an email from the office. Both were reasonable. Neither knew about the other. The material arrived twice, the invoice arrived twice, and the second invoice was paid because it looked exactly like the first one and the approver was in a hurry.
If you buy for a construction company or a manufacturer, you have probably lived some version of this. The fix is rarely a better person. It is a purchase order process that makes the second order visible before it happens, and that checks every invoice against what was actually ordered and received.
This article walks through the purchase order lifecycle, the places where it breaks, and how to automate the parts that machines do well while keeping people in the decisions that need judgment.
What a purchase order actually is
A purchase order (PO) is a document your company issues to a supplier that says what you want, in what quantity, at what price, with what delivery terms. Once the supplier accepts it, it is generally treated as an agreement, so the text on it matters. Beyond that legal function, a PO does two jobs inside your own company.
First, it records a commitment. The moment a PO is approved, money is spoken for even though no invoice exists and no cash has left. If your accounting only sees expenses when invoices are paid, your project cost reports are always behind reality. A job that looks under budget on paper may already be over budget in commitments.
Second, it creates the reference that every later document points to. The receiving report cites the PO number. The invoice should cite the PO number. The payment ties back to it. Without that thread, matching becomes a guessing game.
The lifecycle, step by step
A healthy PO moves through a handful of states. Naming them explicitly is the first act of automation, because software needs to know where each order stands.
| State | What it means | Who usually owns it |
|---|---|---|
| Requisition | Someone asks to buy something | Requester, such as a superintendent or a production planner |
| Pending approval | The request is waiting on a budget holder | Approver |
| Approved and issued | The PO is sent to the supplier | Buyer |
| Acknowledged | The supplier confirms price, quantity and date | Buyer |
| Partially received | Some goods or services have arrived | Receiving or site |
| Fully received | Everything ordered has arrived | Receiving or site |
| Invoiced and matched | Invoice agrees with PO and receipt | Accounts payable |
| Closed | Nothing further is expected | Buyer |
| Cancelled | Withdrawn before completion | Buyer |
Notice that "partially received" exists. Construction and manufacturing orders rarely arrive in one piece, and a process that only understands "open" and "closed" cannot cope with a delivery of 60 percent of the order.
Start at the requisition, not the PO
Most bad purchasing is decided before a PO exists. Someone needs a part, finds a supplier, and agrees on a price in conversation. By the time the PO is written, it documents a decision rather than controlling one. This is sometimes called an after-the-fact PO, and it is the single most common way for controls to erode.
A requisition form fixes this if it is genuinely easier than the workaround. It should capture the job or cost center, the item and specification, the quantity, the needed-by date, a suggested supplier, and an estimated cost. Make the job code a required field and make it a pick list, not free text, so that costs land where they belong.
Two small features pay for themselves quickly. A duplicate warning that checks open POs and requisitions for the same item, job and supplier would have caught the rebar problem above. A catalog or price list for repeat items lets the requester choose from agreed prices instead of typing numbers.
Approvals that match how authority really works
Approval rules should mirror the authority your company already grants, not a theoretical hierarchy. Typical dimensions are dollar amount, cost category, job, and whether the supplier is new.
A simple rule table might read as follows. These thresholds are illustrative and yours will differ.
| Condition | Approver |
|---|---|
| Under $2,500, catalog item, approved supplier | Requester's supervisor |
| $2,500 to $25,000 | Project manager or department head |
| Over $25,000 | Operations director plus finance |
| Any amount, new supplier | Finance, who checks the vendor record first |
| Any amount, over the job budget | Project executive |
Build in two safeguards. First, an approver should never approve their own requisition. Second, an approval should expire or return to the queue if the PO is later changed in a material way, such as a higher price. Otherwise someone can get a small amount approved and then edit it upward.
For small teams, one more practical point. Approvals must be possible from a phone, in a truck, with a weak signal. If approval requires a laptop at a desk, people will route around it. In Puerto Rico, where a storm can interrupt office connectivity for days, a mobile approval path with a documented fallback, such as a signed email from a named delegate, keeps purchasing moving without abandoning control.
Change orders are where budgets go to die
A PO is not static. Quantities shift, specifications change, schedules slip. In construction there is also the owner-driven change order on the customer side, which in turn triggers purchase changes on your side. If these are handled by phone and memory, the PO stops reflecting reality, and three-way matching later becomes an argument.
Treat a PO change as a new version of the same PO. Keep the original, record who changed what and why, and require approval based on the new total and on the size of the change. Show the commitment as the current approved version, with the history one click away.
A useful rule is that any change which increases the PO value beyond a set percentage or dollar amount re-triggers approval. Another is that a change to a supplier, unit price or delivery date is communicated to the supplier through the system, so that the acknowledgment is refreshed as well.
For jobs with customer change orders, link them. A purchase change that exists because of customer change order 14 should say so, which makes it easy to bill the customer for the cost and to explain the margin later.
Receiving, the step everyone skips
The receiving report is the evidence that goods or services arrived. It is also the most neglected document in small companies, because the people who sign for deliveries are busy with something else.
Make it light. A delivery ticket photo attached to the PO line from a phone, with a quantity entered and a note for damage or shortage, is enough for most cases. For services and subcontract work, the equivalent is an approved progress claim or a completed timesheet tied to a scope.
Partial receipts need to be first class. Receiving 40 of 100 units should reduce the open quantity to 60 and leave the PO open. Over-receipts, such as 105 of 100, should raise a flag rather than silently succeed, because someone has to decide whether you keep the extra.
Three-way match, explained plainly
Three-way match is the control that compares three documents before an invoice is paid.
- The purchase order says what you agreed to buy and at what price.
- The receiving record says what actually arrived.
- The supplier invoice says what the supplier is asking you to pay.
If quantity and price agree across all three, within a defined tolerance, the invoice can be approved for payment automatically. If they do not, it goes to an exception queue with the reason stated. Two-way match, which skips receiving, is acceptable for services and for low-value items, where the cost of verifying exceeds the risk.
Tolerance is the lever that keeps this practical. A tolerance of two percent or $25, whichever is lower, on unit price might let a fuel surcharge or rounding through, while quantity tolerance is usually stricter because shipping 98 of 100 and invoicing for 100 is a real difference. These numbers are illustrative. Choose yours deliberately and write them down.
A worked example (hypothetical)
A manufacturer orders 500 brackets at $4.20, so the PO is $2,100. Receiving logs 480 on the first delivery. The invoice arrives for 500 at $4.20, $2,100.
The system compares the invoice to the received quantity, not the ordered quantity. It finds 480 received and 500 invoiced. That is a quantity mismatch of 20 units, or $84. The invoice goes to the exception queue marked "invoiced beyond receipts." The buyer calls the supplier, learns that the remaining 20 ship Thursday, and the invoice is held, or paid for 480 with the balance on credit. Without three-way match, $84 may not seem worth catching. Across hundreds of orders and many suppliers, it is the difference between a controlled process and a leaky one.
Matching keys and idempotency
For automation to match documents, it needs reliable keys. The PO number and line number are the primary ones. The supplier's own order or packing slip reference is a secondary key that helps when PO numbers are missing from invoices, which is common.
Systems that create POs from emails, forms or integrations should be idempotent. That means submitting the same request twice produces one PO, not two. A simple technique is to give each requisition a unique identifier at creation and refuse to generate a second PO from the same identifier. This is the technical form of the duplicate warning mentioned earlier, and it protects against a double click or a retried network request.
Vendor setup and fraud controls
Purchase order fraud and error often start with the vendor record. A few controls cost little and prevent a lot.
- Require a tax form and a verified legal name before a supplier can receive a PO.
- Segregate duties, so the person who creates vendors is not the person who approves payments.
- Verify bank detail changes through a call to a number you already had on file, never a number in the email that requested the change.
- Flag POs just below approval thresholds, and flag many small POs to one supplier in a short period, which may indicate splitting to avoid approval.
- Review new suppliers and rarely used suppliers monthly.
None of this requires an expensive tool. It requires that the rules be written, assigned to someone, and enforced by the system rather than by memory.
What to automate and what to leave to people
Machines are good at routing, reminding, comparing and recording. People are good at judgment, negotiation and exceptions.
| Automate | Keep human |
|---|---|
| Routing requisitions to the right approver | Deciding whether to buy and from whom |
| Reminders for overdue approvals and late deliveries | Negotiating price and terms |
| Duplicate detection | Resolving disputes with suppliers |
| Three-way match within tolerance | Approving exceptions beyond tolerance |
| Posting commitments to job cost | Deciding on substitutions and change orders |
| Audit trail of every version and approval | Periodic review of supplier performance |
Things that go wrong
Some failures recur often enough to plan for.
- Stale commitments. POs that were never closed inflate reported commitments. Run a monthly report of open POs older than a set age and close or cancel them deliberately.
- Catalog drift. Prices in the system fall out of date, so every invoice triggers a mismatch and people stop trusting the exceptions. Assign an owner to the price list.
- Approval bottlenecks. If one person approves everything, they become the queue. Delegation rules, with an end date, solve this.
- Free-text everything. Item descriptions typed differently each time defeat reporting. Use item codes where you can.
- Orphaned receipts. Deliveries with no PO happen, particularly for emergency purchases. Give them a defined path, such as an after-the-fact PO with a required reason, rather than letting them disappear.
Questions to ask a software vendor
When you evaluate a procurement or ERP module, ask for specifics.
- Can POs be versioned, with approvals that reset on material changes?
- Does receiving support partial deliveries and over-receipts?
- Can you set match tolerances by price, quantity and category?
- Can commitments flow to job cost reports before invoices exist?
- Can approvals happen on a phone, including with limited connectivity?
- What does the audit trail show, and can you export it?
- Can you import your existing vendor and item data, and export it if you leave?
A Monday morning plan
Begin small and prove the value in one job or one department.
- List your open POs and mark those more than 90 days old. Close what is truly done.
- Write down your approval thresholds as a table and test whether the current practice matches.
- Pick one category, such as materials for a single project, and require every purchase to have a PO before the order is placed.
- Add a receiving step with a phone photo of the delivery ticket.
- Compare the next ten invoices to POs and receipts by hand, and record every mismatch and its cause. Those causes become your tolerance rules.
- Once the rules are stable, automate routing, reminders and the match.
Procurement is a place where small fixes compound, because every order passes through the same few steps. If you would like help sketching the process for your own company, or reviewing how your accounting system handles commitments and matching, I am happy to talk it through. Ozcorp InfraOps works with small teams on exactly this kind of operational wiring, with InfraOps Base starting at $500 per month and vendor and license charges billed separately.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.