ERPNext Brazil NF-e / SPED Compliance

Key Features

NF-e 4.00 XML build and digital signing with A1 or A3 certificates, transmitted to the correct state SEFAZ web service

Automatic emission on Sales Invoice submit via a `hooks.py` `on_submit` doc event, with the chave de acesso and protocolo written back to the document

DANFE print format generated from the authorized NF-e, ready to print or attach as PDF

Cancelamento, Carta de Correção Eletrônica (CC-e), and inutilização events handled as tracked NF-e event records

ICMS calculation including Substituição Tributária (ST), DIFAL for interstate B2C, FCP, and base-reduction scenarios

IPI, PIS, and COFINS computation by CFOP/CST so nota totals reconcile to the ERPNext general ledger

Fiscal operation profiles: DocTypes mapping CFOP, CST/CSOSN, NCM, CEST, and origem per product and operation

SPED Fiscal (EFD-ICMS/IPI) file generation with blocks 0, C, E, and H populated from posted documents

SPED Contábil (ECD) file generation from the ERPNext chart of accounts and journal entries

SEFAZ contingency handling (SVC-AN/SVC-RS) with a scheduler event that polls and reconciles pending authorizations

Whitelisted methods and Frappe REST API endpoints for emit, cancel, and status-query from external systems

Role profiles and permission rules separating fiscal emission (fiscal operator) from accounting close (accountant)

Homologação (test) vs Produção environment switch driven by a single settings DocType, so testing never hits live SEFAZ

Structured transmission logs capturing every request/response XML for audit and SEFAZ reconciliation

Client scripts adding an NF-e status panel, DANFE button, and event timeline directly on the Sales Invoice form

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks 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.

What you get

Installable source code for the pinned Frappe/ERPNext version you run (v15 or v16), as a proper Frappe app

Installation and configuration on your environment, including certificate, SEFAZ endpoints, and fiscal-profile setup

Technical documentation: DocType reference, hooks, whitelisted methods, scheduler events, and CFOP/CST mapping model

End-user guide plus a live training session for your fiscal and accounting operators

UAT on a staging copy of your data with a documented rollback plan before production cutover

SEFAZ homologação validation covering emission, cancellation, and correction events

Post-go-live support window for defect fixes and SEFAZ-driven adjustments

Git repository handover with full history so you own and can extend the app

Who this is for

Fiscal / Tax Manager

Owns SEFAZ compliance and monthly SPED filing. Needs NF-e authorized correctly the first time and EFD/ECD files that pass validation, without rekeying invoices into a separate emissor.

ERPNext / Frappe Administrator

Runs the ERPNext instance and must keep it upgrade-safe. Wants Brazilian fiscal logic delivered as a clean Frappe app — DocTypes, hooks, scheduler events — with a git repo, not core patches they can't maintain.

Finance Controller / CFO

Responsible for accurate ICMS/IPI/PIS/COFINS treatment and a clean ledger. Needs the numbers on every nota to reconcile to ERPNext accounting and audit-ready transmission logs.

Operations / Billing Lead

Issues invoices daily and needs a simple cockpit on the Sales Invoice to emit NF-e, print DANFE, and handle cancellations without leaving ERPNext.

How ERPNext Brazil NF-e / SPED Compliance Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
NF-e SEFAZ integration	Built into ERPNext: signs and transmits NF-e 4.00 to the correct UF, writes protocolo back	Possible but you design SEFAZ handling from scratch	Often a generic connector needing heavy config	No NF-e concept at all
SPED Fiscal & Contábil	EFD-ICMS/IPI and ECD generated from posted ERPNext documents	Built to your spec if you have the fiscal expertise	Partial block coverage, may need manual assembly	Not generated
ICMS ST / DIFAL / PIS / COFINS	Computed per CFOP/CST, reconciled to the ledger	Depends entirely on your team's tax modeling	Common cases covered; edge cases often gaps	Standard tax templates only, no BR fiscal rules
Fit to your operations	Scoped to your UFs, regime, and NCM/CFOP catalog	Fully tailored but you carry all the risk	Configure to a fixed model, limited flexibility	Generic, not Brazil-specific
Upgrade safety	Clean Frappe app, no core patches, pinned to v15/v16	Varies with build discipline	Varies by vendor maintenance	Upgrade-safe but lacks the feature
Delivery	Build-to-order, typically 2–4 weeks from confirmed scope	Weeks to months depending on hiring and ramp	Fast to install, slow to fit	Immediate but incomplete
Ownership & source	Full source plus git repository handover — you own it	You own it and maintain it alone	Usually licensed, no source	Open source but no BR module
Support after go-live	Post-go-live support window plus optional maintenance	Whatever you staff internally	Vendor support tiers, variable responsiveness	Community only

Frequently Asked Questions about ERPNext Brazil NF-e / SPED Compliance

Is this an existing app I can download and install today?

No. This is a build-to-order engagement. ECOSIRE designs, builds, installs, and supports the app on your ERPNext instance after we confirm scope — it is not an off-the-shelf Frappe Marketplace download.

How long does delivery take?

Typically 2–4 weeks from confirmed scope. The exact timeline depends on how many UFs you operate in, your tax regime, the size of your NCM/CFOP catalog, and which SPED blocks you must file. The scoping call sets the concrete schedule.

Which ERPNext versions do you support?

Frappe/ERPNext v15 and v16. We build and pin against the exact version and site you run so the app is upgrade-safe, with no modifications to ERPNext core.

How does it connect to SEFAZ, and do I need a certificate?

The app builds and signs the NF-e 4.00 XML with your A1 or A3 digital certificate and transmits directly to the correct state SEFAZ web service, including SVC contingency. You provide the certificate; we configure the endpoints and homologação testing.

Do ICMS ST, DIFAL, and the SPED files come standard?

Tax logic is scoped to your operations. ICMS (including ST, DIFAL, FCP, and base reductions), IPI, and PIS/COFINS are computed per CFOP/CST, and we generate SPED Fiscal (EFD-ICMS/IPI) and SPED Contábil (ECD). We confirm the exact blocks and scenarios you need during scoping.

What about support and updates after go-live?

Every engagement includes a post-go-live support window for defect fixes and SEFAZ-driven adjustments. Because you receive the full source and git repository, you can also extend it in-house or contract ongoing maintenance with ECOSIRE.

Do we own the code?

Yes. You get installable source code and a full git repository handover for the version you run. The app is yours to keep, extend, or hand to another team.