This module is usefull if there are multiple companies in the same Odoo database and those companies sell goods or services among themselves. It allow to create an invoice in company A from an invoice in company B.
Imagine you have company A and company B in the same Odoo database. First scenario: company B create an invoice with company A as customer. The module will automate the generation of the supplier invoice in company A. Second scenario: company A create an invoice with company B as supplier. The module will automate the generation of the customer invoice in company B.
Table of contents
Configuration
To configure this module, you need to go to the menu Settings > General Settings, go to the tab Multi-Companies then check Multi-companies
You now have access to other checks Common Product Catalog and Invoice Auto Validation.
To customize products sharing don’t hesitate to override _compute_share_product() in res.company model.
Known issues / Roadmap
This module cannot be fully used in combination with remove_odoo_entreprise module. If you need both, uninstall remove_odoo_entreprise, complete settings with account_invoice_inter_company and then re-install remove_odoo_entreprise.
Product mapping: would be nice to have a matrix with the products on the left side and on the top row the companies.
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Odoo S.A. (original module inter_company_rules)
Andrea Stirpe <a.stirpe@onestein.nl>
Akretion <https://www.akretion.com>:
Chafique Delli <chafique.delli@akretion.com>
Alexis de Lattre <alexis.delattre@akretion.com>
David Beal <david.beal@akretion.com>
Tecnativa <https://www.tecnativa.com>:
Jairo Llopis
David Vidal
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.
This module is part of the OCA/multi-company 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 odoo12-addon-account-invoice-inter-company 12.0.2.1.3
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_account_invoice_inter_company-12.0.2.1.3-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_account_invoice_inter_company-12.0.2.1.3-py3-none-any.whl |
Release files / odoo12_addon_account_invoice_inter_company-12.0.2.1.3-py3-none-any.whl
| Download URL | odoo12_addon_account_invoice_inter_company-12.0.2.1.3-py3-none-any.whl |
|---|---|
| Size | 99.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56f3c676a178de631e48c87216eac66a0ac555469a480c60a090a7d92c764c4c
|
|
BLAKE2b-256 checksum How to use checksums |
c39de548f20ae1965ae9646f052d82d30367c068357384d93006d8ac24fff742
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-account-invoice-inter-company 12.0.2.1.3
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.
