This is built to order, so lead time depends on how many countries and document formats are in scope. A single-country build (for example ZATCA or India GST alone) is typically delivered in a few weeks; multi-country scopes take longer. After scoping we give you a firm timeline. We install on your sandbox first, run a full end-to-end test against the authority's test environment, then promote to production — so go-live happens only after you've seen it clear real sample documents.

Tax authorities revise their formats — ZATCA phases, ETA schema updates, IRP API versions and Peppol profile changes all happen. Your purchase includes an agreed support and update window during which ECOSIRE handles issue resolution and keeps the in-scope country formats aligned with the published specifications. Because it's a per-tenant extension we own, we ship updates straight to your tenant. Beyond the included window, continued maintenance is available on a renewable basis.

No. This is a custom per-tenant extension that ECOSIRE builds, installs and supports on your specific environment. There is no instant AppSource download. That's deliberate — e-invoicing depends on your tax registrations, certificates, authority endpoints and document layouts, which a one-size listing can't configure correctly.

Yes. The extension is built in AL to current per-tenant extension standards, so it deploys on Business Central Online (SaaS) and on supported on-prem versions. Where a country requires local certificate handling or a signing component (for example ZATCA's cryptographic stamp), we confirm the right architecture for your deployment during scoping.

Yes — that's the point of this build. We map your manufacturing flow so that production output, item tracking and BOM-driven line detail surface correctly on the compliant invoice, and we trigger generation at the right lifecycle stage (post, release or dispatch). India's e-way bill, for instance, is wired to the dispatch event rather than just invoice posting.