Whether an invoice is issued in German, English or both is not normally decided by a blanket language rule in Germany. What matters is that the mandatory information is complete and unambiguous, the tax treatment is correct, the customer’s requirements are met and the document can still be audited later. This guide explains German law as at 23 September 2026 and is not tax or legal advice.
The short answer
German is usually the simplest choice for a customer in Germany. English is commonly practical in international business, while a bilingual invoice can prevent questions on both sides. The German VAT Act does not impose a general rule that every invoice must be written in German. However, German is the official language of tax procedures under section 87 of the Fiscal Code, so a tax office may request a translation of a foreign-language document.
Language does not change the VAT details required on the invoice or the e-invoice rules. A complete English invoice can be better than an incomplete German one. For public authorities, large customers and procurement portals, the specified language, format and channel take priority.
A practical decision table
| Situation | Usually sensible | Check first |
|---|---|---|
| Supplier and customer in Germany | German | Contract, ordering process, e-invoice duties |
| German customer with English as its group language | German or bilingual | Customer approval workflow |
| Foreign customer | English or bilingual | Contract, tax and destination-country rules |
| Public-sector customer | Language specified in the order, often German | Tender documents, routing ID, XRechnung and portal |
| Cross-border EU B2B supply | English or bilingual | VAT IDs, place of supply, reverse charge and filings |
Choose for everyone who processes the invoice, not only the original contact. Purchasing, accounts payable, tax advisers and auditors must also understand it.
Does German law prescribe an invoice language?
Section 14 of the German VAT Act lists invoice requirements but contains no general German-language requirement. For ordinary transactions, an invoice is therefore not invalid merely because it is written in English or another language.
This does not permit vague wording. Authenticity, integrity and legibility must be ensured. The invoice must clearly identify the supplier, customer, transaction, consideration and VAT treatment. Contractual language clauses, recipient specifications and special rules may narrow the practical choice.
Which details must be clear?
A standard invoice must generally contain:
- the supplier’s and customer’s full names and addresses;
- the supplier’s tax number or VAT identification number;
- the issue date and a unique sequential invoice number;
- quantity and type of goods or scope and type of service;
- date or period of supply;
- consideration split by VAT rate and exemption;
- agreed reductions not already reflected;
- VAT rate and amount, or a clear reference to the applicable exemption.
Bank details, payment terms, purchase-order number and a contact are useful but are not, solely for that reason, mandatory VAT details. Nor is the place of supply a universal invoice field. Reduced requirements apply to invoices up to EUR 250 under section 33 UStDV.
Special wording and cross-border cases
Depending on the transaction, section 14a UStG requires additional details—for example both VAT IDs in certain intra-EU cases or a “reverse charge” reference. Businesses applying the German VAT exemption scheme for small businesses (Kleinunternehmerregelung) must not show VAT and should clearly refer to the exemption under section 19 UStG.
Following the Federal Ministry of Finance letter dated 17 September 2025, the tax administration accepts equivalent terminology from another official EU language for certain statutory invoice references. In a German audit context, “Steuerschuldnerschaft des Leistungsempfängers / Reverse charge” is still especially clear. The place-of-supply and reporting analysis must be completed before issuing the invoice; language cannot replace it.
What may the tax office request?
German is the official language under section 87 of the Fiscal Code. If foreign-language invoices, accounting documents or contracts are submitted, the authority may request a translation and, where justified, one prepared by a publicly appointed or sworn translator. If the requested translation is not supplied, the authority may obtain one at the party’s expense.
English is often understood in practice, but there is no right to an English-language tax audit. A German explanation or bilingual document is prudent for high-value transactions, unusual service descriptions or complex agreements.
German, English or bilingual?
German minimises questions from German customers, advisers and the tax office. It is the robust default when the contract and communication are German.
English suits an international recipient when the terminology is unambiguous. Do not improvise translations of German tax concepts if doing so obscures their legal meaning.
Bilingual combines both advantages but needs controlled templates. Each amount, date and tax treatment must have one meaning. Divergent language blocks create a contradiction, not a convenience.
How to create a reliable bilingual invoice
Use approved terms side by side, such as “Rechnungsnummer / Invoice number” and “Leistungsdatum / Date of supply”. Keep names, addresses, IBAN, VAT IDs, currency and figures unchanged. State in the contract which language prevails if prose differs.
Translate descriptive fields only; do not create a second tax calculation. Credit notes, cancellations and corrections should follow the original invoice’s language model and reference it unambiguously.
Customers in Germany and recurring work
For a German B2B customer, German is normally the friction-free starting point. If the group language is English, ask before the first invoice whether English is sufficient or whether accounts payable expects German field names.
Record the choice in the customer profile. A stable template prevents language, currency and statutory wording from changing between billing periods. For continuing services, make the service and billing period especially clear.
Foreign customers and EU transactions
English is often the shared language for a foreign customer. You must still check the destination country’s invoice rules and the German VAT classification. EU B2B workflows often need VAT-ID validation and correct reverse-charge wording; exports require different evidence.
A bilingual document helps when German accounts and a foreign recipient use the same invoice. Agree the currency, payment route, bank fees and governing law as well. These are commercially important points that invoice language alone cannot resolve.
E-invoices: language and format are different
An e-invoice contains structured, machine-readable data. A PDF sent by email is generally not an e-invoice under the statutory definition. Since 1 January 2025, businesses established in Germany must be able to receive e-invoices. Transitional issuance rules remain: all issuers may generally use other invoices until the end of 2026; where the issuer’s previous-year turnover does not exceed EUR 800,000, the transition generally runs until the end of 2027. Small businesses under the Kleinunternehmerregelung are exempt from issuing e-invoices but must be able to receive them. The official Federal Ministry of Finance e-invoice FAQ explains details and exceptions.
The human-readable rendering can be English while the structured data uses standardised codes and fields. The structured record is authoritative. The visual version and data must agree; a polished bilingual PDF cannot correct a wrong tax code.
XRechnung, ZUGFeRD and public-sector customers
XRechnung implements European standard EN 16931 in Germany and is especially relevant for public procurement. Check the currently accepted version and recipient rules before sending; the official XRechnung versions and bundles are updated over time. ZUGFeRD may also qualify as an e-invoice where the chosen profile meets the legal requirements.
Public bodies may additionally specify a routing ID, purchase-order reference, transmission channel and portal. The order and portal instructions control. A PDF attachment next to an XRechnung does not replace missing structured mandatory data.
Workflow before the first invoice
- Check the contract, order and customer instructions for language and format.
- Classify the transaction: domestic, EU, non-EU, exempt or reverse charge.
- Determine standard and special mandatory wording.
- Choose a controlled German, English or bilingual template.
- For e-invoices, test the permitted format and delivery channel.
- Verify names, addresses, tax ID, number, dates, service, consideration and VAT.
- Archive the original format together with validation and transmission evidence.
Invoices must generally be retained for eight years under section 14b UStG, beginning at the end of the year in which they were issued. Other records or ongoing proceedings can require longer retention.
Common mistakes
- Using English although the customer requires German or a particular portal.
- Confusing the German tax number with a VAT ID.
- Describing the service or service period too vaguely.
- Explaining reverse charge informally but omitting the required reference.
- Showing different totals, dates or terms in German and English.
- Treating a normal PDF as an e-invoice.
- Retaining only the visual copy instead of the original structured record.
- Continuing to apply the former ten-year period even though invoices are now generally retained for eight years.
Frequently asked questions
Is an English invoice valid in Germany?
It can be, provided all applicable details are complete, clear and legible. Contractual or sector requirements can still demand German, and the tax office may request a translation.
Must every invoice be bilingual?
No. Bilingual presentation is a practical option, not a general duty. It is valuable when a German issuer, foreign recipient and German audit all need the same information.
Must “reverse charge” be written in German?
Equivalent terms in other official EU languages are accepted for certain mandatory references. “Steuerschuldnerschaft des Leistungsempfängers / Reverse charge” is particularly clear. The underlying tax treatment must, of course, be correct.
Can an e-invoice contain English text?
Yes, if the format, codes and mandatory fields are valid and the recipient can process it. The language of the visual rendering and the technical data format must be assessed separately.
Which version controls if the texts conflict?
The contract or invoice should identify a prevailing language. However, a priority clause cannot cure contradictory tax totals or structured data; those must match in every representation.
Conclusion
German is the robust default in German business, English is a permissible and useful working language for international customers, and a controlled bilingual invoice is often the best bridge. Legal reliability comes from the combination of complete details, correct VAT treatment, a compliant e-invoice format, recipient requirements and consistent data—not from language alone.
Official sources and date
Reviewed on 23 September 2026 against section 14 UStG, section 14a UStG, section 14b UStG, section 33 UStDV, section 87 AO, the Federal Ministry of Finance e-invoice FAQ, the Ministry’s VAT Application Decree and the official XRechnung versions.