If you run a Brazilian operation on ERPNext, the compliance gap shows up fast. ERPNext core models Sales Invoices, taxes, and the general ledger, but it has no concept of a Nota Fiscal Eletrônica, no SEFAZ web-service integration, and no way to emit the SPED Fiscal (EFD-ICMS/IPI) or SPED Contábil (ECD) files that Receita Federal expects. Teams end up rekeying every invoice into a separate emissor, reconciling ICMS/IPI/PIS/COFINS by hand, and assembling SPED blocks in spreadsheets — a slow, error-prone process that risks rejected notas and fiscal penalties.

ECOSIRE builds a dedicated Frappe app that closes that gap inside ERPNext itself. We add a proper module with DocTypes for the NF-e envelope, fiscal operation profiles (CFOP/CST/NCM mapping), and SEFAZ transmission logs, wired into your existing Sales Invoice through hooks.py doc events. When an invoice is submitted, a server-side handler builds the NF-e 4.00 XML, signs it with your A1/A3 certificate, transmits it to the correct state SEFAZ (or the SVC contingency environment), and stores the returned protocolo de autorização and chave de acesso back on the document. The authorized NF-e drives a print-format DANFE, and the same fiscal data feeds the SPED generators.

Technically the app is standard, upgrade-safe ERPNext engineering — no core patches. Tax logic lives in server scripts and Python methods that compute ICMS (including ST, DIFAL, and reduction bases), IPI, and PIS/COFINS by operation, so the numbers on the nota match the ledger. Whitelisted methods and the Frappe REST API expose emission, cancellation (carta de correção / cancelamento), and status-query endpoints for your other systems. Scheduler events poll pending authorizations and retry contingency batches. Role profiles and permission rules keep fiscal emission separate from accounting, and client scripts give operators a clean cockpit on the invoice for NF-e status, DANFE printing, and event history.

Because this is build-to-order, nothing ships until we understand your reality. We start with a scoping call to confirm your UFs, tax regime (Simples Nacional, Lucro Presumido, or Real), certificate type, product NCM/CFOP catalog, and which SPED blocks you must file. We then build against your ERPNext v15 or v16, validate in a SEFAZ homologação (test) environment, and run UAT on a staging copy of your data before touching production. Typical delivery is one working week from confirmed scope. You receive the full source, a git repository handover, and a post-go-live support window — you own the app and can extend it or hand it to another team at any time.