This release is a pre-release and may not be stable for production use.
Base Factur-X
This is the base module for the implementation of the Factur-X and ZUGFeRD standards. The standard Factur-X 1.0 is the same as ZUGFeRD 2.0 (the name Factur-X is always used in France, whereas in Germany many people still use the name ZUGFeRD). It is a standard based on CII (Cross-Industry Invoice) for electronic invoicing. The great idea of the Factur-X/ZUGFeRD standard is to embed an XML file inside the PDF invoice to carry structured information about the invoice.
Table of contents
Configuration
To configure this module, you need to:
go to the menu Sales > Configuration > Products > Units of Measures and check the UNECE Code for the units of measures.
go to the menu Invoicing > Configuration > Accounting > Taxes and, for each tax, set a UNECE Type Code and a UNECE Category Code.
go to the menu Invoicing > Configuration > Management > Payment Methods and assign a UNECE Code to the payment methods that are selected in the payment modes.
To avoid the manual configuration of taxes, look for a module l10n_XX_account_tax_unece in the OCA project of your localization; if such a module exists (it exists at least for the Netherlands and France), install it and it will auto-configure the taxes created by your localization.
Usage
This module doesn’t do anything by itself, but it is used by 2 other modules:
account_invoice_facturx that generate Factur-X 1.0 (i.e. ZUGFeRD 2.0) customer invoices/refunds,
account_invoice_import_facturx that imports ZUGFeRD 1.0 and Factur-X 1.0 (i.e. ZUGFeRD 2.0) supplier invoices/refunds.
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
Alexis de Lattre <alexis.delattre@akretion.com>
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/edi 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-base-facturx 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 | Reset |
|---|---|---|---|---|
| odoo12_addon_base_facturx-12.0.1.0.0.99.dev6-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo12_addon_base_facturx-12.0.1.0.0.99.dev6-py3-none-any.whl
| Download URL | odoo12_addon_base_facturx-12.0.1.0.0.99.dev6-py3-none-any.whl |
|---|---|
| Size | 26.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd60dd6040bd5db6b41734e9a62ab1985f83c9c34bcb66289fa3901e0749fd16
|
|
BLAKE2b-256 checksum How to use checksums |
504a7b10ea29b092de30b88d2b607c923e7177ee960863c758510aba62c37436
|
| 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-base-facturx 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.
