This release is a pre-release and may not be stable for production use.
Account Invoice ZUGFeRD
With this module, the PDF customer invoices and refunds generated by the Qweb reporting engine of Odoo will comply with the ZUGFeRD standard at Comfort level. The ZUGFeRD standard is a standard based on CII (Cross-Industry Invoice) for electronic invoicing. The great idea of the ZUGFeRD standard is to embed an XML file inside the PDF invoice to carry structured information about the invoice. So, with a ZUGFeRD PDF invoice :
no need to change your habbits and those of your customers: you can still send your PDF invoices by email as usual.
customers equiped with a modern accouting software will be able to import the invoice automatically as supplier invoice by taking advantage of the embedded XML file,
customers with an ancient accounting software will just open the PDF file with their PDF reader and manually encode the document as supplier invoice in their accounting software.
The PDF invoices generated by this module have been validated by the ZUGFeRD eInvoice validation portal and the validation system says that the invoices have 0 errors.
Installation
This module requires the Python library PyPDF2. To install it, run:
sudo pip install PyPDF2Configuration
You just need to do the configuration of the module base_zugferd (see the description of that module for more information).
Usage
On the form view of a customer invoice/refund, just click on the Print button as usual to get the ZUGFeRD-compliant PDF file.
Known issues / Roadmap
Add a hook in the _run_wkhtmltopdf() of the report module to embed the XML file inside the PDF file just after its generation and before it is saved as attachment (and do the same for the report_aeroo module) and try to have the related pull request accepted in Odoo. The current inherit of the get_pdf() is not good because it is not called when selecting the invoice from the attachment. In the meantime, you should always use the Print Invoice button to have a ZUGFeRD compliant file.
develop glue modules (or use hasattr() ?) to add to the XML file pieces of information that is carried out by fields defined in other modules such as sale or stock (customer order reference, incoterms, delivery address, etc…).
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.
Credits
Contributors
Alexis de Lattre <alexis.delattre@akretion.com>
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo8-addon-account-invoice-zugferd 8.0.1.0.0.99.dev13
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 |
|---|---|---|---|---|
| odoo8_addon_account_invoice_zugferd-8.0.1.0.0.99.dev13-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_account_invoice_zugferd-8.0.1.0.0.99.dev13-py2-none-any.whl |
Release files / odoo8_addon_account_invoice_zugferd-8.0.1.0.0.99.dev13-py2-none-any.whl
| Download URL | odoo8_addon_account_invoice_zugferd-8.0.1.0.0.99.dev13-py2-none-any.whl |
|---|---|
| Size | 36.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
122cebd9ec366ed9d15613d1f6d493f0a270f0aaf8eadfd1477c1cf730661790
|
|
BLAKE2b-256 checksum How to use checksums |
005cf3684f3b2b63bee5cec299b71f7d7c5dc1e4756418051b5d8ca50ecaa298
|
| 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 odoo8-addon-account-invoice-zugferd 8.0.1.0.0.99.dev13
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.
