OdooWiki OCA HUB

Account Edi Retrieve Partner From Purchase Order

account_edi_retrieve_partner_from_purchase_order folder_open OCA/edi open_in_new
Uncategorised License: AGPL-3

Retrieves the partner from the related purchase order if set in UBL document

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

When a vendor bill is imported from a UBL e-invoice, this module fills in the vendor from the matching purchase order, so the bill is linked to the right supplier automatically.

This module improves the import of vendor bills from UBL electronic invoices (the standard XML format used for e-invoicing).

When Odoo reads such an invoice and the document mentions an origin reference, the module looks for a purchase order whose order number or vendor reference matches that origin, and which is in the confirmed or done state. If it finds one, the vendor on the bill is replaced by the vendor of that purchase order.

  • It works during the import of a UBL invoice into a bill form.
  • It only acts when the invoice carries an origin reference.
  • It searches purchase.order records by name or by vendor reference.
  • It only considers purchase orders that are confirmed or completed.
  • When a match is found, the bill's vendor is set from the purchase order.

There are no new menus, buttons, reports or settings: the change happens silently while importing the electronic invoice. It touches the electronic invoicing import logic for UBL 2.0 and the purchase order data, and it depends on the account_edi_ubl_cii and purchase modules.

Depends on

account_edi_ubl_ciipurchase

Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.