Brazil: Document Types

Brazilian electronic fiscal documents implemented in the Gosocket + NDD integration:

Model	Type	Name	Main use	Flow	Status
55	NF-e	Nota Fiscal Eletrônica	Sale of physical goods. B2B operations.	📤 📥	🟢
57	CT-e	Conhecimento de Transporte Eletrônico	Freight transport. Issued by carriers.	📤 📥	🟢
58	MDF-e	Manifesto Eletrônico de Documentos Fiscais	Consolidates CT-es or NF-es into a transport manifest.	📤 📥	🟢
62	NFCom	Nota Fiscal de Serviço de Comunicação Eletrônica	Invoicing for communication and telecommunication services.	📤 📥	🟡
65	NFC-e	Nota Fiscal de Consumidor Eletrônica	Sales to the end consumer (B2C). Implementation via xPOS in progress.	📤	🟡
N/A	NFS-e	Nota Fiscal de Serviços Eletrônica	Services. Issued at the municipal level (no unified model).	📤 📥	🟢

Legend

📤 AR Process

Document issuance (sales)

📥 AP Process

Document reception (purchases)

🟢 Implemented

Document in production in Gosocket

🟡 In implementation

Document in development or testing stage

Technical notes

RPS format — every document is transformed into NDD's standard format called RPS (Recibo Provisório de Serviços) before being sent to the authority. It is not exclusive to NFS-e; it is NDD's input format regardless of the document type. The GUF/DTE → RPS transformation is performed by the XSLT.

NFS-e without a unified model — unlike NF-e, CT-e and MDF-e (which operate under the SEFAZ national model), NFS-e has no single schema: each municipality may be on the national environment (SEFAZ) or on its own legacy system (local environment). This is the reason the Municipality Availability document exists, and why the De/Para rules are especially relevant for NFS-e.