🇩🇴 Dominican Republic

This sheet assumes you know the xPOS-Core communication protocol. Here we only document what is specific to the Dominican Republic.

Summary

Aspect	Value
country code	do
Tax authority	DGII
Pattern	A — XML with XSD
Supported inputType	json, xml, txt
Extra endpoint	–
Output	Signed tax XML

XSLT mapping

XSLT	Use
input_to_dte_do.xslt	json and xml inputs → XML <root> → Gosocket XML.
other_to_dte_do.xslt	txt input → Gosocket XML. Does not go through input_to_dte.
dte_to_fiscal_do.xslt	Gosocket XML → DGII tax DTE.
custom_response_do.xslt	Generates custom_response when applicable.

Document types (typeDoc)

WebSocket example uses typeDoc=31.

typeDoc	Document
31	Electronic fiscal credit invoice
32	Electronic consumer invoice
33	Electronic debit note
34	Electronic credit note
41	Electronic purchases
43	Electronic minor expenses
44	Electronic special regimes
45	Electronic governmental
46	Electronic export voucher
47	Electronic voucher for payments abroad

Type 32 is dual: depending on the amount and the configuration it is issued as a full invoice or as a Summary (RFCE), with its own status-query path. Since version 2.7.0 each status is precisely associated with the corresponding document.

Dominican Republic-specific response fields

The Dominican Republic returns the entire core + full tax echo (statusCode/Description/Message) + applicationResponse + timeGeneration. It does not return timeValidation.

countryIdentificationCode in the Dominican Republic is the e-NCF (Electronic Tax Receipt Number).

WebSocket example

Illustrative values. The structure is real; the data are examples.

{
"env": "sbx",
"operation": "consolidate",
"typeDoc": 31,
"country": "do",
"inputType": "xml",
"origin": "<issuer taxId>",
"document": { /* DTE Republica Dominicana */ }
}

Particular notes

• Publishes in Inbox-Gosocket.
• The xdoc format is not available in the Dominican Republic; use json, xml or txt.

Changes in version 2.7.0

• Improved handling of the dual summary/invoice voucher (RFCE): each status is precisely associated with the corresponding document.
• Summary tracking automatically uses the correct provider according to the document type.
• Vouchers issued to recipients with a foreign identifier now come out with their query QR code and with status tracking before the DGII. Already-issued documents were valid: what was missing was the QR and the tracking.