ERP Selection Consultant, Saudi Arabia

Why e-invoicing evidence comes before features

ZATCA has rolled out FATOORAH in phases, first requiring electronic generation of invoices and then integration with its platform for taxpayers called up in successive groups. Which obligations apply to your business, and when, is something to confirm with your tax advisor and from ZATCA's own guidance. For selection, the practical point is simpler: any system you shortlist must be able to meet the obligations you have now and those you expect to have.

Most vendors will say yes to that. So I ask for evidence instead of assurances:

• How does the system create the structured invoice, the cryptographic stamp and the QR code on simplified invoices?
• Is integration with the authority built into the product, or delivered through a third-party connector, and who supports that connector?
• How are standard invoices cleared and simplified invoices reported, and what happens when the authority rejects one?
• How are several branches or invoicing units onboarded?
• Who updates the solution when technical specifications change, and at whose cost?

The answers go into the scoring sheet in writing. A vendor that cannot explain its approach clearly in selection is unlikely to explain it better in the middle of a go-live. The wider compliance picture is covered on the Saudi ERP consultant page.

Arabic screens, printouts and Hijri dates in demos

Arabic support is easy to claim and hard to judge in a demo run in English. A system can have translated menus and still print a tax invoice with broken right-to-left alignment, truncated Arabic item names or mixed-up numbering. Because the engagement runs in English, I make sure the people who will use the system in Arabic are in the room when it matters.

For each shortlisted product I ask the vendor to switch the interface to Arabic and run part of the script that way. Your staff then score a few things directly:

• Whether field labels and messages make sense to a Saudi user, not just to a translator.
• How a bilingual tax invoice, delivery note and statement of account look when printed and as PDF.
• Whether Arabic customer and item names can be searched and sorted properly.
• How Hijri dates appear on contracts, employee documents or reports where your business uses them, alongside Gregorian dates in the ledger.

Arabic wording on templates is written or checked by your team or the partner, never by me. What I do is make sure language quality is scored as seriously as functionality, because poor Arabic output is one of the most common reasons Saudi users quietly return to spreadsheets after go-live.

Shortlists for Saudi businesses at different stages

Saudi buyers come to an ERP decision from very different starting points, and the shortlist should reflect that rather than a generic market list.

A newly established branch or subsidiary of a foreign group often needs to fit a parent company standard, local e-invoicing and Arabic documents at the same time. Options may include extending the group's system, a localized Dynamics 365 Business Central setup, or a lighter local ledger feeding group reporting.

A family-owned trading, contracting or services company moving off an older accounting package commonly weighs Odoo, Zoho and ERPNext, sometimes alongside a local product built specifically for the Saudi market.

A multi-company group or a regular government supplier may need heavier approvals, consolidation and audit trails, and can justify adding SAP Business One or a larger suite to the evaluation.

For each case, local products deserve a fair hearing. They may handle Arabic and local compliance with less effort, while a global platform may offer more room to grow. The scoring sheet makes that trade-off explicit instead of leaving it to instinct. My ERP evaluation page explains the scoring method, and the Zoho vs ERPNext comparison covers one frequent pairing.

Comparing implementation partners in the Kingdom

For most Saudi projects the partner decides the outcome as much as the software. Partners range from small teams focused on one platform to larger firms covering Riyadh, Jeddah and the Eastern Province, and some deliver mainly from outside the Kingdom with a small local presence. Each model can work. What matters is whether the people who will deliver your project are capable and available.

In partner interviews I ask questions that a sales presentation rarely answers. Who is the named project manager and how many other projects are they running? Which consultants have delivered e-invoicing integration on this platform before? Who will train your users in Arabic, and will they be on site or online? What are support hours across the Saudi working week and during Ramadan? How are change requests priced?

Reference calls follow. I ask each partner for Saudi customers of similar size and industry, then hold guided conversations about how the project went, how e-invoicing go-live was handled and how support has been since. Patterns across several references tell you more than any proposal. If you already have proposals and want them read side by side, the vendor proposal review covers that step on its own.

Data location, licensing and the contract

Saudi Arabia has a personal data protection law, and some sectors and government-linked customers expect data to be held inside the Kingdom. Whether that applies to you is a question for your legal advisor. In selection, I make sure each vendor answers the same questions: where production and backup data are stored, whether an in-Kingdom hosting option exists and at what trade-offs, who at the vendor or partner can access the data, and how a complete export works if you leave.

Licensing needs the same discipline. I compare how each option counts users, whether approval-only or self-service users are cheaper, how additional companies or branches are charged, what the renewal terms say and which connectors carry their own subscription. E-invoicing connectors in particular sometimes have separate fees based on invoice volume or units.

Finally, I review the contract and statement of work with your team before signature. I check that the scripted demo scenarios appear in scope, that payment milestones are tied to accepted deliverables rather than dates, and that support and warranty terms are clear. If the contract has an Arabic version, your legal advisor should confirm which language governs. The broader approach is described under ERP vendor selection, and the Saudi Arabia overview lists my other services there.