Arabic ERP Saudi Arabia: Do You Really Need It in Arabic?
Almost every ERP sold in Saudi Arabia now says “full Arabic support”. Some mean a translated menu. Some mean invoices that print in Arabic. A few mean a system that genuinely works in Arabic from data entry to the final report. And many buyers are not sure which of these they actually need.
Here is the short answer. You do not necessarily need your whole team working in an Arabic interface. But you do need certain outputs in Arabic, because Saudi law requires them. The question is which ones, and how well your ERP produces them.
I am Mohamed Abdul Baseeth, founder of Maas Consult Middle East Co. We have delivered 1,000+ ERP implementations in Saudi Arabia, most of them bilingual, and Arabic print formats are among the most common things we fix in systems other people set up. This guide separates what the law requires from what is a matter of preference, and shows how to test any ERP’s Arabic before you commit.
Quick Answer
Saudi rules require several business records in Arabic, regardless of the language your team uses day to day. Tax invoices and simplified invoices must be issued in Arabic, with other languages allowed only as a translation. VAT records and commercial books must be kept in Arabic. Employment contracts and employee records must be in Arabic, and the Arabic version prevails over any other language. So your ERP must produce correct Arabic outputs. An Arabic interface is a separate choice: it matters when Arabic-speaking staff, owners or auditors use the system directly. Most Saudi businesses are best served by a bilingual ERP: Arabic where the law and customers require it, and each user’s preferred language everywhere else.
Key Takeaways
- “Arabic ERP” can mean four different things: Arabic outputs, Arabic data, an Arabic interface and Arabic reports. Ask vendors which ones they mean.
- Arabic invoices are a legal requirement. English can appear alongside, but the Arabic text is treated as conclusive.
- VAT records must be kept electronically within the Kingdom, in Arabic, for at least six years, and longer for capital assets and real estate.
- An English-only interface is fine for an English-speaking finance team, as long as the system’s Arabic outputs are correct.
- Broken Arabic letters in PDFs and missing Arabic names on invoices are the most common failures. Test for them before you buy.
What Saudi Law Actually Requires in Arabic
| Requirement | What it says | Source |
|---|---|---|
| Tax invoices and simplified invoices | Must be issued in Arabic. Other languages may be added, but the Arabic information is conclusive and other languages are a translation. | ZATCA VAT guideline on records and invoicing |
| VAT records | Arabic applies to record keeping. Records must be kept electronically within the Kingdom, generally for at least six years; for capital assets, the useful life plus five years; for real estate, at least 15 years. | ZATCA VAT guideline on records and invoicing |
| Commercial books | Books must be kept in Arabic and kept, with related correspondence and documents, for at least ten years. Electronic books are allowed for businesses that keep accounts on computer. | Law of Commercial Books |
| Employment data, records and contracts | Arabic is the language for employment data, records, files and contracts. If another language is used alongside, the Arabic text prevails. | Saudi Labor Law, Article 9 |
| Workplace safety instructions | Must be posted in Arabic, and in other languages workers understand where needed. | Saudi Labor Law, Article 122 |
The invoice rules come from ZATCA’s VAT guideline on records and invoicing (version 3, May 2026). The commercial books rules are in the Law of Commercial Books, and the employment rules in the Saudi Labor Law.
What ZATCA Allows on an Arabic Invoice
An Arabic invoice does not have to be written entirely in Arabic script. ZATCA’s guideline allows:
- Numerals in either Arabic-Indic (١٢٣) or Western (123) form
- Currency symbols and codes such as SAR or USD as part of the Arabic content
- Dates in numerals, for example 2026/11/05
- Invoice numbers in numerals or a mix of numerals and letters, as long as they are sequential and unique
- Names of people, places, branches and products in Latin characters, since names are usually not translated
What it does not allow is an invoice that is entirely in English. Field labels such as “Tax Invoice”, “VAT Number” and “Total including VAT” need Arabic text, and the amounts must be stated in Saudi riyals.
The Four Layers of an “Arabic ERP”
When a vendor says “Arabic support”, ask which of these four layers they mean.
1. Arabic Outputs
These are documents that leave your business: tax invoices, credit notes, quotations, delivery notes, statements, payslips and employment contracts. This layer is legally required for invoices, books and employment documents, and expected by most Saudi customers and government bodies.
2. Arabic Data
This is the information stored in the system: customer names, item descriptions, addresses and units of measure. Good bilingual ERPs store both an English and an Arabic version of key fields, so the right one prints on each document.
3. Arabic Interface
This is the menus, forms and screens your users see. It matters when Arabic-speaking staff create transactions themselves, and it should be selectable per user, so an English-speaking accountant and an Arabic-speaking storekeeper can share the same system.
4. Arabic Reports and Communications
This includes management reports, Excel exports, emails, SMS and WhatsApp messages, and printed labels. This layer is often forgotten until a manager asks for a report in Arabic, or a customer receives an email with garbled text.
When Do You Need an Arabic Interface?
You need Arabic outputs in every case. Whether you need an Arabic interface depends on who uses the system.
An Arabic interface matters when:
- Saudi staff, including newly hired graduates, enter transactions in stores, sales or HR
- Owners or managers who read Arabic more comfortably review dashboards and approve documents
- Auditors, government inspectors or bank officers need to review records directly
- Your customers and suppliers communicate mainly in Arabic
An English interface can be enough when:
- Your finance and operations teams work in English
- Arabic speakers rarely use the system directly
- The system’s Arabic outputs are correct and tested
Most Saudi businesses end up in between: a bilingual system where each user chooses their own language and documents print in Arabic, or in Arabic and English side by side.
Bilingual Done Right: What Good Setup Looks Like
- Two name fields for key records. Customers, suppliers, items and company details each carry an Arabic and an English name, and each print format uses the right one.
- Bilingual invoice layout. Arabic and English labels side by side, with right-to-left Arabic text that stays aligned in tables.
- Arabic buyer details on B2B invoices. The customer’s name and address in Arabic, as registered.
- Amount in words in Arabic. Not legally required, but many Saudi customers, banks and government entities expect it on invoices and cheques.
- A consistent numeral choice. Decide whether documents use Western or Arabic-Indic numerals, and keep it consistent.
- Hijri dates where needed. Some contracts, government documents and HR records show Hijri dates alongside Gregorian ones.
- Per-user language. Each user works in their preferred language without affecting anyone else.
The Technical Problems Nobody Mentions in the Demo
- Broken Arabic letters in PDFs. Arabic letters change shape depending on their position in a word. If the PDF engine or font does not support Arabic shaping, words print as disconnected letters. This is the most common failure we see.
- Reversed or misaligned text in tables. Mixed Arabic and English in the same column can flip direction or push numbers to the wrong side.
- Search and sorting. Arabic searches may miss results because of different forms of the same letter, for example أ, إ and ا.
- Excel exports. Some exports lose Arabic characters or display them as question marks.
- Emails and messages. Templates may display Arabic incorrectly if the encoding or layout direction is wrong.
- Barcode and shelf labels. Label printers and templates often handle Arabic poorly without the right fonts.
None of these is hard to fix, but each needs to be tested before go-live, not discovered when an invoice reaches a customer.
A 12-Point Arabic Test for Any ERP
Ask for a demo with your own data and check each item.
- Print a B2B tax invoice in Arabic, and in Arabic and English side by side.
- Check that Arabic words are joined correctly in the PDF, not broken into separate letters.
- Confirm the customer’s Arabic name and address appear on the invoice.
- Print a credit note and a simplified invoice in the same layout.
- Check that all mandatory invoice labels appear in Arabic.
- Switch the interface to Arabic for one user and English for another, at the same time.
- Enter an item and a customer with both Arabic and English names, and search for them in Arabic.
- Export a sales report to Excel and open it: are the Arabic characters intact?
- Print a payslip and an employment letter in Arabic.
- Show the amount in words in Arabic on an invoice.
- Send an invoice by email and check how the Arabic displays.
- Print a barcode or shelf label with an Arabic product name.
A system that passes all twelve is genuinely ready for Saudi use. One that fails several will cost you time and credibility with customers.
How the Main ERP Options Handle Arabic
All the major platforms sold in Saudi Arabia offer Arabic, but the quality of the setup matters more than the vendor’s claim.
- ERPNext offers an Arabic interface with a right-to-left layout. Language can be set for the whole system or per user, and bilingual print formats are built during implementation. Our guide to ERPNext customization in Saudi Arabia explains how print formats and custom fields are adapted.
- TallyPrime added multilingual operations, including Arabic, in TallyPrime 5.0. According to Arabian Business, users can view and manage vouchers, print invoices and produce reports in their preferred language. Our TallyPrime sales and solutions team sets up bilingual invoice formats.
- Odoo, SAP and Microsoft Dynamics all offer Arabic, but how complete it is depends on the product, edition and the localisation work done by your implementation partner.
- Saudi cloud accounting tools such as Qoyod, Daftra and Wafeq were built for the Saudi market and are Arabic-first.
Whichever you consider, run the 12-point test above. For a wider comparison of platforms, see our ERP software buyer’s guide for Saudi Arabia.
Arabic and ZATCA E-Invoicing
Arabic requirements and e-invoicing overlap but are not the same thing. ZATCA’s e-invoicing rules govern the electronic invoice format and its integration with the Fatoora platform. The Arabic requirement governs what the invoice shows to the customer. A system can pass ZATCA’s technical checks and still produce an invoice that does not show the required information in Arabic, so test both. Our ZATCA e-invoicing page covers the technical side, and our ERPNext ZATCA integration guide explains the setup in ERPNext.
What Adds Effort to an Arabic Setup
We do not publish fixed prices, but these factors decide how much work Arabic adds to an implementation:
- Translating master data: item names, customer names and units of measure
- Designing print formats: invoices, credit notes, quotations, statements, payslips and contracts
- Arabic reports and dashboards: the management reports your team actually uses
- Emails, messages and labels: templates that leave the system
- Training: in Arabic for users who need it
Our ERPNext training in Saudi Arabia can be delivered for Arabic-speaking teams.
Common Mistakes with Arabic ERP
- Assuming a translated menu means Arabic invoices. Interface language and print formats are separate.
- Printing English-only invoices. This does not meet ZATCA’s Arabic requirement.
- Storing only one name per customer or item. You then have to choose between Arabic and English on every document.
- Testing on screen but not in print. Arabic often looks fine on screen and breaks in the PDF.
- Forgetting HR documents. Employment contracts and records must be in Arabic, with Arabic prevailing.
- Leaving Arabic to the end. Print formats and master data take time, so plan them from the start.
A Hypothetical Example: A Riyadh Distributor Going Bilingual
Picture a Riyadh distributor whose finance team works in English, while its storekeepers, drivers and many customers work in Arabic. Its first system printed invoices in English with an Arabic title added at the top, and Arabic product names printed as disconnected letters.
During the move to a bilingual ERP setup, every customer and item gets an Arabic and an English name. Invoices print in Arabic and English side by side, with the customer’s Arabic name and address and the amount in words in Arabic. Storekeepers use the interface in Arabic, while the accountants use English. Payslips and employment letters print in Arabic. Before go-live, the team runs the 12-point test with real invoices and fixes the PDF font issue.
This is an illustration built from common patterns, not a named client case.
From the Field
The quickest way to judge an ERP’s Arabic is not the demo screen. It is the PDF. Ask the vendor to print one of your real invoices, with a long Arabic product name and a customer name in both languages, and email it to you. Whatever arrives in your inbox is what your customers will see.
Frequently Asked Questions
Does an ERP in Saudi Arabia have to be in Arabic?
The interface does not have to be in Arabic, but certain outputs do. Tax invoices must be issued in Arabic, and VAT records, commercial books and employment records must be kept in Arabic.
Can an invoice in Saudi Arabia be in English?
Only alongside Arabic. ZATCA allows other languages as a translation, but the invoice must include the required information in Arabic, and the Arabic text is conclusive.
Can I use Western numbers on an Arabic invoice?
Yes. ZATCA allows either Arabic-Indic or Western numerals, recognised currency symbols and codes, and names of people, places and products in Latin characters.
What is a bilingual ERP?
A bilingual ERP stores key data in both Arabic and English, lets each user choose their interface language, and prints documents in Arabic, English or both side by side.
Do employment contracts need to be in Arabic?
Yes. Under Article 9 of the Saudi Labor Law, employment data, records, files and contracts must be in Arabic. If another language is also used, the Arabic text prevails.
Does ERPNext support Arabic?
Yes. ERPNext offers an Arabic interface with a right-to-left layout, language settings per user, and bilingual print formats configured during implementation.
Does TallyPrime support Arabic?
Yes. TallyPrime 5.0 introduced multilingual operations including Arabic, so users can manage vouchers, print invoices and produce reports in their preferred language.
Why does Arabic text break in my ERP’s PDF invoices?
Usually because the PDF engine or font does not support Arabic letter shaping. The fix is a font and print setup that joins Arabic letters correctly, tested on real invoices.
How long must Arabic business records be kept?
VAT records generally for at least six years, longer for capital assets and real estate, and commercial books and related documents for at least ten years.
Is an Arabic interface needed for ZATCA compliance?
No. ZATCA’s requirements apply to the invoices and records, not to the language of the screens your staff use.
Final Thoughts
“Do we really need it in Arabic?” has a clear answer: you need Arabic where the law, your customers and your Arabic-speaking staff need it, and a choice everywhere else. That points most Saudi businesses to a bilingual ERP, set up so that invoices, books and employment documents come out correctly in Arabic, while each user works in the language they are most comfortable with. Test the outputs, not the menu, and the decision becomes much easier.
If you are planning a bilingual rollout, our ERPNext implementation guide for Saudi Arabia explains how we build it from the start.
