Finance · Accounts payable · 6 min read

Checking supplier bills against orders and receipts, automatically, in Odoo

Matching a bill to its order and what arrived is a set of exact rules. MadeEasy runs those rules in your own Odoo, posts only what passes, and writes the reason on every bill it holds back.

11 November 2026 · By Micheal Akinkuotu, Founder

Every accounts payable team knows the check: open a supplier's bill, find its purchase order, find what was received, and compare. Is the price what we agreed? Did we receive what we are being billed for? Have we seen this bill before? It is careful, repetitive work, and the mistakes it lets through are expensive: a price that crept up, a part delivery billed in full, the same invoice paid twice.

Watch it run

A real run on a demo company's Odoo: six draft bills from one day, checked, posted, noted and signed off.

Where the manual check slips

The rules are simple to state and tedious to apply: the unit price within an agreed tolerance of the order (we used 2%), nothing billed beyond what was received, every line tied to an order, and no supplier reference billed twice. Applied by hand across a pile of bills, a 4% price rise or a 60-of-100 delivery billed in full is easy to miss.

What MadeEasy does in Odoo

  1. Reads the day's draft bills, their lines, the purchase order lines they belong to and the quantities received, through Odoo's own API.
  2. Matches every line by the fixed rules, as code: the same answer every time, and no AI anywhere in the decision.
  3. Posts the clean bills up to your limit, each only once, even if the run is interrupted and resumed.
  4. Notes every bill it holds back, on the bill itself in Odoo, with the exact reason: "unit price 27.00 is 8% above the purchase order's 25.00".
  5. Reports once to accounts payable: one email listing each bill held back and why.

Who signs off

A clean bill above the limit (10,000 in our demo) waits for the Finance Manager. The run pauses and asks; only an approval posts it. A no ends the run there, with the reason recorded, and nothing after the sign-off happens. That last point is not a nicety: in testing we found and fixed a case where a declined bill would still have been posted, before any customer process relied on it.

How we know it is right

Before it went live, the process passed five cases written before it was built, each on its own day of bills in the real Odoo:

  • one bill that matches its order and receipt (posted, nothing else);
  • a price 4% over, a bill with no order, and a price 1.7% over, inside the tolerance (one posted, two noted, one email);
  • a clean bill of 12,765 that the Finance Manager declines (not posted);
  • a day with no bills (nothing happens);
  • six bills of every kind, signed off (two posted, four noted, one email naming the four).

After the tests we read every bill's state back from Odoo, and the emails from the sending mailbox. All matched the answers written in advance.

Trying it on your own Odoo

The process needs one thing from you: an Odoo user for MadeEasy and its API key, kept in the process's own secret store. Your limit, your tolerance and who signs off are written into the process in plain words, and your team can change them through its assistant, tested again before the change goes live.

Bring the bills your team checks by hand

Tell us which system they live in and the rules you apply. We will show you the check running there, tested on your own past bills.