A build-to-order X++ extension covering NF-e, NFS-e and CT-e in Dynamics 365 Finance & Operations: SEFAZ authorisation, contingency, DANFE output and SPED-ready fiscal books data. Built to order by ECOSIRE for Dynamics 365 F&O (build-to-order) — indicative price from $1599.00 USD; request a quote for a scoped proposal.
A build-to-order X++ extension covering NF-e, NFS-e and CT-e in Dynamics 365 Finance & Operations: SEFAZ authorisation, contingency, DANFE output and SPED-ready fiscal books data.
Built to order
Brazil is the hardest fiscal environment most F&O programmes will meet. A sale is not authorised by a single national service but by the SEFAZ of the issuing state, each with its own availability and its own contingency behaviour. The document itself — NF-e — carries a layered tax calculation where ICMS, ICMS-ST, IPI, PIS and COFINS interact with CFOP, CST/CSOSN, NCM and the operation's origin and destination. Services are a different document entirely (NFS-e, governed municipally), freight is another (CT-e), and everything eventually has to reconcile into SPED fiscal and accounting obligations.
The operational risk is blunt: goods cannot legally leave the dock without an authorised NF-e and a printable DANFE. When a state service is down, you need contingency, not a queue. When a document is rejected for a CFOP that does not match the operation, someone has to see that message, not a generic failure. And the fiscal data behind it all has to be complete enough that SPED files can be produced from the system rather than reconstructed from it.
ECOSIRE builds a Brazilian fiscal document extension for your Dynamics 365 Finance & Operations environment. It is X++ extension code in a dedicated model — event handlers, chain of command, table and form extensions, no overlayering — packaged and released through your LCS or Azure DevOps pipeline.
Sales invoices, transfer orders and returns produce NF-e XML with the fields the layered tax model actually requires: CFOP per line derived from the operation, CST or CSOSN, NCM, origin, unit conversion, and the ICMS / ICMS-ST / IPI / PIS / COFINS groups. Ledger dimensions and posting profiles stay in F&O where they belong; the extension reads them rather than duplicating them, so the fiscal document and the financial posting cannot drift apart.
A transmission service handles certificate-based signing and the call to the SEFAZ authorisation service for the issuing state, storing the protocol number, authorisation key and returned XML. State-level endpoint configuration lets a group operating in several states run one code base. When a service is unavailable, contingency handling issues the document under the configured contingency mode and reconciles it when the service returns — with the reconciliation tracked, not left to memory.
DANFE output is generated for print and PDF from the authorised XML. Where freight is in scope, CT-e is handled with the same authorisation and storage pattern. NFS-e, being municipal, is built against the specific municipalities in your scope — this is quoted explicitly, because a build covering three municipalities is a different job from one covering thirty.
The full correction lifecycle is implemented: cancellation inside the permitted window, carta de correção electronica for permitted field corrections, and inutilização for unused number ranges. Each stores the authority's response against the document, so the fiscal history is complete.
Batch framework jobs drive transmission, status query and retry with bounded, idempotent logic keyed on the document — a re-run never produces a second authorisation attempt for an already authorised key. A workspace shows pending, authorised, rejected and contingency documents with the SEFAZ rejection text attached, and a monitoring tile for documents blocking dispatch. Fiscal books data is exposed through data entities over OData and the Data management framework so SPED generation and your Power BI reporting read the same records. Where your warehouse operation needs it, authorisation status is surfaced so the warehouse mobile app flow does not release a load whose document is not authorised.
Manufacturers, distributors and multi-state operations running Brazilian legal entities on F&O, particularly groups issuing from more than one state, moving goods between their own sites, or carrying both goods and service revenue in the same entity.
This is built to order — there is no ready-made download. A scoping call establishes your legal entities, issuing states, municipalities for NFS-e, whether CT-e is in scope, your certificate handling, and your tax determination setup. You get a fixed quote against that written scope. ECOSIRE builds against your F&O version, delivers a deployable package, and installs it in your test or sandbox environment, where we authorise real document shapes against the SEFAZ homologation environment with your fiscal team present. Production cutover follows your normal release process, and a support window covers defects and authority-driven schema changes after go-live.
Lead time is typically two to four weeks from signed quote for a focused NF-e scope; broad scope across many states, municipalities and CT-e is quoted with its own timeline at scoping.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Owns SPED obligations and cannot afford fiscal data that has to be reconstructed from spreadsheets each period. Fiscal document data held against the source transaction and exposed as data entities makes the books an extract rather than a rebuild.
Cannot release a truck without an authorised NF-e and a printable DANFE, and loses hours when a state service is unavailable. Contingency issuance plus authorisation status visible in warehouse operations keeps dispatch moving instead of stalling at the gate.
Is standardising several Brazilian entities onto one F&O environment and does not want a separate build per state. State-level configuration over a single extension model keeps the deployment and the upgrade path singular.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| NF-e authorisation against state SEFAZ services | Included | Partial support | Included |
| Contingency issuance with tracked reconciliation | Included |
From $1599.00
Starting point — quoted to your scope
| Partial support |
| DANFE print and PDF from authorised XML | Included | Partial support | Included |
|---|
| CT-e freight document handling | Included | Not included | Partial support |
|---|
| NFS-e for named municipalities | Included | Partial support | Partial support |
|---|
| Cancellation, CC-e and inutilizacao lifecycle | Included | Partial support | Included |
|---|
| Fiscal data exposed as entities for SPED extraction | Included | Not included | Partial support |
|---|
| Source code delivered to your repository | Included | Included | Not included |
|---|
An X++ extension that imports bank statements into Dynamics 365 F&O and fuzzy-matches lines against payments, deposits and fees. Built to order for your legal entities after a scoping call and fixed quote.
A behaviour-aware treasury forecasting app for Dynamics 365 Finance & Operations. Built to order as an X++ extension after a scoping call and a fixed quote — nothing is pre-built or downloadable today.
A built-to-order forecasting and planning layer for Dynamics 365 Finance & Operations, with external demand signals, explainable forecasts and scenario comparison. Scoped and built by ECOSIRE after a fixed quote.
A build-to-order X++ extension that captures vendor invoices, extracts line data, matches them against purchase orders with tolerance rules and routes exceptions through F&O workflow. ECOSIRE builds it for your entity structure after a fixed quote.