E-invoicing by country

E-invoicing in Luxembourg: mandates, formats, sending and receiving

Dynafis combines invoice validation, recipient capability, country profiles and evidence for Luxembourg. The permitted route is determined per legal entity, transaction and environment; Peppol is only one part of the overall process.

What applies in this country?

B2G e-invoices in Luxembourg must use structured, Peppol-enabled processes. B2B remains voluntary but can use the same interoperable rail. Luxembourg uses Peppol as the common B2G delivery rail. Scheme 9938 is a routing identity and must not be treated as a VAT number; Dynafis validates the identifier type separately.

Who is affected?

The profile distinguishes B2B, B2G and cross-border. Scope also depends on establishment, tax registration, recipient type, public procurement and cross-border context.

Networks and portals

Relevant networks and portals include Peppol and CTIE. Dynafis validates Peppol BIS Billing 3.0, UBL and EN 16931 and the addressing schemes 9938 as separate concerns.

Networks and portals
  • Peppol
  • CTIE
Formats and profiles
  • Peppol BIS Billing 3.0
  • UBL
  • EN 16931
Identifiers
  • 9938
What Dynafis supports today

Dynafis can use the direct country rail in production after legal-entity configuration, recipient discovery and technical evidence have passed.

Coverage boundaries

The support status describes Dynafis technical coverage, not a blanket legal or tax approval. National reporting, fiscalization, archive or signature duties may apply in addition to invoice exchange.

Sending process
  1. 01

    Determine legal entity, transaction type and recipient country

  2. 02

    Validate recipient ID, scheme and document profile

  3. 03

    Freeze the canonical invoice and run the country preflight

  4. 04

    Execute the permitted exchange, clearance and reporting rails

  5. 05

    Reconcile provider statuses, receipts and evidence

Receiving process
  1. 01

    Retrieve from Peppol, the national platform or a partner connector

  2. 02

    Store the legal original separately from the transport artifact

  3. 03

    Validate profile, sender, totals and correction references

  4. 04

    Assign the document to the correct legal entity in the shared inbox

Corrections and status
  1. 01

    Reference the original and profile version unambiguously

  2. 02

    Choose credit note, correction, replacement or cancellation only when supported

  3. 03

    Reconcile status history, reporting and evidence together

For accountants and multi-client work

For accountants and multi-client work

Accounting firms configure Luxembourg per client and legal entity. Credentials, provider accounts, documents and production approvals never inherit between clients; month-end checks remain traceable per legal entity.

For accountants and multi-client work
FAQ
Is e-invoicing mandatory in Luxembourg?

B2G e-invoices in Luxembourg must use structured, Peppol-enabled processes. B2B remains voluntary but can use the same interoperable rail. The exact scope must be assessed for the legal entity and transaction.

Is Peppol sufficient for Luxembourg?

Not automatically. Peppol may be an exchange rail, but it replaces national clearance, reporting or fiscalization such as Peppol and CTIE only when the active country profile explicitly permits it.

What does Dynafis support for Luxembourg today?

Dynafis can use the direct country rail in production after legal-entity configuration, recipient discovery and technical evidence have passed.

Sources and review status

Reviewed: · lu-regulatory-2026.07.29