This release is a pre-release and may not be stable for production use.
Netherlands ICP Statement
This module extends the Netherlands BTW Statement module (BTW aangifte report), by adding the statement for the Intra-Community transactions declaration (ICP declaration).
The ICP declaration report is based on line 3b - Leveringen naar landen binnen de EU (omzet) of the BTW aangifte report. The period is also the same as the one selected in the BTW aangifte report.
This ICP declaration report includes:
the VAT identification numbers of your customers;
the total amount of intra-Community supplies from the Netherlands for every customer during the selected period.
Table of contents
Configuration
This module makes use of the tax tags “3b” and “3b diensten”.
If the default Odoo Dutch chart of accounts is installed (module l10n_nl) then “3b” tag is automatically present in the database. In this case you should add the “3b diensten” teg and set it into the tax definition.
If a non-standard chart of accounts is installed, you have to manually create the tax tags and properly set them into the tax definition. The name of the tags must be formatted this way: “+3b (omzet)”, “-3b (omzet)”, “+3b diensten (omzet)”, “-3b diensten (omzet)”.
Usage
To use this module, you need to:
Create a BTW Statement: a new tab ICP Statement will be displayed; the tab contains the lines of the ICP declaration report.
In tab ICP Statement press the Update button in order to recompute the ICP statement lines.
Printing a PDF report:
If you need to print the report in PDF, open a statement form and click: Print -> NL ICP Statement
Multicompany fiscal unit:
In case one single tax statement is created for companies belonging to a fiscal unit, the sum of the intra-Community supplies and services of all the companies will be written down in the totals of that tax statement.
After the fiscal unit tax statement is created and posted, for each of the companies belonging to a fiscal unit that trades intra-Community, create its own ICP report separately.
Known issues / Roadmap
Add checks to avoid errors in the report, e.g. no VAT code, tax-code not matching fiscal position, 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 to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Andrea Stirpe <a.stirpe@onestein.nl>
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/l10n-netherlands project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo14-addon-l10n-nl-tax-statement-icp 14.0.1.0.1.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 | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_l10n_nl_tax_statement_icp-14.0.1.0.1.dev6-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_l10n_nl_tax_statement_icp-14.0.1.0.1.dev6-py3-none-any.whl |
Release files / odoo14_addon_l10n_nl_tax_statement_icp-14.0.1.0.1.dev6-py3-none-any.whl
| Download URL | odoo14_addon_l10n_nl_tax_statement_icp-14.0.1.0.1.dev6-py3-none-any.whl |
|---|---|
| Size | 33.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
860da89573fc313727a98653e3b6e9e4c08b44e798677c0a70d2f662db581098
|
|
BLAKE2b-256 checksum How to use checksums |
4a0b19cfa0e58d7b18c8d9873f25896154cb16c9785c891c7709973f2c9205cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo14-addon-l10n-nl-tax-statement-icp 14.0.1.0.1.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.