The l10n_ec_withhold module is designed to facilitate the management of withholding taxes in the context of Ecuadorian localization. Withholding taxes play a crucial role in financial transactions, both in the procurement of goods and services (purchases) and the sale of products or services (sales). This module streamlines the process of handling withholding taxes, ensuring compliance with Ecuadorian tax regulations.
Table of contents
Usage
To effectively utilize the l10n_ec_withhold module, follow these essential steps:
Journal, Agencies, and Emission Points Configuration:
For each journal, specify whether it will be used for withholding taxes on purchases or withholding taxes on sales. This can be configured in the journal settings.
- Navigate to Invoicing > Configuration > Accounting > Journals. - Set up relevant journals for electronic withholding.XML Code Configuration in Taxes: In order to align with Ecuadorian tax reporting requirements, the module introduces a feature where users must configure XML codes for taxes. This ensures that the generated tax reports comply with the specified XML standards mandated by local tax authorities.
Tax Support Configuration: Users can now configure the “Tax Support” (tax justification) at both the line level and the invoice level. This flexibility allows businesses to provide detailed tax justifications for individual line items, enhancing transparency in tax documentation. Additionally, users have the option to set a global “Tax Support” at the invoice level, providing a comprehensive view of the tax justifications for the entire document.
Position Fiscal Activation for Withholding Taxes: To enable the withholding tax functionality seamlessly, users need to activate it in the fiscal position settings for both the supplier and the company. This ensures that the system takes into account the specific fiscal requirements related to withholding taxes during transactions with the designated supplier.
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
Leonardo Gomez (https://github.com/gomezgleonardob)
Ricardo Jara (https://github.com/rvjaraj)
Jorge Luis (https://github.com/mestizosdev)
Luis Romero (https://github.com/lojanet)
Carlos Lopez (https://github.com/celm1990)
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-ecuador 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-l10n-ec-withhold 17.0.1.0.1
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_l10n_ec_withhold-17.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_l10n_ec_withhold-17.0.1.0.1-py3-none-any.whl |
Release files / odoo_addon_l10n_ec_withhold-17.0.1.0.1-py3-none-any.whl
| Download URL | odoo_addon_l10n_ec_withhold-17.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 62.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1aaed394e3a3b688d8b789cdfe25342deffda2cd5db7d9692974ad881d73430
|
|
BLAKE2b-256 checksum How to use checksums |
3ee2c3c3efc338851a2fd00172c0e13c81c5b20c78b0b9f1fa87bb683f986391
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo-addon-l10n-ec-withhold 17.0.1.0.1
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.
