CARF Compliance Liechtenstein: Practical Checklist for Casps (2026)

Liechtenstein’s implementation of the OECD Crypto-Asset Reporting Framework (CARF) and the revised Common Reporting Standard (CRS) entered into force on 1 January 2026, creating binding data-collection and reporting obligations for every crypto-asset service provider operating in or passporting through the principality. CARF compliance in Liechtenstein is no longer a future planning exercise, it is a live operational requirement, with the first electronic submissions due to the Liechtenstein Fiscal Authority (Liechtensteinische Steuerverwaltung, LLV) by 30 June 2027 for the 2026 reporting period. This guide delivers a step-by-step compliance checklist, maps out the required data fields, and walks CASP compliance officers, general counsel and CFOs through the LIDES-portal submission process so that no deadline is missed and no penalty is triggered.

Executive Summary & TL;DR

The crypto-asset reporting framework is Liechtenstein’s most significant expansion of automatic exchange of information (AEOI) since the original CRS rollout. It captures exchanges, custodial wallet providers, brokers and certain decentralised-finance intermediaries that meet the statutory definition of a Reporting Crypto-Asset Service Provider. Here is the minimum action list every in-scope entity should complete:

• Determine reporting status. Perform a legal classification of your services against the CARF Act definition of a Reporting CASP. If you hold, transfer or exchange crypto assets on behalf of clients, the presumption is that you report.
• Register with LLV via the LIDES portal. The Liechtenstein Fiscal Authority requires all Reporting CASPs to register electronically before their first submission window.
• Map data fields now. CARF requires granular transactor identification, transaction-type categorisation, gross proceeds/fair-market-value calculations and counterparty jurisdiction data. Start the technical build immediately.
• Implement enhanced due diligence. CARF due-diligence procedures sit alongside, but are not identical to, existing KYC/AML requirements under the Token and Trustworthy Technology Services Act (TVTG).
• Submit by 30 June. Reports for each calendar-year reporting period must be filed electronically with LLV by 30 June of the following year. The first live submission window therefore closes 30 June 2027.
• Retain records for a minimum of ten years. Expect LLV to request supporting documentation during spot audits; archival policies must be in place from day one.

Industry observers expect that the LLV will treat the first reporting cycle as a supervised learning phase, but that administrative penalties will be applied from the second cycle onward where non-compliance is evident.

What Is CARF and Why Liechtenstein Implemented It

The Crypto-Asset Reporting Framework is an international tax-transparency standard developed by the OECD and endorsed by the G20. It extends the logic of the CRS, automatic, multilateral exchange of financial-account information between tax authorities, to crypto assets that were previously outside the CRS perimeter. Under CARF, a Reporting CASP must collect identifying information on each user, record specified transaction details and report them annually to its home jurisdiction’s competent authority, which then exchanges that data with partner jurisdictions under a dedicated multilateral competent-authority agreement (the CARF MCAA).

Liechtenstein committed to CARF implementation as part of the OECD Global Forum on Transparency and Exchange of Information for Tax Purposes. As a jurisdiction with a mature blockchain-services ecosystem, anchored by the TVTG, the principality had a strategic incentive to adopt early: demonstrating crypto tax transparency protects Liechtenstein’s reputation, sustains its financial-centre model and prevents unilateral action by trading partners.

CARF vs CRS: A Quick Comparison

CRS targets traditional financial accounts, bank deposits, custodial securities, insurance contracts and fund interests. It was never designed to capture decentralised digital assets held outside conventional custodial structures. CARF fills that gap by defining a new category of reportable persons (crypto-asset users) and a new category of reporting entities (CASPs).

The two frameworks share the same exchange infrastructure (the MCAA model) and similar due-diligence logic, but CARF introduces its own data fields, notably transaction-type categorisation and gross-proceeds calculations denominated in the operating currency of the CASP. Where an entity is both a CRS-reporting financial institution and a CARF-reporting CASP, both sets of obligations apply concurrently.

Legal Framework in Liechtenstein: TVTG, CARF Act and CRS Revision 2026

Liechtenstein’s crypto-asset regulatory stack rests on three pillars. The first is the Token and Trustworthy Technology Services Act (TVTG), enacted in 2020, which established a comprehensive licensing regime for blockchain-based service providers and created the legal concept of tokenised rights. The second is the CARF Act, transposed into domestic law by the government and published via the Liechtenstein Law Gazette. The third is the CRS revision 2026, which amends the existing CRS legislation to align with OECD amendments covering indirect crypto-asset holdings, electronic money and central-bank digital currencies.

Together, these instruments mean that crypto is unambiguously legal in Liechtenstein, but that operating a crypto-asset business now carries layered compliance obligations spanning licensing (TVTG / MiCAR), anti-money-laundering (Due Diligence Act), and tax reporting (CARF / CRS).

Key Statutes and Administrative Guidance

The consolidated text of the CARF MCAA implementation can be found in the Liechtenstein legal database. The Regierung (government) published the domestic transposition and explanatory notes as a formal attachment. CASPs should monitor LLV’s dedicated CARF information page for technical circulars, XML schema updates and portal registration instructions. For TVTG licensing questions, the Financial Market Authority (FMA) remains the primary supervisory body.

Key Dates and CARF Compliance Liechtenstein Timeline

Timing is the single most common source of confusion. The table below consolidates every critical date from the legislative process through to the first live filing deadline.

The critical operational window is the twelve months between 1 January 2026 and the 30 June 2027 submission deadline. Any CASP that has not yet begun its implementation programme is already behind schedule.

Who Must Report? Reporting Scope and Entity Mapping

The CARF Act defines a Reporting Crypto-Asset Service Provider as any entity or individual that, as a business, effectuates exchange transactions in crypto assets for or on behalf of customers. This captures three core business models: custodial exchanges, crypto-asset brokers and custodial-wallet providers. It also extends to entities that facilitate peer-to-peer trades where the platform retains a degree of control over the transaction.

Entities that only provide non-custodial software, for example, open-source wallet interfaces where the user alone holds private keys, are generally outside scope. However, this determination is fact-sensitive: if the provider retains any backup-key access, or if the architecture permits the provider to block or redirect transactions, the legal test may tip toward reporting status. CASPs operating under MiCAR passporting arrangements must determine whether Liechtenstein or the home-member-state competent authority is the primary reporting jurisdiction, depending on where the CASP is resident for CARF purposes.

Where doubt exists, the recommended approach is to seek a formal ruling or, at minimum, to document the legal analysis supporting a non-reporting classification. LLV has the authority to challenge classifications during audit.

Data Fields, Data Mapping and Recordkeeping for CARF Compliance in Liechtenstein

One of the most operationally demanding aspects of Liechtenstein crypto compliance is the data-mapping exercise. CARF requires CASPs to collect, validate and report a defined set of data elements for each reportable user and each reportable transaction. The OECD’s technical guidance specifies the schema; LLV adopts it with minor local formatting requirements for the LIDES submission.

Recordkeeping. LLV expects Reporting CASPs to retain all underlying data, source documents, self-certifications, exchange-rate calculations and submission confirmations, for a minimum of ten years from the end of the reporting period to which they relate. Records must be accessible in a format that LLV can audit, which in practice means structured digital archives with search and retrieval capability.

The data-mapping project is the longest lead-time item in most CASP implementation programmes. Industry observers expect mid-size CASPs to require three to six months of development time to retrofit existing ledger systems and build the extraction pipeline needed to produce CARF-compliant XML files.

Practical 12-Step Compliance Checklist for CASPs

This is the core operational section. Each step includes a deliverable, a recommended owner, and sample evidence that an audit-ready CASP should maintain. The checklist assumes a mid-size CASP with a three-to-six-month implementation timeline.

1. Legal classification of services. Engage legal counsel to map every product and service line against the CARF definition of a Reporting CASP. Deliverable: signed legal opinion or internal memorandum. Owner: General Counsel. Evidence: classification matrix with statutory references.
2. Assign a CARF compliance owner and governance structure. Designate a named individual responsible for CARF programme delivery. Establish a cross-functional working group (legal, operations, technology, finance). Deliverable: board-approved compliance charter. Owner: Chief Compliance Officer.
3. Register on the LIDES portal with LLV. Access the Liechtenstein Fiscal Authority’s dedicated CARF registration page, complete entity identification, and obtain portal credentials. Deliverable: LIDES account confirmation. Owner: Compliance / Operations. Evidence: registration receipt.
4. Implement enhanced due diligence and KYC procedures. Update onboarding workflows to capture CARF-specific data (TIN, jurisdiction of tax residence, self-certification). Deliverable: revised KYC policy and updated onboarding forms. Owner: Compliance. Evidence: policy version log and sample self-certification template.
5. Map transaction types and product catalogue to CARF categories. Each internal transaction code must map to one of the CARF-defined categories (exchange, transfer, retail payment, other). Deliverable: transaction-mapping matrix. Owner: Product / Operations. Evidence: signed-off mapping document.
6. Build the technical data pipeline and PII mapping. Construct the extraction, transformation and loading (ETL) process that pulls reportable data from core systems and formats it into the CARF XML schema. Deliverable: operational data pipeline with automated scheduling. Owner: CTO / Engineering. Evidence: pipeline architecture diagram and test-run logs.
7. Establish wallet-to-identity correlation methods. Document the policy and technical method used to link blockchain addresses to verified account holders. This is essential for transfer-type transactions. Deliverable: wallet-correlation policy. Owner: Compliance / Engineering. Evidence: policy document and sample correlation report.
8. Automate reporting and validation routines. Implement schema-validation checks that run before every submission. The XML file must conform to the OECD CARF schema as adopted by LLV. Deliverable: automated validation script. Owner: Engineering. Evidence: validation test results and error logs.
9. Establish internal controls and reconciliation procedures. Run quarterly reconciliations between the CARF data extract and the core ledger to catch discrepancies before the annual filing. Deliverable: reconciliation procedure and exception-handling protocol. Owner: Finance / Compliance. Evidence: quarterly reconciliation reports.
10. Define data-retention and archival policies. Implement a ten-year retention schedule for all CARF-related records, including self-certifications, exchange-rate sources, submission files and LLV correspondence. Deliverable: data-retention policy. Owner: Legal / IT. Evidence: archival system configuration and retention-schedule document.
11. Conduct test submissions and dry runs. Before the live 30 June deadline, submit sample files through the LIDES portal to identify formatting errors and validation failures. Deliverable: successful test-submission confirmation. Owner: Compliance / Engineering. Evidence: test-submission receipt and error-resolution log.
12. Review client-facing contract clauses and notices. Update terms of service, privacy notices and client agreements to reflect the new data-collection and reporting obligations. Inform existing clients of the change. Deliverable: updated agreements and client notification. Owner: Legal. Evidence: revised contract templates and distribution log.

The likely practical effect for most mid-size CASPs will be an implementation cost equivalent to 1.5 – 3 full-time-equivalent staff over a six-month build period. Early-stage CASPs with modern tech stacks may complete the programme faster; legacy platforms with fragmented databases should budget additional time.

Reporting Mechanics: LIDES Portal and Submission Process

The LIDES portal is the LLV’s secure electronic channel for all AEOI submissions, including CARF. To use it, a Reporting CASP must first register on the LLV’s CARF-specific information page, providing entity-identification details and appointing an authorised representative. Once credentialed, the submission process follows these steps:

• Prepare the XML file. Generate the report in the OECD CARF XML schema. Validate locally using the LLV-published schema definition before upload.
• Upload via LIDES. Log in to the portal, select the CARF submission module, and upload the validated XML file. The portal runs server-side validation and returns a status notification.
• Resolve validation errors. Common errors include mismatched TIN formats, missing jurisdiction codes and schema-version conflicts. Correct and resubmit within the filing window.
• Retain the submission receipt. Download and archive the portal’s confirmation receipt. This is your primary evidence of timely filing.

The annual submission deadline is 30 June for the preceding calendar-year reporting period. Late filings and nil returns (where applicable) must still be submitted through LIDES. The portal generally opens for submissions in early Q1 each year.

Penalties, Enforcement and Risk Allocation

Liechtenstein’s administrative-penalty framework for AEOI non-compliance operates on a proportionality principle. Penalties may be imposed for failure to register, failure to file, late filing, incomplete or inaccurate reports, and failure to maintain adequate records. The LLV is the competent authority for CARF enforcement, while the FMA retains supervisory jurisdiction over TVTG-licensed entities for licensing and AML matters.

Beyond direct financial penalties, the reputational risk of non-compliance should not be underestimated. Liechtenstein’s position as a reputable crypto-friendly jurisdiction depends on demonstrable adherence to international standards. A CASP that is publicly cited for CARF non-compliance faces downstream consequences including enhanced scrutiny from correspondent banks, loss of MiCAR passporting credibility, and potential difficulties renewing TVTG registrations. Industry observers expect the LLV to publish aggregated compliance statistics after the first reporting cycle, which will increase transparency around enforcement intensity.

Cross-Border Issues and the CRS Revision 2026

The CRS revision 2026 is not merely a cosmetic update. It expands the scope of reportable financial assets to include specified electronic money products, central-bank digital currencies and indirect holdings of crypto assets through investment vehicles. For CASPs, this means that a single client relationship may generate both a CARF report (for direct crypto-asset transactions) and a CRS report (for fiat balances, e-money products or fund interests held on the same platform).

Where a CASP operates cross-border, whether through MiCAR passporting, branch structures or reverse-solicitation arrangements, the question of where to report becomes critical. The general CARF principle is that the CASP reports to the jurisdiction in which it is tax-resident. For Liechtenstein-resident CASPs serving EU clients, the report flows from LLV to the partner jurisdiction under the CARF MCAA. For EU-authorised CASPs passporting into Liechtenstein, the reporting obligation generally remains with the home-member-state competent authority, but the CRS addendum may create overlapping duties that require careful mapping.

MiCAR Passporting and the Reporting Nexus

CASPs holding a MiCAR authorisation in an EU member state and providing services into Liechtenstein under the EEA passporting framework must determine whether Liechtenstein or the home member state is the “jurisdiction of tax residence” for CARF purposes. The distinction turns on the entity’s place of incorporation and effective management, not the location of its customers. Where Liechtenstein is the jurisdiction of residence, the CASP reports through LLV. Where it is not, the CASP must ensure compliance with the equivalent CARF transposition in the home state, and should verify that the CARF MCAA covers the relevant exchange relationships.

DAC8, the EU directive on administrative cooperation covering crypto-asset reporting, runs in parallel with CARF for EU/EEA member states. Liechtenstein, as an EEA member, is expected to align its domestic framework with DAC8 requirements over time. Early indications suggest that the domestic CARF Act already meets or exceeds most DAC8 obligations, but compliance teams should track any supplementary transposition measures.

Conclusion: 90-Day Action Plan for CARF Compliance in Liechtenstein

For compliance officers starting or accelerating their CARF programmes today, the following six priorities should be completed within 90 days:

1. Finalise the legal classification of your entity’s reporting status and obtain a signed legal opinion.
2. Complete LIDES-portal registration with LLV and confirm portal credentials.
3. Approve the revised KYC policy and deploy updated self-certification forms to all client-facing channels.
4. Deliver the transaction-mapping matrix and begin the technical data-pipeline build.
5. Schedule a test submission through LIDES for Q4 2026 at the latest.
6. Update all client-facing contracts and issue data-processing notices reflecting new CARF obligations.

Liechtenstein crypto compliance is entering a new phase. The principality’s decision to adopt CARF early signals both regulatory maturity and supervisory seriousness. CASPs that invest in robust compliance infrastructure now will protect their licences, their banking relationships and their competitive position. Those looking for specialist guidance on CARF implementation in Liechtenstein can consult qualified regulatory-compliance professionals through the Global Law Experts lawyer directory.

Sources

1. Liechtenstein Fiscal Authority (LLV), CARF page
2. Regierung des Fürstentums Liechtenstein, published law (Regierung PDF)
3. Gesetze.li, Liechtenstein consolidated law / CARF MCAA entry
4. OECD, CARF commitments and technical guidance
5. KPMG TaxNewsflash, Liechtenstein CARF regulation enacted
6. Chambers, CARF MCAA & CRS addendum thought leadership
7. Bergt & Partner, local law firm insights on CARF Act and CRS revision
8. PwC Global Crypto Regulation Report (2026)
9. S&P Global / Market Intelligence, CARF & DAC8 overview
10. BankingHub, CARF/DAC8 reporting explainer