This release is a pre-release and may not be stable for production use.
L10n EU OSS
This module has been created to help with the tax mapping according to the EU One-Stop-Shop law, that concerns many companies that carry out distance sales.
Table of contents
Configuration
To configure this module, you need to:
Go to Invoicing > Configuration > Settings > Taxes.
You can see that user can choose Add new taxes for applying EU taxes regarding OSS.
Select the company where you want to add these new taxes.
Select the EU countries where you can send your goods.
Select if you want these new taxes to be configured as included in price.
Select the general, reduced, super reduced and second super reduced taxes according your accounting plan.
Remember that you shouldn’t configure unexisting taxes for your accounting plan.
Click Create Fiscal Positions and Taxes button to continue.
According your configuration, new taxes and fiscal positions will be created.
NOTE: You should use account_fiscal_position_partner_type module configuration for making the workflow easier.
Usage
After the corresponding configuration of this module:
Create a new partner and assign an EU country (different from the one set in your company).
Check that this new partner has been configured as a Customer in Fiscal Position Type field.
Create a new product and set its taxes.
Create a new Quotation for the customer and add the new product in a sale order line.
User will see that taxes will be set according the delivery address country taxation.
You can create directly an invoice without starting from a SO and the pertinent taxes will be applied as well.
Known issues / Roadmap
This module doesn’t take into account if one or more products have different type of taxes in the destination contry.
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
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/account-fiscal-rule 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 odoo11-addon-l10n-eu-oss 11.0.1.0.0.99.dev3
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 |
|---|---|---|---|---|
| odoo11_addon_l10n_eu_oss-11.0.1.0.0.99.dev3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_l10n_eu_oss-11.0.1.0.0.99.dev3-py2.py3-none-any.whl |
Release files / odoo11_addon_l10n_eu_oss-11.0.1.0.0.99.dev3-py2.py3-none-any.whl
| Download URL | odoo11_addon_l10n_eu_oss-11.0.1.0.0.99.dev3-py2.py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8eccd1c05927fdacdb7731d54e41998d35d0ac47e49c9b2757f5047dad03fef2
|
|
BLAKE2b-256 checksum How to use checksums |
b1396e304fc0a79e7ed41d052ff9333feb56b622e31f529c775066f5bc648084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo11-addon-l10n-eu-oss 11.0.1.0.0.99.dev3
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.
