Electronic invoice in Liechtenstein

The Definitive Guide to E-Invoicing in Liechtenstein: Navigating the lack of strict mandates, public-sector EN 16931 acceptance, and seamless Peppol (9936 LI:VAT) onboarding without local accreditation.

Select a country

Overview

Liechtenstein has no general mandatory e-invoicing regime for domestic B2B or B2C, and no continuous transaction control, clearance or real-time invoice reporting. The electronic invoice regime that exists is confined to B2G, and even there it is a recipient-side acceptance duty: contracting authorities must be able to receive and process EN 16931 invoices for procurement above the applicable thresholds.

There is one detail that makes Liechtenstein genuinely unusual among European countries, and it is worth knowing before any project starts. The Liechtensteinische Landesverwaltung states that for qualifying contracts it accepts XML or PDF — with PDF given as the preferred option — sent by email. Peppol is not the official B2G route.

9936 LI:VAT

the active Peppol scheme for the Liechtenstein VAT number

PDF preferred

the state's own published preference for public-sector invoices, sent by email

10 years

the retention period for business books and supporting documents

Timeline

Short, because Liechtenstein implemented the EU procurement directive and has announced nothing since.

Already in force

27 November 2018

Art. 49b ÖAWG enters into force

The Öffentliches Auftragswesen Gesetz — the public procurement act — implements Directive 2014/55/EU. The duty applies to Land Liechtenstein from this date. See B2G.

27 November 2019

Extended to the remaining contracting authorities

The transitional provisions set this date for the other authorities covered by Art. 2 ÖAWG. Equivalent logic applies under the sector procurement legislation for utilities.

January 2025

eMWST becomes the compulsory VAT channel

All VAT administrative processes must run through the eMWST portal — registration and deregistration, returns and corrections, applications, account information and correspondence with the Steuerverwaltung. Paper filing of the relevant VAT forms ceased to be admissible after December 2024. This is not e-invoicing — see The model.

Nothing is scheduled ahead. No published draft, specification or date for a domestic B2B mandate was found in the material of the Regierung, the Steuerverwaltung or the Lilex legal database. And the EU's 1 July 2030 ViDA date should not be entered in a Liechtenstein roadmap — see Switzerland, the EU and ViDA.

B2G and Art. 49b ÖAWG

Art. 49b ÖAWG provides that, for procurement above the applicable thresholds, contracting authorities must accept and process electronic invoices conforming to the European e-invoicing standard and using a syntax published in the Official Journal of the EU.

Read the verb carefully. The obligation is framed as Entgegennahme und Verarbeitung — receipt and processing — and it falls on the buyer. It is not a supplier-side issuance mandate in the manner of Italy, Poland or Belgium: no general national rule requires a supplier to send the state only an e-invoice rather than any other admissible invoice.

How the state actually receives invoices

The Landesverwaltung's own practical page goes further than the law requires in the opposite direction: for public contracts above the thresholds it accepts XML or PDF, with PDF stated as the preferred option, and asks for such invoices to be sent by email. The operational route is therefore supplier → email → Landesverwaltung. Peppol is not a mandatory routing layer.

For the structured XML route the requirements are the European standard, the core elements under Art. 44a ÖAWV, and an EU-published syntax. But a supplier that sends a compliant PDF by email is doing exactly what the state has asked for.

B2B and B2C

No mandate in either, and none announced. The Mehrwertsteuergesetz (MWSTG), in its version applicable from 1 January 2026, requires a supplier to issue an invoice on the recipient's request carrying the necessary particulars: identification of supplier and recipient, the date or period of supply, the nature and extent of the supply, the consideration, and the VAT rate and amount.

The statutory definition is format-neutral

The law defines a Rechnung broadly as any document by which consideration for a supply is charged to a third party, regardless of what the document is called. Art. 26 governs the content of the invoice — it does not prescribe an electronic format. Nothing requires UBL, CII, Peppol BIS or any structured e-invoice.

For B2C there is likewise no structured e-invoicing obligation and no announced timeline. The MWSTG regulates invoice content and provides a specific simplification for receipts issued by automated cash registers below a defined value threshold — but it introduces no mandatory B2C XML, Peppol or e-invoice channel.

The model

Functionally, Liechtenstein is a non-CTC, ex-post VAT control model with a limited B2G e-invoice reception regime. The flow is supplier → buyer, followed by VAT accounting and reporting and possible audit. It is not supplier → tax authority clearance → buyer, and not supplier AP → buyer AP with a tax authority as fifth corner.

What does not exist

Any national system in which the invoice first clears the tax authority

A tax-issued invoice clearance ID, or validity conditional on prior approval

An Access Point forwarding invoice data to the tax authority as a fifth corner

Near-real-time transmission of each invoice transaction

eMWST is not a CTC platform

This distinction matters and is easy to get wrong. Since January 2025 all VAT administrative processes must go through the eMWST portal, and paper filing of the relevant forms is no longer admissible. That is a real digitalisation obligation — but the official description covers VAT returns and administrative communication, not the transmission of every outgoing or incoming invoice transaction.

No clearance, no mandatory Peppol five-corner, no invoice-level real-time reporting requirement.

Formats and PDF

For structured XML invoices falling under Art. 49b ÖAWG, Liechtenstein law requires conformity with the European standard for electronic invoicing. The XML must contain the core elements under Art. 44a ÖAWV and use a syntax published in the Official Journal.

UBLUBL 2.1 / ISO/IEC 19845

UN/CEFACT CIICross Industry Invoice D16B

National CIUSNone published — Liechtenstein adds no local extensions of its own

Where the PDF sits

In most countries this heading introduces a restriction. In Liechtenstein it introduces the opposite. For public contracts above the thresholds the Landesverwaltung accepts PDF and states a preference for it, with delivery by email. There is no supplier-side obligation to send structured XML instead.

In domestic B2B and B2C, PDF and paper remain entirely normal — the MWSTG's definition of an invoice is format-neutral, so a PDF is a perfectly valid invoice provided it carries the required particulars.

Identifiers

The country-specific Peppol participant addressing scheme is 9936 — LI:VAT, the Liechtenstein VAT number, and it is active in the official OpenPeppol participant identifier scheme list.

Format

9936:

No separate Liechtenstein-specific EAS for the commercial register number was found. General-purpose international schemes exist in the list, but they should not be presented as a mandatory national Liechtenstein company identifier.

One nuance for anyone mapping identifiers. The Liechtenstein authorities note that the Swiss UID is not a universal company identifier inside the Liechtenstein administration; interaction with the Landesverwaltung uses the PEID, and the five-digit Liechtenstein VAT number continues to exist separately. That is an administrative identification system — the PEID is not a Peppol EAS.

Peppol in Liechtenstein

Peppol is available as voluntary international infrastructure. It is not a national mandatory channel, and — unusually for Europe — it is not the official B2G route either, since the state's published process is email.

No Liechtenstein Peppol Authority appears in the OpenPeppol Authority list

No Liechtenstein-specific Peppol Authority Specific Requirements were found — the governance framework allows a Peppol Authority to set them, but there is no national authority here to do so

The practical consequence for a service provider is the simplest possible one: standard OpenPeppol certification and governance is what applies. See Requirements for providers.

Switzerland, the EU and ViDA

Liechtenstein and Switzerland

The two countries form a common VAT application area under a bilateral VAT agreement: territories treated as Inland under the Swiss VAT Act form a single VAT area for both states, and VAT for companies seated in Liechtenstein is administered by the Liechtenstein Steuerverwaltung. A Liechtenstein–Switzerland transaction therefore cannot be analysed as an ordinary export to a third country. It creates no Peppol or structured e-invoicing obligation either.

Liechtenstein and the EU

Liechtenstein is in the EEA, but the EEA is not the EU VAT area and the EEA Agreement does not include harmonised taxation. So a supply from Liechtenstein to Germany or France is not automatically an intra-Community supply between two member states, and the term intra-EU supply should not be used for it. What has to be analysed instead is the place of supply, whether goods or services, the supplier's VAT registration or establishment, the recipient's VAT status, reverse charge or import treatment, and the e-invoicing rules of whichever member state's VAT scope the transaction falls into.

Do not put "ViDA cross-border mandate 01.07.2030" in a Liechtenstein roadmap. ViDA amends the EU VAT Directive, and harmonised taxation falls outside the EEA Agreement, so it does not become Liechtenstein national VAT law. The accurate formulation is: no Liechtenstein mandate announced; EU ViDA obligations from 1 July 2030 may affect Liechtenstein businesses only where the transaction or business falls within the relevant EU VAT scope.

The practical test is EU VAT nexus. A Liechtenstein company VAT-registered and reporting relevant supplies in Germany may well have to meet the EU and German digital reporting requirements in that scope. A Liechtenstein company registered and taxable only in Liechtenstein does not automatically fall under anything on 1 July 2030.

Requirements for providers

No additional national accreditation regime for Peppol Access Points was found — nothing comparable to the Slovak digitálny poštár. The official Liechtenstein e-invoicing rules create no national Access Point licence, and with no Liechtenstein Peppol Authority in the OpenPeppol list there is no body to impose a national requirements layer.

National AP accreditationNot found

Foreign EU-certified AP may serve LI clientsYes, under the general OpenPeppol framework

Local establishmentNo Liechtenstein-specific requirement found

Official electronic mailboxNot required for Access Point onboarding

What onboarding a Liechtenstein client actually needs

01 Ordinary participant onboarding and KYC validation under OpenPeppol governance

02 Validation of the client's right to use the participant identifier

03 Correct registration of the participant and its capabilities through SMP and SML

04 Support for the relevant EAS — in particular 9936 LI:VAT where the LI VAT number is used

Two regimes not to conflate

Art. 54 MWSTG requires taxable persons without residence or a business seat in Liechtenstein to appoint a representative resident or seated there for their VAT procedural obligations. That is a VAT tax representation requirement on the taxpayer. It is not a requirement on a Peppol Access Point, and it does not mean a German Access Point needs a local representative to onboard Liechtenstein end users. Similarly, eMWST, eID.li and eVertretung are taxpayer-to-tax-authority infrastructure — not an e-invoice mailbox or an Access Point prerequisite.

Archiving

Business books, supporting documents and business correspondence must be kept for ten years. The Amt für Justiz publishes a dedicated information sheet on keeping, retaining and archiving business books, and it is the practical starting point for designing an archive — linked under Resources.

Because there is no clearance platform, nothing is stored on your behalf — the whole archive is the business's own responsibility

Art. 86 MWSTG makes improper keeping, preparation, retention or production of books, supporting documents and business papers a punishable procedural breach in its own right

Where an invoice was sent as structured XML, retaining the XML rather than only a rendered PDF is what preserves the evidential value of the format you chose

Confirm the exact period and any extension for the specific taxes and years with a Liechtenstein adviser — ten years is the general commercial rule, and the VAT limitation period drives the practical outer edge.

Penalties

There is no supplier-side fine for not issuing a Peppol or electronic invoice, for a structural reason: no general supplier-side issuance mandate exists in B2G, B2B or B2C. Art. 49b ÖAWG obliges the contracting authority to accept and process compliant e-invoices, so no administrative e-invoicing fine of the kind seen in mandatory-clearance countries can attach to a supplier.

In a procurement context, breaching the terms of a particular contract can have consequences — but no fixed supplier fine of the "CHF X per non-electronic invoice" kind was found. The ÖAWG's own sanctions operate in the procurement sphere: in certain subsidised procurement arrangements a serious breach of the law can lead the government to withdraw a subsidy entirely. That is not a penalty for sending a PDF instead of XML.

The general VAT penalties still apply

Art. 86 MWSTGUp to CHF 10,000 for defined procedural breaches, including improper keeping, preparation, retention or production of books, supporting documents, business papers and other records

Art. 87 MWSTGUp to CHF 400,000 for VAT evasion. In defined circumstances the ceiling rises to CHF 800,000, and where the tax advantage obtained exceeds the statutory penalty, an intentional infringement can be penalised up to twice the tax advantage

Art. 88 MWSTGTax fraud through intentional use of false, forged or substantively untrue accounting records or other documents — imprisonment up to one year or a monetary penalty of up to 360 daily rates

Art. 89 MWSTGQualified tax evasion — imprisonment up to two years or a monetary penalty of up to 360 daily rates

One invoice-specific consequence is worth knowing. Under Art. 27 MWSTG, a person who improperly shows VAT, or shows too high an amount of VAT, is in principle liable to pay the amount shown — unless the conditions for correction or the no-tax-loss exception are met. That is a real risk in template and mapping errors.

VAT deduction

An electronic invoice is not the sole legal basis for input VAT deduction. Art. 28 MWSTG allows a taxable person, within its business activity, to deduct among other things domestic VAT invoiced to it, declared acquisition or reverse-charge VAT, and import VAT paid or payable in the cases the law provides for. Paragraph 3 ties the deduction to proof that the input VAT was paid.

Nowhere does the statute say the invoice must be a structured electronic invoice, EN 16931 XML or a Peppol document — and the definition of Rechnung is format-neutral in any case.

A plain paper or PDF invoice does not become invalid for VAT deduction merely because it is not a UBL or CII e-invoice. What matters is that the document and the underlying transaction allow the right to deduct to be proved, and that the substantive VAT requirements are met.

How we help

Liechtenstein asks almost nothing of a provider — which changes the question from compliance to whether structured invoicing is worth doing at all. Where it is, this is the work:

EN 16931 in both syntaxes — UBL 2.1 and UN/CEFACT CII D16B — for the structured B2G route

Onboarding Liechtenstein participants on 9936 LI:VAT, without a local entity, licence or representative

PDF generation and email delivery where that is what the public buyer actually prefers

Correct VAT presentation, so Art. 27 MWSTG liability for an overstated amount never arises from a template

Ten-year archiving of the invoice and its supporting documents

The national CIUS an EU counterparty needs, for Liechtenstein companies with EU VAT nexus

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in Liechtenstein?

No, for any segment. Domestic B2B and B2C have no mandate, no CTC and no announced date. In B2G, Art. 49b ÖAWG obliges contracting authorities to accept and process EN 16931 invoices for procurement above the applicable thresholds — a recipient-side duty from 27 November 2018 for Land Liechtenstein and 27 November 2019 for the remaining authorities. No general rule requires a supplier to issue only an e-invoice.

Is it true the government prefers PDF?

Yes — and it is the single most surprising fact about Liechtenstein. The Landesverwaltung's published process for public contracts above the thresholds states that it accepts XML or PDF, with PDF as the preferred option, sent by email. Peppol is not a mandatory routing layer and is not the official B2G channel. Where the structured XML route is used, it must meet the European standard, the Art. 44a ÖAWV core elements and an EU-published syntax.

Can I serve Liechtenstein clients from my existing Peppol Access Point?

Yes. No national accreditation regime, Access Point licence, local establishment requirement or official mailbox was found, and there is no Liechtenstein Peppol Authority to impose national requirements. A German or other EU certified Access Point can onboard a Liechtenstein company directly — what is needed is ordinary OpenPeppol onboarding and KYC, validation of the client's right to the participant identifier, correct SMP/SML registration, and support for EAS 9936 LI:VAT.

Does the VAT representative requirement apply to my Access Point?

No, and these two regimes should never be merged. Art. 54 MWSTG requires taxable persons without residence or a business seat in Liechtenstein to appoint a local representative for their VAT procedural obligations. That binds the taxpayer, not the service provider. A foreign Access Point does not need a Liechtenstein representative to onboard end users. The same applies to eMWST, eID.li and eVertretung — taxpayer-to-tax-authority infrastructure, not an Access Point prerequisite.

Is eMWST a clearance or reporting system?

No. Since January 2025 all VAT administrative processes must run through the eMWST portal — registration, returns and corrections, applications, account information and correspondence — and paper filing of the relevant forms is no longer admissible. But the official description covers VAT returns and administrative communication, not the transmission of individual invoice transactions. There is no invoice-level clearance or reporting leg anywhere in the Liechtenstein system.

Does ViDA apply to Liechtenstein from 2030?

Not as a national mandate. Liechtenstein is in the EEA, but the EEA Agreement does not include harmonised taxation, so amendments to the EU VAT Directive under ViDA do not become Liechtenstein VAT law. Writing "ViDA mandate = 1 July 2030" into a Liechtenstein roadmap would be legally wrong. A Liechtenstein business can be caught indirectly where its transaction or VAT registration falls within an EU member state's VAT framework — but the source of the obligation is EU and member state law, not a Liechtenstein mandate.

Is a Liechtenstein–Germany sale an intra-EU supply?

No, not automatically — the EEA is not the EU VAT area. What has to be analysed is the place of supply, whether goods or services, the supplier's VAT registration or establishment, the recipient's VAT status, reverse charge or import treatment, and the e-invoicing rules of the member state in whose VAT scope the transaction falls. Note also that Liechtenstein and Switzerland form a common VAT application area under a bilateral agreement, so LI–CH transactions are not ordinary third-country exports either.

Do I need a structured e-invoice to deduct VAT?

No. Art. 28 MWSTG allows deduction of domestic VAT invoiced to you, declared acquisition or reverse-charge VAT, and import VAT in the cases provided for, with the deduction tied to proof that the input VAT was paid. The statute does not require the invoice to be structured, EN 16931 XML or a Peppol document, and the definition of an invoice is format-neutral. A paper or PDF invoice remains valid provided the document and the underlying transaction prove the right to deduct.

Summary

Liechtenstein did the minimum the procurement directive required and stopped. Contracting authorities have had to accept EN 16931 invoices since 2018 and 2019; suppliers have never been required to send them; and domestic B2B and B2C have no mandate, no clearance, no reporting and no announced date. eMWST digitalised VAT administration in 2025, but it handles returns and correspondence — not invoices.

The detail to carry into any planning is that the state itself asks for PDF by email. Adopting structured invoicing in Liechtenstein is a business decision about automation, not a compliance obligation.

For a certified European Access Point, Liechtenstein is open: no national accreditation, no local licence, no office, no official mailbox. Support 9936 LI:VAT and standard OpenPeppol governance and you can onboard directly. Two things to keep straight in any document you publish about it — the VAT representative requirement binds the taxpayer, not you; and 1 July 2030 is not a Liechtenstein date.

Resources

Mehrwertsteuergesetz (MWSTG) — Lilex The consolidated VAT act: Art. 26 on invoice content, Art. 27 on overstated VAT, Art. 28 on deduction and Art. 86–89 on penalties Lilex — the Liechtenstein legal database Where the ÖAWG and ÖAWV texts live, including Art. 49b and the Art. 44a core elements Merkblatt on keeping, retaining and archiving business books The Amt für Justiz information sheet — the practical basis for designing a compliant ten-year archive Liechtensteinische Landesverwaltung The state administration, including the eRechnung page setting out how public-sector invoices are actually to be sent Peppol Electronic Address Scheme code list Where 9936 LI:VAT sits, and confirmation of its active status Peppol BIS Billing 3.0 The profile to use where structured exchange is chosen — Liechtenstein publishes no CIUS of its own Peppol Directory Check whether a Liechtenstein counterparty is registered before assuming the Peppol route is open

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial