Electronic Ecuadorian Localization
The l10n_ec_account_edi module is a crucial component in the Odoo ecosystem, specifically tailored for businesses operating in Ecuador. This module facilitates Electronic Invoicing compliance with the requirements set forth by the Ecuadorian tax authorities. It streamlines the generation and management of electronic invoices, ensuring adherence to legal standards and promoting efficiency in billing processes.
Features
Electronic Invoice Generation: The module enables the automatic generation of electronic invoices in compliance with the Ecuadorian tax regulations. This includes the incorporation of required data fields and formats mandated by the tax authorities.
Digital Signature Integration: l10n_ec_account_edi integrates digital signature capabilities into the electronic invoicing process. This ensures the authenticity and integrity of the generated electronic invoices, meeting the legal requirements for electronic documents.
Automated Submission: The module streamlines the submission process of electronic invoices to the tax authorities’ systems. It automates the communication and transmission of invoice data, reducing manual intervention and minimizing errors.
Real-time Validation: Before submission, the module performs real-time validation checks to ensure that the generated electronic invoices comply with the current legal standards. This helps in identifying and rectifying issues proactively.
Known issues
The SRI authorization response field numeroAutorizacion normally equals the generated clave de acceso, so the module reuses the single l10n_ec_xml_access_key field instead of keeping a separate l10n_ec_authorization_number field. The SRI value is only persisted when it differs from the generated key (e.g. contingency). If a contingency flow ever returns a divergent authorization number, it overwrites the access key and that divergence is kept as a documented limitation.
Table of contents
Configuration
To set the RUC of the electronic system provider according to SRI Resolution NAC-DGERCGC26-00000027
Go to Invoicing > Configuration > Settings.
In the Ecuadorian Localization section, set the RUC Provider.
The SRI authorization number returned by the web service is stored automatically on each authorized electronic document, next to the authorization date. No manual configuration is needed
Go to Invoicing > Configuration > Ecuadorian SRI > XML Electronic Documents.
Check the Authorization Number(EC) column of the list, or open a document to see it in the form.
Usage
To effectively utilize the l10n_ec_account_edi module, follow these essential steps:
Electronic Signature Configuration:
Upload your electronic signature in the required .p12 format through the module’s configuration settings. Ensure that the provided electronic signature is valid and complies with Ecuadorian regulations.
- Navigate to Invoicing > Settings > Ecuadorian SRI > Electronic Signature Certs. - Upload your electronic signature file in .p12 format.Company Data Configuration:
Input and verify the company’s information, including addresses and RUC, to ensure accurate and compliant electronic invoice generation.
- Navigate to Settings > Companies > [Your Company]. - Update company details, addresses, and RUC information.Journal, Agencies, and Emission Points Configuration:
Configure the necessary accounting parameters such as journals, agencies, and emission points to align with your business structure and legal requirements.
- Navigate to Invoicing > Configuration > Accounting > Journals. - Set up relevant journals for electronic invoicing.General Settings:
In the Odoo settings for electronic invoicing, select the uploaded electronic signature and specify the environment (testing or production) for accurate invoice generation and submission.
By completing these configurations, your Odoo instance with the l10n_ec_account_edi module will be well-prepared for Electronic Invoicing in Ecuador,
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
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-account-edi 19.0.1.0.0.2
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 | Reset |
|---|---|---|---|---|
| odoo_addon_l10n_ec_account_edi-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_l10n_ec_account_edi-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_l10n_ec_account_edi-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 169.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
520d9464151362f5920f08393c70d7eec2d7fe06c90b943639933c0659f3991e
|
|
BLAKE2b-256 checksum How to use checksums |
a12942f6040a5b6d29ec308aa6455022ad9d57cf7ec9e29d56a83c566765a70b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-l10n-ec-account-edi 19.0.1.0.0.2
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.
