Typical lead time is one working week from kickoff, depending on scope (VAT and Arabic invoicing alone is faster; adding WPS and corporate-tax fields takes longer). We start with a short discovery of your VAT posting setup, number series and bank WPS spec, build the AL extension, publish it to your sandbox for your sign-off, then install to production. This is build-to-order, so the timeline reflects real configuration against your tenant — not an instant download.

The extension ships with an upgrade codeunit and proper app versioning so it survives Microsoft's monthly platform and base-app updates. The build includes two weeks of go-live support for fixes and adjustments. After that, we offer an optional support and maintenance retainer that covers update-compatibility testing on your sandbox before each major BC release, plus changes to keep pace with FTA rule revisions (for example new VAT-return boxes or corporate-tax guidance).

No. This is delivered as a per-tenant extension that ECOSIRE builds, publishes and installs directly on your tenant. That lets us tailor it to your exact VAT posting groups, chart of accounts and bank WPS specification rather than shipping a one-size-fits-all AppSource app. If you later want an AppSource-distributable version, we can scope that separately.

No. Everything is implemented as table extensions, page extensions and event subscribers layered above the base app, with dedicated permission sets. The core objects are untouched, which is exactly why the extension can be upgraded cleanly alongside Microsoft's releases and removed without leaving the base app altered.

Yes. We can expose the VAT-return and corporate-tax data through Business Central API pages over the standard REST/OData endpoint, so your Power BI dashboards and Power Automate flows read live BC data. If you use Dataverse, the same API can sync the relevant entities into your Power Platform environment.