Skip to main content

How does the NDD integration work?

NDD Space acts as a mandatory fiscal middleware between Gosocket and Brazilian tax authorities (SEFAZ and Prefeituras). Gosocket generates the document in its standard format (GUF/DTE), sends it to NDD, and NDD handles the transformation, validation and submission to the appropriate authority.


The transformation chain​

Every document passes through this chain before reaching the tax authority:

Each step has a specific responsibility:

GUF / DTE
Gosocket's generic integration format. The issuer builds the document once using this format; Gosocket and NDD handle the rest.
XSLT
Technical transformation from GUF to the NDD intermediate RPS format. NDD applies the SetNFe, SetCTe or SetMDFe stylesheets according to the document type.
De/Para rules
Field mapping specific to each municipality and TaxID. Adapts the standard format to the particularities of each Prefeitura.
NDD Space
Middleware that validates schema and digital signature, manages retries and returns the approved XML (with the tax authority access key) to Gosocket.

Two directions: issuance and reception​

The integration operates in both directions of the tax document.


Reception: two entry routes​

Reception in Brazil has a particularity compared to other countries: it requires activation in NDD Space to work.

Inbox / Upload
The supplier sends the XML directly to the Gosocket inbox. Requires a forwarding email configured on the recipient TaxID. Up to 10 retries within 30 minutes.
Periodic synchronization
NDD actively queries available documents for the TaxID every 4 hours. New documents appear in Inbox marked as "Synced from NDD".
Mandatory activation in NDD Space

Each customer (TaxID) must be activated in the NDD Space portal before starting the integration. Without this activation, reception stops at Status 5 (Error) and issuance cannot proceed.


Document lifecycle​

The document status can be queried at any time with GetDocument, and subsequent events (cancellation, correction letter) are executed with ChangeDocumentStatus.