Vendor Bill Match Check

Three-way match between the purchase order, the receipt and the vendor bill, with a company-level tolerance and one exception report you check before you pay.

3-way match for vendor bills, on the bill itself

Odoo will happily post a vendor bill that does not match what you ordered or what you actually received. This module runs a three way match (purchase order, goods receipt, vendor bill) on every bill line linked to a purchase order line and puts every mismatch on one screen, before that bill gets paid.

It does not block the post, it does not touch the accounting entry, and it does not run an approval workflow. It builds an exception row: what was ordered, what was received, what was billed, and by how much they disagree. Someone in accounting looks at the exceptions and decides what to do about them.

What's included

• A bill match check that runs automatically the moment a vendor bill is posted, and again on demand from a "Check bill match" button on the bill.
• One exception row per mismatching bill line, carrying the ordered quantity, the received quantity, the billed quantity, the ordered unit price, the billed unit price, the quantity variance and the price variance.
• Five exception types: billed over received, billed over ordered, price over ordered, no purchase order on the bill line, and not received at all.
• A quantity tolerance and a price tolerance, set once per company under Accounting settings. A variance inside the tolerance is not an exception; it is simply not reported.
• A smart button on the vendor bill showing the exception count, so you see it without opening a second screen.
• One list view with a pivot, grouped by exception type and by vendor, with a default filter for what is still unresolved.
• A "Resolved" flag with who resolved it and when. Resolving is an acknowledgement with an audit trail, not a wizard and not a correction to the ledger - the bill itself is never touched.
• Recompute is idempotent: running the check again after a bill's lines have not changed leaves the same rows in place, it does not duplicate them.
• Security tied into the standard Odoo accounting groups, Invoicing and Accounting Manager. No separate access group to learn or assign.
• Multi-company data isolation by record rule, so a user working across companies never sees another company's exception rows.
• A business guide and a technical guide, each in English and Standard Arabic, included with the module under its own doc/ folder.
• Depends on Odoo's own account, purchase and stock modules only. No OCA dependency, no extra library.

What this does not do, and where the tolerance stops

Compatibility

Every series below is built and tested on a real database of that version, not assumed from another branch.

Documentation

Four documents ship inside the module, under its doc/ folder: a business guide and a technical guide, each in English and in Standard Arabic. The business guide covers the workflow from purchase order to receipt to bill, the tolerance setting, the exception report screen, and what the currency mismatch flag means. The technical guide documents the model, every field, the security groups and record rules, how the match is computed line by line, and how to extend the module with an extra exception type.

Support

Support requests go to support@mohamadfayad.com, answered in English and Arabic during Gulf hours. The store's refund window covers the usual case: if something advertised on this page is missing or does not work as described, that is a refund, not a back-and-forth. Read "What this does not do" above before buying - this module reports mismatches, it does not block a post, run an approval, or edit the bill.