Idoo CFDI — Mexican CFDI 4.0 e-Invoice Stamping via idoo.de

How it works

This module does not build or sign XML locally and does not manage CSD certificates on disk. The entire construction of the voucher, signing with the CSD, and stamping with the PAC are completely delegated to the idoo.dev service via POST /v1/facturas/timbrar_arreglo: the module builds a JSON from the Dolibarr invoice, sends it, and saves what the API returns (UUID, XML, PDF).

Registering the issuer's CSD is also done from the module (Modules > Idoo CFDI > Configure issuer CSD), but the .cer/.key files are never persisted in Dolibarr: they are read from PHP's temporary upload, base64-encoded, sent via HTTPS to POST /v1/emisores/subir_csd, and immediately discarded from memory.

Installation

• Copy the idoocfdi/ folder to htdocs/ (or to htdocs/custom/ if installed as an external module).

• Activate the module from Home > Setup > Modules/Applications.

• Go to Modules > Idoo CFDI > Setup: Choose environment (sandbox or production) and enter the corresponding API Key (obtained from the idoo.dev portal at /portal/apikeys).

• Enter the issuer's RFC, legal name, tax regime, and issuance postal code.

• Go to Configure issuer CSD and upload the CSD's .cer/.key/password.

• For each third party that will receive a CFDI, fill in their tax data — the module reuses native Dolibarr fields whenever they exist, instead of duplicating them:

  • RFC: in the native "Prof. ID 1" field on the third-party card (the module relabels it as "RFC" for Mexican third parties upon activation).

  • Postal code: the third party's address field (Zip Code) is used as the fiscal address. If the customer's fiscal address is different from their address in Dolibarr, adjust the Zip Code before stamping.

  • Tax regime: the native "Type of legal entity" (fk_forme_juridique) field of the third party is used — Dolibarr already comes preloaded with the SAT's 19 tax regimes for Mexico in that catalog (Setup > Dictionaries > Legal forms), so you don't need to enter it twice.

  • Default CFDI Usage: in the third party's extra fields tab (this one is specific to the module and has no native Dolibarr equivalent).

• For each product, fill in the SAT Product/Service Code and SAT Unit Code (if left blank, the module's default configuration will be used, with the risk that the SAT will reject the CFDI if that default does not apply to the actual product).

• Grant permissions to users who will stamp/cancel invoices (Home > Users & Groups > (user) > Permissions) — by default, only read/consult permission is enabled; stamping and canceling are fiscally sensitive permissions that must be explicitly enabled.

Scope of this version (v1)

Standard Dolibarr "Invoice" (Income) type only, MXN currency, no line discounts, with transferred VAT (16%/8%/0%) per line. Supported actions: stamp, check status, regenerate PDF, cancel.

Out of scope (roadmap)

• Credit notes / related egress (type E)

• Payment complement (REP / PPD)

• Global invoice (point of sale)

• Foreign trade / waybill (carta porte) / addendas

• Multi-issuer (multiple RFCs in the same installation)

• Complete SAT Product/Service and Unit codes catalog with search functionality (currently free-text fields per product)

• IEPS tax and ISR/VAT withholdings

• Line discounts

• Foreign currency with exchange rate

• Module's own REST API (currently interface buttons only)

Security

• The API Key lives solely in llx_const (module constants), never in extrafields or in code.

• The CSD never touches Dolibarr's disk or database.

• Each API call is logged in llx_idoocfdi_facturas_log to allow debugging SAT rejections without re-issuing the call, but these records never include the CSD, CSD password, API Key, or XML/PDF binaries (which are already saved as invoice attachments).

Support

This module is part of Idoo's services.