Skip to main content

Invoice Receipt Evidence

Purpose​

Invoice Receipt Evidence extends Invoice PO Attachments so a file attached to a linked inventory transfer can support a vendor document’s attachment requirements. It adds Classify Receipt Evidence to the existing Attachment Compliance page. There is no standalone menu or separate app.

The integration follows the bill’s purchase lines to their orders and those orders’ transfers. A receipt number typed into a reference field is insufficient.

Before you start​

Provide matching packages for Invoice Attachment Rules, Invoice PO Attachments (corvus_account_attachment_guard_purchase) and native Purchase/Inventory integration (purchase_stock). This helper declares the latter two dependencies and automatic installation when available. No Enterprise-only dependency is declared.

Have an administrator configure the base app’s document classes and posting rules. Upload the supporting file to the exact linked transfer. The helper does not create receipts, validate stock moves or copy files to the bill.

This guide uses the 19.0 source workflow, with limited comparisons of other listed versions. No runtime test was performed for this guide.

Access and roles​

Invoice users (account.group_account_invoice) can use the classification wizard. They need write access to the draft vendor document and read access to the transfer and its attachment. Base-app company and classification checks still apply. Accounting managers control posting policy and exceptions; installing this helper does not grant inventory access.

Workflow​

  1. Open a draft vendor bill whose native purchase-line links lead to a purchase order with a linked transfer. Check the source relationship before choosing evidence.
  2. Open Attachment Compliance and select Classify Receipt Evidence.
  3. Select a linked transfer, then an attachment owned by that transfer. Choose an active document class in the bill’s company, such as Delivery Proof, and enter a reason.
  4. Select Classify Evidence. The wizard records receipt provenance and the transfer relationship without copying the file.
  5. Select Refresh Checklist. The base guard evaluates the classified file against the effective posting rule’s counts, types and other constraints.
  6. When the requirements are satisfied, use normal posting. If an exception is needed, follow the base app’s manager approval workflow for a rule that allows it. Inspect Attachment Audits after posting.

Practice scenario​

In an authorised test database, fictional Northbank Components supplies 20 boxes against a purchase order. The purchase has a linked receipt and a draft vendor bill created from its lines. Attach a sample delivery note to the receipt, classify it from the bill as Delivery Proof and refresh the checklist. With a matching rule and valid file, the source-derived expected result is one accepted Delivery Proof document. This case was not executed.

Use a transfer from a different purchase as a negative case: matching product or supplier names do not make that file valid evidence for this bill.

Troubleshooting and limitations​

  • No receipt linked through an exact purchase line: the bill must retain its purchase-line relationship and the related order must have a linked transfer. A manually typed receipt reference does not meet the requirement.
  • Select an attachment owned by the exact receipt: upload to, and select from, the transfer itself. PO-owned files use Classify PO Evidence.
  • The receipt file is still rejected: inspect document class, company, readability and the base rule’s file checks. Duplicate content may not increase the accepted count.
  • Classification changed after posting: posted classifications are protected by the base app. The helper is a draft evidence workflow.

The source selection is based on the order’s linked transfers and does not impose a completed-receipt-state filter. Do not treat successful classification as proof that stock was received, quantities reconciled, or a three-way match completed. Those facts must be reviewed in the native purchase and inventory records.

Qualified catalogue pairs are 15.0, 16.0, 18.0, 19.0 and 20.0. A 17.0 source version exists but is not a qualified live-demo pair here. Bridge comparisons retain the source-link logic; older versions adapt access checks and form modifiers, and 20.0 uses the revised ACL format. These comparisons are not runtime certification.

Live Test — Odoo 19.0 · Choose the exact version in the Corvus catalogue.

Related guides: Invoice Attachment Rules and Invoice PO Attachments.