Score where vendor bills get stuck.
Use this scorecard before an AP exception queue audit, during an Odoo cleanup sprint, or when deciding whether AP automation is worth piloting.
0Not visible, not owned, or handled outside Odoo.
1Partly visible, but ownership or evidence is inconsistent.
2Visible in Odoo, owned, aged, and backed by evidence.
Invoice Intake
- Vendor bills arrive through a controlled email alias, portal, or upload path.
- Duplicate vendor invoice numbers are checked before payment approval.
- Uncoded bills are visible before month-end close pressure starts.
PO and Receipt Matching
- Odoo shows whether each bill line matches the purchase order and receipt.
- Partial receipts are routed to receiving instead of sitting with AP.
- Price and quantity tolerances are documented by product or vendor type.
Exception Routing
- Buyer review, receiving follow-up, freight review, and manager approval are separate states.
- Each exception has an owner, due date, and evidence attached.
- Finance can see aging by exception type, not just invoice date.
Controls and Close
- No payment is triggered by automation without human approval.
- Month-end AP blockers are visible before the last week of close.
- Audit trail shows who approved, held, corrected, or rejected each bill.
0-3: manual risk
AP is mostly relying on people to remember the process. Start with visibility and exception ownership.
4-6: cleanup opportunity
The workflow exists, but finance still lacks a clean queue map. Start with routing and evidence.
7-8: pilot-ready
The process is clear enough to test automation safely on one queue, vendor group, or exception type.
Want this mapped against your Odoo workflow?
Book a 20-minute AP exception queue audit. We will identify the first queue or exception type worth cleaning up.