Bilingual tax invoices: an Arabic/English guide
ZATCA requires Arabic on every tax invoice issued in Saudi Arabia, full stop — English alone isn't compliant, even if every customer you deal with reads English fine. Plenty of businesses also want English on the same invoice, for international customers, foreign-owned parent companies, or their own audit trail. The cleanest way to satisfy both is one properly built bilingual invoice, not two separate versions.
Why Arabic is mandatory, not optional
Saudi tax law requires invoices to be issued in Arabic, and ZATCA's e-invoicing regulations carry that requirement forward into the structured, QR-coded invoices Phase 1 introduced. An English-only invoice, however well designed, isn't a compliant tax invoice on its own — Arabic has to be present, even if English is added alongside it.
Why businesses add English anyway
The most common reasons: the customer is an international buyer who doesn't read Arabic, the business itself has foreign ownership and needs English for internal reporting, or the finance team simply wants a document that's usable without translation later, during an audit or a due diligence review. None of these override the Arabic requirement — they just explain why English gets added on top of it.
What actually needs to appear in both languages
Company name and address, customer details, line-item descriptions, quantities, unit prices, VAT amounts and totals should all appear in both Arabic and English on a proper bilingual invoice. Fields that are purely numeric, like amounts and dates, don't need duplicating since numerals read the same either way, but every text label and description does.
Layout matters more than people expect
Arabic reads right-to-left, and a bilingual invoice needs to reflect that natively, not bolt an Arabic column onto an English left-to-right template. A common and avoidable mistake is running Arabic text through a layout built for English, which leaves punctuation, numbers, and alignment looking backwards or awkward. Done properly, the Arabic side reads right-to-left and the English side reads left-to-right, each formatted the way a native reader of that language would expect.
Where the QR code and compliance fields fit in
The mandatory ZATCA QR code, invoice hash, and structured fields required under e-invoicing rules sit on top of the bilingual content, not instead of it — a bilingual invoice still needs to meet every Phase 1 structural requirement covered on our QR code invoicing page.
How Booksara handles this
Booksara renders both languages on every line automatically, with Arabic formatted right-to-left and English left-to-right on the same document, so there's no separate template to maintain or manual translation step to remember. Every invoice still carries the required QR code and structured fields, so bilingual formatting and compliance aren't two separate jobs.
Frequently Asked Questions
Is Arabic required on Saudi tax invoices?
Yes. Saudi tax law and ZATCA's e-invoicing regulations require Arabic on every tax invoice — an English-only invoice isn't compliant on its own.
Can I issue an invoice in English only?
No, not as a compliant tax invoice. English can be added alongside Arabic, but Arabic has to be present.
Which fields need to appear in both languages?
Company and customer details, line-item descriptions, and labels for amounts and totals. Purely numeric fields like dates and figures don't need duplicating.
Does a bilingual invoice still need the ZATCA QR code?
Yes. The QR code, invoice hash, and other structured Phase 1 fields apply regardless of how many languages the invoice is written in.
Does Booksara generate bilingual invoices automatically?
Yes. Booksara renders Arabic and English on every invoice line automatically, with correct right-to-left formatting for Arabic, alongside the required QR code and compliance fields.
A bilingual invoice shouldn't mean double the work. Try Booksara free and see Arabic and English rendered correctly on the same invoice, every time.