Business Central Advisor, Saudi Arabia

How FATOORAH compliance usually reaches Business Central

For Business Central in Saudi Arabia, VAT reporting, Arabic invoice layouts and the integration with ZATCA's e-invoicing platform have commonly been supplied by partner-built or third-party apps rather than by the core product. That picture can shift, so I check where things stand for each project. What matters more is understanding the chain you are buying: the app that stamps and signs the invoice, any middleware that talks to the authority, and the partner who configures both.

I put a short list of questions to every bidder and ask for written answers. Which document types are covered, including simplified and standard tax invoices plus their credit and debit notes? Where are the cryptographic keys and certificates stored, and who renews them? What does a user see when an invoice is rejected or returned with warnings, and can it be corrected without a manual workaround? How have past specification changes been delivered, and are future changes inside the support fee?

Then I test. UAT should include submissions to the authority's sandbox where the app supports it, invoices in foreign currency, invoices with discounts and advances, and a credit note against an invoice from an earlier period. Your tax advisor confirms which phase and obligations apply to you.

VAT posting groups, zakat workings and dimensions

Business Central picks the VAT treatment for each line by combining the business VAT group set on the customer or vendor with the product VAT group on the item or account. For a Saudi company I build those combinations with your advisor: standard-rated domestic sales, zero-rated exports and other zero-rated supplies that apply to you, exempt supplies, imports where VAT is settled through customs or reverse charge, and purchases where input VAT cannot be recovered. Each combination is traced to a box on the return and to the fields printed on the tax invoice.

Zakat is calculated outside the ERP by your advisor, but the ledger has to give them clean inputs. I make sure the chart of accounts separates the balances they will ask for, for example investments held for the long term, balances with related parties, provisions and each class of fixed asset, rather than burying them in broad accounts that need analysis every year.

Dimensions then carry the management view: project, branch, region, cost center or contract. Contractors usually need project as a mandatory dimension on cost accounts, while distributors focus on branch and product line. I keep the set small and set default values on customers, vendors and items, so users are not deciding coding on every line. My requirements gathering service documents these rules in the BRD.

Arabic documents, Hijri dates, banks and payroll boundaries

Business Central's interface language and its printed documents are separate questions. A finance team may work in English while tax invoices, delivery notes and customer statements must show Arabic alongside English. I list every report with its required fields, language and alignment, and check how right-to-left text behaves in PDFs, emails and exports. Where contracts, government correspondence or HR processes need Hijri dates, I record exactly which documents need them so the partner can say whether a localization feature, an app or a custom layout will provide them.

Banking needs similar precision. Saudi banks' corporate portals each accept their own upload formats for supplier and salary payments. I collect those specifications and ask how each file will be produced: through configurable file mapping inside the system, a banking app, or a manual export and upload. For reconciliation, I agree how statements are imported, how bank charges and partial customer receipts are matched and how foreign currency accounts are revalued.

Payroll, GOSI contributions and wage protection submissions are usually managed in a dedicated HR and payroll system that sends summarized journals to Business Central. I define that interface, including cost allocation to projects, so the boundary is clear in the scope and in UAT.

Family groups, intercompany and migration from local systems

Many Saudi businesses sit inside a family group: a trading company, a contracting company, a real estate holding and perhaps a services company, each with its own commercial registration and VAT number. In Business Central each becomes a separate company. I design how they transact with each other: intercompany partners, mapped accounts, recharges for shared staff and premises, and the inbox and outbox flow that creates the matching document in the receiving company. A consolidation company then produces the group view, with eliminations agreed with your auditors. The multi-company ERP page explains the pattern in general terms.

Migration sources vary widely. Some groups run a local Arabic accounting package, others an older NAV or AX system, a few use Tally, and contractors often hold project costs and retention in spreadsheets. I plan what moves as open items: unpaid invoices, open purchase orders, project balances, retention receivable and payable, stock by warehouse, and what remains archived. Before cutover, your finance lead approves the figures for each company: ledger totals, amounts owed by customers and to suppliers, and VAT control accounts.

I run these sessions remotely in Arabia Standard Time, with recorded walkthroughs for site teams. The data migration service page covers the method.

What I look for in a Saudi SOW, and when a smaller system will do

Saudi Business Central proposals often describe compliance in a single sentence. I break that sentence apart. Is the e-invoicing app named, and is its subscription in the estimate? Who performs onboarding with the authority for each company? Are Arabic layouts for every listed document included, or only the tax invoice? Is migration limited to master data? How many UAT rounds will the partner support, and does post go-live support cover Sunday to Thursday hours? Each gap becomes a written question, as I describe under reviewing vendor proposals.

Business Central can also be too heavy for the job:

• One company with straightforward sales may be better served by a cloud accounting product that already integrates with ZATCA.
• A group that cannot name an internal owner for tax setup and masters will end up depending on the partner for every change.
• Where every user needs to work fully in Arabic, test the complete interface with real staff before committing.

Related reading: Dynamics 365 in Saudi Arabia, my Saudi ERP consultant page or the Saudi Arabia hub. The ERP evaluation service compares alternatives against your requirements.