DGII Dominican Republic — Electronic invoicing (e-CF)

Overview

The DGII nodes connect your workflows to the Dominican Republic’s electronic invoicing (DGII, e-CF). The e-CF is an XML signed with XMLDSig (digital certificate). Submission requires a token obtained through a 3-step flow: request a seed, sign it and validate it. With the token the e-CF is sent to reception, which returns a TrackId; the status (Accepted / Rejected) is queried separately.

Node	What it does
DGII: Issue invoice (dgiiEmitirFactura)	Tax Credit Invoice (31) or Consumer Invoice (32)
DGII: Credit/Debit note (dgiiEmitirNota)	Debit Note (33) or Credit Note (34)
DGII: Query status (dgiiConsultarEstado)	Queries an e-CF’s status by its TrackId
DGII: Rendering / QR (dgiiRepresentacion)	Generates the printed representation (RFCE) with QR

The e-CF is XML signed with XMLDSig and uses a TrackId

The document is an XML signed with an XMLDSig signature (digital certificate). Authentication is a 3-step flow (seed → signature → token). Submission does not give the final result: it returns a TrackId, and the status is queried afterward (Accepted, Rejected, ConditionallyAccepted, InProcess). The security code is the first 6 characters of the signature. The e-NCF has 13 characters: E + type(2) + sequence(10). The general ITBIS rate is 18%.

Credential

The nodes use a credential of type DGII. Create it under Credentials → Add → Dominican Republic / DGII with:

Field	Description
Issuer RNC	The national taxpayer registry number.
Digital certificate (.p12)	With its password; used to sign and authenticate.
Legal name / Trade name	Issuer details.
Address, municipality, province	Issuer location.
Environment	Test (TesteCF), Certification (CerteCF) or Production (eCF).

Issue an invoice (31 / 32)

Node: DGII: Issue invoice. precioUnitario values are without ITBIS; Floogos computes the ITBIS (18%) and totals. The Tax Credit Invoice (31) requires the buyer’s RNC; the Consumer Invoice (32) does not.

{
  "tipo": "31",
  "comprador": { "rnc": "101023122", "razonSocial": "B2B Client SRL" },
  "items": [
    { "descripcion": "Consulting service", "cantidad": 1, "precioUnitario": 100 }
  ]
}

The node returns the e-NCF, the TrackId, the security code and (by default) queries the status once.

Credit and debit notes (33 / 34)

Node: DGII: Credit/Debit note. The note references the origin e-NCF via informacionReferencia:

{
  "tipo": "34",
  "comprador": { "rnc": "101023122", "razonSocial": "B2B Client SRL" },
  "informacionReferencia": { "ncfModificado": "E310000000001", "fecha": "2026-07-29", "codigoModificacion": 1 },
  "items": [ { "descripcion": "Return", "cantidad": 1, "precioUnitario": 30 } ]
}

codigoModificacion: 1 voids the referenced receipt, 2 corrects text, 3 corrects amounts.

Query the status

Node: DGII: Query status. Queries an e-CF by its TrackId and returns the status (Accepted, Rejected, ConditionallyAccepted, InProcess). Useful when reception stayed InProcess.

Printable rendering (QR)

Node: DGII: Rendering / QR. Generates the printable rendering in HTML (exportable to PDF), with the e-NCF, the security code and the QR pointing to the DGII’s stamp lookup.

Error handling

Situation	Retryable	What to do
DGII rejects (Rejected)	No	The node returns the messages. Fix the e-CF.
Expired certificate	No	Renew the .p12 and update the credential.
Auth (seed/token)	No	Check the certificate and the environment.
Network / Timeout	Yes	Transient; automatically retried.

DGII sandbox

Always test in TesteCF / CerteCF before production, and validate the XML structure against the DGII’s official XSD. The full XAdES signature (QualifyingProperties) must be validated against the test environment.

See also

• Retry queue (DLQ) — how failed executions are retried.
• HTTP node — for services not covered by these nodes.