Skip to main content
Back to Blog
purchase-ordersodooerp

Last reviewed:

Odoo 3-Way Match: How Bill Control Works and Where It Stops

By Fluxity Team

Three-way matching in Odoo compares a vendor bill against two other records before it is paid: the purchase order (what you agreed to buy, at what price) and the receipt (what actually arrived). If the bill asks for more than was received, or at a different price, someone should look before money leaves.

Odoo supports this natively through two settings: the Control Policy on each product and the 3-way matching option in Purchase settings. This guide explains how they work together, what Odoo does when a bill does not match, and where teams usually add a check of their own.

How Does Three-Way Matching Work in Odoo?

Odoo's matching rests on one question per product: should a bill be based on what was ordered or on what was received? According to Odoo's documentation:

  1. Control Policy, on each product. On the product's Purchase tab, choose On ordered quantities or On received quantities. With received quantities, a bill created from the PO only includes what has been received so far.
  2. 3-way matching, in Purchase settings. Under Purchase ‣ Configuration ‣ Settings ‣ Invoicing, enable 3-way matching. It works with products set to received quantities.
  3. Should Be Paid, on the bill. With 3-way matching on, each bill gets a Should Be Paid field on its Other Info tab: Yes, No, or Exception. It tells whoever pays bills whether the bill agrees with the PO and the receipts.
  4. Billing Status, on the PO. The purchase order shows Nothing to Bill, Waiting Bills, or Fully Billed, so you can see which receipts still need a bill.

In Odoo 17 and 18 there was also a company-wide Bill Control default for new products. In Odoo 19 the docs set the policy on each product. The 3-way matching module is not in Odoo's open-source Community code, so confirm availability for your edition.

What Happens When a Bill Doesn't Match in Odoo?

Odoo flags the bill; it does not stop it. When a draft bill is edited so it no longer agrees with the PO and receipts, the Should Be Paid field moves to Exception. In the documentation's words, Odoo "notices the discrepancy, but does not block the changes or display an error message."

That design leaves the control with people. It works when the person running payments filters on Should Be Paid before every run. It is weaker when:

  • Bills are paid in batches by someone who does not check the field.
  • The bill was not created from the PO. The comparison needs the bill's lines linked to PO lines. A bill keyed or digitized without that link has nothing to compare.
  • The product uses ordered quantities. Services and non-stocked items are often set to ordered quantities, so there is no receipt to match.

How Does Odoo Handle Partial Receipts?

With the received-quantities policy, Odoo bills only what has arrived. If a PO line orders 100 units and 60 are received, a bill created from the PO starts at 60. When the remaining 40 arrive, the PO shows Waiting Bills again, and a second bill covers them.

Partial receipts break down when the vendor's invoice does not follow the receipts: the vendor invoices all 100 up front, or invoices 60 across two documents, or ships a substitute product. Then someone has to reconcile the printed invoice with what Odoo would bill, line by line.

Where Do Teams Add a Check Before the Bill Exists?

The gap in a flag-not-block design is timing: the mismatch is visible only after the bill is in Odoo. Teams close it in one of three ways:

  1. A payment-run rule. Pay only bills with Should Be Paid set to Yes, and review every Exception first. This costs nothing, but depends on discipline.
  2. Always create bills from the PO. Use Create Bill on the purchase order so lines are linked, then attach the vendor's PDF. That gives Odoo lines to compare, but somebody still keys or checks the vendor's numbers against Odoo's.
  3. Match before the bill is created. An AP automation layer reads the vendor's invoice, matches it against the PO and receipts synced from Odoo, and creates the bill only when it agrees, or holds it for a person when it does not.

Here is how the third option works in Fluxity:

  • Match mode per vendor. Each vendor is set to no PO, 2-way (invoice against PO), or 3-way (invoice against PO and receipt), so services vendors do not wait for receipts that will never come.
  • Received minus billed. Each line's invoiced quantity is compared with what is still billable on its PO line: received minus already billed. Billing exactly what arrived is a match even when the order is not complete, and a second partial invoice matches too. Re-billing quantity already billed stays flagged.
  • Hold, then recheck. With the receipt gate on, a PO invoice with no matching receipt waits as Awaiting receipt and is rechecked automatically, by default on day 3 and day 7, instead of reaching Odoo early.
  • Dollar thresholds. Price and quantity differences can block the push, flag it for review, or just notify, depending on their dollar size.
  • The amount is read back. Odoo builds the lines of a PO-based bill itself, so after creating it Fluxity reads the bill back. If the amount differs from the invoice, the bill is marked for review and a second bill is never created.

The bill still lands in Odoo as a draft. Odoo's own Should Be Paid flag keeps working on it, so the two checks stack rather than compete.

What Should You Set Up First?

  1. Set Control Policy deliberately. Stocked and shipped goods: received quantities. Services and subscriptions: ordered quantities.
  2. Turn on 3-way matching if your edition includes it, and add Should Be Paid to the vendor bill list view your payment run uses.
  3. Agree a rule for Exceptions: who reviews them, and how quickly.
  4. Measure how often Exceptions reach a payment run. If the answer is "regularly," the control needs to move earlier, before the bill exists.

Odoo 3-Way Match FAQs

Does Odoo support three-way matching?

Yes. With products set to bill on received quantities and 3-way matching enabled in Purchase settings, Odoo marks each bill Should Be Paid: Yes, No, or Exception, based on the PO and receipts.

Does Odoo block a vendor bill that doesn't match the PO?

No. Odoo's documentation says it notices the discrepancy but does not block the change or show an error. The Should Be Paid field shows the Exception for someone to act on.

What is the difference between ordered and received quantities in Odoo?

It is the product's Control Policy. Ordered quantities lets you bill everything on the PO at once; received quantities limits the bill to what has arrived.

Should services go through three-way matching?

Usually not. A service has no receipt to match, so services are typically set to ordered quantities and checked against the PO alone (2-way), or handled with no PO at all.


Further Reading