Bilingual Tax Invoice UAE: Arabic + English PINT-AE Format Guide 2027

Is Arabic mandatory on a UAE tax invoice?

The short answer is no, not by default — but yes, on request. Under Article 5 of Cabinet Decision No. 52 of 2017 (the Executive Regulations to the VAT Law), a UAE VAT-registered business may issue tax documentation in English. The same article gives the UAE Federal Tax Authority (FTA) explicit authority to require an Arabic translation when needed for audit, dispute resolution or compliance review. In practice this means every UAE business issuing tax invoices should be capable of producing a clean Arabic version of any invoice on demand. The cheapest, lowest-risk way to be ready is to issue bilingually from day one. For background on the full field set required under Article 59, see our UAE tax invoice format 2026 guide. For the broader e-invoicing rollout context, our UAE e-invoicing 2026 brief covers the timeline.

The bilingual question gets sharper from 1 January 2027, when Phase 1 of the UAE’s PEPPOL PINT-AE e-invoicing mandate goes live for VAT-registered businesses with annual revenue at or above AED 50 million. From that date, structured XML invoices flow peer-to-peer through accredited access service providers (ASPs), and the customer-facing presentment file (the PDF your buyer actually opens) becomes a second, parallel artefact. The XML can carry bilingual line items natively. The PDF should mirror that. We help SMEs prepare their item masters and templates through our e-invoicing setup advisory service.

What “bilingual” really means inside PINT-AE

PINT-AE is the UAE-specific PEPPOL International Invoice profile, built on top of UBL 2.1, the same Universal Business Language XML standard used across more than 90 countries for structured e-invoicing. UBL 2.1 has a built-in concept that most accounting teams miss: nearly every text element in the schema can be repeated with a languageID attribute, allowing the same field to carry multiple languages in one structured document.

For a UAE bilingual tax invoice, the elements that benefit most from language tagging are:

1. cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name — supplier’s legal name in both English and Arabic
2. cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name — customer’s legal name in both languages
3. cac:InvoiceLine/cac:Item/cbc:Name — short product or service name per line
4. cac:InvoiceLine/cac:Item/cbc:Description — extended item description per line
5. cac:PaymentTerms/cbc:Note — payment terms text
6. cbc:Note at invoice header — general invoice notes, often containing legal text or reverse-charge statements

The transmission mechanism is the 5-corner DCTCE model (Decentralised Continuous Transaction Controls and Exchange). Your accounting system (corner 1) sends to your ASP (corner 2), which transmits to the buyer’s ASP (corner 3), which delivers to the buyer’s system (corner 4). Corner 5 is the FTA, which receives a reporting copy of each invoice in near-real-time. All five corners see the bilingual payload — the Arabic version is not “extra” data, it is part of the structured invoice itself.

Which fields to translate, which to leave alone

Not every field needs an Arabic translation. Some are language-neutral by nature — TRNs, dates, monetary amounts, VAT percentages. Others must be translated because they carry meaning a human reads. Here is the practical field-by-field mapping we use when preparing client item masters for PINT-AE readiness.

The supplier’s Arabic legal name must match exactly what appears on the trade licence — not a transliteration. UAE trade licences carry an Arabic name and an English name as two separate fields; the e-invoice must use both. The same applies to the customer when they are a UAE entity. For foreign customers, the Arabic field can carry a transliteration or be left to the English version only via languageID='en'.

RTL is your ERP’s job, not the standard’s

Arabic is read right-to-left. This is straightforward for a single Arabic word inside an English paragraph — modern browsers and PDF renderers handle inline bidirectional text well. It becomes harder for a full bilingual invoice layout where you have parallel columns, tables and totals that need to flow in different directions on each language side.

The accounting platforms most commonly used by UAE SMEs handle Arabic with varying levels of polish out of the box:

• SAP S/4HANA — full RTL support via SAPscript / SmartForms; bilingual PDF templates are a configuration job, not a development job
• Oracle NetSuite — supports Arabic locale and RTL PDF templates; SuiteScript needed for complex bilingual layouts
• Microsoft Dynamics 365 Business Central — Arabic localisation pack required; bilingual templates supported via Word merge layouts
• Tally Prime — Arabic via “Multilingual” feature; PDF export is functional but rarely premium-looking without template work
• Zoho Books — bilingual template support via custom HTML/CSS; RTL flips automatically when Arabic locale is set on the customer record
• QuickBooks Online — Arabic UI in MENA edition; bilingual invoice templates require export to PDF software like Adobe Acrobat for fine-tuning
• Odoo — strong Arabic support via the l10n_ae localisation module; bilingual QWeb templates well documented
• Wafeq — UAE-native cloud accounting platform; bilingual invoices supported natively without template work

The PDF your customer reads vs the XML the FTA reads

This is the distinction that trips up most accounting teams. Under PINT-AE, two artefacts exist for every invoice:

1. The structured XML payload — UBL 2.1 invoice in PINT-AE format, transmitted through the 5-corner DCTCE network, legally binding, the single source of truth for tax purposes
2. The customer-facing presentment file — typically a PDF, human-readable, what your customer opens in their email or WhatsApp, what their accounts team prints and files

The XML is the legal record. The PDF is the courtesy copy. But here’s the thing — UAE business culture treats the PDF as the invoice. Disputes, payment delays, reconciliation queries: they all happen against the PDF, never the XML. So PINT-AE may not formally mandate a bilingual PDF, but your actual commercial relationship usually does.

“

The XML is what the FTA reads. The PDF is what your customer reads. Both must say the same thing in both languages, or the audit catches you twice.

The cleanest pattern is PDF/A-3 with embedded XML. PDF/A-3 is a long-term archival PDF format that allows arbitrary file attachments inside the PDF. The XML payload becomes an attachment inside the customer-facing PDF — one file, both layers. Your customer opens what looks like a normal bilingual invoice. Their accounting software can extract the embedded XML if it supports PINT-AE. The FTA audit team can retrieve either layer on demand. ASPs like Avalara, Comarch, Basware, Pagero, Edicom and Sovos all support PDF/A-3 generation as part of their PINT-AE delivery workflow.

Where we see the Arabic side go wrong

Across the SME invoices we review for e-invoicing readiness, the same Arabic-side errors keep appearing. Most are template-level mistakes that compound across thousands of invoices once the template is deployed:

1. Hijri dates — the FTA recognises Gregorian only. Using Hijri creates date-of-supply ambiguity and is flagged in audit.
2. Wrong VAT label — using “VAT” in Latin letters on the Arabic side. The correct form is “ضريبة القيمة المضافة” or the abbreviated “ض.ق.م”.
3. Inconsistent currency symbol — switching between “AED”, “د.إ” and “درهم” on the same invoice. Pick one form and stay with it across all line items, subtotals, totals and payment terms.
4. Transliterated supplier name — writing the supplier’s Arabic name as a phonetic English spelling instead of the legal Arabic name on the trade licence.
5. Stale legal Arabic — using terminology from the pre-VAT era (2017 and earlier). The VAT lexicon was standardised by the FTA; using outdated terms suggests poor compliance hygiene.
6. Mirrored numbers — Western digits (1, 2, 3) and Eastern Arabic digits (١، ٢، ٣) used inconsistently on the same document. Both are acceptable but mixing them on one invoice is a red flag.
7. Missing TRN label translation — showing only “TRN” in Latin script on the Arabic side. The Arabic equivalent “رقم التسجيل الضريبي” should appear alongside.
8. Reverse-charge note missing in Arabic — if Article 48 reverse charge applies, the statement that the recipient is liable to account for VAT must be present in both English and Arabic to be enforceable for the buyer’s input-VAT recovery.

For credit notes, the same bilingual rules apply, plus the document title becomes “Tax Credit Note / إشعار دائن ضريبي”. Read more in our UAE VAT services guide for the wider VAT compliance picture.

The translator, ERP and ASP workflow

The bilingual workflow we run for clients preparing for PINT-AE has three stages:

Stage 1 — Item master review. Export your full list of invoiced items and services from the ERP. A native Arabic-speaking translator with UAE business context reviews each line for Arabic equivalent, VAT category and standard description. This is a one-off project, typically AED 2,000 to AED 8,000 depending on item count, that pays back across every invoice you issue for the next decade. The output is a clean mapping table that gets imported back into the ERP item master.

Stage 2 — Template build. Your ERP’s PDF template gets reworked to support bilingual layout. The recommended pattern is a two-column layout: English on the left side reading left-to-right, Arabic on the right side reading right-to-left, with mirrored table flows on each side. Totals appear once, centred or on the dominant-language side. This is typically a 4 to 12 hour engagement with your ERP implementation partner.

Stage 3 — ASP configuration. Your accredited ASP — whether Avalara, Comarch, Basware, Pagero, Edicom or Sovos — needs to be configured to extract the bilingual fields from your ERP and tag them correctly with languageID attributes in the outgoing UBL XML. ASPs charge typically AED 1.50 to AED 4 per outgoing invoice on the standard volume tiers; bilingual configuration is usually included in setup at no extra per-invoice cost.

For businesses below the AED 50M Phase 1 threshold, Phase 2 lands on 1 July 2027 — six months later. The same preparation steps apply. The intra-group VAT-group transition exemption runs until 1 January 2029 for entities issuing supplies only within their VAT group, but this is a narrow carve-out and most groups still benefit from bilingual readiness across their external invoices.

Worked example: a bilingual UAE tax invoice

Here is a stripped-down sample of a bilingual UAE tax invoice for a B2B supply above AED 10,000, showing the parallel English and Arabic layout. The structure satisfies Article 59 of Cabinet Decision 52/2017 on both language sides and is PINT-AE ready in terms of field coverage.

═══════════════════════════════════════════════════════════════════════
TAX INVOICE                                              فاتورة ضريبية
═══════════════════════════════════════════════════════════════════════

SUPPLIER / المورد
Velmont Crest Accounting          فيلمونت كرست للمحاسبة
Downtown Dubai, UAE               وسط مدينة دبي، الإمارات
TRN: 100 1234 5678 9001           رقم التسجيل الضريبي: 100 1234 5678 9001

RECIPIENT / المستلم
Yellow Rock Trading LLC           يلو روك للتجارة ذ.م.م
JAFZA South, Dubai                جافزا الجنوبي، دبي
TRN: 100 9876 5432 1003           رقم التسجيل الضريبي: 100 9876 5432 1003

Invoice No / رقم الفاتورة: INV-2027-0142
Invoice Date / تاريخ الفاتورة: 2027-01-15
Supply Date / تاريخ التوريد: 2027-01-15

────────────────────────────────────────────────────────────────────────
Description / الوصف                    Qty   Unit    Net      VAT 5%
                                       الكمية الوحدة الصافي   الضريبة
────────────────────────────────────────────────────────────────────────
Monthly bookkeeping retainer            1    9,500   9,500    475.00
باقة المحاسبة الشهرية

VAT advisory — Q1 review                1    3,500   3,500    175.00
استشارات ضريبة القيمة المضافة - الربع الأول

────────────────────────────────────────────────────────────────────────
Net Amount / المبلغ الصافي                            AED 13,000.00
VAT (5%) / ضريبة القيمة المضافة (٥٪)                  AED    650.00
TOTAL DUE / الإجمالي المستحق                          AED 13,650.00
────────────────────────────────────────────────────────────────────────

Payment terms / شروط السداد:
Net 30 days from invoice date.
السداد خلال ٣٠ يوماً من تاريخ الفاتورة.

A few things to notice in this layout. The supplier and recipient names appear in both their licensed English form and their licensed Arabic form — not transliterations. The TRN itself is identical on both sides because it is numeric. The invoice date is shown in Gregorian Western digits; the Arabic side can equally show “٢٠٢٧/٠١/١٥” if your template uses Eastern Arabic digits consistently. The VAT label is fully translated, including the “(5%)” appearing as “(٥٪)” on the Arabic side. The currency is “AED” throughout for stylistic consistency — “د.إ” would be equally valid as long as it is used consistently.

For the structured XML payload that accompanies this PDF presentment under PINT-AE, the relevant UBL excerpt looks like this:

<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="EA">1</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="AED">9500.00</cbc:LineExtensionAmount>
  <cac:Item>
    <cbc:Name languageID="en">Monthly bookkeeping retainer</cbc:Name>
    <cbc:Name languageID="ar">باقة المحاسبة الشهرية</cbc:Name>
    <cbc:Description languageID="en">Monthly bookkeeping services for January 2027</cbc:Description>
    <cbc:Description languageID="ar">خدمات المحاسبة الشهرية لشهر يناير ٢٠٢٧</cbc:Description>
    <cac:ClassifiedTaxCategory>
      <cbc:ID>S</cbc:ID>
      <cbc:Percent>5.00</cbc:Percent>
    </cac:ClassifiedTaxCategory>
  </cac:Item>
</cac:InvoiceLine>

Both <cbc:Name> elements appear in the same <cac:Item>, distinguished only by the languageID attribute. The buyer’s receiver displays whichever language its user has configured; the FTA audit copy sees both.

For cross-border bilingual invoicing under corporate tax, see our corporate tax services guide. For the full e-invoicing timeline, our UAE e-invoicing 2026 brief covers ASP selection and transition windows.

A bilingual tax invoice in the UAE is structured data discipline, not a translation task. It lives in your item master, your ERP, your PDF template and your ASP configuration — four places, one setup. Get it right once and every invoice you issue carries the full Arabic and English audit trail. After that, you genuinely stop thinking about it.