You buy
Purchasing
A PO you send to a supplier to commit to a purchase.
- Who approves
- Budget holder or purchasing lead approves before it is sent.
- Ends with
- Supplier confirmation, then goods received.
Workflow guide
Purchase Order Processing: From Incoming Document to Approved Record
Short answer
PO processing turns an incoming purchase order into an accurate, approved record. Capture the fields, check them against your master data, hold anything duplicated, revised, mismatched or missing, route it to a named owner, then record, confirm and track it. Approvals and payments stay with your team.
First, name the process
Three processes get called “PO processing”.
They have different owners and different approvals. Decide which one you mean before anyone writes an SOP.
You sell
Customer order entry
A PO a customer sends you, entered as a sales order in your system.
- Who approves
- Checked against customer, item and price records; your team confirms.
- Ends with
- Order confirmation, then fulfilment.
You pay
Invoice approval
A supplier invoice matched against the PO and goods received before payment.
- Who approves
- Finance approves payment under its own authority.
- Ends with
- Payment run and closed PO.
The workflow
Seven steps from inbox to closed.
Every exception stops the line and gets a person. Nothing is resolved by guessing.
Step 01 / 07- 01Intake
Receive the PO from an agreed channel, log the received date and keep the original file.
- 02Capture
Read header and line fields into a draft record. Keep a link to the source document.
- 03Validate
Check customer, ship-to, items, units, prices and dates against your master data.
- 04Flag exceptions
Hold anything duplicated, revised, mismatched or missing. Don’t guess.
- 05Route and approve
Send exceptions to the named owner. Approvals stay with your team.
- 06Record and confirm
Save the approved record, send the confirmation and note the status.
- 07Track and close
Follow the order to fulfilment or matching, then close and report.
Field map
Where each field goes — and what to check.
Hover or tap a highlighted field on the sample PO to see its record field and validation rule.
Sanitised, fictional example
PURCHASE ORDER
No. CP-58217 Rev 0
Date 3 Nov 2026
Bill-toCedar & Pine Hardware
Acct 30418
Acct 30418
Ship-toStore 14, dock 2
Riverside
Riverside
| Part no. | Description | Qty | Unit | Price |
|---|---|---|---|---|
| CPH-2210 | Wood screws 4×40 | 40 | CS | $18.40 |
| CPH-3308 | Wall plugs 8mm | 25 | BX | $9.75 |
| CPH-1175 | Hinge, brass 75mm | 60 | EA | $3.20 |
Requested12 Nov 2026
TermsNet 30
Authorized byJ. Rivera
Validation rule
Select a field to see its rule.
PO number → External referenceMust be unique for this customer. Search open and closed orders before entry.
Revision → RevisionRev 0 is new. Any higher number is a change: compare with the saved version.
PO date → Order dateUse the document date, not the date received. Log both.
Bill-to → Customer accountMatch to the customer master by account number, not by name alone.
Ship-to → Delivery addressMust be an approved ship-to on the account. New addresses go to the account owner.
Customer part no. → Item codeTranslate through the cross-reference table. No match means an exception.
Quantity → QuantityCheck against the unit before entering. Watch for decimals and thousands separators.
Unit → Unit of measureConvert with the item master (e.g. 1 CS = 12 EA). Unknown units are exceptions.
Unit price → PriceCompare with the price list or contract. Differences are flagged, never overwritten.
Requested date → Requested deliveryCheck against lead time. Past or impossible dates go to the account owner.
Terms → Payment termsMust match the account. Terms changes need finance approval.
Authorized by → Buyer contactRecord the name and contact. Missing authorisation is a hold if your rules require it.
| PO field | Value | Record field | |
|---|---|---|---|
| PO number | CP-58217 | → | External reference |
| Revision | Rev 0 | → | Revision |
| PO date | 3 Nov 2026 | → | Order date |
| Bill-to | Cedar & Pine Hardware | → | Customer account |
| Ship-to | Store 14, dock 2 | → | Delivery address |
| Customer part no. | CPH-2210 | → | Item code |
| Quantity | 40 | → | Quantity |
| Unit | CS | → | Unit of measure |
| Unit price | $18.40 | → | Price |
| Requested date | 12 Nov 2026 | → | Requested delivery |
| Terms | Net 30 | → | Payment terms |
| Authorized by | J. Rivera | → | Buyer contact |
Exceptions
The five exceptions that stop a PO.
For each: how it looks, the check that catches it, what to do, what not to do, and who decides.
Duplicate PO
Same PO number arrives twice — often a resend or a CC.
Saved orderCP-58217 · 3 lines · $1,215
New emailCP-58217 · 3 lines · $1,215
HoldCheck
Search the external reference across open and closed orders before creating a record.
Do
Link the new file to the existing order and mark it “duplicate received”. Confirm with the buyer if anything differs.
Don’t
Create a second order “just in case”.
Escalate to
Account owner
Unit of measure mismatch
The customer orders in cases; your item master sells in each.
PO line40 × CS
Item masterSold in EA · 1 CS = 12 EA
HoldCheck
Compare the PO unit with the item master and the conversion table.
Do
Convert only when an approved conversion exists (40 CS = 480 EA) and note it. Otherwise hold the line.
Don’t
Enter 40 EA, or assume a pack size.
Escalate to
Item data owner / account owner
Revision or change order
A “Rev 1” arrives after the original was entered.
Rev 0 (saved)Hinges · 60 EA · 12 Nov
Rev 1 (new)Hinges · 90 EA · 19 Nov
HoldCheck
Compare every field with the saved version, line by line.
Do
List the changes, check the order status (not yet picked?), then update under your change rules and keep both versions.
Don’t
Overwrite the saved order without a comparison.
Escalate to
Order desk lead
Price difference
The PO price doesn’t match your price list or contract.
PO price$18.40 / CS
Price list$19.10 / CS
HoldCheck
Compare each line price with the current price list or contract.
Do
Hold the line and ask the account owner which price applies. Record the decision on the order.
Don’t
Change the price to match either document yourself.
Escalate to
Account owner / sales
Missing or unknown data
A new ship-to address, an unknown part number or no authoriser.
PO ship-toStore 22, dock 1
AccountNo such ship-to on file
HoldCheck
Validate customer, ship-to and part numbers against master data.
Do
Hold the order, request the missing detail using an approved template and log the follow-up date.
Don’t
Add a new address or item to master data without approval.
Escalate to
Account owner / master-data owner
Escalation
Hold, route, and write it down.
Example escalation messages. Short, factual, and they name the decision needed.
| Exception | Record status | Owner | Example message |
|---|---|---|---|
| Duplicate PO | No — link to existing | Account owner | “We received CP-58217 again on 4 Nov. We have it as order 10442. Please confirm no new order is needed.” |
| Unit mismatch | Hold the line | Item data owner | “Line 1 is ordered in CS. We sell this item in EA. Please confirm the quantity in EA.” |
| Revision | Hold changes | Order desk lead | “Rev 1 changes hinge quantity 60 → 90 and date 12 → 19 Nov. Order is not yet picked.” |
| Price difference | Hold the line | Account owner | “PO price $18.40/CS, list price $19.10/CS. Which should apply?” |
| Missing data | Hold the order | Master-data owner | “Ship-to ‘Store 22, dock 1’ isn’t on the account. Please confirm or add it.” |
Measure it
Four signals that the process is working.
Agree targets with your team; these are the measures, not benchmarks.
Accuracy
Share of sampled records with no field errors against the source.
Turnaround
Time from received to recorded or held, against the agreed target.
Open exceptions
Held items by type and age, with an owner for each.
Rework
Records corrected after entry — a sign the SOP or master data needs work.
Definitions
PO terms, in plain English.
- Purchase order (PO)
- A buyer’s document that commits to buy stated items, quantities and prices.
- Sales order
- Your internal record of what a customer ordered, often created from their PO.
- Customer order entry
- Turning an incoming customer PO into a sales order in your system.
- Invoice approval
- Checking a supplier invoice against the PO and receipt before payment is authorised.
- Line item
- One row on a PO: item, quantity, unit and price.
- Unit of measure (UOM)
- How a quantity is counted — each, case, box, pallet. Conversions live in the item master.
- Revision / change order
- A new version of a PO that changes an earlier one. Compare before updating.
- Duplicate PO
- The same PO received more than once. Link it; don’t re-enter it.
- Item master
- Your system’s list of items, codes, units and conversions.
- Customer or vendor master
- Your list of approved accounts, addresses and terms.
- Cross-reference
- A table that translates a customer’s part numbers into your item codes.
- Two- and three-way match
- Comparing PO and invoice (two-way), plus goods received (three-way), before payment.
- Blanket PO
- A PO covering repeated deliveries over a period, released in parts.
- Exception queue
- Where held documents wait for a named owner to decide.
- Source reference
- A link from the record back to the original document, so any entry can be checked.
FAQs
PO processing questions
Including what should stay with your team.
The administration that turns a PO into an accurate record: receiving it, capturing the fields, checking them against your data, routing exceptions, recording the approved result and tracking it to completion.
No. Purchasing, customer order entry and invoice approval are separate processes with different owners. Invoice approval authorises payment, which should stay with your finance team.
Duplicate POs, unit-of-measure mismatches, revisions or change orders, price differences and missing or unknown data such as a new ship-to address or part number.
The administrative steps can, when there is a written SOP, least-access permissions, a clear exception route and sample checks. Approvals, pricing decisions and payments stay with your team.
Usually your ERP or order system, email or an EDI/portal feed, spreadsheets for logs and, where volumes justify it, document-processing software that reads PO fields for human review.
Yes. We map your fields and exceptions, write the operating instructions and run the agreed steps in your systems, with exceptions routed to your named owners.
Need help with your PO workflow?
Send us one sanitised PO. We’ll map it with you.
We document the fields, checks and exceptions first, then agree what our team handles and what stays with yours.