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.

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.

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.

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.

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.

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.