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
Update date: 2026-07-02