Updating Commercial Agreements for CRS, CARF & Globe: Liechtenstein Contract Clauses for 2026

Liechtenstein’s simultaneous rollout of three cross-border tax-transparency regimes, the amended Common Reporting Standard (CRS 2. 0), the new Crypto-Asset Reporting Framework (CARF) and automatic exchange of Global Anti-Base Erosion (GloBE) minimum-tax data, means that every commercial agreement touching the jurisdiction needs a compliance review in 2026. Together, these frameworks expand who must collect data, what data must be exchanged and with whom it is shared, creating contractual risk that existing boilerplate simply does not address. For in-house counsel, CFOs, trustees, foundation administrators and external lawyers drafting or renegotiating Liechtenstein contract clauses for CRS CARF 2026 obligations, the window for updating agreements is narrow: reporting periods have already begun, and the first filing deadlines follow within months.

This guide provides the practical clause bank, liability-allocation models and amendment templates needed to close that gap.

CRS 2.0, CARF and GloBE, What Changed for Liechtenstein and When

Before drafting a single clause, counsel must understand the three regimes now layered onto Liechtenstein’s existing automatic-exchange architecture. Each imposes distinct obligations on different categories of reporting entity, and each carries its own first-deadline pressure point.

CRS 2.0 in Brief

The revised CRS, sometimes called “CRS 2.0”, broadens the scope of reportable financial products and tightens due-diligence requirements for financial institutions. Liechtenstein approved implementation of the amended CRS alongside CARF, with domestic effect for reporting periods starting in 2026, according to KPMG’s tax newsflash on Liechtenstein’s approval of CARF and the revised CRS. For CRS Liechtenstein practitioners, the key changes include expanded coverage of electronic-money products, central bank digital currencies and specified insurance products, plus enhanced look-through rules for passive entities.

CARF, Who Is in Scope

The CARF Act 2026 brings crypto-asset service providers (CASPs) into the automatic-exchange net for the first time. Under the framework, any entity or individual that, as a business, effectuates exchange transactions in reportable crypto assets on behalf of customers must collect and report transaction-level data for reportable users. Liechtenstein has committed to implementing CARF in line with the OECD’s timeline, as confirmed by the Liechtenstein National Administration (LLV) on its dedicated CARF information page. CASPs already registered under the Token and Trusted Technology Service Providers Act (TVTG) will need to layer CARF data-collection obligations on top of existing regulatory requirements, a point that intersects directly with the CASP licence and EU crypto compliance framework.

GloBE Automatic Exchange, GIRs and MNEs

Liechtenstein’s GloBE amendment introduces automatic exchange of minimum-tax data for multinational enterprises (MNEs) with consolidated revenues meeting the EUR 750 million threshold. MNEs must file Global Information Returns (GIRs) containing top-up tax calculations and Qualified Domestic Minimum Top-up Tax (QDMTT) reconciliation data. Liechtenstein joins the GloBE data exchange Liechtenstein network from 2026, according to analysis published by Bergt Law. For contract counsel, the critical implication is that intra-group service agreements, cost-sharing arrangements and joint-venture contracts must now allocate responsibility for compiling and delivering GIR data accurately and on time.

Comparison: Reporting Obligations by Entity Type

Who Is Responsible: Party-by-Party Obligations

Allocating reporting liability correctly starts with identifying which party in the contractual chain holds the primary regulatory obligation. Getting this wrong creates exposure for both sides: the obligated party faces penalties for non-compliance, while the non-obligated party may find itself dragged into enforcement proceedings if its contract promised data it could not deliver.

Financial Institutions, CRS Obligations and Practical Red Flags

Under CRS 2.0, the reporting financial institution (RFI) bears the primary duty to collect, verify and transmit account-holder data to the Liechtenstein tax authority. Practical red flags for contract negotiations include: custodians relying on self-certification forms that have not been updated for CRS 2.0 expanded fields; fund administrators that sub-delegate due diligence without contractual flow-down clauses; and nominee arrangements where the beneficial owner’s data sits with a third party not bound by the agreement. Contracts between RFIs and their service providers, administrators, transfer agents, IT vendors, should expressly state who is the “reporting entity” and impose obligations on the other party to supply data in the prescribed format and timeline.

Crypto-Asset Service Providers, CARF Data Collection

CASPs face a new category of obligation that has no direct contractual precedent in most Liechtenstein agreements. The data to collect includes the reportable user’s name, address, jurisdiction of tax residence, TIN, date of birth and, for each reportable crypto-asset transaction, the type of crypto asset, aggregate gross proceeds and number of units. Counsel negotiating CASP-related international commercial contracts should build data-collection mechanics directly into the agreement rather than relying on general regulatory compliance undertakings.

MNEs, GIR Registration and QDMTT Alignment

For MNEs, the GloBE obligation flows primarily to the Ultimate Parent Entity (UPE) or a designated filing entity. However, constituent entities in Liechtenstein may be required to supply the data that populates the GIR. Intra-group contracts, management-services agreements, cost-sharing arrangements and IP-licensing deals, must therefore include clear data-supply covenants. The recommended default allocation rule is straightforward: the entity that holds or generates the data bears the obligation to compile and deliver it; the entity that files the GIR bears the obligation to file accurately and on time; and both parties share an interest in a mutual indemnity for losses arising from the other’s failure.

Liechtenstein Contract Clauses for CRS CARF 2026: The Clause Bank

The following sample clauses are designed for adaptation into Liechtenstein-law-governed commercial agreements. Each clause includes a negotiation note highlighting the key risk-allocation decision. These should be reviewed with local counsel before execution.

Representations and Warranties

Sample Clause 1, CRS/CARF Status Representation. “Each Party represents and warrants that, as of the date hereof and throughout the term of this Agreement, it has determined its classification under the Common Reporting Standard (as amended) and, where applicable, the Crypto-Asset Reporting Framework, and has registered with the Liechtenstein tax authority as a Reporting Financial Institution or Reporting Crypto-Asset Service Provider, as required by applicable law.”

Negotiation note: The counterparty should resist giving this rep if it relies on a third-party administrator for its CRS/CARF classification. In that case, qualify the rep with a knowledge qualifier and add a covenant to notify promptly if classification changes.

Sample Clause 2, Tax-Residence Representation. “The Account Holder / Reportable User represents that the information provided in the self-certification form annexed hereto is true, complete and correct, and undertakes to notify the Reporting Entity within 30 calendar days of any change in tax-residence status.”

Negotiation note: This is a standard tax-reporting clause in contracts with natural-person counterparties. It should be paired with a right for the reporting entity to withhold services or payments if the self-certification is not updated within the notice period.

Sample Clause 3, CASP Registration Warranty. “The Service Provider warrants that it holds a valid registration as a Crypto-Asset Service Provider under the Liechtenstein CARF Act and the Token and Trusted Technology Service Providers Act (TVTG), and that such registration authorises it to effectuate the exchange transactions contemplated under this Agreement.”

Negotiation note: CASPs should ensure the warranty is limited to registrations actually required for the specific services provided, not a blanket warrant covering all possible CARF categories.

Data Collection and Transfer Clause

Sample Clause 4, Data-Supply Covenant. “The Data-Supplying Party shall collect, maintain and transmit to the Reporting Party, in machine-readable format and by no later than [45] calendar days before the applicable reporting deadline, all data fields required under CRS 2.0 and/or CARF for each Reportable Account or Reportable User, as applicable. The Data-Supplying Party shall promptly notify the Reporting Party of any data gaps, inconsistencies or corrections identified after transmission.”

Negotiation note: The number of days before the reporting deadline is a key negotiation point. Reporting parties should push for at least 45 days to allow validation and correction cycles. Data-supplying parties will resist anything beyond 30 days, citing operational burden. Where the parties cannot agree, consider a tiered approach: preliminary data at 60 days, final data at 30 days.

Indemnities, Tax-Reporting Indemnity Clause for Liechtenstein

A contract indemnity clause Liechtenstein practitioners will recognise as market-standard should cover two scenarios: a primary indemnity for breach of reporting obligations and a capped indemnity for data-quality failures.

Sample Clause 5, Primary Tax-Reporting Indemnity. “The Indemnifying Party shall indemnify, defend and hold harmless the Indemnified Party from and against any and all losses, penalties, fines, costs (including reasonable legal fees) and liabilities arising directly from the Indemnifying Party’s failure to comply with its reporting obligations under CRS, CARF or GloBE as allocated under this Agreement, except to the extent such failure results from the Indemnified Party’s breach of its own data-supply obligations hereunder.”

Sample Clause 6, Capped Data-Quality Indemnity. “The Data-Supplying Party’s aggregate liability for losses arising from inaccurate, incomplete or late data provided under Clause [X] shall not exceed [EUR amount or percentage of contract value] per reporting period, provided that this cap shall not apply to losses arising from the Data-Supplying Party’s wilful misconduct or gross negligence.”

Negotiation note: Caps should be calibrated to the potential penalty exposure. Industry observers expect Liechtenstein administrative penalties for CARF non-compliance to follow the proportionality framework already in place for CRS violations. Carve-outs for gross negligence and fraud are non-negotiable in most institutional contexts.

Cooperation and Audit Clause

Sample Clause 7, Cooperation Obligation. “Each Party shall cooperate in good faith with the other Party and with any competent authority in connection with any audit, inquiry or information request relating to CRS, CARF or GloBE reporting obligations under this Agreement. Each Party shall grant the other reasonable access to relevant records and personnel, subject to applicable data-protection requirements.”

Transitional Amendment Clause

Sample Clause 8, Regulatory Change Mechanism. “If any amendment, revision or successor legislation to CRS, CARF or GloBE requires a change to the reporting obligations, data fields or timelines contemplated by this Agreement, the Parties shall negotiate in good faith to amend this Agreement within [60] days of such change becoming effective. If the Parties fail to agree on amendments within such period, either Party may terminate this Agreement upon [90] days’ written notice.”

Negotiation note: The termination right is a powerful backstop that incentivises good-faith negotiation. Counterparties with significant switching costs may prefer a fallback to expert determination rather than termination.

Allocating Liability, Practical Negotiation Models

Beyond individual clauses, counsel need a structural model for how Liechtenstein contract clauses for CRS CARF 2026 obligations allocate risk across the deal. Three models predominate in current market practice.

Model A, Service Provider Bears Reporting Risk

This model is appropriate where the service provider controls the data and the reporting infrastructure. Typical scenarios include: fund administrators reporting on behalf of a fund; CASP platforms reporting on behalf of clients; and payroll or treasury service providers filing withholding data. Under Model A, the service provider takes on the primary reporting obligation and indemnifies the principal for regulatory penalties arising from reporting failures.

Model B, Principal Bears Reporting Risk

Model B applies where the client or principal maintains direct relationships with account holders or reportable users and merely outsources discrete operational tasks. For instance, an MNE constituent entity that outsources accounting but retains the obligation to supply GIR data to the UPE should bear the reporting risk. The vendor provides a limited data-accuracy warranty but does not assume the filing obligation.

Model C, Shared Liability with Indemnity Trigger Matrix

Model C is the most flexible and increasingly the most common for complex, multi-party arrangements. It uses a liability allocation table that maps each reporting obligation to a responsible party and defines indemnity triggers for each category of failure.

How to Update Commercial Agreements for 2026: Amendment Checklist

For existing agreements that predate the 2026 changes, a formal amendment or side letter is required. The approach depends on the formality requirements of the original contract and whether Liechtenstein law mandates notarisation.

Step-by-Step Execution in Liechtenstein

• Step 1, Audit existing contracts. Identify all agreements with CRS, CARF or GloBE-exposed counterparties. Flag contracts that lack tax-reporting representations, data-supply covenants or regulatory-change mechanisms.
• Step 2, Determine formality requirements. Under Liechtenstein law, most commercial contract amendments do not require notarisation unless the underlying agreement itself was notarised or the amendment concerns real property, certain corporate resolutions or foundation deeds. Where the original was notarised, the amendment must follow the same form.
• Step 3, Draft the amendment. Use a short, targeted amendment incorporating the sample clauses from the clause bank above. Annex updated self-certification forms and a data-reporting schedule specifying fields, formats and deadlines.
• Step 4, Execute and register. Have both parties sign the amendment. Where notarisation is required, execute before a Liechtenstein public notary. File any required commercial-register updates if the amendment alters the corporate structure or governance of a reporting entity.

Template Amendment Clause

“This Amendment No. [X] to the [Agreement Name] dated [date] (the ‘Original Agreement’) is entered into as of [date] by and between [Party A] and [Party B]. The Original Agreement is hereby amended by inserting the following new clauses [as Clause X.1 through Clause X.8]: [insert clauses from clause bank]. All other terms and conditions of the Original Agreement remain in full force and effect. This Amendment shall be governed by and construed in accordance with the laws of the Principality of Liechtenstein.”

Side Letter vs. Formal Amendment

A side letter is appropriate where the changes are limited in scope, for example, adding a single CARF data-supply covenant to a custody agreement. A formal amendment is preferable where multiple clauses are inserted, existing indemnities are restructured or the amendment alters the economic allocation of risk. Early indications suggest that institutional counterparties in Liechtenstein’s financial-services sector are opting for formal amendments to provide clearer enforceability in regulatory proceedings.

Due Diligence Liechtenstein: Pre-Closing Checklist for M&A, Trusts and Foundations

For transactional counsel conducting due diligence Liechtenstein-side, whether on an acquisition target, a foundation or a trust structure, the 2026 regimes add a discrete category of risk that must be diligenced separately.

Targeted Due-Diligence Items

• CRS/CARF registration status. Confirm whether the target is registered as an RFI or CASP with the LLV. Request copies of registration confirmations and any correspondence with the tax authority.
• Historic reporting compliance. Review prior-year CRS filings for completeness and timeliness. For CASPs, verify whether any CARF pre-registration or data-mapping exercises have been completed.
• Contract portfolio review. Identify all contracts with counterparties that generate reportable data. Flag agreements that lack updated tax-reporting clauses.
• GloBE exposure. For MNE targets, confirm whether the group exceeds the EUR 750 million consolidated revenue threshold and whether GIR filing processes are documented.
• Penalty exposure. Request disclosure of any pending or concluded enforcement actions, late-filing penalties or data-quality remediation orders from the LLV.

Data-Mapping Requirements

Acquirers should require targets to produce a data map showing the flow of reportable data from source systems through to the tax-authority filing portal. This map should identify all third-party vendors, sub-processors and manual intervention points, each of which represents a potential break in the data chain and a corresponding contractual risk.

Representation Schedules for Sellers

In share-purchase or asset-purchase agreements, include a dedicated schedule in which the seller represents the target’s CRS, CARF and GloBE compliance status. This schedule should survive closing for a minimum of two reporting cycles (typically 24 months) to cover the period during which errors in pre-closing filings may be discovered by the LLV. For more on structuring cross-border commercial agreements effectively, see our international commercial contracts guide.

Enforcement Risk, Penalties and Indemnity Limits

Liechtenstein’s tax authority has administrative penalty powers for failures to comply with CRS, CARF and GloBE reporting obligations. While the specific penalty ranges under the new CARF Act are expected to follow the proportionality framework already established for CRS violations, the practical effect for contract drafters is clear: indemnities must be calibrated to real penalty exposure, not arbitrary figures.

When drafting indemnity caps for tax-reporting clauses in contracts, counsel should consider the following guardrails:

• Caps. Set aggregate caps per reporting period, typically expressed as a fixed EUR amount or a percentage of annual fees under the contract.
• Baskets. Include a de minimis threshold below which individual claims do not count toward the cap, to filter out trivial data-quality issues.
• Survival periods. Indemnities should survive termination for at least the period during which the LLV may initiate proceedings, typically three to five years for tax-related matters.
• Carve-outs. Gross negligence, wilful misconduct and fraud should always be carved out from any cap or limitation.

Cross-border enforcement adds a further layer: where Liechtenstein exchanges data with a partner jurisdiction that then identifies a discrepancy, the resulting inquiry may reach back to the data-supplying party in Liechtenstein. Contracts should address this scenario with a specific cooperation clause and a clear allocation of the costs of responding to foreign-authority inquiries.

Conclusion: Next Steps for Updating Liechtenstein Contracts in 2026

The convergence of CRS 2. 0, CARF and GloBE reporting obligations in 2026 represents the most significant expansion of Liechtenstein’s automatic-exchange framework since the original CRS implementation. For practitioners, the priority is immediate and practical: audit existing contract portfolios, identify gaps, and deploy the Liechtenstein contract clauses for CRS CARF 2026 set out in this guide. The clause bank, covering representations, data-supply covenants, indemnities, cooperation obligations and amendment mechanics, provides a starting point that should be adapted to each deal’s specific risk profile. Counsel advising financial institutions should focus on CRS 2. 0 expanded fields; those advising CASPs should prioritise CARF data-mapping and CASP registration requirements; and those advising MNE groups should ensure intra-group agreements allocate GIR data responsibilities clearly.

Engaging a Liechtenstein-qualified contract lawyer and, where formal amendments require it, a local notary is strongly recommended to ensure enforceability and compliance before the first filing deadlines arrive.

Sources

1. Liechtenstein National Administration (LLV), CARF page
2. Chambers and Partners, Liechtenstein CARF/CRS analysis
3. Bergt Law, CARF insights
4. Bergt Law, GloBE amendment analysis
5. OECD, CARF commitments
6. KPMG, Liechtenstein CARF/CRS statement adopted
7. KPMG, Liechtenstein CARF and revised CRS approved
8. Legal500, Crypto-asset transparency 2.0 thought leadership
9. Marxer Attorneys, CARF insights
10. FinTech Global, CRS 2.0 reshaping tax compliance
11. Sovereign Group, CRS 2.0 and CARF explainer