· Import operations
Supplier PO to invoice reconciliation for GCC importers
Fix the receipt first, use one reference number, match line by line, and set tolerance rules before your next shipment.
Start by checking whether your team treats a receipt and an invoice as one document. They are not. A shipment can cover several purchase orders, and one invoice can cover several shipments. Fix the receipt step first, then let the invoice match what you actually received.
Shipments and invoices are separate records
International suppliers may not ship exactly what you ordered in one go. A supplier may consolidate two purchase orders into one container and invoice only the lines that went out. The warehouse sees a packing list, the finance team sees a vendor bill, and neither document points to the other unless you create that link yourself.
A contributor on Odoo's forum described this pattern: a supplier consolidated multiple purchase orders into one shipment and invoiced only what was shipped. The contributor could not see which receipt belonged to which shipment because the system created one receipt per order. [1]
Odoo's official vendor bill documentation confirms that multiple bills for the same purchase order may be issued when a vendor ships partially or requests a deposit. The Bill Reference field is designed to match products when they are received. Use it. [3]
Record the receipt at the dock, not at the desk
When goods arrive, create a receipt against what is physically on the pallet, not against what the purchase order says. Take the supplier's packing list, note any shortages or overages, and attach that document to the receipt. Check whether your system lets you create a receipt from a packing list; if it does, select the items that actually arrived and link them to one shipment reference. Do not assume this capability exists in Odoo unless you verify it in your version.
In Odoo, the Bill Reference field on the vendor bill should carry the supplier's invoice number or shipment number. The documentation says this field is used to match products when they are received. Without that reference, matching a partial bill to the right receipt weeks later is difficult. [3]
If you use Shopify, check whether your apps or exports hold purchase receipts. If not, apply the same receipt-first principle in a spreadsheet. Record what arrived against the packing list, keep one shipment reference, and match line by line before paying.
Match line by line, not total to total
A total match hides line-level changes that can cost you money. In a Neo Praxis demonstration, a fictional quotation kept the same AED400 total while one line's quantity went up and another line's unit price went down. A total-only check would have missed both edits. The same risk applies when you compare a supplier's invoice total to your purchase order total.
Compare every line on the vendor bill against the receipt: item code, quantity, unit price, and currency. Flag any difference in a shared spreadsheet or your system's comment thread so the finance team sees it before approving payment. A quantity overage on one line cannot be offset by an underage on another unless you have agreed that rule in writing.
A Cin7 user reported that receiving a different quantity than ordered blocked the invoice step, forcing manual undo work. In that system, without a configured tolerance, a quantity mismatch may force manual handling before payment. Check your own system's behavior: does a receipt and invoice quantity mismatch block payment, or can you proceed with a note? [2]
Set tolerance rules with finance before the exception
Sit with your finance lead and decide what differences are acceptable without escalation. Common examples are quantity within a small agreed band, unit price within an agreed percentage, freight or landed cost within an agreed absolute amount, and currency rounding within an agreed fraction. Write these tolerances into a one-page procedure and attach it to the supplier record.
Do not let the person receiving goods make tolerance decisions on the spot. The receiver records what arrived; the finance lead decides whether the difference is acceptable. That separation prevents a warehouse clerk from approving a price change they were never meant to approve.
When a custom module is not worth buying
Before you pay for custom software, take your last quarter's records. Count the hours your team spent on reconciliation and the actual cost of your worst pricing or quantity error. Ask the developer to state the annual saving in hours and prevented errors using these measured numbers, not industry averages. Then compare that with the module's licence and maintenance costs.
Odoo's vendor bill screen already includes Auto-Complete to pull data from a past purchase order, Bill Reference for matching, and an Aged Payable report for outstanding balances. Try these on one supplier for a month before paying for a custom module. [3]
What to do this week
Pick your most active supplier. Gather the last three shipments and their purchase orders, receipts, and vendor bills. Write down where the link breaks: missing reference, no receipt for partial shipment, or a total-only check that hid a price change. Fix that one supplier's process first.
Then test the fix with the next shipment. Record the receipt at the dock using the packing list, set the reference on the vendor bill when it arrives, and match line by line before payment. If the finance team can approve the invoice without calling the warehouse, the process is working.
