| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4219 |
| Technical Name |
l10n_do_ecf_inbound |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
Dominican e-CF Inbound
DGII e-CF reception & Aprobacion Comercial (Ley 32-23) for Odoo 18 & 19
Receive supplier e-CF documents from the DGII, validate them, and send the Aprobacion Comercial (commercial approval or rejection) back — the receiver half of the Dominican Republic e-CF flow, built directly into Odoo.
Receive & parse supplier e-CF
Loads a received DGII ECF XML (Encabezado, Emisor, Comprador, Totales, DetallesItems) and normalises it into header parties, amounts and lines — whether uploaded by hand or pulled from the DGII inbox.
Aprobacion Comercial (ACECF)
Builds the DGII ACECF commercial-approval document (RNCEmisor, eNCF, RNCComprador, Estado) for both Aprobado and Rechazado, with the recognised DGII rejection reason codes, and an ARECF acuse de recibo.
Integrity checks before you approve
Validates the received e-NCF structure, the issuer and buyer RNC against the published DGII mod-11 check, confirms the document is addressed to your company, and recomputes the declared ITBIS and total from the line detail to catch tampering or errors.
Draft vendor bills automatically
Each received e-CF can spawn a draft vendor bill matched to the supplier RNC (the partner is created if needed), with the e-NCF carried as the bill reference for a clean audit trail.
Inbox polling & auto-approve
An optional scheduled job polls the DGII inbox for e-CFs awaiting a response, downloads and parses each one, and — when enabled — auto-approves the documents that pass every integrity check.
Bring-your-own-key transport
The DGII endpoints ship as editable defaults and authentication is BYOK: your token and certificate stay in your database. Built on the shared e-Invoice Core Engine, with no duplicated plumbing.
Compatible with Odoo 18 & 19
Disclosure: this module transmits commercial-approval data to the DGII endpoint you configure using credentials you provide (bring-your-own-key). Nothing is sent anywhere else.
Screenshots
Received Supplier E Cf E3100
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4219 |
| Technical Name |
l10n_do_ecf_inbound |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module