This release is a pre-release and may not be stable for production use.
Sales order invoicing grouping criteria
This module allows to use custom criteria for grouping sales orders to be invoiced.
Default criteria for grouping (invoicing partner and currency used) will be always applied, as if not respected, there will be business inconsistencies, but you can add more fields to split the invoicing according them.
Table of contents
Configuration
For creating new grouping criteria:
Go to Invoicing > Configuration > Management > Invoicing Grouping Criteria.
Create or modify existing criteria, selecting fields belonging to “Sales Order” header model for grouping according them.
Invoicing address and currency will always be applied with the selected ones.
For setting a different grouping criteria for a specific customer:
Go to Invoicing > Sales > Master Data > Customers.
Open the desired customer.
Go to Invoicing page.
Set on “Sales Invoicing Grouping Criteria” the desired grouping criteria.
For setting a different default grouping criteria than the standard for the whole company:
Go to Invoicing > Configuration> Settings.
Locate inside “Sales Order Invoicing” section, the field “Default Grouping Criteria”.
Introduce there the grouping criteria to be applied by default. If empty, the general default of invoicing address + currency will be applied.
Usage
Go to Sales > Invoicing > Orders to Invoice.
Select sales orders whose invoicing you want to do.
Click on Action > Invoice Order.
Click on “Create and View Invoices” button.
On that moment, the grouping criteria will be applied, and you will see different invoices if the criteria doesn’t match for them.
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
-
Pedro M. Baeza
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/account-invoicing project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo12-addon-sale-order-invoicing-grouping-criteria 12.0.1.0.0.99.dev6
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 |
|---|---|---|---|---|
| odoo12_addon_sale_order_invoicing_grouping_criteria-12.0.1.0.0.99.dev6-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_sale_order_invoicing_grouping_criteria-12.0.1.0.0.99.dev6-py3-none-any.whl |
Release files / odoo12_addon_sale_order_invoicing_grouping_criteria-12.0.1.0.0.99.dev6-py3-none-any.whl
| Download URL | odoo12_addon_sale_order_invoicing_grouping_criteria-12.0.1.0.0.99.dev6-py3-none-any.whl |
|---|---|
| Size | 35.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
581505a48493a86fec99f662bdbfc8f8b86b9388f491f22acee5c95ddf5014cf
|
|
BLAKE2b-256 checksum How to use checksums |
8a7d24225d084108ad9b4804dcb797dc2f0e1b288d70b78b506cd9f3a0db1e1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo12-addon-sale-order-invoicing-grouping-criteria 12.0.1.0.0.99.dev6
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.