Most supplier disputes come down to a mistyped quantity, price, or term.
PDF, JPG, PNG, BMP, HEIC, TIFF
Submit your purchase orders
Drop documents here, or choose a file
Up to 50 files per batch
Uploading...
Most supplier disputes come down to a mistyped quantity, price, or term. Extract every purchase order accurately and you keep a clean record of exactly what was agreed, so discrepancies are settled by the data, not by memory.
A discrepancy is any difference between what the purchase order says and what the supplier acknowledged, shipped, or invoiced. Some are genuine supplier errors. Many start inside the buying organization, when the order was keyed incorrectly or changed without the record being updated.
The invoice unit price differs from the PO unit price. The cause can be an expired quote, a price increase that was never agreed, or a PO that was keyed with the wrong price in the first place.
The PO says 10 cases, the invoice says 120 each. The quantities may agree once the unit of measure is converted, or they may not, and the only way to know is a line-level record with the unit on it.
Payment terms, delivery dates, and freight terms on the invoice do not match the order. Without the agreed terms on record, the conversation turns into one side against the other.
A revised PO was issued, but both versions were entered. The supplier ships against one and invoices against the other, and AP cannot tell which order the invoice belongs to.
Discrepancies are settled by comparing documents line by line, which only works if the purchase order exists as clean, complete data. PurchaseOrders turns each PO into structured rows with the exact quantity, unit, unit price, and terms as printed, and flags patterns that usually lead to disputes.
Every line item comes back with SKU, description, quantity, unit of measure where printed, unit price, and line amount, so the comparison with the invoice or acknowledgment is a lookup, not a hunt through PDFs.
A unit price that sits well away from what you normally pay the same supplier for the same item is flagged, together with the typical price and how many earlier orders it is based on.
The same PO number from the same supplier on more than one document is flagged with both documents named, which catches superseded and duplicate orders before they are invoiced twice.
A different tax ID, address, or payment terms from the last order for that supplier is shown side by side, so a changed term is noticed before it becomes a dispute.
Disputes get resolved fastest when the agreed order exists as clean data, so precise purchase order line item extraction gives you the exact quantity and price to point to. Many discrepancies actually start as missing purchase order data from manual entry, and reconciling an invoice against the PO line by line is the same three-way check explained in what is a 3-way match. Keep the record in a purchase order PDF to Excel export so any line is easy to pull up.
Before chasing every small difference, agree how much variance you accept: purchase order tolerance explains how price and quantity tolerances are set, and purchase price variance covers how price differences are measured and reported.
Each type of discrepancy has a field on the purchase order that settles it. Compare that field first.
| Discrepancy | How it shows up | PO field to check |
|---|---|---|
| Price | Invoice unit price differs from the order | Unit price and currency on the PO line |
| Quantity | More or fewer units invoiced or shipped | Ordered quantity and any partial delivery terms |
| Unit of measure | Quantities look wrong by a factor such as 12 or 24 | UOM on the PO line and pack size in the description |
| Item | A substitute or different SKU was supplied | SKU, supplier part number, and description |
| Terms | Different payment or freight terms on the invoice | Payment terms and Incoterms in the PO header |
| Duplicate | Two invoices or shipments against one order | PO number, revision number, and order date |
Three-way matching compares the purchase order, the goods receipt, and the invoice. A clean PO record is the first of those three and the one most often at fault when it was keyed by hand.
A repeatable routine for settling differences with facts rather than memory.
Find the purchase order and any revisions. If the order only exists as a PDF, extract it so you have the lines, quantities, units, prices, and terms as structured data.
Set the PO lines next to the invoice, the goods receipt, and the supplier acknowledgment if there is one. Compare quantity, unit of measure, unit price, and line amount for each line, then the header terms.
Tip: Convert units before comparing quantities. Many apparent quantity errors are case versus each.
Decide whether the difference is a supplier error, an internal keying error, an unrecorded change order, or a variance inside your agreed tolerance. The cause decides who corrects what.
Request a credit note or corrected invoice, amend the PO, or approve the variance. Record the outcome against the PO number so the next discrepancy with that supplier starts from the full history.
It is any difference between the purchase order and a related document from the supplier, most often the invoice, the delivery note, or the order acknowledgment. Typical differences are unit price, quantity, unit of measure, item substituted, payment terms, and delivery date.
Start with the unit price on the PO line and any quote or contract it references. If the invoice is higher without an agreed change, ask the supplier for a credit note or a corrected invoice. If your PO was wrong, amend it. Record the outcome against the PO number either way.
The buying organization. If the supplier invoiced what was actually agreed and the PO in the system shows something else, the fix is to amend the PO. This is one reason to capture purchase orders from the source document instead of retyping them.
It compares the purchase order, the goods receipt, and the invoice, line by line. The invoice is approved only when quantity and price agree across all three within your tolerance. Anything outside the tolerance is routed to an exception queue for review.
It depends on your policy, the value of the order, and the category. Many teams set a small percentage or a fixed amount per line, and a tighter tolerance for high-value items. Write the tolerance down so AP and buyers apply the same rule.
Some can. Duplicate PO numbers, unit prices that differ from your usual price for the same supplier and item, and changed vendor details can all be checked when the purchase order is captured, before goods are received or an invoice is matched.
Choose your plan