Luxembourg VAT Invoice Requirements: 2026 Checklist

Luxembourg VAT invoice requirements start with one practical split: invoices over EUR 100 usually need the full VAT invoice details, while invoices at or below EUR 100 can use a simplified format only if the transaction does not concern another EU Member State. That threshold is the fastest way to review the rule set because it tells you, at the outset, whether you should expect a full compliance checklist or a shorter document.

For most day-to-day reviews, a full invoice should let you identify the parties, the issue date, the sequential invoice number, the VAT number, the taxable amount, the VAT due, and any special wording required by the transaction. In Luxembourg, that baseline often sits alongside local company details that foreign teams miss, including the wording R.C.S. Luxembourg with the registration number and, where relevant, the business permit number. If the transaction is exempt within the EU, the review does not stop with the visible invoice fields. You also need to confirm the customer's VAT number in VIES and keep proof of the check.

That is why Luxembourg invoice requirements are best handled as an operational checklist rather than a generic tax summary. You are not just asking whether the document looks plausible. You are checking whether it supports VAT treatment, deductibility, and downstream AP validation. According to Luxembourg's official VAT invoice content rules, a VAT invoice must contain nine core items, and a five-item simplified invoice is allowed only when the invoice does not concern another EU Member State and the total does not exceed EUR 100 including VAT.

The rest of this checklist follows that structure. First, confirm whether you are dealing with a full invoice or a simplified invoice. Then check the Luxembourg-specific identifiers and any scenario-based wording. Finally, confirm whether cross-border evidence or public-sector context adds another control step.

---

Full invoice checklist for amounts over EUR 100

When the total is over EUR 100, the safest approach is to review the invoice as a full Luxembourg VAT invoice and verify that the document can stand on its own for tax and AP purposes. A good working checklist is:

• Supplier identification: the seller's name and enough business detail to identify the legal entity issuing the invoice.
• Customer identification: the buyer's identity where the transaction requires it.
• Issue date: the date the invoice was issued.
• Sequential invoice number: a unique numbering reference that fits the supplier's invoicing sequence.
• Description of the supply: what was sold or provided, including the nature and extent of the supply, in a way that lets you understand the taxable transaction.
• Taxable amount: the amount before VAT.
• VAT rate and VAT amount due: the rate applied and the tax charged.
• Supporting details for the VAT treatment: any wording or references needed to explain why VAT was charged, not charged, or treated in a special way.

In practice, the VAT identification number is one of the most important control points in this full-invoice review. If the supplier VAT number is missing, incorrect, or inconsistent with the transaction, the invoice becomes harder to validate and can create questions around VAT deduction. Finance teams should also check whether the commercial description, tax base, and VAT amount align with what was actually purchased. A document can contain the right boxes and still fail the real control if those boxes do not support the tax treatment.

This is where Luxembourg invoice mandatory fields become more than a drafting exercise. For AP teams, the invoice has to be reviewable without guessing. For issuers, the invoice has to explain the transaction well enough that the customer does not come back for a corrected version. If you compare regional approaches, how Germany handles mandatory VAT invoice fields and small invoices shows the same compliance problem framed differently, which helps highlight why Luxembourg's own threshold and local identifiers deserve separate attention.

When the EUR 100 simplified invoice rule applies

Luxembourg simplified invoice rules are useful, but only if you apply the threshold correctly. The key point is that the EUR 100 limit is measured including VAT, and the simplified format is not available where the invoice concerns another EU Member State. If either condition fails, you should move back to the full-invoice checklist instead of accepting a shorter document.

For a qualifying simplified invoice, the document can be lighter than a full invoice, but it still needs enough information to identify the supplier, date the document, describe the goods or services, and show the VAT-inclusive amount with the information needed to determine the tax due. In other words, a lower-value invoice is not a free-form receipt. The simplified format reduces the field set, but it still has to support a review of what happened and how VAT was handled.

The operational test is straightforward. Check the total first. If the document is for EUR 96 including VAT and the supply is domestic, a simplified invoice may be acceptable. If the same document relates to another EU Member State, or if the total comes to EUR 112 including VAT, the simplified route falls away and the supplier should issue a full invoice. That is why Luxembourg invoice under 100 searches often reflect a live AP question rather than academic interest.

This threshold also helps you avoid a common process mistake: reviewing all low-value invoices with the same relaxed standard. Luxembourg does not give that flexibility for every small document. If you want a useful regional comparison, how Andorra splits full and simplified invoices under IGI shows a similar control question outside the EU VAT framework, while another EU example of full and simplified VAT invoice rules shows how another Member State handles the same distinction. Latvia's VAT invoice requirements are another useful benchmark because they combine a different simplified-invoice threshold with specific rules on foreign-currency VAT disclosure and wording for special cases. Even so, the Luxembourg threshold still needs to be applied on its own terms.

---

Luxembourg-only identifiers and wording that teams often miss

Many invoice errors in Luxembourg do not come from missing totals or dates. They come from using a generic template that ignores local identifiers and transaction-specific wording. If you issue or review Luxembourg invoices regularly, you should check not only the VAT fields but also the company details that make the document locally complete.

Start with the issuer's identity. Depending on the entity, the invoice may need to reflect the legal form, the registered office, the wording R.C.S. Luxembourg together with the registration number, and the business permit number where that number is applicable. These details matter because they help tie the invoice back to the real Luxembourg business issuing it. They also matter operationally because foreign finance teams often inherit invoice layouts built for another jurisdiction and assume the local company details are interchangeable.

The next review layer is wording. Certain VAT situations call for a specific expression on the invoice, and leaving that wording out can make the document harder to defend or process correctly:

• Reverse charge: where the customer accounts for the VAT, the invoice should carry the reverse charge wording that signals auto-liquidation.
• Cash accounting: where the transaction falls under cash-accounting treatment, the invoice should show comptabilite de caisse.
• Self-billing: where the customer issues the invoice on behalf of the supplier, the document should reflect that this is self-billing and use the corresponding auto-facturation wording.

Treat these labels as compliance content, not decoration. They explain why the tax treatment or invoicing process differs from a standard domestic VAT charge. In a live workflow, that means your control should ask two questions together: "Is this the right wording for the scenario?" and "Does the rest of the invoice support the same treatment?" That approach catches more real errors than checking wording in isolation.

Intra-EU evidence, VIES checks, and the limited B2G context

Cross-border invoicing adds a second layer of control to Luxembourg VAT invoice requirements. If the supplier is treating the sale as an exempt intra-Community supply, the invoice is only part of the file. The seller should validate the customer's VAT number in VIES, keep proof of that validation, and retain the supporting evidence that matches the cross-border treatment. Without that record, the invoice may say the right thing while the underlying VAT position remains hard to defend.

For finance teams, the practical lesson is that invoice review and evidence review should happen together. Check that the customer's VAT number appears where it should, confirm that the cross-border treatment is reflected consistently, and make sure someone has retained proof of the VIES check. If the business is relying on an intra-EU exemption, the control should not end with "the invoice looks fine." It should end with "the file supports the treatment."

This is also the right place to keep Luxembourg's e-invoicing context in proportion. B2G e-invoicing is relevant if you invoice Luxembourg public bodies because public-procurement rules have required electronic invoicing in that setting since March 18, 2023. If you need the route-level details, Luxembourg's public-sector Peppol and MyGuichet workflow explains when suppliers use each channel and what foreign or occasional suppliers need to submit compliantly. That does not mean Luxembourg has a broad domestic B2B or B2C e-invoicing mandate that replaces the invoice-content rules covered here. For most readers, the main issue remains invoice content, VAT evidence, and document controls, with the public-sector rule sitting beside that as a narrower operational requirement.

---

AP review priorities and common Luxembourg invoice mistakes

Before you approve or issue a Luxembourg invoice, run through a short control list:

• Confirm the format: is this a full invoice or a simplified invoice, and does the EUR 100 threshold actually allow the shorter format?
• Check the local identifiers: if the issuer is a Luxembourg entity, are the R.C.S. Luxembourg details and any required business permit information present?
• Review scenario wording: does the document need reverse-charge, cash-accounting, or self-billing wording?
• Check the VAT support: do the taxable amount, VAT treatment, and VAT evidence line up with the transaction?
• Escalate cross-border files: if the invoice relies on an intra-EU treatment, has the VAT-number check and supporting evidence been retained?

The most common Luxembourg invoice mistakes are predictable. Teams use a generic EU template and miss the local identifiers. They treat every low-value invoice as if simplified invoicing automatically applies. They omit wording such as auto-liquidation or auto-facturation because the commercial system was not configured for special cases. Or they focus on the visible invoice and forget the VIES evidence needed to support the VAT treatment. Each of those mistakes can slow payment, trigger supplier rework, or weaken the file behind VAT recovery.

It also helps to keep this article's scope clear. Luxembourg VAT invoice-content rules tell you what the document should contain and what supporting checks belong beside it. They are not the same as the doctrine about whether an invoice can be treated as accepted in a dispute. If you need that separate legal context, see how the accepted invoice principle affects disputed Luxembourg invoices. If your work is more comparative, the Ireland and Germany references above are better follow-up reads. For day-to-day AP control, though, the highest-value step is still the same: check the threshold first, then the local identifiers, then the wording and evidence.