🇩🇴 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, xdoc, 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.
xdoc_to_dte_do.xslt	xdoc 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.

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.