Brazil NFe / Fiscal Compliance for Business Central

Recursos Principais

NF-e (model 55) and NFC-e (model 65) XML assembly, digital signing, and transmission to the SEFAZ authorization web services with full rejection-code handling

NFS-e service-invoice issuance routed to the relevant municipal web service, with per-municipality layout handling

DANFE and DANFE-NFC-e PDF generation for printing, email, and customer delivery

SEFAZ contingency modes (offline/SVC) so issuance continues during authorizer downtime, with automatic re-transmission when the service recovers

Complete Brazilian tax engine: ICMS (including ST, DIFAL, FCP), IPI, PIS, COFINS, and municipal ISS, calculated per transaction

CFOP and NCM mapping on items and operations driving correct fiscal treatment by origin/destination state and operation type

Table and page extensions on Item, Customer, Vendor, and Tax Setup for fiscal master data (CEST, tax origin, fiscal classification)

SPED Fiscal (EFD-ICMS/IPI) and SPED Contribuições (EFD-PIS/COFINS) period export in the accountant-ready layout

Cancellation, correction letter (CC-e), and inutilization (number-range void) flows against SEFAZ

Asynchronous SEFAZ communication via BC job queue entries with retry, status polling, and error logging

Event subscribers hooked into the standard sales/service posting flow so fiscal documents fire on Post without changing user workflow

Dedicated permission sets and BC REST/OData endpoints exposing fiscal document status to Power BI and Power Platform

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

Microsoft Dynamics 365 Business Central does not ship native Brazilian fiscal localization, which leaves Brazilian operations unable to issue legally valid electronic invoices or meet SPED obligations out of the box. ECOSIRE builds this gap closed as a per-tenant AL extension installed directly on your Business Central environment (cloud SaaS or on-premises), not a generic AppSource download you self-configure.

The extension wires Brazil's fiscal document lifecycle into BC's standard posting flow. Posting a sales invoice triggers an event subscriber that assembles the NF-e/NFC-e XML, signs it, and transmits it to the relevant SEFAZ web service, then handles the authorization protocol, rejection codes, and contingency (offline) modes. Service invoices route to the appropriate municipal NFS-e webservice. We generate the DANFE/DANFE-NFC-e PDF for printing and customer delivery.

Brazilian tax complexity — ICMS (including ST, DIFAL, and FCP), IPI, PIS, COFINS, and municipal ISS — is modelled through table and page extensions on items, customers, and tax setup, with CFOP and NCM mapping driving the correct fiscal treatment per transaction and origin/destination state. Period-end SPED Fiscal (EFD-ICMS/IPI) and SPED Contribuições (EFD-PIS/COFINS) files export in the layout your accountant submits.

Everything is delivered with dedicated permission sets, job-queue entries for asynchronous SEFAZ communication and retries, and BC REST/OData endpoints so issuance status is visible to Power BI or a Power Platform flow. Because tax rules and SEFAZ layouts change frequently, we scope an honest build lead time and a maintenance arrangement to keep you compliant as legislation shifts. You own the source; we keep it running.

O que você ganha

A per-tenant Business Central AL extension (.app) installed on your environment — sandbox first for UAT, then production

Source code for the extension handed to you, with the AL project structure and build instructions

Configured fiscal master data and tax setup: CFOP/NCM mapping, ICMS/IPI/PIS/COFINS/ISS rules, and SEFAZ/municipal endpoint configuration for your states and municipalities

Digital certificate (A1/A3) integration configured for SEFAZ signing within your environment

Permission sets, job-queue setup for SEFAZ transmission, and OData endpoint configuration

Admin and finance-user documentation plus a handover/training session, with a defined post-go-live support and maintenance window

Para quem é isso

Fiscal / Tax Analyst (Analista Fiscal)

Owns NF-e issuance, CFOP/NCM correctness, and SPED submission. Needs documents to authorize at SEFAZ on the first attempt and the SPED files to validate without errors at period close.

Finance Controller of a Brazilian operation on BC

Runs Business Central for a Brazilian entity or subsidiary and needs legally valid fiscal documents and tax compliance without bolting on a separate Brazilian ERP.

IT / BC Administrator

Responsible for the BC environment, extension deployment, certificate management, and the job queue. Wants a clean per-tenant extension they can manage and update rather than unsupported custom code.

Como Brazil NFe / Fiscal Compliance for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
NF-e / NFC-e / NFS-e issuance to SEFAZ built into BC posting flow	Incluído	Suporte parcial	Incluído
Complete Brazilian tax engine (ICMS/ST/DIFAL, IPI, PIS, COFINS, ISS)	Incluído	Suporte parcial	Incluído
SPED Fiscal and SPED Contribuições export in accountant-ready layout	Incluído	Suporte parcial	Suporte parcial
Built, installed, and supported by the vendor on your environment	Incluído	Não incluído	Suporte parcial
Source code ownership and no per-document/per-seat lock-in	Incluído	Incluído	Não incluído
Tailored to your exact states, municipalities, and tax scenarios	Incluído	Incluído	Suporte parcial
Ongoing maintenance for SEFAZ layout and legislation changes	Incluído	Não incluído	Incluído

Perguntas frequentes sobre Brazil NFe / Fiscal Compliance for Business Central

How long does delivery take, and is this an instant AppSource download?

No — this is a build-to-order extension, not an instant AppSource install. After we confirm your scope (states, municipalities for NFS-e, NF-e vs NFC-e, tax regimes), we build and configure the extension, install it to your sandbox for UAT, then promote to production. A typical engagement runs a few weeks depending on how many municipalities and tax scenarios are in scope; we give you a firm timeline before work starts.

What happens with ongoing support and updates after go-live?

Brazilian fiscal rules, SEFAZ XML layouts, and SPED schemas change regularly. We include a post-go-live support window and offer an ongoing maintenance arrangement that keeps the extension aligned with layout/legislation changes, BC version upgrades, and any new states or municipalities you add. You own the source code, so you are never locked in.

Does this work on Business Central cloud (SaaS) and on-premises?

Yes. It is delivered as a per-tenant AL extension and works on BC SaaS and on-premises. SEFAZ communication and certificate handling are configured to fit your deployment model — for SaaS we use the supported AL/HTTP and certificate-handling patterns; for on-prem we adapt to your network and certificate store.

Can it issue NFC-e for retail/POS as well as NF-e?

Yes. We build NF-e (model 55) for standard sales, NFC-e (model 65) for consumer retail with its DANFE-NFC-e output, and NFS-e for services. Which models you need is part of scoping, since each has its own SEFAZ/municipal endpoint and contingency behavior.

How does it handle the complex Brazilian taxes like ICMS-ST and DIFAL?

The tax engine models ICMS including Substituição Tributária (ST), DIFAL for interstate sales, and FCP, alongside IPI, PIS, COFINS, and municipal ISS. Calculation is driven by CFOP/NCM/CEST mapping and origin/destination state, set up against your operations during the build so the right values flow into both the fiscal XML and the BC ledger entries.

Do we get the source code and BC API access?

Yes. You receive the AL source for the extension and ownership of it. Fiscal document status is exposed through BC REST/OData endpoints and standard permission sets, so you can surface issuance and rejection data in Power BI or drive a Power Platform flow without us holding the keys.