What Language to Put on a VAT Invoice (Wording, Narratives, and Languages)

"What language should be on the invoice?" turns out to mean two different questions, and both matter. One is which natural language the invoice is written in (English, French, Arabic, Japanese). The other is the specific wording the law expects to appear: the label, the reverse charge narrative, the exemption reference, the words your customer's tax authority is going to look for. Get either wrong and the invoice can be rejected, the buyer's input VAT claim denied, or your VAT return treated as non-compliant.

This guide covers both. Skip to the section you need.

Which natural language should the invoice be in?

The general rule across most jurisdictions: invoices can be issued in any language, but the tax authority can ask for a translation into the local language for audit purposes. The supplier bears the cost of translation. In practice this means English is fine almost everywhere for issuance, but you should be ready to provide a translation if asked.

Specific country positions:

• EU: Article 248a of Directive 2006/112/EC lets each Member State require translation of invoices received by businesses in that country. Most do not enforce this on issuance, but Italy, France, and Germany have all asked for translations during audits.
• United Kingdom: HMRC accepts English invoices for UK supplies and cross-border supplies. Translation can be requested during a VAT inspection.
• UAE: Tax invoices may be in English or Arabic. The Federal Tax Authority can request an Arabic translation.
• Saudi Arabia: ZATCA Phase 2 e-invoices must be issued in Arabic. Bilingual Arabic and English is acceptable, but Arabic is the legally controlling text.
• Japan: Qualified invoices may be issued in English; bilingual is common. The T-number formatting must be exact regardless of language.
• China: Fapiao must be in Simplified Chinese. Foreign-language commercial invoices are not a substitute.
• Brazil: NF-e and NFS-e must be in Portuguese.
• Russia: Tax invoices must be in Russian.

The pattern is simple. Most of the world accepts English. Civil-law jurisdictions with structured e-invoicing (Saudi Arabia, China, Brazil, Russia, plus Italy SDI on the technical envelope) require the local language for the legally controlling document. Bilingual works almost everywhere if you have the bandwidth.

The label: what to call the document

Some jurisdictions require a specific label at the top of the document. Others do not.

• EU: No specific label is mandated by Directive 2006/112/EC. "Invoice" is fine; "VAT Invoice" is common practice.
• UK: No prescribed wording. "VAT Invoice" is the convention.
• UAE: The words "Tax Invoice" must appear clearly (Article 59 of the Executive Regulation).
• Saudi Arabia: The words "Tax Invoice" are required, plus the QR code and the mandated XML envelope.
• Bahrain, Oman, Egypt: "Tax Invoice" label required, mirroring the GCC pattern.
• Singapore: "Tax Invoice" required when GST is charged.
• Australia: "Tax Invoice" required for taxable supplies above A$82.50.
• Japan: No label is required; the document is identified as a qualified invoice by the presence of the registered T-number.

Reverse charge wording (cross-border B2B)

When you sell B2B services across a border and the buyer accounts for the VAT in their country, the invoice must say so. The exact words the law accepts vary, but every jurisdiction wants something unambiguous.

EU (Article 226(11a) of the VAT Directive)

Any of the following are accepted by all Member States:

• "Reverse charge"
• "Reverse charge: VAT to be accounted for by the recipient"
• "Reverse charge under Article 196 of Council Directive 2006/112/EC"

The mention can be in any official EU language. Citing Article 196 is the most defensible form because it removes ambiguity about which reverse charge applies (Article 196 is the cross-border B2B services rule).

United Kingdom

HMRC accepts any narrative that makes the reverse charge clear. Common phrasings:

• "Reverse charge: Customer to pay the VAT to HMRC"
• "VAT to be accounted for by the recipient under the reverse charge"
• "Reverse charge: S55A VATA 1994 applies" (for the domestic construction reverse charge specifically)

UAE

Article 48 of the Federal Decree-Law 8/2017 governs reverse charge. Acceptable wording:

• "Subject to reverse charge under Article 48 of the UAE VAT Law"
• "Reverse charge applies. VAT to be accounted for by the recipient."

Saudi Arabia

"Reverse charge mechanism applicable" or "VAT to be accounted for by the customer". For B2B cross-border supplies, the structured ZATCA invoice carries a specific reason code rather than free text alone.

Australia, New Zealand, Singapore, Canada

The B2B "reverse charge" concept exists but is implemented as zero-rating or out-of-scope on the supplier side, not as a reverse charge on the invoice. The wording you typically use:

• "GST not charged. Recipient to self-assess under [Division 84 (AU) / Section 8(4B) (NZ) / Section 14(1)(b) (SG) / s.218 ETA (CA)]."

Japan

Japan's electronic services regime for foreign suppliers is a B2C registration scheme. For B2B, the foreign supplier issues an invoice without consumption tax and notes "Subject to reverse charge under the Japanese Consumption Tax Act". The Japanese customer self-assesses.

Zero-rated, exempt, and out-of-scope: how to phrase it

Whenever VAT is not charged, the invoice should say why. Article 226 of the EU directive requires a reference to the relevant exemption provision. Useful patterns:

• Zero-rated export: "Zero-rated export under Article 146 of Directive 2006/112/EC" or "Zero-rated under VAT Notice 703 (UK)"
• Intra-EU supply of goods: "Intra-Community supply, exempt under Article 138 of Directive 2006/112/EC"
• Out-of-scope: "Outside the scope of UK VAT" or "Out of scope: place of supply is the recipient's country under Article 44"
• Exempt supply: "Exempt supply under Article 135(1)(d) of Directive 2006/112/EC" (financial services example)

The pattern is the same everywhere. State the treatment, cite the article, and keep the wording stable across all your invoices. Tax inspectors look for consistency; mixed phrasings on similar transactions invite questions.

Currency wording

If you invoice in a non-local currency, the VAT amount must be stated in the local currency in addition to the invoice currency:

• EU: VAT amount in euro (or the Member State's national currency).
• UK: VAT amount in sterling.
• UAE: VAT amount in AED.
• KSA: VAT amount in SAR.
• Japan: Consumption tax amount in JPY.

Recommended phrasing: "Total VAT due: 380.00 EUR (1,500.00 USD invoice value at 1.0000 EUR/1.2632 USD on the tax point date 2026-04-15)." Pick a published rate source (ECB, the local central bank, or HMRC's monthly published rates) and stick with it.

E-invoicing changes the game in some jurisdictions

In countries with structured e-invoicing, the "language" on the invoice is partly XML, not free text. The tax authority parses fields, not paragraphs. This means:

• The reverse charge narrative is encoded in a field (for example, InvoiceTypeCode 388 in UBL plus a TaxExemptionReasonCode), not just typed into a footer.
• The exemption reference is a code (VATEX-EU-AE for reverse charge under the EU code list), not a free string.
• Free text is still allowed in human-readable rendering, but the XML is the legally controlling document.

The countries where this matters today: Italy, France (PDP, phasing), Germany (B2B receipt 2025, issuance 2027 to 2028), Poland (KSeF), Spain (VeriFactu), Romania (RO e-Factura), Hungary (RTIR), Saudi Arabia (Fatoora), India (IRN), Brazil (NF-e), Mexico (CFDI), Chile, Peru, Colombia, Turkey. Cross-border B2B in the EU joins the list from July 2030 under ViDA.

You can check the current state for any jurisdiction with our free e-invoicing mandate tracker, which lists the format, clearance model, language requirement, and go-live date for 150 jurisdictions.

What to do if you got it wrong

Two questions: was VAT collected at all, and was the wording incorrect on an otherwise compliant invoice?

• Wording missing or wrong, VAT correctly accounted for: Issue a corrected invoice with the same number plus a suffix (for example, INV-2025-0918-R1) referencing the original. Most tax authorities accept this if done before the audit.
• VAT charged when it should have been reverse charge: Issue a credit note for the original invoice and reissue without VAT plus the reverse charge narrative. Update the VAT return for the period.
• Reverse charge applied when VAT should have been charged: Issue a credit note and reissue with VAT. The customer is liable for the missing VAT plus interest in most jurisdictions.

For the mechanics of correcting an invoice, see our credit note guide.

Quick reference: copy-pasteable narratives

Standard wordings you can drop into invoice templates today:

• EU B2B cross-border services: "Reverse charge: VAT to be accounted for by the recipient under Article 196 of Council Directive 2006/112/EC."
• EU B2B intra-Community supply of goods: "Intra-Community supply, exempt under Article 138 of Council Directive 2006/112/EC."
• UK to non-UK B2B: "Outside the scope of UK VAT. Place of supply is the recipient's country."
• UK reverse charge: "Reverse charge: Customer to account for VAT to HMRC."
• UAE reverse charge: "Subject to reverse charge under Article 48 of the UAE VAT Law."
• Australia B2B from non-resident: "GST not charged. Recipient to self-assess under Division 84 of the GST Act."
• Japan B2B from non-resident: "Subject to reverse charge under the Japanese Consumption Tax Act."
• US export of services: "Sale of services to a foreign customer. No US sales tax applies." (Sales tax, not VAT, but commonly asked.)

For the country-by-country comparison of full invoice content requirements, see our companion post on VAT invoice requirements for SaaS by country.