Optional validation of VAT via VIES
This module extends base_vat module features allowing to know if VIES validation was passed or not.
Then you can use “VIES validation passed” field in order to show VAT ID with or without country prefix in invoices, for instance.
NOTE: Although VIES validation is set in your company, this validation will not block VAT ID write (main difference to Odoo standard behavior) if this VAT ID is valid in its country.
Table of contents
Configuration
In order to activate VIES validation, you must set this option in Settings: Settings > Account > Verify VAT Numbers
Usage
When VIES VAT Check is activated:
Odoo will try to validate VAT against VIES online service
If passed, then “VIES validation passed” field will be True
If not passed, then try to validate using country validation method
If validated, then “VIES validation passed” field will be False
If not validated, then a ValidationError will be shown to user
When VIES VAT Check is not activated:
“VIES validation passed” field will be always False
You must prefix VAT with country code (ISO 3166-1 alpha-2) and if you want to bypass country validation you can use “EU” code
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
Rafael Blasco <rblasco@moduon.team>
Antonio Espinosa <antonio.espinosa@tecnativa.com>
Sergio Teruel <sergio.teruel@tecnativa.com>
David Vidal <david.vidal@tecnativa.com>
Rodrigo Bonilla <rodrigo.bonilla@factorlibre.com>
Alexandre Díaz <alexandre.diaz@tecnativa.com>
Harald Panten <harald.panten@sygel.es>
Eduardo de Miguel <edu@moduon.team>
Emilio Pascual <emilio@moduon.team>
Jairo Llopis (Moduon)
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 maintainers:
This module is part of the OCA/account-financial-tools 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 odoo-addon-base-vat-optional-vies 16.0.1.1.1.5
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 |
|---|---|---|---|---|
| odoo_addon_base_vat_optional_vies-16.0.1.1.1.5-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_base_vat_optional_vies-16.0.1.1.1.5-py3-none-any.whl |
Release files / odoo_addon_base_vat_optional_vies-16.0.1.1.1.5-py3-none-any.whl
| Download URL | odoo_addon_base_vat_optional_vies-16.0.1.1.1.5-py3-none-any.whl |
|---|---|
| Size | 36.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3585118581de09452ac83954a3ba6911f7c12e6f48d21151e985c49c022b126
|
|
BLAKE2b-256 checksum How to use checksums |
010e6dd0da8c6eb1e0eb5caae65475d90c0085734674c1eb80a1546e606218ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-base-vat-optional-vies 16.0.1.1.1.5
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.
