Liechtenstein e-invoicing
No Liechtenstein data file exists anywhere in this repository — no country policy, no identifiers, no tax system, no transmission channel. Nothing on this page is implemented. It is here so that someone who wants Liechtenstein support knows what adding it would involve. The countries Invoicerr does cover are listed in the country directory.
Liechtenstein's e-invoicing follows the Swiss framework, a consequence of the customs and monetary union between the two countries. The Tax Administration (Steuerverwaltung) runs an eVAT portal for VAT transactions, alongside the Swiss QR-bill format used for payments.
What supporting Liechtenstein would involve
| System | eVAT Portal, built on the Swiss e-invoicing framework |
| Authority | Steuerverwaltung — Tax Administration |
| Format | A national XML schema (Swiss QR-bill / Swiss XML standard). No provider in backend/src/modules/documents/formats/ builds it today. |
| Transmission | Submission to the eVAT Portal. No transport in backend/src/modules/documents/transports/ talks to it today. |
Carried over from an earlier research pass in this repository's own history, and never checked against a primary source. Leads, not facts — confirm every line before writing it into a data file.
- eVAT portal became mandatory for VAT transactions from January 2025.
- Model described as post-audit, aligned with the Swiss tax system.
Which catalogues a contributor would add
Adding a country is data, not code. Adding a country is the procedure and the contract each file has to satisfy; this is only the shopping list for Liechtenstein.
country-policy/data/li.json— which document actions Liechtenstein allows. Start here: without this file every action is refused with a 403, naming the country.country-identifiers/data/li.json— which national identifier a party must carry.tax/tax-systems/data/li.jsonandvat-rates/data/li.json— the tax kind, and the rate ladder offered on an invoice line.correction-routes/data/li.json— all eleven canonical correction routes,unverifiedwhere unresearched, never omitted.b2g-routing/data/li.json— the channel and format a public buyer in Liechtenstein requires.transports/channel-policy/data/li.json— whether a channel is legally required of a seller established in Liechtenstein, and from what date.archive/retention/data/li.json— how long an archived document is kept, and what the duration is counted from.
Add mentions/, content-requirements/, country-fields/, reporting/ and
domestic-reverse-charge/ only where the law actually gives them content.
Data alone will not finish the job here: the eVAT Portal is a transmission channel this repository does not implement, and its own QR-bill format has no format provider. Both are code, not a JSON file — see When a country needs more than a file.
Want Liechtenstein supported?
Check the open compliance issues first. If there is no issue for Liechtenstein, open one and name which of the files above you need — a request that names one mechanism is far more actionable than "please add Liechtenstein".