Jump to content
Comparison — Business Systems

Arabic ERP: What Actually Makes a System Arabic

A translated interface is not localisation — five tests that expose the difference in half an hour of a free trial

Snad Team8 min readاقرأ هذا المقال بالعربية
In this article6 sections

Almost every vendor writes that it supports Arabic. The claim is literally true and practically insufficient.

Language support can mean the menus were translated while the screen still reads left to right, date fields are Gregorian only, and the invoice prints in an order your accountant does not recognise.

This article names no vendor and ranks nobody. It gives you five tests to run yourself on any system during its free trial, so you learn where it stands before you subscribe.

Translation is one thing, localisation another

Translation changes the words. Localisation changes the layout as well.

The difference shows in details that look small until you use them daily:

  • Screen direction: do menus genuinely begin on the right, or is Arabic text sitting inside a left-to-right layout?
  • Table column order: in a right-to-left table the first column starts on the right. A mirrored table turns reading a sales report into work rather than a glance.
  • Forms and printing: the printed invoice and the exported report — do they inherit the direction, or revert when exported to PDF?
  • Alphabetical sorting: are customer names sorted correctly in Arabic?

None of this appears on a vendor's page. All of it appears in the first ten minutes of a trial, if you know where to look.

The Arabic invoice is a rule, not a preference

Here the subject moves from comfort to compliance.

A tax invoice in Saudi Arabia is issued in Arabic, and another language may be added alongside it. So an Arabic invoice is not a matter of taste, and a system that prints only English field labels leaves you outside the requirement however comfortable its interface is.

What to check specifically:

  • Field labels on the printed invoice rather than on screen: the tax number, value added tax, the total including tax
  • Item names — does the system accept an Arabic item name, or store English and display a translation?
  • Credit and debit notes — do they print in Arabic like the invoice?

In Snad invoices and notes are issued in Arabic, and integration with the Zakat, Tax and Customs Authority begins with the Basic plan and is included in Pro — it is not part of the free plan.

Dates: Hijri and Gregorian together

Most global systems know one calendar. A Saudi business lives with two on the same day.

Where that shows in practice:

  • Employee contracts and leave are sometimes counted on the Hijri calendar
  • Government obligations and seasons follow the Hijri calendar
  • Invoicing and financial reporting are Gregorian

A system that knows only the Gregorian calendar does not stop you working — but it moves the conversion into an employee's head or a side file, and that is where the error happens.

The practical test: enter a Hijri date into a date field and watch. If the system rejects it or silently converts it to something else, learn that now rather than six months of data later.

The digits that break your spreadsheet

This is the most overlooked detail, and its effect is immediate.

Eastern Arabic numerals look correct on screen, but to spreadsheet software they are not numbers. Exported to a file and opened in Excel they arrive as text: they will not sum, will not sort numerically, and will not enter any formula.

The result is an accountant retyping an entire column by hand — or worse, building a report on an incomplete total without noticing.

What the system should provide:

  • Display in whichever digits you prefer in the interface
  • Export in Latin digits (0123456789) for CSV and Excel files
  • A stable decimal separator that does not change with the interface language

The test: export any report containing figures, open it in Excel, and select the column. If no sum appears in the status bar, the file holds text rather than numbers.

Five tests you can run yourself

Do not ask a vendor whether they support Arabic — the answer is always yes. Run these five inside the free trial:

#The testWhat it proves
1Open a sales report and see where the first column beginsA right-to-left layout, or Arabic text in a left-to-right template
2Issue an invoice and print it to PDFArabic on the printed invoice, not just on screen
3Create an item with an Arabic name and search part of itCorrect Arabic storage and indexing
4Export a report to Excel and select the amounts columnCalculable numbers, or text
5Create a user and switch their language to EnglishWhether the data survives the switch

Five tests take under half an hour and spare you every claim on a vendor's page.

One last note about support rather than software: the language your question is answered in, and the working hours it is answered within, are as much a part of being Arabic as the interface. Send a question during the trial and see when and in which language the reply arrives.

Frequently asked questions

What is the difference between a translated system and a localised one?
Translation changes the words; localisation also changes the layout: right-to-left screens, table column order, direction inherited by printing and export, and correct Arabic alphabetical sorting.
Must a tax invoice be in Arabic?
Yes. A tax invoice in Saudi Arabia is issued in Arabic and another language may be added alongside it. Check the printed invoice rather than the entry screen, and check the credit and debit notes with it.
Why will my figures not sum after export to Excel?
Usually because the export used Eastern Arabic numerals, which spreadsheet software treats as text rather than numbers. The test: select the amounts column in Excel; if no sum appears in the status bar, the file holds text.

Try what you read on your own numbers

Start on the free Starter plan: 2 of Snad's nine apps for one user, with no end date.

Starter stays free · 7-day trial of any paid plan, no card