Sale invoice Policy
This module adds an invoicing policy on sale order level in order to apply that invoicing policy on the whole sale order.
That invoicing policy can take three values:
Products Invoicing Policy: The sale order will follow the standard behavior and apply the policy depending on products configurations.
Ordered Quantities: The sale order will invoice the ordered quantities.
Delivered Quantities: The sale order will invoice the delivered quantities.
Following the chosen policy, the quantity to invoice and the amount to invoice on each line will be computed accordingly.
You will be able also to define a default invoicing policy (globally per company) that can be different than the default invoicing policy for new products.
Table of contents
Use Cases / Context
In Odoo, products have their own invoicing policy that can be:
Invoicing on ordered quantities
Invoicing on ordered quantities
Following that configuration, when trying to create invoices from sale orders, each line of product will apply its invoicing policy.
In some cases, user needs to apply an invoicing policy on a whole sale order.
The solution proposed here is to add an invoicing policy on sale order level.
Configuration
Go to Sale > Configuration > Settings > Sale Invoice Policy
Choose the one that fits your needs.
Usage
Create Sale Order
Select Invoicing Policy on Sale Order or let it on Products Invoicing Policy
The created invoices will use the configuration on sale order.
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
Cédric Pigeon <cedric.pigeon@acsone.eu>
François Honoré <francois.honore@acsone.eu>
Denis Roussel <denis.roussel@acsone.eu>
Alexei Rivera <arivera@archeti.com>
Luis J. Salvatierra <luis.salvatierra@factorlibre.com>
Alejandro Ji Cheung <alejandro.jicheung@factorlibre.com>
Ioan Galan <ioan@studio73.es>
Laurent Mignon <laurent.mignon@acsone.eu>
Marie Lejeune <marie.lejeune@acsone.eu>
Jacques-Etienne Baudoux (BCIM) <<je.bcim.be>>
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/sale-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-sale-invoice-policy 19.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 | Reset |
|---|---|---|---|---|
| odoo_addon_sale_invoice_policy-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_sale_invoice_policy-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_sale_invoice_policy-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 40.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ec6e2a2ce3b829b19829ea0bf571a48ce818e69d7179575bd7b10965572631f
|
|
BLAKE2b-256 checksum How to use checksums |
5104626536f6c767f48cebbc3b0c5ca87c60a844793cfd046eae2c4c1110746e
|
| 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-sale-invoice-policy 19.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.
