Saudi (KSA) Localization Pack for Business Central

Key Features

Hijri/Gregorian dual calendar exposed via AL table and page extensions on sales, purchase and finance documents, with bidirectional conversion logic in a dedicated codeunit

Arabic right-to-left RDLC/Word report layouts for the tax invoice, credit memo, and customer statement with correct Arabic glyph shaping and bidi flow

KSA VAT posting groups and setup mapped to ZATCA tax categories (standard, zero-rated, exempt, out-of-scope)

Withholding tax (WHT) engine — configurable rates, automatic accrual entries, and printable WHT certificates, applied through purchase posting event subscribers

Bilingual (Arabic + English) tax invoice header and line text driven from BC item and customer translation tables

ZATCA-ready master-data validation for company VAT registration number, Commercial Registration (CR) number, and structured address fields

Dedicated permission sets shipped inside the extension so the new functionality is governed alongside standard BC roles

Job Queue entries (optional) for recurring WHT accrual posting and Hijri period rollover tasks

Master data and localized fields exposed through the standard BC REST/OData v4 API and Dataverse virtual/synced entities for Power BI and Power Platform

Installed as a signed per-tenant extension — no modification of the BC base application, upgrade-safe across Microsoft's monthly service updates

Event-subscriber architecture (no base-app object changes) so the pack coexists with other AppSource and per-tenant extensions

Configuration package / RapidStart data so VAT, WHT and calendar setup can be replicated across Sandbox and Production

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The Saudi (KSA) Localization Pack closes the statutory gaps that Business Central core leaves open for Saudi-based companies — the requirements that sit beyond e-invoicing. ECOSIRE builds it for your tenant as a per-tenant AL extension (table/page extensions, codeunits and event subscribers), installs it on your Business Central environment, and supports it after go-live.

This is build-to-order, not an instant AppSource download. After purchase, ECOSIRE confirms your VAT registration profile, chart-of-accounts layout, and document templates, then delivers the signed .app package and deploys it to your Production (and Sandbox) environment.

What it adds: - Hijri/Gregorian dual calendar — a Hijri date field surfaced via table and page extensions on key documents, with conversion logic in AL so postings, statements and printed documents can show both calendars. - Arabic RTL document layouts — Word/RDLC report layouts for the tax invoice, credit memo and statement with right-to-left flow and proper Arabic shaping. - KSA VAT & WHT — VAT posting setup aligned to ZATCA categories plus a withholding-tax engine (rates, certificates, accruals) wired through purchase posting via event subscribers. - Bilingual tax invoices — Arabic + English line and header text driven from item/customer translations. - ZATCA-ready master data — validated company VAT number, CR number, and address fields so the data is clean for any ZATCA e-invoicing integration (this pack covers the statutory layer; pair it with a ZATCA e-invoicing connector for Phase 2 clearance).

Permission sets ship with the extension. Where you want automation (recurring WHT accruals, period rollovers), we schedule it via the BC Job Queue. Master data stays queryable through the standard BC REST/OData API and Dataverse-synced entities for Power Platform reporting.

What you get

Signed per-tenant AL extension (.app) built for your Business Central version, deployed to your Production and Sandbox environments by ECOSIRE

Configured KSA VAT posting setup and withholding-tax rates matched to your chart of accounts during onboarding

Arabic RTL report layouts for tax invoice, credit memo and statement, applied to your document templates

Permission sets imported and a setup/configuration package (RapidStart) for replicating configuration

Source AL project handed over (your code, your tenant) with build and deployment notes

Admin walkthrough session covering Hijri calendar use, VAT/WHT posting, and bilingual invoice generation

Post-go-live support window with bug fixes and Microsoft service-update compatibility checks

Who this is for

Finance Controller at a Saudi-based company

Needs VAT and withholding tax handled correctly inside Business Central, with audit-ready bilingual tax invoices and Hijri dates on statutory documents — without spreadsheets or manual workarounds at period close.

Business Central partner / implementer serving KSA clients

Wants a ready-built, upgrade-safe localization extension to drop into a client implementation rather than re-developing Hijri conversion, RTL layouts and WHT logic from scratch on every project.

IT / ERP manager at a GCC group expanding into Saudi Arabia

Rolling out Business Central to a new KSA entity and needs the statutory localization layer in place, with clean ZATCA-ready master data and API/Dataverse access for group reporting.

How Saudi (KSA) Localization Pack for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Hijri/Gregorian dual calendar on documents	Included	Partial support	Partial support
Arabic RTL tax-invoice & statement layouts	Included	Partial support	Included
KSA VAT posting setup aligned to ZATCA categories	Included	Partial support	Included
Withholding tax (WHT) engine with certificates	Included	Partial support	Partial support
ZATCA-ready master-data validation (VAT/CR/address)	Included	Partial support	Partial support
Installed & deployed for you on your tenant	Included	Partial support	Not included
Source AL project handed over to you	Included	Included	Not included
Upgrade-safe (no base-app modification)	Included	Partial support	Included
Tailored to your chart of accounts & templates	Included	Included	Not included
Ongoing support from the builder	Included	Partial support	Partial support

Frequently Asked Questions about Saudi (KSA) Localization Pack for Business Central

Is this an instant download from Microsoft AppSource?

No. This is a build-to-order extension. ECOSIRE builds the AL extension for your specific Business Central version and VAT/CR profile, then installs it as a signed per-tenant extension on your environment. There is no AppSource one-click install — you get a configured, deployed solution plus the source project.

What is the delivery lead time?

Typical delivery is 2–4 weeks from purchase, depending on how customized your document templates and chart of accounts are. The first days are an onboarding call to confirm your VAT registration, CR number, posting setup and report templates; we then build, deploy to your Sandbox for sign-off, and promote to Production.

How are ongoing support and Microsoft updates handled?

The price includes a post-go-live support window for bug fixes and compatibility checks against Microsoft's monthly Business Central service updates. Because it's built as a per-tenant extension using event subscribers (no base-app changes), it's upgrade-safe by design. We offer an optional ongoing support/maintenance retainer beyond the included window.

Does this make me fully compliant with ZATCA e-invoicing (Fatoorah)?

This pack covers the statutory localization layer — Hijri calendar, Arabic RTL invoices, KSA VAT, WHT, and clean ZATCA-ready master data. It does not by itself perform ZATCA Phase 2 clearance/reporting to the FATOORA platform. It prepares your data so a dedicated ZATCA e-invoicing connector can integrate cleanly; ECOSIRE can scope that as a companion project.

Will it conflict with other extensions or break on a Business Central upgrade?

No base-application objects are modified. The pack uses table/page extensions and event subscribers, so it coexists with AppSource apps and other per-tenant extensions and survives Microsoft's service updates. We validate it against your sandbox before each major version update if you keep a support retainer.

Can the localized data be used in Power BI and Power Platform?

Yes. The new fields and master data are exposed through the standard BC REST/OData v4 API and through Dataverse-synced entities, so you can report on VAT, WHT and Hijri-dated transactions in Power BI and build flows in Power Automate without bespoke integration work.