What happens when the freight quote, purchase order, receipt, and invoice do not match?
A freight quote, purchase order, receipt, and invoice do not reconcile automatically, because each one is evidence of a different question: freight cost, delivered quantity, purchasing terms, or inventory accuracy. A mismatch is diagnosed by identifying which specific pair disagrees, not by assuming whichever number looks lowest or highest is the error.
LanePilot is a TMS and WMS for small and mid-sized manufacturers, distributors and warehouses, not a freight broker. That distinction matters here, because reconciling these four documents is exactly the kind of workflow a combined freight-and-warehouse system is built to organize: some of it runs automatically, some of it is a total-level check, and some of it still has to be worked by a person looking at a physical dock.
Four documents, four different questions
Treat each document as testimony about a single, narrow question, not as a general record of "what happened."
- Quote: what a carrier or vendor said the price would be, before the freight moved.
- Purchase order: what the buyer committed to pay for, and how much of it, before anything shipped.
- Receipt: what actually arrived, counted and condition-checked at the moment it was physically present.
- Invoice: what a carrier or vendor is billing for, after the fact.
None of these four is a neutral master record the other three are checked against. Each is written by a different party, at a different moment, for a different purpose. A mismatch is not one problem with one cause. It is one of four possible comparisons, and the fix depends on which comparison actually failed.
Quote vs. invoice: the outbound freight-cost question
On an outbound shipment, the quote is what a carrier agreed to charge and the invoice is what it actually billed. When those disagree, that is a freight-cost question, the one most shippers already call invoice auditing: matching accessorials, fuel surcharges, and reclassifications against what was quoted. We covered that mechanism in how automatic invoice audit recovers money from freight billing errors and will not repeat it here. For this piece, the short version is enough: quote-versus-invoice is an outbound comparison, and the one in this list a system can check line by line without a person opening a box.
Purchase order vs. receipt: the inbound quantity question
On the inbound side, the purchase order says how much was ordered. The receipt says how much showed up. When those two disagree, that is a quantity question, and it gets answered at the dock, not in an accounting system. A receiving record built against the PO line, noting an over, short, or damaged count and the reason, turns "the numbers don't match" into a specific, defensible claim: this many units short, this reason, this line of this PO.
Purchase order vs. supplier invoice: the purchasing question
Separately, the supplier's invoice can be checked against what was received on the purchase order. That is a purchasing question: did the vendor bill for what actually crossed the dock. On LanePilot Warehouse ($119 a month, additive to any freight plan and never a replacement for one), this comparison runs as a total check, comparing the invoice total against the total value received, at each line's own unit cost, and treating a match within plus or minus 5 percent as clean. The PO total is shown alongside for context. It is worth being precise about what that catches: a total-level match flags a vendor invoice that is meaningfully higher or lower than the value received, but it cannot by itself tell you whether the gap is a price change, a quantity change, or both, because it is a total check, not a line-by-line match. Isolating the cause is what the receipt is for, which is why the next comparison matters as much as this one.
Receipt vs. inventory: the accuracy question
Last, the receipt can be compared to what inventory records show on hand. When those disagree, that is an accuracy question, usually meaning something moved, was miscounted, or was never posted after it physically arrived. That comparison gets its own full treatment in why inventory does not match after receiving.
Why the receipt decides what is recoverable
Of the four documents, only one is written at the moment the freight is physically present: the receipt. The quote and the purchase order exist before freight moves. The invoice is written after. The receipt is the only one created at the dock, by the person looking at what actually arrived.
That timing is why the receipt, not the PO and not the invoice, decides whether an inbound discrepancy is recoverable at all. 49 CFR 373.101 requires a motor carrier's receipt or bill of lading to show the names of consignor and consignee, the origin and destination, the number of packages, a description of the freight, and its weight, volume, or measurement. That is general background on what a carrier's own paperwork must contain, not legal advice about any specific shipment, and it says nothing about deadlines. How long a claim stays open after that receipt is written depends on the carrier and on the terms of that shipment's bill of lading or contract, so read that paperwork rather than assume a fixed window.
A vendor chargeback letter built from a receiving discrepancy works the same way: it states what the PO called for, what the receipt shows actually arrived, and asks the vendor for their basis for the difference. It is a factual request, not a legal filing, and LanePilot does not send it. The shipper sends or files it themselves, the same choice covered in vendor chargeback or carrier claim.
A worked example: one purchase order, four numbers that disagree
The following is an illustrative example using round, demo numbers. It is not a real shipment or a statistic about the industry.
A vendor quotes $22.00 per unit for 40 units of one SKU, delivered by LTL. The purchase order is written against that quote: 40 units at $22.00, a PO total of $880.00.
The shipment arrives. Receiving checks it in against the PO line at the dock and finds 37 units, with 3 coded short for "carton crushed in transit, product not recovered." Inventory is posted from that receipt, 37 units on hand, not the 40 the PO called for.
The supplier invoice follows, billing 40 units at $23.50 each, an invoice total of $940.00. The PO-to-invoice check compares that total against what was received. Receiving recorded 37 units at $22.00, which is $814.00, so the invoice is $126.00 over ($940.00 minus $814.00), about 15.5 percent, well outside a 5 percent tolerance, and the check flags it. What the check cannot do is say why, because it is a total check, not a line-by-line match. The PO and the receipt split the $126.00 into two separate causes. The first is a price variance: the invoice charges $1.50 more per unit than the PO's $22.00, across all 40 units, which is $60.00. The second is a quantity shortfall: the invoice still bills for 40 units though only 37 arrived, and those 3 units at the PO's $22.00 cost are $66.00 of billed goods never received. Only the receipt shows that second cause.
One shipment, two separate, correctly diagnosed problems that together make the $126.00 the total check flagged: a $60.00 price variance and a $66.00 quantity shortfall, which only the receipt can show.
How do you run the three-way match, in order?
The three-way match is the standard accounts payable control for inbound goods: before a supplier invoice is paid, it is checked against two other documents, the purchase order and the receipt. Each document proves one thing, and the order matters, because each step narrows what the next one has to explain.
- The purchase order proves what was agreed. Purchasing creates it before anything ships, with the vendor, item, quantity and unit cost on each line. It is the yardstick, so nothing else is judged until it exists.
- The receiving record proves what arrived. At the dock, the receiver checks the delivery in line by line against the purchase order and records any over, short or damaged quantity with a reason. The receiver signs the carrier's delivery receipt, not the purchase order, and notes any exception on it before signing, because the carrier's paperwork and the vendor's purchase order feed two separate recoveries.
- The supplier invoice states what is owed. It arrives last, and accounts payable compares the invoice total against what was ordered and what was received, and the billed quantity against the quantity actually received.
- Pay when the three agree. If they do not, hold the payment and resolve the difference with the vendor first, using the receipt as the evidence of what showed up.
This is the routine version of the match. It is deliberately not a second tour of the four-document diagnosis above: it is the order of operations that sits in front of an accounts payable payment run. The same procedure is the working rhythm of warehouse receiving, and related pieces cover the receiving leg of the match and a case where an invoice matched the purchase order and not the two receipts.
How is a partial receipt handled before accounts payable pays?
Many purchase orders do not arrive in one delivery. The warehouse products, and the warehouse free trial, handle that on a single purchase order: each PO line shows its cumulative received quantity and what is still outstanding, every delivery stays in receipt history, and Receive remaining opens a new receipt for the same PO line when the next delivery arrives, instead of rewriting the first one.
Here is an illustration with round, made-up numbers. A line calls for 50 units and 30 arrive first. After that delivery the line reads 30 received and 20 outstanding. When the rest arrives, Receive remaining opens a second receipt for the same line, and checking in 20 more brings the line to 50 received and 0 outstanding. The rule for accounts payable follows from it: pay against cumulative received, not against the first receipt and not against the purchase order total. If an invoice for all 50 units shows up after the first delivery, hold payment for the 20 units that have not arrived yet.
What the match does and does not cover in LanePilot
Two limits are worth stating plainly, because they decide where a person has to look.
- The purchase order to invoice check is total-only, never line-level. On LanePilot Warehouse, it compares a single invoice total against the total value received, within plus or minus 5 percent. It does not compare lines, and it cannot tell you which line, or whether price or quantity, caused a gap. Reading billed quantity against cumulative received, line by line, is a person's step, using the receipt.
- Inbound freight invoices are not audited automatically. The audit engine runs on outbound freight. Inbound freight cost is entered manually, and recovery on the inbound side runs through the discrepancy captured at receiving and the vendor chargeback letter that LanePilot Warehouse drafts. LanePilot does not send, file or negotiate that letter with a vendor or carrier. The shipper sends it.
The boundary: no single match spans all four documents
One automated match covering all four documents would be simpler to describe, but it would not be true, and claiming it would be the wrong thing to tell a shipper trying to get money back. Quote-versus-invoice runs automatically on connected carriers. The supplier-invoice check, against what was received, is a total-level check on LanePilot Warehouse. PO-versus-receipt and receipt-versus-inventory depend on what a person records at the dock. Four documents, four questions, and the discipline that recovers money is asking which pair disagrees before reaching for a dispute letter.
LanePilot is one system, web-based with nothing to install, carrying a shipper's freight side and warehouse side in a single login: see LanePilot's combined TMS and WMS for small and mid-sized manufacturers, distributors and warehouses. An account is free to create, no card required, at lanepilottech.com/signup.
Frequently Asked Questions
What is a three-way match?
A three-way match compares a purchase order, a receipt and a supplier invoice before the invoice is paid. The purchase order shows what was agreed, the receipt shows what arrived, and the invoice shows what is billed. Payment is released only when the three agree, or when the difference has been resolved with the vendor.
How does LanePilot handle a purchase order that arrives in more than one delivery?
One purchase order can be received across multiple deliveries in the warehouse products. Each PO line shows cumulative received and outstanding quantities, each delivery stays in receipt history, and Receive remaining opens a new receipt for the same line on the next delivery. Before paying, compare the billed quantity with the cumulative received quantity.
Does LanePilot reconcile all four documents automatically?
No single check spans all four. Quote-versus-invoice auditing runs automatically on connected carriers, outbound only. PO-versus-invoice is a total-level check (invoice total against the value of what was received, within plus or minus 5 percent) on LanePilot Warehouse, not a line-by-line match. PO-versus-receipt and receipt-versus-inventory depend on what is recorded at receiving, the only document written while the freight is physically present.
What deadline applies to a receiving discrepancy?
There is no single deadline that applies to every shipment. Timing depends on the carrier and on the terms of that shipment's bill of lading or purchase contract, so check that specific paperwork rather than assuming a fixed number of days.
Who sends a vendor chargeback or carrier dispute letter?
The shipper does. LanePilot drafts the letter from the documented discrepancy, quoted against billed, but does not send, file, or negotiate with a carrier or vendor on a shipper's behalf.
What does LanePilot Warehouse add to this?
Receiving and OS&D capture come with Warehouse Essentials ($79 a month); LanePilot Warehouse ($119 a month) adds the PO-to-invoice total check described above. Both are standalone products bought in addition to any freight plan, including the free plan, never instead of one, and neither carries freight allowances of its own.