Belgium Invoice Language Requirements: Trilingual Guide

Belgian invoices must be issued in the official language of the region where the issuing company has its registered office. Not the customer's preferred language, not the language of the transaction, and not English — the language of the seller's registered region. Get it wrong, and the invoice can be declared legally null and void.

Belgium's three official languages map to four distinct regions, each with its own language legislation governing commercial documents including invoices:

Region	Required Language	Governing Legislation
Flanders	Dutch	Decree of 19 July 1973 (Taaldecreet)
Wallonia	French	French Community decree on the use of languages in social relations
German-speaking Community (Eupen-Malmedy)	German	German Community language legislation
Brussels-Capital Region	Dutch or French (issuer's choice)	Bilingual status under coordinated Brussels language laws

The determining factor is the company's registered office (siège d'exploitation / exploitatiezetel) — the address of the place of business as registered with Belgian authorities. A company headquartered in Ghent must invoice in Dutch even when billing a French-speaking client in Liège. A firm registered in Brussels can choose either Dutch or French.

Which invoice fields must comply? All legally mandatory elements under the Belgian VAT Code must appear in the required language. This includes:

• The word "invoice" itself (factuur in Dutch, facture in French, Rechnung in German)
• Full identification of both parties (name, address, VAT number)
• Invoice date and sequential number
• Description of goods or services supplied
• Unit prices, quantities, and total amounts
• VAT rate(s) applied, VAT amount, and any exemption references

Non-mandatory content — such as general terms and conditions, payment instructions, or supplementary commercial notes — has more flexibility and may appear in additional languages. But every field that the Belgian VAT Code requires on a valid invoice must be in the region's official language. An accompanying translation is permitted as a supplement, never as a substitute.

These rules carry real weight for international trade. According to Eurostat's intra-EU trade data for 2024, Belgium exported 332.3 billion euros in goods to other EU member states in 2024, making it the EU's third-largest intra-EU exporter behind Germany and the Netherlands. That volume of cross-border commerce means Belgium's language rules touch a substantial number of international invoicing relationships daily.

What "Null and Void" Means for Non-Compliant Invoices

Issuing a Belgian invoice in the wrong language is not a minor administrative error. Under Belgian commercial law, a court can declare that invoice nietig (null and void), which means it is legally unenforceable. The issuing company cannot use it to compel payment through legal proceedings. The invoice, for all practical purposes, ceases to exist as a legal document.

The practical consequence is severe. If your company issues an invoice in French to a customer whose registered office sits in the Dutch-speaking region, that customer can raise the language violation as a defense in court. They are not obligated to pay based on that document. You effectively lose your legal right to collect the debt until you replace the non-compliant invoice with one drafted in the correct language.

This is not a theoretical risk gathering dust in legal textbooks. Belgian courts have invoked language-based nullity in commercial disputes, and debtors have successfully used the wrong-language defense to avoid or delay payment. A buyer looking for grounds to contest or stall a payment obligation will find Belgium's language laws remarkably cooperative.

The remedy exists, but it costs you. The issuing company can correct the situation by issuing a replacement invoice in the proper language. The original nullity does not permanently destroy the underlying debt. However, the correction introduces delays that compound quickly:

• Cash flow disruption while the replacement invoice is prepared, delivered, and a new payment term begins
• Administrative overhead from reissuing documents, updating records, and communicating with the customer
• Lost leverage in any ongoing payment dispute, since the debtor had a valid legal defense during the interim period

For companies managing high volumes of Belgian invoices across language regions, even a small percentage of non-compliant invoices can create a persistent drag on collections.

For comparison, Canada's bilingual invoice requirements under Bill 96 impose regulatory fines for non-compliance in Quebec, but the invoice remains a valid commercial document. Belgium's approach is more severe — rather than penalizing the issuer with a fine, the law attacks the legal enforceability of the debt itself. The creditor's ability to collect through the courts depends on language compliance.

---

The EU Ruling That Changed Belgium's Cross-Border Invoice Rules

Before 2016, Flanders enforced a strict Dutch-only requirement for all invoices, including those sent to companies in other EU member states. A Flemish company invoicing a supplier in France or Italy had no legal option to issue that invoice in any language other than Dutch. The business relationship, the recipient's language, the commercial practicality of the arrangement — none of it mattered. Dutch was mandatory, full stop.

That changed on 21 June 2016, when the Court of Justice of the European Union delivered its judgment in Case C-15/15 (New Valmar BVBA v. Global Pharmacies Partner Health Srl). The case involved a Flemish company whose invoices to an Italian partner were challenged under Belgium's language laws. The CJEU ruled that Flanders' requirement to issue cross-border invoices exclusively in Dutch violated Article 35 TFEU, the treaty provision guaranteeing free movement of goods. The Court's reasoning was direct: forcing companies to invoice foreign partners in a language those partners could not read constituted a measure having equivalent effect to a quantitative restriction on exports. It created a barrier to cross-border trade that EU law does not permit.

Belgium's Legislative Response: The 2017 Decree

Belgium moved relatively quickly. The Decree of 7 July 2017 modified the Flemish language rules specifically for cross-border invoices, creating a new framework that preserved the regional language obligation while accommodating the CJEU's ruling.

Under the amended rules, a company may now issue a supplementary copy of the invoice in a different language alongside the original. While the CJEU case and the 2017 Decree specifically addressed the Flemish Taaldecreet, the underlying principle extends to all Belgian language regions — a Walloon or German-speaking Community company may similarly provide a supplementary translation for EU/EEA cross-border invoices. The conditions are specific:

• Both parties must understand the chosen language. You cannot simply pick any language; there must be a demonstrable shared understanding.
• The recipient must be established in an EU or EEA member state. The exception was designed to address the free movement concern at the heart of the CJEU ruling.
• Any official EU/EEA language may be used for the supplementary copy, provided the mutual comprehension requirement is met.

What the 2017 Exception Does Not Cover

The critical limitation is twofold. First, the original invoice in the region's required language remains mandatory. The Dutch, French, or German version (depending on the region) must still exist. The translated copy supplements it; it never replaces it.

Second, this exception applies only to EU/EEA cross-border invoices. If you are invoicing a company in the United States, Switzerland, or the United Kingdom post-Brexit, the 2017 framework offers no relief. For non-EU/EEA recipients, the original language-only rule applies in full — your invoice must be issued in the language required by the region where your registered office is located, with no supplementary translation option under this decree.

---

Wrong Language, Valid VAT Deduction: The Legal Paradox

Belgian invoice language rules create a striking contradiction: an invoice issued in the wrong language can be commercially void yet perfectly valid for VAT purposes. These two legal tracks operate independently, and understanding where they diverge is essential for anyone managing Belgian VAT compliance.

The commercial consequence is straightforward. An invoice that violates the regional language requirement is null and void under the Decree on the Use of Languages. The issuing party cannot rely on that document to enforce payment through Belgian courts.

The VAT consequence follows entirely different logic. Circular letter AAF n02/2013, issued by the Belgian tax administration on 23 January 2013, established that the right to VAT deduction cannot be refused solely because invoice details appear in a non-official language. The tax authority's position is grounded in economic substance: what matters for VAT purposes is whether a genuine taxable transaction occurred and whether the invoice contains the information needed to verify that transaction. The language in which that information is presented does not alter the underlying economic reality.

To illustrate how these tracks diverge in practice: a Flemish company receives an invoice written entirely in French from a Walloon supplier. Under commercial law, that invoice is null and void in the Flemish Region. The Flemish company cannot be compelled to pay based on that document, and the supplier cannot use it to pursue payment in court. Yet under VAT law, the same Flemish company is fully entitled to deduct the VAT charged on that invoice. The tax administration will not deny the deduction on language grounds alone.

For recipients of non-compliant invoices, the correct course of action is twofold. First, claim the VAT deduction — you are entitled to it regardless of the language issue. Second, request a corrected invoice from the supplier in the appropriate language for commercial enforceability. These two steps happen in parallel; there is no need to wait for a language-compliant replacement before exercising your right to deduct.

This paradox shifts the entire burden of non-compliance onto the supplier. The recipient suffers no VAT disadvantage from receiving an invoice in the wrong language. The supplier, however, faces a serious problem: they have issued a document that entitles the recipient to a VAT deduction and documents a real transaction, but that same document cannot be used to enforce payment if a dispute arises. The commercial risk sits squarely with the party that failed to comply with the language requirement.

---

Belgium's Language Rules Under the 2026 E-Invoicing Mandate

Belgium's 2026 B2B e-invoicing mandate requires domestic invoices to use the Peppol BIS 3.0 structured format. This raises a straightforward question: does switching to structured e-invoices eliminate the language requirement?

The short answer is no. But the longer answer reveals a meaningful shift in how language compliance works in practice.

Peppol BIS 3.0 transmits invoice data as standardized XML fields. Amounts, dates, tax codes, party identifiers, line item quantities, and VAT calculations all sit in language-neutral structured fields. A "Total Amount" field contains a number. A tax category code is a code. These elements carry no natural language content, which means they cannot violate any regional language rule. For the bulk of an invoice's structured data, the language question simply does not arise.

What does not change is the treatment of free-text fields. Peppol invoices include fields for goods and services descriptions, payment terms, notes, and additional references. These fields carry natural language content, and that content remains subject to Belgium's regional language legislation. A company with its registered office in the Flemish Region must still write its invoice descriptions in Dutch, even when those descriptions sit inside a Peppol XML envelope.

E-invoicing therefore reduces but does not eliminate language compliance obligations. Companies transitioning to Peppol should not assume the structured format renders language rules irrelevant. Your ERP or invoicing software must be configured to generate free-text content in the correct regional language based on the issuing entity's registered office location. Language logic needs to be built into your e-invoicing workflows, not treated as a problem that structured data solves automatically.

Belgium is not implementing e-invoicing in isolation. Several EU member states are rolling out or planning similar mandates, each layering local compliance requirements on top of the Peppol standard. France's upcoming e-invoicing mandate, for example, introduces its own set of domestic requirements alongside the structured format. For companies operating across multiple EU jurisdictions, the pattern is consistent: structured e-invoicing standardizes the data layer, but local regulatory obligations persist in every free-text field you populate.

---

Cross-Border Invoice Compliance: A Practical Checklist

Knowing the legal framework is half the equation. Applying it correctly to your specific business structure is what actually keeps invoices enforceable. The scenarios below cover the most common configurations for companies operating in or selling to Belgium.

Determine Your Scenario

Scenario 1: Single Belgian registration in Flanders, Wallonia, or the German-speaking Community. Your registered office dictates the invoice language for every transaction, regardless of where your customer is located within Belgium. A company registered in Namur (Wallonia) invoicing a client in Antwerp (Flanders) must issue that invoice in French. The customer's language preference is irrelevant under the Decree on the Use of Languages.

Scenario 2: Registered in the Brussels-Capital Region. You may choose Dutch or French on a per-invoice basis. There is no legal obligation to match the customer's language, but maintaining a consistent pattern for each customer relationship simplifies audit trails. Pick one language per client and document the rationale in your invoicing policy.

Scenario 3: Multiple offices across Belgian regions. Each establishment issues invoices in the language of its own region. A company with branches in Ghent and Liège produces Dutch invoices from the Ghent office and French invoices from the Liège office. The critical factor is which entity or branch is the legal issuer on the invoice, not where the goods are delivered or the service performed. If your company uses a centralized invoicing system, the language is still determined by which entity appears as the legal issuer — not by where the system is physically hosted. Ensure your ERP assigns the correct language template based on the issuing entity's registered office, not the billing address or delivery location.

Scenario 4: Non-Belgian EU/EEA company invoicing a Belgian customer. Belgium's regional language laws bind companies based on their registered office location within Belgium. As a foreign company, these rules do not apply to you — issue invoices according to your own country's requirements or in the language agreed with your customer. Your Belgian customer can still deduct the VAT on your invoice regardless of the language (per Circular AAF n02/2013, discussed above). If the trade flows the other direction — a Belgian company invoicing you — they must follow their regional language rules and may provide a supplementary translation in a shared language under the 2017 cross-border exception.

Compliance Checklist

Use this as a pre-launch review for new invoicing workflows or an annual verification for existing ones.

• Confirm the registered office address of every entity that issues invoices. The street address determines the language region, not the mailing address or commercial headquarters.
• Map each address to its language region. Flanders requires Dutch. Wallonia requires French (or German in the eastern cantons). Brussels permits Dutch or French.
• Verify that all mandatory invoice fields use the correct language. This includes the description of goods or services, payment terms, legal mentions, and any required VAT annotations. Numerical fields (amounts, dates, VAT numbers) are language-neutral.
• For cross-border EU/EEA invoices, prepare the legally required original in the correct regional language first. If the recipient needs a version in another language, issue a supplementary copy clearly marked as a translation. The original-language version remains the legally binding document.
• For non-EU/EEA recipients, issue the invoice in the required regional language only. No cross-border translation exception applies outside the EU/EEA framework established by the CJEU ruling.
• Configure your invoicing software to generate content in the correct language based on the issuing entity's location, not the customer's location. If you operate from multiple Belgian regions, ensure each entity or branch has its own language template.
• Document your language policy in writing. In the event of a tax audit or a commercial dispute where nullity is raised, a written policy demonstrates systematic compliance rather than ad hoc guessing.

The Broader European Picture

Belgium's language rules are one layer of a wider patchwork of country-specific invoicing requirements across European markets. Companies operating across multiple jurisdictions encounter different compliance demands in each — from Switzerland's QR-bill format requirements to Belgium's language rules to varying e-invoicing mandates. Building invoicing workflows that can adapt to each country's requirements without manual intervention for every transaction is the common challenge.