Add an extra Company dimension on Invoices for consolidated Invoice Analysis
By default Customer and Supplier invoices can be linked to a contact within a company, but the company is not a direct reference in the database structure for invoices. Journal Entries are however always linked to the company and not to contacts, so that Accounts Payable and Receivable are always correct and consolidated at company level.
When many different contacts/departments need to be invoiced within the same parent company, this can make reporting by Company more difficult: reports are directly based on the database structure and would not provide an aggregated company dimension.
This modules solves the problem by adding an explicit company reference on invoices, automatically computed from the invoice contact, and use this new dimension when grouping the list of Invoices or the Invoice Analysis report by Partner.
Note: this module will likely be removed for the next major OpenERP version and directly integrated in the core accounting.
Metadata
Release files for openerp-account-report-company 7.0.406
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openerp-account-report-company-7.0.406.tar.gz | 10.3 kB | Without provenance | Details for openerp-account-report-company-7.0.406.tar.gz |
Release files / openerp-account-report-company-7.0.406.tar.gz
| Download URL | openerp-account-report-company-7.0.406.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db63e0fbe490c4b4c6c00ebf09c6d19d2c12e64b2be1a1833f57532f28eb36a6
|
|
BLAKE2b-256 checksum How to use checksums |
429576fc17639ca4093f7323cfb37881ecc0f87b4a4d7423b52bfd8364f5ea06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for openerp-account-report-company 7.0.406
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.