ERP Audit Consultant, Saudi Arabia

Why Saudi companies review an ERP that is already live

An ERP that went live to meet an e-invoicing deadline was judged on one test: could it issue a valid invoice? Everything else was secondary. Months later, the side effects show up in finance. Rejected invoices pile up in a queue nobody owns, the VAT return needs adjustments, sales staff keep their own price lists, and month-end depends on one person who understands the workarounds.

A structured review helps when:

• Leadership wants to know whether the current platform can support the next stage of growth, or only the last deadline.
• The external auditor or zakat advisor keeps raising queries about how figures were produced.
• The implementation partner has moved on and nobody internal understands the configuration fully.
• The group plans to add a branch, a new company or a new region and wants the foundations checked first.

To be clear about boundaries: this is not a statutory audit and gives no opinion on your financial statements. It does not confirm that you meet ZATCA requirements either; that confirmation comes from your vendor, your advisor and the authority's own processes. What it does is document how the system behaves, where it falls short and what to do about it. The underlying method follows my ERP health check, adapted to Saudi conditions.

Reviewing the e-invoicing connection and invoice data

E-invoicing in the Kingdom ties the ERP directly to the authority, which turns invoice data quality into an operational issue. If the connection fails or invoices are flagged, the problem reaches customers and cash collection, not just the tax return. The audit looks at the connection as a working process rather than a technical feature.

Points I check, using a sample of real documents:

• Whether the integration is built into the ERP or provided by a separate connector, and who supports each part.
• Where rejected or warned invoices go, who is notified and how quickly they are corrected.
• Whether credit and debit notes reference the original invoice correctly.
• Whether customer records carry valid VAT numbers and complete addresses where they are needed.
• Whether invoice numbering and branch or device setup match how the business actually issues invoices.
• Whether staff can cancel or edit an invoice after submission in ways that break the trail.

Your advisor decides which invoice types and integration requirements bind your business, and the technical specification belongs to the authority and the vendor. I record what the system does, with screenshots and document references, so they can confirm whether it meets the requirement. For the wider Saudi picture, see the Saudi ERP consultant page.

Ledger structure for VAT and zakat reporting

A rushed setup often copies a generic chart of accounts and adds tax codes on top. That works for issuing invoices, but it makes reporting harder. The VAT return is assembled from reports that do not quite agree with the ledger, and the zakat or income tax computation is built in a spreadsheet because the accounts do not separate the items your advisor needs.

In the ledger review I look at:

• Whether output and input VAT accounts reconcile to the figures submitted in returns, period by period.
• Whether imports, exports, exempt and zero-rated supplies are recorded in a way the return report can read directly.
• Whether fixed assets, provisions and related-party balances are held in accounts that can be identified for zakat purposes.
• Whether a group with Saudi and foreign ownership keeps entities separate enough for different obligations to be calculated.
• Whether reports can be run on both Gregorian and Hijri dates where your processes or contracts use the Hijri calendar.

I do not decide how any item should be treated for VAT or zakat. The output is a mapping review and a set of specific questions, so your advisor can tell you what to change and the change can be made once, cleanly, in the ERP.

Arabic outputs, payroll data and user access

Arabic is required on many Saudi documents, and print templates are frequently the last thing finished before go-live. I review every customer-facing template for missing fields, broken right-to-left layout, mixed numbering and totals that differ from the screen. The engagement runs in English, so the Arabic wording itself is checked by your own staff or a local partner against a list I prepare.

Payroll deserves attention even when a separate HR system calculates salaries. I check that payroll postings arrive in the ERP with the right cost centers, that end-of-service provisions are calculated and reconciled consistently, and that employee data in the ERP agrees with what is sent to the bank and to government platforms. Rules for those calculations come from your HR advisor; the audit checks that the system applies them the same way every month.

Access is the final part. I look for:

• Users who can create a customer, issue an invoice and post a credit note without a second approval.
• Shared or generic logins used at branches or by the partner.
• Former staff and partner consultants with active accounts.
• Rights to change tax codes, numbering or closed periods held by more people than necessary.

Each access finding comes with a suggested fix that a lean finance team can actually maintain.

Integrations, report trust and the findings report

Saudi businesses often connect the ERP to point-of-sale systems, ecommerce platforms, delivery apps, banks and a separate HR tool. Each link is a place where data can fail silently. I list every integration, check how errors surface and compare a sample of transactions on both sides. Where staff re-key data between systems, the review records how often and why.

Management reporting is tested the same way. I pick the figures leadership actually uses, trace them back to the ledger and source documents, and explain any differences. I also compare license and subscription counts with real usage, so you can see what is paid for and idle.

The report is written for decision-makers. Findings are grouped by area, each with the evidence, the business effect, the likely cause and a recommended action, and ranked so that anything affecting invoicing, tax filing or cash comes first. A separate list holds questions for your tax and HR advisors. I present it remotely to leadership and, if you choose, to your implementation partner. Fixes can be done internally, through the partner, or with my help as part of ERP optimization. If the system is not yet stable after go-live, read about ERP rescue in Saudi Arabia, and for general context see the Saudi Arabia overview.