Working through it
The question of Arabic on invoices reflects a real feature of the UAE system: Arabic is the official language, and official and legal documentation can be required in Arabic, while in commercial practice English is very widely used and accepted. Navigating this means understanding both the formal position and the practical reality.
Formally, Arabic is the official language of the UAE, and the FTA operates in Arabic as well as providing for English. The tax legislation and the FTA can require that records and documentation be maintained or provided in Arabic, and this can extend to invoices and other tax documents, particularly when the FTA is examining a business’s affairs. So the underlying legal position gives Arabic a status that a business cannot simply ignore.
Practically, however, the vast majority of business-to-business commerce in the UAE is conducted in English, and English or bilingual invoices are routinely issued and accepted between businesses. Most companies invoice in English day-to-day without any difficulty, and their customers, being in the same commercial environment, expect and accept this. So the reality of ordinary invoicing is English-dominant.
The way to reconcile the formal position and the practical reality is to issue in English (or bilingually) routinely while retaining the ability to produce Arabic when it is required. The situations where Arabic may specifically be needed are formal ones (an FTA audit, a request from the authority, a legal or official process) where you may be asked to provide documentation in Arabic. A business that can produce an Arabic version of its invoices and records when asked is well positioned; one that cannot may face difficulty if the FTA requires it. So the answer is not a simple yes or no but a practical stance: English for routine commerce, Arabic capability for when it is formally required.
The formal position versus everyday practice
Understanding both dimensions lets you take a sensible, low-risk stance on invoice language:
- Arabic is the official language, and the FTA can require records and documentation, including invoices, in Arabic
- English is widely used and accepted: most business-to-business invoicing in the UAE is in English or bilingual
- Formal processes may require Arabic: an FTA audit or request may ask for documentation in Arabic
- Day-to-day commerce is English-dominant: customers generally expect and accept English invoices
- The safe stance is dual capability: issue in English routinely, but be able to produce Arabic when required
The tension between the official status of Arabic and the practical dominance of English is resolved not by choosing one but by covering both: English for everyday invoicing, Arabic capability for when the FTA or a formal process requires it. That stance keeps you compliant without unnecessary daily burden.
When Arabic is likely to be needed
Knowing the situations where Arabic may specifically be required helps you prepare for them rather than being caught out, since they tend to be formal rather than routine.
The clearest case is an FTA audit or examination. When the authority is reviewing your affairs, it may require documentation, including invoices and records, to be provided in Arabic, since it operates in the official language. A business that has issued everything in English and cannot produce Arabic versions may face difficulty or delay in responding. Formal requests from the FTA outside an audit can similarly involve Arabic. And certain legal or official processes may require Arabic documentation.
Outside these formal contexts, the day-to-day need for Arabic on invoices is limited, routine commercial invoicing between businesses proceeds in English. So the pattern is that Arabic tends to be required in formal, authority-facing situations rather than in ordinary trade. This is why the sensible preparation is not to issue every invoice bilingually as a matter of course, which may be unnecessary effort, but to ensure you have the capability to produce Arabic versions when a formal situation calls for it.
The practical implication is to build Arabic capability into your invoicing and record-keeping infrastructure. Many accounting and invoicing systems can produce bilingual or Arabic documents, so configuring this ability, even if you use English by default, means that if the FTA requires Arabic, you can provide it. A business that has thought about this in advance responds to an Arabic requirement smoothly; one that has not may scramble to translate records under the pressure of an audit.
A practical stance on invoice language
For most UAE businesses, the sensible approach to invoice language balances everyday practicality against the formal status of Arabic, and it is worth setting deliberately rather than defaulting.
The recommended stance is: issue invoices in English or bilingually for routine commerce, which suits your customers and the commercial environment; ensure your accounting or invoicing system is capable of producing Arabic versions of invoices and records; and be ready to provide Arabic documentation if the FTA or a formal process requires it. This gives you the practicality of English for daily use and the compliance safety of Arabic capability for when it matters.
The reason to be deliberate about this, rather than simply assuming English is always fine, is that the official status of Arabic is real and the FTA’s ability to require it is genuine. A business that only realises Arabic may be required when an audit asks for it is in a weaker position than one that built the capability in advance. At the same time, over-engineering, insisting on bilingual invoices for every transaction when English is accepted and Arabic is not currently being demanded, is unnecessary effort for most businesses. The middle path of English-by-default with Arabic-capability is proportionate.
Because the specifics (exactly when Arabic is required, and how it interacts with e-invoicing and evolving requirements) can change and can depend on your circumstances, it is worth confirming the current position for your business, particularly if you operate in contexts where Arabic documentation is more likely to be required. As with much of tax compliance, the goal is to be prepared for the formal requirement without carrying unnecessary daily burden, which for invoice language means English for commerce, Arabic when required, and the systems in place to switch between them without friction.
What trips people up
- Assuming English is always sufficient, when the FTA can require Arabic in formal processes.
- Being unable to produce Arabic versions when an audit or the FTA requires them.
- Over-engineering with bilingual invoices for every transaction when English is accepted.
- Only realising Arabic may be required when an audit asks for it.
- Not configuring your system to produce Arabic where needed.
- Ignoring the official status of Arabic because English dominates commerce.
- Failing to confirm the current position for your specific circumstances.
How to act on this
- Issue invoices in English or bilingually for routine commerce.
- Configure your system to produce Arabic versions of invoices and records.
- Be ready to provide Arabic documentation if the FTA requires it.
- Confirm the current position for your circumstances, especially where Arabic is more likely required.
- Build the capability in advance rather than scrambling during an audit.
Related questions
Frequently Asked Questions
Do my invoices need to be in Arabic?
UAE tax invoices are commonly issued in English and widely accepted, but Arabic is the official language and the FTA can require documentation, including invoices, in Arabic. The safe position is to issue in English routinely while being able to produce Arabic where required, particularly in an audit or formal process.
Can I invoice only in English?
For routine commerce, generally yes, most business-to-business invoicing in the UAE is in English and customers accept it. But you should retain the ability to produce Arabic versions, because as the official language Arabic can be required by the FTA, especially during an audit or a formal request. English by default, Arabic capability in reserve.
When would I actually need Arabic invoices?
Mainly in formal, authority-facing situations (an FTA audit or examination, a formal request from the authority, or certain legal or official processes) where documentation may be required in Arabic. Day-to-day commercial invoicing between businesses proceeds in English, so the Arabic need tends to be formal rather than routine.
Should I issue every invoice bilingually?
Not necessarily. That may be unnecessary effort for most businesses if English is accepted and Arabic is not currently being demanded. The proportionate approach is English or bilingual for routine invoicing, with the system capable of producing Arabic when a formal situation requires it, rather than bilingual-everything as a default.
What if the FTA asks for Arabic during an audit?
If you have the capability to produce Arabic versions of your invoices and records, you can respond smoothly. If you have only issued in English and cannot produce Arabic, you may face difficulty or delay. This is why building Arabic capability into your invoicing system in advance is worthwhile even if you use English by default.
How do I prepare for a possible Arabic requirement?
Ensure your accounting or invoicing system can produce bilingual or Arabic documents, so that if the FTA requires Arabic you can provide it without scrambling. Many systems support this. Configuring the ability in advance, even while using English routinely, is the practical preparation for a formal Arabic requirement.
Is English or Arabic more accepted in practice?
In everyday commerce, English is dominant, most UAE business-to-business invoicing is in English or bilingual, and customers expect and accept it. Arabic’s importance is in its official status and the FTA’s ability to require it, which surfaces in formal contexts rather than routine trade. Both matter, in different situations.
Does e-invoicing change the language position?
The interaction of language requirements with the structured e-invoicing format is part of the evolving framework, so confirm the current position as e-invoicing applies to you. The general stance (English for commerce, Arabic capability for formal requirements) still holds, but the specifics of how language works within structured invoicing are worth checking.
Should I confirm the position for my business?
Yes, particularly if you operate in contexts where Arabic documentation is more likely to be required, or if the specifics matter to you. The exact requirements can depend on circumstances and can change, so confirming the current position for your business ensures your stance on invoice language is both compliant and proportionate.
Tell us how you invoice and who your customers are. We will set up your system to issue in English routinely and produce Arabic when the FTA requires it, a proportionate, compliant stance without daily burden.
Check my compliance status 058 101 9570
Last reviewed 27 July 2026. Rates, thresholds and deadlines change, the e-invoicing provider deadline has already moved once. Confirm current requirements with the Federal Tax Authority before acting, or ask us to check your position.