The starting point
A purchasing archive may support evaluation of how an organization authorizes, receives and reconciles a purchase. The useful unit is often an order line with its changes and exceptions. Spend totals or invoice PDFs alone cannot explain which goods arrived or why a discrepancy was approved.
Illustrative record structure. No actual business data is shown.
Why the connection matters.
The reasoning behind an exception may be more informative than a final paid status. Keep the original requested quantity, actual receipts, later revisions and review decisions distinguishable. A current approved supplier list is a reference table; it does not prove that every historical purchase followed the same rule.
Records worth describing.
- Partial deliveries and backorders
- Receipt shortages and replacement decisions
- Invoice discrepancies with approval history
Identify the policy the records describe.
Odoo’s purchase documentation distinguishes billing on ordered quantities from billing on received quantities. It also documents editable draft bills and an exception state. These are product examples, not evidence that your business uses those settings. Ask the owner which controls applied during the retained period and whether manual decisions survive in the archive. A payment recommendation is not the underlying receipt evidence.
Keep commercial terms out of the first inventory.
Describe order versions, receipt coverage, allocation links and exception categories without sharing suppliers, negotiated prices or invoice contents. VOID can explore fit through that metadata with no upfront seller referral fee. Receiving-program compensation may depend on its conditions and is disclosed before an introduction. Approving a named recipient and descriptive handoff does not authorize a purchasing sample, financial export or license.
Hypothetical screening example
Illustration: hold an unsupported receipt claim.
A fictional purchase order requests 80 units. The archive contains a 50-unit receipt and a bill for 80, with an approval note saying the remainder was expected later. The inventory retains the discrepancy and missing later receipt. It describes an exception decision, rather than relabeling all 80 units as received because the bill was paid.
Next decision. Hold a complete-receipt claim; a narrower exception-history description may remain useful.
Questions to start with.
- Can split receipts be allocated to the correct order lines?
- Are the historical policy and human exception recorded separately?
- Which supplier agreements or confidential terms affect the proposed scope?
Keep bank information, negotiated terms, supplier communications and confidential attachments within the company’s review environment. A completed match or paid invoice does not establish permission for a new external use.
Source notes
Software documentation describes possible record structures. It does not establish your retained history, rights or buyer acceptance.
Odoo 19.0 — purchase control policiesOdoo · Checked 2026-10-11Vendor billing can use ordered or received quantities. Draft bill changes can produce an exception state, and the payment recommendation can be changed manually. These are configuration-specific examples.