Do UAE e-invoices need to be in Arabic? What the guidelines actually say

The UAE Electronic Invoicing Guidelines (version 1.1, June 2026) describe the framework as designed to support both the Arabic and English languages. They do not set a rule that every e-invoice must carry Arabic text, and they do not require translation.

The mandatory fields document lists 41 fields for an electronic tax invoice: identifiers, dates, the seller and buyer, the buyer’s TRN where the buyer is registered, currency, amounts and tax. None of the fields is described as a language field. An e-invoice is a structured data file, so what matters is that each field holds the right value.

Language rules are not only set by tax law. A ministry or a semi-government buyer may ask for Arabic descriptions in its purchase terms. A family-owned group may want its Arabic trade name to match its licence exactly. And when the FTA or a court reviews records, Arabic is the official language of the state, so an owner may decide to keep Arabic versions of key documents.

These are commercial and practical reasons, not e-invoicing rules. The answer for most businesses is to hold both names cleanly in their records and let each buyer’s preference decide what appears on the readable copy.

The real risk is not language but inconsistency. A buyer’s legal name on its trade licence might be “مؤسسة الريان للتجارة العامة”, its English trade name “Al Rayyan General Trading Est.”, and your sales team might have typed “Rayyan Trading”. When structured data is checked against registration records, a sloppy English nickname is a bigger problem than a missing Arabic one.

Take the time to record each customer’s legal name exactly as it appears on the licence or TRN certificate, in the script it uses there, with a separate field for the short name your team prefers.

A Fujairah IT company bills a federal entity AED 84,000 plus AED 4,200 VAT for a network upgrade. The entity’s procurement terms ask for Arabic and English descriptions on supporting documents. The company keeps its invoice data in one record: the English line “Network switch installation, 12 sites” and the Arabic “تركيب محولات الشبكة، 12 موقعاً”, both stored against the item.

When e-invoicing applies to this supply, the structured invoice carries the required fields through the company’s ASP. The readable copy for the procurement file shows both languages. Nothing has to be retyped and the amounts match in both places.

If you decide to carry Arabic on your documents, do it once and do it properly. Patchy translation, where some items have Arabic and others do not, looks worse than a clean English-only file.

• Copy each customer’s legal name from its licence or TRN certificate, character for character.
• Keep your own Arabic trade name exactly as it appears on your licence.
• Write Arabic item descriptions for the products and services government or family-group buyers actually purchase.
• Ask a native speaker on staff or your accountant to review the Arabic text once, before it is used on live invoices.
• Record which buyers have asked for Arabic, so the sales team knows which readable layout to send.

HelloBooks stores Arabic and English text on customer and item records, so invoices and quotes can show both. The AI agent reads Arabic and English on supplier bills and receipts you upload, pulls out the supplier name, TRN, date and totals, and posts the bill for review. The software interface itself is in English.

If your buyers want a particular bilingual layout, the team can set up the invoice template for you; book a call at /book-a-demo or write to hello@hellobooks.ai. Your accountant should check the Arabic wording on any template before it goes into use.