B2B e-invoicing Luxembourg: what the bill provides

Where does the Luxembourg B2B e-invoicing obligation stand?

It is not yet in force. In Luxembourg, structured electronic invoicing is mandatory only towards the public sector, and has been since 18 March 2023. A bill tabled on 30 July 2026 under number 8815 extends that obligation to domestic commercial transactions between businesses established in Luxembourg. It has not yet been voted.

The distinction to hold on to is one of scope. Since 18 March 2023, any economic operator invoicing a Luxembourg public body under a public procurement or concession contract must transmit a compliant electronic invoice through an authorised channel, the Peppol network or the MyGuichet.lu portal. That obligation is complete: it depends neither on the invoice amount nor on the size of the business. We set it out in our article on electronic invoicing in public contracts.

Between private businesses, nothing has changed to date. A PDF invoice sent by email remains lawful in Luxembourg B2B. That is precisely what bill 8815 sets out to change, and the reason the question deserves attention now rather than at the vote.

What does bill 8815 actually provide?

The Government Council of 17 July 2026, chaired by Prime Minister Luc Frieden, approved a bill amending, first, the law of 16 May 2019 on electronic invoicing in the context of public procurement and concession contracts and, second, the amended law of 12 February 1979 on value added tax. The text transposes article 1 of Council Directive (EU) 2025/516 of 11 March 2025. It was tabled with the Chamber of Deputies on 30 July 2026 under number 8815, on the initiative of the Minister of Finance Gilles Roth.

Its purpose, in the words of the government statement, is to extend the electronic invoicing obligation, currently applicable to public procurement and concession contracts, to domestic commercial transactions between businesses established in Luxembourg. Two words carry the whole scope. Domestic: the transactions covered are internal ones. Established: the test turns on where both parties are established, not on their nationality or that of their group.

The same Council approved a draft grand-ducal regulation establishing the common delivery network and the technical alternatives made available for electronic invoicing. Its stated aim is to prevent senders and recipients from being forced to deploy and use separate, non-interoperable technical solutions. That instrument, more than the law itself, will determine the scale of your IT project.

The timetable for entry into force is set out in the tabled text. We do not reproduce here the dates circulating in the professional press since the summer of 2026: they could not be confirmed against an official source as at this article's publication date, and a bill in parliamentary procedure remains open to amendment, including on its dates. File 8815 at the Chamber of Deputies is the only reference to consult before committing spend on the strength of a deadline.

What counts as a compliant electronic invoice?

Not a digitised invoice. A compliant electronic invoice is a structured file a system can read and process without human intervention. A PDF, even signed, even sent automatically, remains an image the recipient has to read or re-key. The distinction is not semantic but legal: it decides whether the obligation is met.

The Luxembourg technical framework is already settled for the public sector. Any format authorised on the Peppol network is automatically compliant with the European standard EN 16931-1:2017. Two syntaxes are legally admitted: XML UBL, defined by ISO/IEC 19845:2015 and maintained by the non-profit OASIS Open, and XML UN/CEFACT CII developed by UN/CEFACT.

In practice, the question "can my software issue structured XML?" replaces the question "does my software produce a presentable PDF?". These are unrelated capabilities. Accounting software that produces an impeccable document does not necessarily produce a compliant file, and the reverse holds too.

The mandatory content of the invoice does not change. The mandatory invoice details required by VAT law and company law remain due, simply carried by structured fields rather than free text. A missing particular is in fact more visible in XML than in a PDF: the field is empty, and the automated check sees it.

Peppol: what is already in place in Luxembourg

The grand-ducal regulation of 13 December 2021 designated the European Peppol network as the common delivery network for automated receipt of electronic invoices by the public sector. Peppol is run by OpenPeppol, an international non-profit association under Belgian law, and meets the seven criteria set out in article 4ter, paragraph 1, sub-paragraph 1 of the amended law of 16 May 2019.

Functionally, Peppol is a network of accredited access points exchanging structured documents with each other, on the model of a messaging service. You do not connect to Peppol directly: you connect to an access point, belonging either to your software publisher or to a third-party provider. For very low volumes, the MyGuichet.lu portal remains the authorised manual channel.

The issue in moving to B2B is therefore not the existence of the network, which has worked for several years, but its extension to a considerably wider directory of recipients. Every Luxembourg business would need a usable identifier, not only those already invoicing the State.

Why the constraint is already here for many businesses

Waiting for the Luxembourg vote is a risky line of reasoning for any company with subsidiaries, establishments or significant invoicing volume in its immediate neighbours. National mandates and the European calendar are triggered independently of Luxembourg law.

Does a foreign mandate apply to an invoice issued from Luxembourg?

Not mechanically, and this is the point most often misread. The German, Belgian and French mandates target domestic B2B, meaning transactions where supplier and customer are both established in the country concerned. A Luxembourg company invoicing a French customer from Luxembourg does not, on that basis alone, fall within the French mandate.

It does fall within it through its local establishment, where one exists. A Luxembourg group with a French branch, a Belgian subsidiary or a German permanent establishment must handle those entities under their own country's law, on their own timetable, without waiting for the Luxembourg text.

Above these national regimes, Council Directive (EU) 2025/516 of 11 March 2025, known as ViDA, makes electronic invoicing the default system for issuing invoices. From 1 July 2030 it requires a structured invoice compliant with the European standard, coupled with near real-time data transmission, for intra-EU business-to-business transactions. Member States that already operated a national reporting regime must align by 1 January 2035. That framework is what the Luxembourg bill anticipates.

What to do now, without waiting for the vote

Three work streams depend on no date at all and are justified regardless of how the parliamentary procedure ends.

The first is the quality of the counterparty database. A structured invoice requires a usable recipient identifier, in practice built from the VAT number or the trade register number. We regularly see customer and supplier databases where the VAT number sits in free text, with or without a country prefix, sometimes in a comment field. That clean-up takes time, cannot be outsourced the week before a deadline, and shows no visible return for as long as nothing compels electronic invoicing. Which is exactly why it keeps being postponed.

The second is the ability to receive. It is the earliest obligation in every neighbouring regime, and the easiest to underestimate. Receiving XML presupposes an integration flow, a way of handling technical rejections and a matching rule against the order or delivery note. An organisation that only knows how to receive PDFs in a shared mailbox has no short path to that capability.

The third is an inventory of your issuing channels. Many companies invoice from two or three different tools: an ERP, a spreadsheet for intra-group recharges, sometimes a customer portal. Each channel will have to be handled, or retired. The inventory takes half a day and avoids the late discovery, which is the real cost driver.

On the files we support, activating an access point on a tool that embeds one natively, registering the identifier and running issuing tests generally amount to a few hours of configuration, billed at the hourly rate published in our pricing grid. The genuinely expensive item is never the activation: it is the counterparty database clean-up and the handling of invoicing flows that bypass the main tool.

One closing point of method. The tax validity of an invoice does not become a technical question because its medium does. VAT position configuration, reverse charge treatment and retention of a reliable audit trail remain accounting matters, whatever the file format. The format changes the pipe, not the responsibility.

Sources and verification

The facts, dates and legal references in this article were verified on 6 September 2026 against the following sources. The Government Council statement of 17 July 2026 published on gouvernement.lu, for approval of the bill and of the draft grand-ducal regulation. Parliamentary file number 8815 at the Chamber of Deputies, for the tabling date of 30 July 2026 and the author of the text. The official portal efacturation.public.lu and the Guichet.lu pages on transmitting and keying in an electronic invoice under a public contract, for the obligation applicable since 18 March 2023, the authorised channels and the admitted syntaxes.

The law of 16 May 2019 and the grand-ducal regulation of 13 December 2021, published on Legilux, for the common delivery network and the article 4ter criteria. The EUR-Lex database, for Council Directive (EU) 2025/516 of 11 March 2025 and its 2030 and 2035 deadlines. The Chamber of Commerce thematic dossier on electronic invoicing, for the German, Belgian and French deadlines and for the domestic reach of those three mandates.

One point could not be verified against an official source at that date: the exact timetable for entry into force provided by bill 8815. The dates carried by the professional press since the summer of 2026 therefore do not appear in this article. They must be confirmed against the parliamentary file, then in the official journal once the law is voted and published.

This article sets out the law as it stands at the publication date. A bill is not a law: it can be amended, delayed or abandoned. Rates, thresholds and calendars change, and any decision binding your structure should be verified as at the date you rely on it.