What is the best way to handle the purchase orders customers send us, and the ones we send suppliers?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: Purchase order (PO) processing is everything that happens to a PO, from the request to buy through approval, a numbered PO, supplier confirmation, receiving, an invoice match and payment. A distributor runs it in two directions: POs you send to suppliers, and POs customers send to you. Errors start with manual typing, mixed units and old prices. Approval limits, a three-way match and clean item data prevent most of them, and AI can read and check PO documents while a person approves the exceptions.

Ranjit Bhinge

You handle purchase orders in two directions, the ones customers send and the ones you send suppliers, and you want one process that holds up in a busy week.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

The two sides of PO processing

A purchase order is a document that says "I will buy these items, in these quantities, at these prices." A distributor sees it from both sides:

  • Buyer side. You send POs to suppliers to restock.
  • Seller side. A customer sends you a PO, and someone turns it into a sales order in your ERP (the system that runs orders, stock and accounts).

The first side gets all the attention in guides. The second is where reps lose hours, so I cover both.

Steps for POs you send to suppliers

Cleverence, a company that sells warehouse scanning software, describes the flow as turning a request into a confirmed order, a received delivery, a matched invoice and a payment. In practice:

  1. Requisition. Someone asks for items, with quantity, needed date and a cost center (the budget line it is charged to).
  2. Approval. An approver signs off based on dollar limits, category and risk.
  3. Sourcing. For new or large items, get quotes and compare total landed cost (price plus freight, duty and handling), not just unit price.
  4. PO creation. The approved request becomes a numbered PO with supplier, addresses, terms, prices and dates. See my purchase order template.
  5. Send and confirm. The supplier acknowledges the PO and the dates.
  6. Receive. Your team checks arrivals against the PO and records shortages or damage before stock is posted.
  7. Three-way match. Accounts payable compares the invoice, the PO and the goods receipt.
  8. Pay and close. Pay on the agreed terms. Close the PO, or keep it open for a backorder (the part that has not arrived yet).

Types of purchase orders

Not every PO is a one-off. Cleverence describes four kinds, and the choice depends on how predictable your buying is:

  • Standard PO. One purchase with set items, quantities, prices and dates. Use it for one-off buys or when volumes and dates are known.
  • Planned PO. Items, prices and a total planned quantity are agreed, but delivery dates come later through releases. Use it when demand is known but timing is not.
  • Blanket PO. One approval covers repeat buying from one supplier, capped by quantity, amount or time. Cleverence suggests an expiry date, a not-to-exceed amount and a review every quarter.
  • Contract PO. Master terms such as pricing and legal terms, with no line items. Each later order refers back to it.

For a distributor, a blanket PO suits steady items like packaging or fasteners. A standard PO suits a special order for one customer.

Steps for POs customers send you

  1. Receive. The PO lands in an inbox, a portal or a fax-to-email service.
  2. Read. Find the customer, ship-to address, PO number, items, quantities, prices and requested date.
  3. Match products. Turn the customer's part number or description into your item code.
  4. Check price and stock. The price must match the customer's agreed price, and stock must cover the quantity.
  5. Enter. Key the order into the ERP or accounting system.
  6. Confirm. Send an order confirmation.
  7. Resolve exceptions. Anything unclear goes back to the customer.

This is the side that automation helps most. See sales order automation for the tools and rules.

Where errors start

Cleverence lists the usual causes: buying outside the process, bad master data such as mismatched units or old prices, slow approvals with no delegate, receiving and matching exceptions that hold up payment, and manual paper work. For a distributor, three failures show up again and again:

  • Unit mix-ups. The PO says a case of 12 and the truck brings single units.
  • Price gaps. The customer's PO shows last year's price, or your supplier's invoice shows a new one.
  • Unknown part numbers. The customer's code is not in your system, and a rep guesses.

Controls that fit a small team

  • Three-way match. The invoice, the PO and the goods receipt must agree. For low-risk buys a two-way match (invoice and PO) may be enough.
  • Tolerances. Cleverence gives an example of a plus or minus 2 percent price variance that passes automatically, with bigger gaps routed to a person. Set your own and write them down.
  • Approval limits in the system. Not on paper, and with a delegate for holidays. For the approval side in detail, see the PO approval process for small businesses.
  • Separation of duties. The person who sets up a supplier should not be the one who approves payment to it.
  • Audit trail. Keep attachments and a record of who did what.

What software handles purchase orders

Your ERP or accounting system is the first place to look, so check what you already pay for. Acumatica, a cloud ERP for distributors, says its purchasing module covers approvals, sourcing and replenishment, and its warehouse module covers receiving with mobile scanning. Odoo, an open-source business suite, sells Inventory and Purchase apps and lists an inventory barcode role on its pricing page. Look at each vendor's current pricing page before you shortlist, because many show quotes only or change by region.

NeedLook for
Send POs and track themPO log, status, supplier acknowledgment
Receive stock correctlyScanning, partial receipts, a record of damage
Pay only what you orderedThree-way match, tolerances, exception queue
Stop retyping customer POsA document reader linked to the ERP

For the payables side, read accounts payable automation.

How systems run the match

The three-way match is a setting, not a manual task, in most systems. Two examples from the vendors' own documentation:

  • Odoo. Its Purchase app has a bill control policy. Under "ordered quantities" a draft bill appears as soon as the PO is confirmed. Under "received quantities" billing waits for receipts and shows an error if you try to bill before anything has arrived. Odoo's three-way matching works only with the received-quantities policy, and it flags each bill as Yes, Exception or No under "Should Be Paid". Odoo notes an edited draft bill is marked Exception but is not blocked.
  • Microsoft Dynamics 365 Business Central. Microsoft's business system for small and mid-size firms. Each PO line has a Qty. to Receive and a Qty. to Invoice field, so you can post a partial receipt and a partial invoice. Microsoft says you cannot invoice something that has not been received. You can combine several receipts on one invoice using the Get Receipt Lines action.

The point for you is to choose the policy on purpose. If you pay on received quantities, short deliveries stop at the match and never reach payment.

How AI helps with purchase orders

AI is useful for reading. It can pull lines out of a PDF PO, compare each price and quantity to your price list, and flag a mismatch. Microsoft's Sales Order Agent, an AI feature in Business Central, shows the pattern: it reads emailed PDFs and images, builds a quote first, and makes a designated person approve every outgoing message. That is the right habit for any tool. See AI document processing for how this works across document types.

A person still owns three things: new customers and suppliers, price differences above your tolerance, and any change to a PO that has already been confirmed.

A worked three-way match (made-up numbers)

You ordered 100 cases at $12.00. The goods receipt shows 96 cases arrived. The supplier invoices 100 cases at $12.20. Your tolerance is 2 percent on price. The price gap is 1.7 percent, so it passes, but the quantity does not match: 96 received against 100 invoiced. The match fails, and the invoice goes to a person to ask for a corrected invoice or a credit for 4 cases. This is the kind of check a system should run for you.

A second example: partial deliveries (made-up numbers)

You order 200 units at $5.00, a $1,000.00 PO. The supplier ships 120 units on Monday and 80 on Friday. After Monday you receive 120, so a system set to bill on received quantities lets the supplier bill only $600.00. The PO stays open with 80 units on backorder. After Friday the second receipt brings the total to 200 and the supplier can bill the remaining $400.00, or one invoice can cover both receipts. If an invoice for $1,000.00 arrives on Monday, the match fails because only $600.00 of goods has been received, and the invoice waits. Without that rule, you pay for 80 units that are still on a truck.

Track the process, not just the paper. Cleverence suggests three measures: the time from request to PO, the first-pass match rate (invoices that match without a person), and the share of spend outside the PO process.

How I'd approach this

I would write down both flows on one page and mark where someone retypes. Then I would fix the data first: one unit of measure per item, one price source, one cross-reference list for customer part numbers. Next I would use the PO features my ERP already has before buying anything. If reps still lose hours keying customer POs, I would add a reader for that one side, with drafts only. If your process is held together by one person who knows the tricks, business process automation is the right place to start.

Questions people ask

What is the purchase order process?

It runs from a request, to approval, a numbered PO, supplier confirmation, receiving, an invoice match and payment. The PO closes when everything is received and paid, or stays open for a backorder.

What is a three-way match?

It compares the invoice, the PO and the goods receipt, so you pay only for what you ordered and received. Small differences inside your tolerance can pass. Larger ones go to a person.

What is the best purchase order software?

Start with the module in your current ERP or accounting system. Look for approvals, receiving with scanning, and matching. Add a document reader only if staff still key POs by hand. See accounts payable automation.

Can AI review purchase orders?

Yes. It can read PO documents, extract the lines, and flag price or quantity gaps. A person should approve exceptions. See AI document processing.

Do customer POs and supplier POs follow the same process?

They mirror each other. Yours to suppliers need approval, receiving and matching. Customers' POs to you need reading, matching and entering as sales orders. See sales order automation.

More in this topic: B2B: order entry and purchase orders (9 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…