What an Arabic-Language Invoice Actually Needs

Running your invoice template through a translator produces Arabic words in a layout designed for English. Native readers notice immediately, in the same way an English speaker notices a document where every line is centred and the dates are in the wrong order. It reads as careless.

This is what actually changes when an invoice is in Arabic, and what most tools get wrong.

Direction Is Not Just Text Alignment

Arabic is written right to left, and that governs the whole document, not just the sentences.

The page flips. Your logo moves to the top right. The client's details move to the left. In a line items table, the description column sits on the right and the amount on the left — the reverse of an English invoice. Reading order runs right to left across the whole layout.

Tables mirror. This is the part tools most often miss. They will render Arabic text correctly inside cells while leaving the column order in English sequence. The result is a document that is technically readable but feels wrong to anyone reading it naturally.

Alignment follows direction. Labels align right. Numbers in an amount column typically align left in an RTL layout, which feels backwards until you have seen a few real invoices.

Mixed content stays coherent. An Arabic invoice containing an English product name, a Latin-script company name, or an IBAN has bidirectional text. The Unicode bidirectional algorithm handles most of this correctly if your tool implements it — and produces scrambled output if it does not. An IBAN rendered backwards is not a cosmetic problem; it is an unpayable invoice.

Letters Have to Join

This is the single most common technical failure, and it is immediately visible.

Arabic letters change shape depending on their position in a word. The letter ha looks different at the start of a word, in the middle, at the end, and standing alone. Correct rendering joins them into connected words.

When a tool fails at this, you get text that reads as disconnected letters in the wrong order — the Arabic equivalent of receiving an invoice that says "e c i o v n i". Native readers can sometimes decode it, but it destroys any impression of professionalism.

If you are producing Arabic PDFs, test with a real Arabic sentence and have a native reader look at the output. Do not trust that it worked because characters appeared.

Which Numerals?

Arabic has two numeral systems in common use, and picking the wrong one is a subtle tell.

Western Arabic numerals (0 1 2 3 4 5 6 7 8 9) are what English uses. Despite the name, these are standard in business documents across much of the Arab world, including the Gulf and North Africa.

Eastern Arabic-Indic numerals (٠ ١ ٢ ٣ ٤ ٥ ٦ ٧ ٨ ٩) are used in Egypt, Iraq, Iran and parts of the Levant, particularly in more traditional or government contexts.

There is no universal right answer. Practical guidance:

• Default to Western numerals for business invoices unless you know otherwise. They are more widely accepted and never actively wrong.
• Ask the client if you are billing a government body or traditional institution in Iraq or Egypt.
• Be consistent. Mixing both systems in one document looks like a bug, because it usually is one.
• Never use Arabic-Indic numerals in an IBAN, account number or reference code. These need to be transcribable exactly.

Numbers themselves stay left-to-right even inside right-to-left text. "١٢٣" reads one-two-three, not three-two-one. If your tool reverses digit order, it is broken.

Dates

Three things go wrong with dates on Arabic invoices.

Format ambiguity. 05/09/2026 is 5 September in most of the world and 9 May in the US. On an invoice with payment terms attached to it, this ambiguity is expensive. Write the month as a word, or use an unambiguous format.

Calendar systems. The Gregorian calendar is standard for business across the Arab world. The Hijri (Islamic lunar) calendar appears in government and religious contexts, and some Saudi documents carry both. If a client asks for Hijri, they will tell you; do not add it speculatively.

Month names. Arabic month names for the Gregorian calendar differ by region. The Levant and Iraq commonly use forms like كانون الثاني for January, while Egypt and the Gulf use يناير. Neither is wrong, but using the form your client's region does not use is another small signal of distance.

Names and Addresses

Name order. Arabic names often follow a given name, father's name, grandfather's name, family name pattern. Do not restructure a client's name into "First Last" because your template has two fields. Use the name exactly as they gave it to you.

Honorifics matter more than in English business writing. Where an English invoice says "John Smith", an Arabic one may reasonably carry a title. Follow the client's lead from how they signed their emails.

Company names are often not translated. A registered company name is a legal identity. If the company is registered under an Arabic name, use the Arabic name. If it is registered in Latin script, keep it in Latin script even in an Arabic document. Translating a registered name creates a mismatch with their records.

Addresses do not always follow the Western structure. Many addresses in the region are descriptive rather than numeric — a district, a nearby landmark, a building name. Do not force them into a street-number-postcode template that does not fit. A wrong-looking address field is not just cosmetic; it can hold up a payment approval.

Fonts

Not every font that displays Arabic displays it well.

The font must actually support Arabic. A font without Arabic glyphs will substitute, and you will get boxes, blank space, or a jarring visual mismatch mid-document.

It must support letter shaping, meaning it needs the positional variants for each letter. A font with partial Arabic coverage can produce text that renders but looks subtly broken.

Line height needs more room than Latin text. Arabic script has diacritics above and descenders below. Line spacing that looks tight and elegant in English will collide in Arabic.

Numerals should be consistent with your choice. Some Arabic fonts default to Arabic-Indic numerals even when you typed Western ones.

Embed the font in the PDF. If the font is not embedded, the reader's machine substitutes something else, and your carefully laid out invoice arrives looking like a different document.

A Practical Test

Before you send an Arabic invoice to a real client, produce one with:

• A full Arabic sentence in the description field
• An English or Latin-script term mixed into that sentence
• An IBAN or account number
• A date
• An amount with decimals
• A long client name

Then open the PDF on a different machine and, if you can, have a native Arabic reader look at it. Ask them one question: does this look like a document a professional company would send? That answer is worth more than any checklist.

Why This Matters Commercially

An invoice is often the only document a client's finance department ever sees from you. If it is well made in their language, it signals that you take the relationship seriously and that working with you will not create extra work for them.

If it arrives with broken letter joining, a mirrored IBAN, and a date nobody can interpret, it signals the opposite — and it lands on the desk of the person who decides when you get paid.

Getting this right is not about linguistic perfection. It is about the invoice looking like it was made for the person receiving it, because it was.