GCC Multi-Country E-Invoicing Suite for Business Central

No. This is a build-to-order engagement. ECOSIRE builds the suite as a per-tenant AL extension scoped to the exact countries, entities and document types you run, then installs it directly on your Business Central environment (cloud SaaS or on-prem). There is no public AppSource listing or self-service download — you get a solution validated against each authority's sandbox before go-live.

Typical lead time is around 4 to 7 weeks depending on how many countries and entities are in scope, whether your tax registrations and gateway credentials are ready, and the complexity of your document types. After a short scoping call we confirm a firm timeline. Single-country scopes are faster; full five-country GCC rollouts sit at the upper end. We validate each profile against the relevant sandbox (e.g. ZATCA Fatoora) before switching any entity to production.

The build includes a post-go-live support window for defects and configuration help. GCC e-invoicing mandates evolve — phases, schema versions and new countries roll out regularly — so we offer an ongoing maintenance arrangement covering regulatory updates to existing country profiles and BC version-compatibility upkeep. Adding a new GCC country later is an additive country-profile codeunit, quoted as a small extension rather than a rebuild.

Yes. It is delivered as a standard AL extension that installs on Business Central online (SaaS) and on-premises. Outbound government calls use BC's HttpClient, run on the Job Queue, and statuses are exposed via the BC REST/OData API so you can surface them in Power BI or the Power Platform if you wish.

Setup is per-company. Each Business Central company holds its own tax registration number, currency, endpoints and credentials through the suite's setup page, while the shared signing, QR and UBL/Peppol core is common code. The central dashboard aggregates document status across all companies and countries so your shared-service team works from one view.

We scope this against your current environment first. The suite uses its own object range, extends posted-document tables and pages additively, and hooks posting through event subscribers rather than modifying base objects — so it coexists with standard localizations and your existing extensions. Any genuine overlap is identified during scoping and handled deliberately.