This release is a pre-release and may not be stable for production use.
Netherlands ICP Statement (apart from BTW)
This module allows users to manage ICP statements separately from BTW statements.
This is useful when the reporting intervals for both differ, ie BTW quarterly, but ICP monthly. As a side effect, misconfigured partners wrt ICP won’t hold off creating BTW statements.
Table of contents
Use Cases / Context
For developers
Most of what this addon does is copying the original vat statement model to a new model l10n.nl.icp.statement, and adapting one2many fields such that they point to this new model. In order to do so, new many2one fields have to be added to all the referenced models, like account.move or account.move.line. The rest is using various techniques to make the code of the original model work on the newly added fields instead of the original ones.
So when migrating this module, watch out for one2many fields being added to the l10n.nl.vat.statement model, they most likely will need to be adapted in the ICP model. Also check that the overrides meant to change actions on l10n_nl_vat_statement_id to l10n_nl_icp_statement_id are still functional and needed.
Usage
To use this module, you need to:
Go to Accounting/Reporting/NL ICP statement
Handle the same way you’d handle a BTW statement
Note there will be an extra column “Error” if some partner is misconfigured for ICP and you won’t be able to post/finalize the statement until you’ve corrected the errors
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
Holger Brunn <mail@hunki-enterprises.com> (https://hunki-enterprises.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.
Current maintainer:
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-l10n-nl-tax-statement-icp-split 14.0.1.0.1.dev2
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_split-14.0.1.0.1.dev2-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_l10n_nl_tax_statement_icp_split-14.0.1.0.1.dev2-py3-none-any.whl |
Release files / odoo14_addon_l10n_nl_tax_statement_icp_split-14.0.1.0.1.dev2-py3-none-any.whl
| Download URL | odoo14_addon_l10n_nl_tax_statement_icp_split-14.0.1.0.1.dev2-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc97fa1d784245d16abaa3fa21b29945a496823caca434cf2583c1bf48d56658
|
|
BLAKE2b-256 checksum How to use checksums |
f5d0f2a4ec1b7fa11016665892c149bd4cf6521ef4656fc6cdbc5202ab8b6dda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-l10n-nl-tax-statement-icp-split 14.0.1.0.1.dev2
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.
