Purchase Company Invoice Address
This module lets you select, on each purchase order, the address of your own company to which the vendor should send the invoice, and prints it on the purchase order and request for quotation reports.
A company can already hold several addresses as child addresses of its partner, for example one invoice address per location, but a purchase order has no field to tell the vendor which of them to invoice, and its reports only show the company address in the header. This module adds that field: the company partner itself (the head office) or any of its invoice addresses can be selected per purchase order.
Table of contents
Configuration
To offer additional locations:
Go to Contacts and open the contact of your company.
In the Contacts & Addresses tab, create an address for the location and set its Address Type to Invoice Address.
Only the company itself and its invoice addresses can be selected on a purchase order. Once an invoice address exists it becomes the address proposed by default on new orders, while the company address stays selectable.
To print an invoice address in the vendor’s language, install report_partner_address and set up the address as described in its readme.
Usage
Go to Purchase > Orders > Purchase Orders and create an order.
Set Company Invoice Address to the address of your company the vendor should send the invoice to.
Print the order or the request for quotation. The address is shown next to the vendor address, unless it is the company’s own address, which the report header already carries.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Toshikimi Shigenobu
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/purchase-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-purchase-company-invoice-address 16.0.1.0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_purchase_company_invoice_address-16.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_purchase_company_invoice_address-16.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_purchase_company_invoice_address-16.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_purchase_company_invoice_address-16.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 29.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a854df8bf391f9369dd5a296b88964355cc88b01cbe2c692e8f5ce5928fd24df
|
|
BLAKE2b-256 checksum How to use checksums |
4101db4a96f683e55ed12b5acf5c1c4db81d4c090f582128be1b26269c766999
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-purchase-company-invoice-address 16.0.1.0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
