NFS-e (Nota Fiscal de Serviços eletrônica) has special handling: validation is municipal (Prefeituras), processing time is longer, and Inbox behaviour differs from CT-e and NF-e.
Participants
| Actor | Role |
|---|
| Suppliers | Send documents in XML format to the Inbox email inbox |
| Gosocket | Electronic document exchange platform |
| NDD | Intermediary between Gosocket and municipal Prefeituras |
| Prefeituras | Local government entities responsible for validating NFS-e |
Flow steps
- Submitted by suppliers — Suppliers send XML to the Inbox email inbox. PDF processing is not currently implemented (depends on NDD OCR activation; to be considered in the future).
- Received by Gosocket — Gosocket receives the XML. Documents are not processed in Inbox at this stage.
- Forwarded to NDD — Gosocket sends the XML to the NDD NFS-e inbox for processing. This inbox is configured in Inbox for each recipient TaxID.
- Processing in NDD — NDD converts the XML to NFS-e format. (PDF conversion via OCR is a future implementation.)
- Storage and processing in NDD — NDD stores the documents and sends them to local Prefeituras for validation. Processing time ranges from 8 to 72 hours.
- Gosocket periodic query — Gosocket queries NDD every hour. Available documents are stored in Inbox and their receipt is confirmed to NDD.
Critical differences from CT-e and NF-e
| CT-e / NF-e | NFS-e |
|---|
| Tax authority | SEFAZ (national) | Prefeitura (municipal) |
| Sync cadence | every 4 h | every 1 h |
| Statuses saved in Inbox | All | Approved and Cancelled only |
| Documents in Error | Saved in Inbox | Not saved |
| Manual reprocessing from Inbox | ✅ Available | ❌ Not available |
| Event processing | 5 types (Cancelamento, Ciência, etc.) | Not applicable |