Purchase Force Invoiced Quantity
This module add a new “Force Invoiced” field to purchase order lines. This field is used as modifier when computing quantity to be invoiced.
Current behaviour: quantity to invoice = delivered - invoiced
Implemented behaviour: quantity to invoice = delivered - invoiced - force invoiced
Table of contents
Use Cases / Context
This module implements additional featured for the Purchase Force Invoiced module.
It covers the following scenarios:
One need to modify the quantity to be invoiced after the products were received. Eg .you negotiated an extra discount from your vendor.
You would like to fix some issues with quantities invoiced cause by incorrect data entry.
Configuration
No configuration is required.
Usage
Open a purchase order and add an amount into the “Force Invoiced” field. Amount to invoice will be adjusted accordingly. This field is optional so you can hide it if you don’t need it.
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
Ivan Sokolov
Dessan Hemrayev
Heliconia Solutions Pvt. Ltd. <https://www.heliconia.io>
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-quantity 18.0.1.1.1.4
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_quantity-18.0.1.1.1.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_purchase_force_invoiced_quantity-18.0.1.1.1.4-py3-none-any.whl |
Release files / odoo_addon_purchase_force_invoiced_quantity-18.0.1.1.1.4-py3-none-any.whl
| Download URL | odoo_addon_purchase_force_invoiced_quantity-18.0.1.1.1.4-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8aff7a4857d183d84712cf2bf87cfa4b467e5720e63f1cce5888faaa582736d1
|
|
BLAKE2b-256 checksum How to use checksums |
85f6606c924ab455853d9d523b4b7be34b4e05032520afa8d9a147e1e7adc106
|
| 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-quantity 18.0.1.1.1.4
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.
