← Writing
November 13, 2026·9 min read· ERP· Finance

Luxembourg's e-invoicing mandate: what France's go-live already broke in SAP AR/AP

By Michel Escoda — Independent Architect & SAP FICO Consultant
Share
Summary

France's e-invoicing mandate went live on 1 September 2026, and it changed more than the file format: rejected invoices must be cancelled and reissued under a new number, lifecycle statuses must be tracked, and credit notes are their own document type. Luxembourg's domestic B2B mandate, with proposed dates of January 2028 to January 2029, is still a Council-approved draft law and may not inherit France's lifecycle-status layer. Across the EU the picture is a matrix of national deadlines, with the Netherlands deliberately waiting for the 2030 ViDA backstop. For SAP AR/AP teams, the work is a cancel-and-reissue procedure, a credit-note mapping audit, and a check of which Document and Reporting Compliance binding is actually in use.

France's e-invoicing mandate went live on 1 September 2026, and the headlines mostly covered it as plumbing: get a certified Peppol connector, generate compliant UBL XML, done. Luxembourg's Government Council approved a draft law in July extending mandatory e-invoicing to domestic B2B, with the first obligations landing in 2028. If you run AR/AP on SAP and you treat that as "France's problem, Luxembourg's future problem, connector swap either way," the France rollout already shows why that reading is wrong — and why the Luxembourg mandate is the next test of the same lesson, not a separate one.

France already proved the point, and broke a habit

The French mandate didn't just require businesses to receive e-invoices as of 1 September 2026, with issuance phased in afterward for larger companies and extended to 1 September 2027 for SMEs and micro-enterprises. It also quietly ended a workaround that AP/AR teams had leaned on for years. Under the Approved Platform (PA) model, once an invoice number is submitted it gets validated for structure, business rules, and duplicate-number checks. According to vatcalc.com's analysis of the French rules, a rejected invoice "should be assumed" to be unreusable once validation fails — it has to be cancelled and recreated with a new identifier, not patched and resent under the old number. French invoicing law always technically required invoices to stay "authentic, complete and unaltered" once issued, but ERP and EDI processes routinely ignored that in practice. The Approved Platform's automated checks remove the shortcut, not by changing the law, but by actually enforcing it.

That is a process change, not a format change, and it comes paired with a second one: France's model requires exchanging invoice lifecycle status messages between supplier, buyer, and tax authority across the life of each document, with several statuses mandatory rather than optional. AP and AR teams now have to actively track and report what happened to an invoice after it was sent, which is new operational surface, not a one-time integration cost. Peppol's own BIS Billing specification adds a third wrinkle that trips up legacy mappings: a credit note is not a negative invoice bolted onto the same pipe. It's its own structured document type, with its own line-item structure and validation rules, which means any SAP configuration or custom EDI mapping that still treats credit memos as a free-text adjustment is likely to hit friction the first time a counterparty enforces that validation.

Inside SAP specifically, the practical trap shows up as a binding, not a feature flag. SAP's Document and Reporting Compliance (DRC) cloud edition is the unified product covering France, Germany, and other country mandates, and SAP is itself an accredited Plateforme Agréée for France. But SAP Community threads from August 2026 show implementers still working through confusion between the legacy "Electronic Invoicing via Peppol" binding, built for the earlier B2G era, and the new "Electronic Invoicing and Reporting via Approved Platform" binding the French private-sector mandate actually requires. Even inside SAP's own tooling, going live on France meant a distinct configuration project, not toggling a connector.

Luxembourg's real timeline: a draft law, not a done deal

Two bridge towers standing with the span between them unfinished and not yet connected — Luxembourg's e-invoicing mandate is a draft law approved at Council stage, not yet an enacted bridge to the 2028-2029 deadlines

Here is the hedge that matters before anything else: Luxembourg's mandate is not yet law. On 17 July 2026 the Government Council approved a draft bill extending mandatory e-invoicing to domestic B2B; per the Luxembourg Chamber of Commerce's summary and corroborating coverage from Banqup, EDICOM, and VATupdate.com, that is a Council-approval stage, not a Chamber of Deputies enactment. Poland's KSeF mandate was delayed twice, from an original July 2024 target to February and April 2026 depending on taxpayer size, and that precedent is a live reason to write Luxembourg's dates as "currently proposed" rather than fixed.

With that caveat stated, the proposed phasing is specific: from 1 January 2028, all Luxembourg businesses must be able to receive compliant e-invoices; from 1 July 2028, large and medium businesses must issue e-invoices for domestic B2B transactions; from 1 January 2029, the issuance obligation extends to all remaining businesses, including small and micro enterprises. The scope is domestic B2B only, both parties Luxembourg-established — cross-border B2B is explicitly excluded for now. The infrastructure is Peppol, which Luxembourg already uses for B2G invoicing: European Commission data shows Luxembourg's B2G e-invoice volume grew from under 100 in 2021 to roughly 1.4 million in 2024 across 11 certified access points, so the rails exist, even if the private-sector mandate doesn't yet.

What Luxembourg explicitly isn't doing, and why that matters

The France-to-Luxembourg comparison has a real limit, and it's worth stating plainly rather than assuming the two mandates are the same mandate on different clocks. As currently drafted, Luxembourg's bill is scoped as mandatory e-invoicing without introducing a domestic real-time e-reporting regime at this stage. That is explicitly different from Belgium, whose e-invoicing mandate (live since 1 January 2026, the first operative domestic B2B mandate in the EU, ahead of France) is described by Vertex and Avalara as already "transitioning toward e-reporting" as a separate next phase planned for 2028.

If Luxembourg doesn't eventually bundle the same CDAR-style lifecycle status exchange that makes France's rollout a workflow problem rather than a connectivity problem, the "this is a process redesign, not a connector swap" thesis may not transfer at the same intensity. A Luxembourg-based AR/AP team should not assume their 2028-2029 project automatically inherits France's invoice-correction and lifecycle-status rework; it should confirm what Luxembourg's final law actually requires, closer to the date, rather than importing France's requirements by default.

The country-by-country trap, and the Netherlands counter-move

A mechanical gear-train of interconnected business modules turning at different rates — Belgium, France, Germany, Spain, and Luxembourg each run their own e-invoicing mandate on a different timeline, with the Netherlands deliberately not engaging this gear until the EU's 2030 ViDA deadline

Zoom out and the picture looks less like a single EU wave and more like a staggered sequence of national bets, each racing toward or deliberately avoiding the same finish line. Belgium is live. France is live. Germany requires receiving since 1 January 2025, with issuance phased in from 2027 for businesses over €800,000 turnover and extending to everyone by 2028. Spain's framework takes effect 6 October 2027 for businesses over €8 million turnover, and 2028 for the rest. Luxembourg's proposed dates sit at 2028-2029. All of this is "pre-ViDA" positioning: the EU-wide VAT in the Digital Age reform makes e-invoicing and digital reporting mandatory for all intra-Community B2B transactions from 1 July 2030 regardless of any member state's domestic timeline, and every national mandate above is effectively getting ahead of that backstop on its own schedule.

Not every country is racing. The Netherlands has explicitly chosen not to legislate an earlier bespoke national mandate the way Belgium, France, Luxembourg, and Germany have, instead targeting domestic B2B e-invoicing for July 2030 and domestic e-reporting for July 2031, aligned directly to the EU's own ViDA dates. That is a legitimate strategic choice — avoid building a domestic system now only to rebuild it again for ViDA in 2030 — and it undercuts any framing that every EU economy is sprinting ahead of the floor. For an SAP finance team with operations across multiple member states, the honest planning takeaway is that there is no single "EU e-invoicing deadline" to design against; there is a matrix of dates that have to be tracked country by country, with real risk that any one of them (Luxembourg's most of all, given its draft-law status) moves again before it's final.

Why governments are doing this at all is less ambiguous: the European Commission's VAT Gap report put the EU-wide compliance gap at €128 billion in 2023, with a policy gap (the difference between potential and actual revenue) of 50.5%. Continuous transaction controls and real-time reporting are the primary lever regulators are using to close that gap, which is the underlying reason the mandate wave keeps expanding rather than settling.

What this actually asks of your SAP AR/AP team

Three things worth doing before any Luxembourg-adjacent deadline, informed directly by what France's go-live actually exposed rather than by the marketing language around any given mandate:

First, treat the current France pilot window, and any Luxembourg phase-in once the law is final, as the testing ground for a cancel-and-reissue procedure with proper new invoice numbering — not as an opportunity to patch the old "resend under the same number" habit into a slightly different connector. Banqup's own guidance to Luxembourg-facing teams is to review current invoicing processes now and confirm Peppol/EN 16931 readiness before the 2028 receive deadline, which is a tacit admission that the France window is meant to be used as a dry run.

Second, audit whether your SAP configuration or custom EDI mapping still handles credit notes and corrections as a cosmetic variant of a normal invoice. Under Peppol BIS Billing 3.0, a credit note carries its own CreditNoteTypeCode and line-item structure; mappings that don't already reflect that will likely surface as rejection or reconciliation friction the first time a platform enforces the distinction, independent of which country's mandate triggers the check.

Third, if your estate runs SAP Document and Reporting Compliance, confirm which binding you're actually on — the legacy Peppol-only binding built for the B2G era, or the newer Approved-Platform binding the France mandate requires — before assuming DRC "already handles" whatever comes next. No Luxembourg-specific DRC country pack has been publicly announced as of this writing; that is 15 months out from the earliest proposed deadline, which is not unusual for SAP's localization cadence, but it is a gap worth tracking rather than assuming SAP will have solved by default.

None of this guarantees Luxembourg's bill passes on schedule, or that it ends up requiring the same lifecycle-status exchange France does. The fair reading is narrower than "the EU e-invoicing wave means total AR/AP transformation everywhere": it's that the one mandate which has actually gone live, France's, changed real operational habits that had nothing to do with connectivity, and that the SAP finance teams who treated it as a config toggle are the ones most likely to be caught rebuilding corrections processes under deadline pressure when their own country's mandate, Luxembourg's included, finally lands.

Sources

  1. KPMG, "Luxembourg's e-invoicing mandate takes shape," 3 Aug 2026.
  2. EIN News, "France's E-Invoicing Pilot Program Starts the Compliance Countdown," 3 Aug 2026.
  3. vatcalc.com, "France B2B e-invoicing & B2C e-reporting final legals," 28 Jul 2026.
  4. vatcalc.com, "France e-invoicing: the end of invoice corrections," Aug 2026.
  5. Basware, "Basware Customers Go Live on France's E-Invoicing Mandate, Two Months Ahead of the September Deadline," 21 Jul 2026.
  6. Global VAT Compliance, "France's E-Invoicing Reform: Are You Ready for 1 September 2026?," 2 Aug 2026.
  7. Thomson Reuters Europe, "E-invoicing in France: regulatory updates and compliance."
  8. Service-Public.gouv.fr (French government), "Electronic invoicing: it's coming soon!"
  9. theinvoicinghub.com, "E-Invoicing & E-Reporting in France: 2026-2027 Mandate."
  10. Peppol official documentation, "Peppol BIS Billing" specification: https://docs.peppol.eu/poacc/billing/3.0/
  11. Banqup, "Luxembourg introduces mandatory B2B e-invoicing," updated 23 Jul 2026.
  12. EDICOM Group, "Luxembourg Makes Progress With The Mandatory Electronic Invoice," updated 28 Jul 2026.
  13. VATupdate.com, "Luxembourg Expands Mandatory Domestic B2B E-Invoicing from 2028," 1 Sept 2026.
  14. European Commission, Digital Building Blocks, "eInvoicing in Luxembourg."
  15. Lasernet Group, "The Complete Guide to 2026 and 2027 E-Invoicing Mandates," 13 May 2026.
  16. SAP Community, "Document and Reporting Compliance" hub and related 2026 community threads (Aug 2026).
  17. Medius, "Compliance gets the invoice in. What happens next is up to you."
  18. European Commission, Taxation and Customs Union, VAT Gap report (2023 data).
  19. European Commission, "VAT in the Digital Age (ViDA)," official page: https://taxation-customs.ec.europa.eu/taxation/vat/vat-digital-age-vida_en
  20. vatcalc.com / EDICOM / Marosa VAT / TrueCommerce — cross-checked country timelines for Belgium, Germany, Spain, Poland (KSeF), and the Netherlands.

Frequently asked

Is Luxembourg's mandatory B2B e-invoicing law in force?

No. On 17 July 2026 the Government Council approved a draft bill extending mandatory e-invoicing to domestic B2B, which is a Council-approval stage and not an enactment by the Chamber of Deputies. The proposed dates are 1 January 2028 for receiving, 1 July 2028 for issuing by large and medium businesses, and 1 January 2029 for all remaining businesses. Poland's KSeF mandate was delayed twice, so these dates should be read as currently proposed rather than fixed.

What did France's e-invoicing go-live change for SAP AR/AP teams?

Beyond the format, it ended the habit of correcting a rejected invoice and resending it under the same number: once validation fails the invoice has to be cancelled and recreated with a new identifier. It also requires lifecycle status messages between supplier, buyer, and tax authority, and under Peppol BIS Billing a credit note is its own document type rather than a negative invoice. In SAP Document and Reporting Compliance, France needs the Approved Platform binding, not the legacy Peppol-only one.

Will Luxembourg's e-invoicing mandate work like France's?

Not necessarily. As currently drafted, Luxembourg's bill mandates e-invoicing without a domestic real-time e-reporting regime, and cross-border B2B is excluded for now. If it does not bundle a France-style lifecycle status exchange, the process-redesign effect may be weaker, so Luxembourg-based teams should confirm what the final law requires instead of importing France's requirements by default.

Need this in your organisation?

I work with a small number of clients each quarter on ERP strategy and IT-department automation. If the questions raised above are live in your team, get in touch.

Start a conversation →
Share