Purchase Force Invoiced
This module adds the possibility for users to force the invoice status of the purchase orders to ‘Fully Billed’, even when not all the quantities, ordered or delivered, have been invoiced.
This feature is useful in the following scenario:
The supplier disputes the quantities to be billed for, after the products have been delivered to her/him, and you agree to reduce the quantity to invoice (without expecting a refund).
When migrating from a previous Odoo version, in some cases there is less quantity billed to what was delivered, and you don’t want these old purchase orders to appear in your ‘Waiting Bills’ list.
Table of contents
Usage
Create a purchase order and confirm it.
Receive the products/services.
Create a vendor bill and reduce the invoiced quantity. The purchase order invoicing status is ‘Waiting Bills’.
Lock the Purchase Order and change its status to ‘Done’.
Check the field ‘Force Invoiced’.
The field is only visible for users that have the technical setting ‘Set purchase orders to Force Invoiced’. By default, all purchase managers have this setting.
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
Jordi Ballester <jordi.ballester@forgeflow.com>
Rattapong Chokmasermkul <rattapongc@ecosoft.co.th>
Bert Van Groenendael <bert.vangroenendael@dynapps.eu>
Stefan Rijnhart <stefan@opener.amsterdam>
Arantxa Gandia <arantxa@studio73.es>
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.
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-force-invoiced 19.0.1.0.1.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_force_invoiced-19.0.1.0.1.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_purchase_force_invoiced-19.0.1.0.1.2-py3-none-any.whl |
Release files / odoo_addon_purchase_force_invoiced-19.0.1.0.1.2-py3-none-any.whl
| Download URL | odoo_addon_purchase_force_invoiced-19.0.1.0.1.2-py3-none-any.whl |
|---|---|
| Size | 34.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8dd62f75a75230ddc7681e85a7820f386ff4d84fba8a1301304e14aac1c9d3df
|
|
BLAKE2b-256 checksum How to use checksums |
ba35d3a0ef5fc9b8a14761b9b54d16ac0649449a9ba2f4f10e55e39d9e079e8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-purchase-force-invoiced 19.0.1.0.1.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.
