Luxembourg is one of the last significant European economies without a generalised B2B e-invoicing mandate. That is changing fast: in July 2026, the Luxembourg government submitted Bill No. 8815 to Parliament, establishing a clear timeline for 2028–2029. For UK and US groups operating subsidiaries or holding structures in the Grand Duchy — as well as for French, Belgian and German groups — the window to prepare is shorter than most finance teams realise.
This article explains the exact state of the regulation, the technical formats required, and the concrete actions CIOs and CFOs must take today.
1. The State of E-Invoicing in Luxembourg in 2026
1.1 What Is Already Mandatory: B2G Since March 2023
Luxembourg is not starting from scratch. Since 18 March 2023, any company billing Luxembourg public-sector entities must transmit structured invoices via the Peppol network (Digiteal). The obligation covers all public procurement contracts and concession contracts, with no minimum invoice threshold.
The technical standard adopted is Peppol BIS Billing v3, based on European standard EN 16931. The Luxembourg Peppol identifier uses prefix 9938 combined with the VAT number (e.g. 9938:LU12345678) or the Trade and Companies Register number. Companies already invoicing Luxembourg public authorities are, in practice, already connected to the Peppol infrastructure.
This point is frequently overlooked by finance teams in foreign groups: if your Luxembourg subsidiary sells to local public contracts, it almost certainly already has an operational Peppol Access Point. The future B2B mandate will build on that same infrastructure.
1.2 Bill No. 8815: The 2028–2029 Timeline
The government approved the text on 17 July 2026 and submitted it to Parliament on 30 July 2026 under reference number Bill No. 8815 (Fonoa). The bill establishes a mandatory domestic B2B e-invoicing regime under the following schedule:
| Date | Obligation |
|---|---|
| 1 January 2028 | All companies must be able to receive compliant electronic invoices |
| 1 July 2028 | Large and medium-sized enterprises must issue electronic invoices |
| 1 January 2029 | All other companies (small, micro) must issue electronic invoices |
Scope: the obligation covers domestic B2B transactions between entities established in Luxembourg for which Luxembourg VAT law requires an invoice. Cross-border transactions, non-taxable supplies in Luxembourg, and intra-EU supplies are explicitly excluded.
Size thresholds for the large/medium distinction (Phase 1 issuance from July 2028): a company falls into this category if it exceeds at least two of the following three criteria, based on 2026 figures:
- Total balance sheet > €7.5 million
- Net turnover > €15 million
- Average headcount > 50 employees
Subsidiaries of international groups established in Luxembourg frequently exceed these thresholds where they carry out distribution or significant service activities. They will therefore be subject to the issuance obligation from 1 July 2028 — just 21 months after the bill was filed.
Important: the bill is still under parliamentary scrutiny. The dates and thresholds above reflect the text as submitted in July 2026 and may be amended before enactment. Monitor developments through the Luxembourg Chamber of Deputies website.
1.3 Luxembourg in the European Context
The Grand Duchy is aligning with a continental trend already well advanced. To contextualise Luxembourg’s relative lateness and the urgency of preparation:
- Belgium: B2B mandate via Peppol since 1 January 2026, penalties enforced since 1 April 2026 (€1,500 per non-compliant invoice). Over 995,000 companies registered on the Belgian Peppol network by 16 March 2026 (SPF Finances Belgium).
- France: issuance obligation for large enterprises since September 2026, rolling out to SMEs through end-2027.
- Germany: reception obligation (XRechnung/ZUGFeRD) since January 2025, issuance obligation for SMEs from July 2027.
- Luxembourg: B2B mandatory from 2028 — the gap is being closed, but businesses have less time to prepare than they think.
The decision to anchor on Peppol — the same network as Belgium and most Nordic countries — is a strategic choice that simplifies cross-border interoperability within the Benelux region and beyond. For UK and US groups that have already dealt with Peppol compliance in Belgium, Norway or Singapore, the Luxembourg implementation will be familiar territory operationally.
2. Formats and Technical Standards
2.1 Peppol BIS Billing 3.0: The De Facto Standard
Bill No. 8815 mandates use of a structured format compliant with European standard EN 16931 transmitted via a four-corner model network. The Peppol network, already in place for B2G, is the expected operational mechanism, subject to confirmation by secondary regulation (Digiteal).
In practice, this means:
- File format: UBL 2.1 or CII (Cross-Industry Invoice), compliant with Peppol BIS Billing v3
- Transmission: via a certified Peppol Access Point — no direct PDF or email exchange
- Receiver identifier: the buyer must be registered on the Peppol network with its Luxembourg identifier (9938:LU + VAT number)
A PDF, even with an XML attachment, is not sufficient. The invoice must be natively structured and machine-processable.
2.2 Factur-X/ZUGFeRD in a Cross-Border Context
For groups combining French, German or other national flows with Luxembourg entities, a practical question arises: which format to use for intercompany flows?
- France → Luxembourg flows: France mandates Factur-X (PDF/A-3 + XML compliant with EN 16931) for supplies subject to the French obligation. For the Luxembourg counterpart, Peppol UBL will be expected. Both formats share the same EN 16931 semantic schema. Most major ERPs allow conversion between the two via a certified dematerialisation operator or Peppol Access Point.
- Germany → Luxembourg flows: Germany uses XRechnung (UBL or CII) and ZUGFeRD, also EN 16931 compliant. Technical compatibility with Peppol is assured, but transmission must go through a Peppol Access Point for the Luxembourg network.
- UK → Luxembourg flows: UK companies are not subject to a Peppol mandate domestically. For Luxembourg-destined invoices, the UK entity’s ERP will need to generate EN 16931-compliant structured files and route them through a Peppol Access Point. Several global operators (Pagero, Basware, Sovos) offer this as part of their multi-country Peppol connectivity packages.
Practical implication: a Luxembourg holding that receives recharges from a French parent, a UK subsidiary and a German affiliate will eventually need to handle multiple reception formats — Factur-X from France, XRechnung/ZUGFeRD from Germany, and Peppol UBL from those already on the network. This multi-format configuration must be anticipated in ERP setup.
3. Practical Impact on ERPs in Luxembourg Subsidiaries
3.1 The Most Widely Deployed ERPs in Luxembourg
The Luxembourg ERP market reflects the country’s international openness:
- SAP S/4HANA and SAP Business One: present in large enterprises and subsidiaries of international groups.
- Microsoft Dynamics 365 Business Central: widely used in mid-market companies, with an active Microsoft partner network in Luxembourg (Cegeka, other Benelux integrators).
- Odoo: adopted by Luxembourg SMEs, with a growing local community. The Peppol module has been natively integrated since version 17.1.
- Unit4 and Exact: these Dutch publishers are naturally present across the Benelux. Unit4 (public sector, services) and Exact (SME accounting) both offer native Peppol coverage.
For UK groups using Sage Intacct, Sage X3 or Access Group solutions, the Luxembourg subsidiary frequently runs on a standalone local ERP — most often Business Central or SAP — rather than the group’s primary system. Compliance planning must therefore address both the subsidiary’s local ERP and the group’s consolidation layer.
3.2 Checking Your ERP’s Peppol Coverage
Technical preparation must begin now, well ahead of the 2028 deadlines. Here is the current Peppol coverage status for the main ERPs:
SAP S/4HANA: the Document and Reporting Compliance (DRC) module manages e-invoicing compliance by country. A Luxembourg-specific localisation will be required. SAP relies on certified Peppol operators (Sovos, Pagero, OpenText) for network transmission. Groups already using SAP for France or Germany will need to add the LU configuration to their DRC compliance cockpit.
Microsoft Dynamics 365 Business Central: Microsoft provides a native e-invoicing framework integrated in D365, with Peppol connectors for multiple countries. The Luxembourg localisation should be confirmed with your local integration partner — the framework exists, its LU parameterisation depends on the availability of the official localisation or a certified partner extension.
Odoo 17+: the Peppol module is natively integrated since version 17.1. The Luxembourg localisation (VAT accounts, chart of accounts) is available. Peppol sending is operational for countries where Odoo is a certified Access Point or via a partner. To verify: LU B2B certification, which Odoo SA will confirm as the regulation progresses.
Unit4 and Exact: these publishers were among the first to integrate Peppol, with their home markets (Netherlands, Belgium) being early adopters. Luxembourg coverage is on their B2B roadmap.
Sage and Access Group: neither has announced a certified Peppol Access Point for Luxembourg B2B at time of writing. Companies using these platforms will need to route via a third-party Access Point connector — a capability both vendors offer through their partner ecosystems for other Peppol-mandated countries.
3.3 Five Actions to Take Now
The regulatory calendar gives until January 2028 for reception readiness and July 2028 for issuance (large/medium enterprises). In practice, with ERP configuration timelines, testing, and staff training, compliance projects must start in 2026–2027.
Action 1 — Audit your outbound flows to Luxembourg public sector. If your Luxembourg subsidiary sells to public contracts, it should already be issuing in Peppol B2G since 2023. Verify the flow is operational and the Access Point is certified and current. This B2G flow is the foundation of the future B2B flow.
Action 2 — Identify your Peppol Access Point for Luxembourg. A Peppol Access Point is the technical link connecting your ERP to the Peppol network. For the Luxembourg market, operators such as Digiteal, Pagero, Sovos and Basware offer connectors. If your ERP already has a Belgium Access Point, it will likely cover Luxembourg with minimal additional configuration.
Action 3 — Map your B2B invoicing flows in Luxembourg. Who are your customers established in Luxembourg? What invoice volumes per month? Which size categories (large enterprises vs SMEs)? This mapping calibrates the compliance effort and anticipates which configurations to deploy per phase of the calendar.
Action 4 — Prepare inbound flows (receiving supplier invoices from Luxembourg). Reception becomes mandatory from January 2028, before issuance. Your ERP must be able to process incoming Peppol invoices automatically: UBL file ingestion, purchase order matching, VAT validation, archiving. This automated processing capability is consistently underestimated in compliance projects.
Action 5 — Train accounting and finance teams. Structured e-invoicing changes reconciliation and approval workflows. Teams accustomed to processing PDFs by email will need to adapt their procedures. This change management takes time and cannot be left to the last minute.
4. The Specific Case of Holdings and Cross-Border Groups
4.1 The Luxembourg Holding in a UK/European Group
Luxembourg hosts a large number of holdings for European and international groups, attracted by the country’s fiscal and legal stability. These structures have specific characteristics that complicate e-invoicing compliance.
A Luxembourg holding that issues management fee recharges or services to its French, Belgian, German or UK subsidiaries must anticipate a multi-layer situation:
- To France: once the French subsidiary is subject to the French obligation, it will require invoices in Factur-X format or via an accredited PDP/PPF operator. The Luxembourg holding will need to adapt its issuance format for French customers.
- To Belgium: Belgium has been mandatory via Peppol since January 2026. If the holding invoices a Belgian VAT-registered entity, it should already be sending via Peppol — if it is not, this is an active non-compliance.
- To UK subsidiaries: UK companies do not have a domestic Peppol requirement. However, structured invoice exchange within a group can still be achieved via Peppol if the UK entity has a Peppol identifier — an option several UK-based operators offer. Otherwise, standard formats (PDF + structured data) apply until UK legislation evolves.
- Intragroup Luxembourg flows: from July 2028 (if the holding exceeds the thresholds), it will need to issue in Peppol for invoices to Luxembourg entities.
A typical UK/EU group must therefore configure its ERP to handle simultaneously: Peppol BIS Billing v3 (for LU and BE), Factur-X (for FR), XRechnung/ZUGFeRD (for DE flows). This is not a project of a few weeks.
4.2 SAF-T and Digital Reporting Under Discussion
Alongside the B2B e-invoicing bill, Luxembourg is closely monitoring the European SAF-T (Standard Audit File for Tax) initiative and the European Commission’s ViDA (VAT in the Digital Age) regulation. Discussions are underway to introduce a periodic digital tax reporting mechanism — distinct from but complementary to e-invoicing.
If Luxembourg SAF-T goes ahead (timeline to be confirmed), companies will be required to periodically transmit structured accounting and invoicing data to the AED (Administration de l’Enregistrement et des Domaines). Businesses that have already structured their flows in Peppol will be in a significantly better position to produce this reporting than those still relying on PDF workflows.
Key Takeaways
Luxembourg is aligning its regulation with European standards on a progressive timeline: mandatory reception in January 2028, mandatory issuance between July 2028 (large/medium enterprises) and January 2029 (all others). The Peppol BIS Billing v3 network, already operational for B2G since 2023, is the technical foundation.
For cross-border groups with Luxembourg subsidiaries or holdings, the preparation window is short. ERP compliance projects — flow auditing, Access Point selection, structured invoicing module configuration, team training — require 12 to 18 months under realistic conditions. Waiting for final law enactment before starting would be a strategic mistake.
For further context, see our complete guide to mandatory Peppol e-invoicing in Belgium — the Belgian model is the closest reference to what Luxembourg is implementing — and our article on France’s first month of live B2B e-invoicing (October 2026) for an operational picture of the difficulties encountered by the first wave of French companies. Our Peppol as a European interoperability standard provides the full technical context for any decision-maker structuring their invoicing systems for the years ahead.
