Skip to main content

Invoice Documents Link

Purpose​

Invoice Documents Link connects Invoice Attachment Rules to native Odoo Documents. It lets an invoice user classify a readable Documents record whose attachment is linked to the invoice. The base app then checks that evidence during posting.

This is a helper integration. It adds Classify Documents Evidence to Attachment Compliance on the invoice; it has no standalone application or configuration menu.

Before you start​

Install matching versions of corvus_account_attachment_guard and native documents. Documents is an Enterprise dependency; the bridge requires an installation with the appropriate Documents entitlement and package. The bridge is marked for automatic installation when its dependencies and package are available.

Configure document classes and posting rules in Invoice Attachment Rules. The Documents record must have an attachment and a traceable relationship to the invoice. A matching supplier or filename is not enough.

This guide is based on the 19.0 source workflow, with selected comparisons for 15.0–18.0. No runtime test was performed. The helper has no qualified standalone live demo in the reviewed catalogue.

Access and roles​

Invoice users (account.group_account_invoice) can use the wizard, subject to write access on the draft invoice and read access on both the Documents record and attachment. The selected active document class must belong to the invoice’s company. Existing Documents access rules still apply; this helper does not make a restricted file readable.

Accounting managers configure the base rules and decide any permitted attachment exception. There is no additional approval group in this bridge.

Workflow​

  1. Open the draft invoice or bill that the source document supports. Ensure the Documents record is attached to that exact accounting document.
  2. On Attachment Compliance, select Classify Documents Evidence.
  3. Select the offered Documents record. The wizard displays its linked attachment. Choose the appropriate document class and enter a reason.
  4. Select Classify Evidence. The server verifies readability and the relationship between the invoice, Documents record and attachment. The classification retains Documents provenance; it does not create a replacement file.
  5. Select Refresh Checklist in the base app. Review accepted counts and any missing or invalid evidence.
  6. Continue the normal posting workflow when compliant, or follow the configured manager-exception process. The base posting audit retains evidence metadata and the decision used at posting.

Practice scenario​

In an authorised Enterprise test database, fictional Cedar Consulting has a draft bill and an original supplier PDF managed through Documents. Link the Documents record to the bill, classify it as Supplier Invoice and refresh the checklist. With a matching requirement and valid file, the expected source-derived result is accepted evidence. The scenario has not been executed.

A PDF on an unrelated Documents record should not qualify simply because its supplier name matches. Keep the exact invoice relationship visible during the exercise.

Troubleshooting and limitations​

  • No document offered: the wizard filters Documents records linked to the current invoice. Check the relationship and your Documents access.
  • The selected Documents record has no attachment: choose a record with an actual attached file.
  • Evidence no longer linked or readable: source relationships and access are rechecked, including when posting. Restore the correct relationship or classify appropriate evidence while the invoice is draft.
  • File classified but requirement incomplete: the base rule still applies MIME type, extension, filename, age, size and duplicate-content checks. Generated invoice output and other excluded assets do not become source evidence through this bridge.
  • Posted invoice: classification is a draft workflow; retained posting evidence is not edited by this helper.

Source packages are present for 15.0–19.0; no 20.0 package is listed for this helper in the reviewed inventory. The 15.0–17.0 bridge uses the older access-check API, and 15.0–16.0 forms use legacy modifiers. Native Documents organisation differs by version, so use the matching package and invoice relationship for your installation.

Choose your exact version in the Corvus catalogue. Confirm availability of the Documents bridge and Enterprise dependency before purchase. No direct purchase page or standalone demo is claimed.

Related guides: Invoice Attachment Rules, Invoice PO Attachments, and Invoice Receipt Evidence.