Ask a global audit platform whether it supports Arabic and you will usually get a yes. Ask what happens after the committee pack is generated, and the answer separates two very different things.
For a Saudi audit function whose committee deliberates in Arabic and whose regulator corresponds in Arabic, this is not a user-experience preference. It is a question about whether the assurance record has one version or two.
The translation trap
The common pattern works like this. The engagement runs in English. Findings are written, rated, and assigned in English. At the end, the committee pack is produced — and then translated, either by a vendor's export feature or, more often, by a member of the audit team the night before the meeting.
That produces a second artefact. And the moment a second artefact exists, it can disagree with the first.
For a function whose entire value rests on the integrity of its record, two versions of the truth is a structural problem, not a cosmetic one.
What "bilingual at the schema level" means
The alternative is to treat Arabic as a property of the data rather than of the output.
In practice that means each field that carries language — a finding title, an observation, a recommendation, a management response — stores its Arabic and English values together, against the same record. The rating, the owner, the due date and the status are language-neutral: they exist once. When a pack is generated in either language, it is rendered from the same engagement record, so the two cannot drift apart. Correct a due date and both packs are correct.
This is also what makes the Arabic pack defensible rather than merely available. A committee reading the Arabic version is reading the audit file, not a derivative of it.
RTL is a layout problem, not a font problem
The second half of the requirement is rendering, and it is routinely underestimated. Producing a credible Arabic committee pack means the whole layout mirrors:
- Tables reverse column order, so the reading eye meets the row label first.
- Numbering and lists align and indent from the right.
- Charts mirror their axes and legends — a bar chart growing leftward reads as growth, not decline.
- Mixed-direction strings — an Arabic finding title containing a Latin system name or a figure — have to render without the fragments reordering.
A platform that swaps the font and calls it Arabic support will produce a pack that is technically in Arabic and visibly foreign to the people reading it. Committee members notice, and it costs the function credibility at exactly the wrong moment.
Why this lands harder in the Kingdom
Saudi functions face this more sharply than most because of what sits above them. The CMA's Corporate Governance Regulations put internal audit under a committee of non-executive directors, and for banks SAMA's internal auditing principles add a prescriptive layer on the function itself — including a five-yearly external quality assessment in which the assessor will look at what the committee actually received.
At that point, "the Arabic pack was translated separately and may differ slightly from the file" is an answer nobody wants to give. The full picture of what governs the function is in the rules that actually govern internal audit in Saudi Arabia.
What to ask a vendor
Three questions cut through most marketing claims:
- Is Arabic stored per field, or applied at export? Ask to see the data model, not the demo.
- If I correct a finding's due date, are both packs correct immediately? If the answer involves regenerating and re-translating, there are two documents.
- Show me a real RTL committee pack — with a table, a chart and a mixed Arabic-Latin string in it.
ControlVista is bilingual at the schema level: Arabic is a first-class language per field, and an RTL Arabic committee pack is generated from the same engagement record as the English one. That is a deliberate architectural choice rather than a localisation project, and it is the part of the audit management software that global incumbents cannot retrofit quickly.
The Kingdom-specific detail sits on our audit management software for Saudi Arabia page, and the vendor landscape on best audit management software in Saudi Arabia.
See how ControlVista feeds the committee or request a demo.