FMA Liechtenstein Publishes ART Guidance: Stablecoin Accounting Impact

Liechtenstein's financial regulator has published a guidance note, FMA-WL 2026/2, on how asset-referenced tokens can be offered to the public or admitted to trading under MiCAR. For finance teams, the practical message is that stablecoin accounting now has to sit alongside a documented, form-based regulatory pathway, and that credit institutions follow a different route from other issuers.

The source is short, and it is worth being precise about what it says and what it does not. The Financial Market Authority (FMA) Liechtenstein describes guidance covering two things: the admission of asset-referenced tokens (ARTs) to a public offer or to trading under the Markets in Crypto-Assets Regulation, and a submission and notification procedure for credit institutions that want to offer ARTs to the public. For both procedures, the guidance provides for the use of an FMA application form, set out as Annex 2. The notice does not, in the text available to us, set out fees, timelines, capital figures or approval outcomes, so this article does not either.

What follows is analysis of what that structure means for the people who have to account for these tokens, audit them, and keep the books defensible. It is written for accounting firms, auditors and CFOs, and it flags where a firm needs to check the full guidance document itself rather than rely on a summary.

What the FMA actually published

Two procedures, one application form

The guidance addresses the authorisation-style steps needed before an asset-referenced token is offered to the public in Liechtenstein or admitted to trading on a platform. It also covers a distinct submission and notification procedure for credit institutions. Rather than leaving applicants to assemble their own documentation format, the FMA points both procedures to a single application form attached as Annex 2.

That matters because a standard form tends to standardise the evidence behind it. When a regulator asks the same questions of every applicant, the issuer, the bank and the service providers around them learn quickly which facts must be on file: who the issuer is, what the token references, how it is structured, and who is responsible for what. Even without the form's contents in front of us, the direction is clear: expect structured, repeatable disclosure rather than free-form narrative.

Why credit institutions get their own route

The split between a general procedure and a notification procedure for credit institutions reflects a familiar regulatory logic: an entity that is already supervised as a bank is not treated the same as a new entrant. The source describes the credit-institution route as a submission and notification process, which suggests the bank's existing status is part of the picture. How far that lightens the burden is a question for the full guidance text, and finance teams should not assume the answer.

For a bank, the consequence is operational. A product team may be ready to launch a token offering while the finance function is still working out how the instrument will be recognised, measured and disclosed. The notification route does not remove that accounting work. It only changes the regulatory sequence that runs in parallel with it.

What the notice does not tell us

It is just as useful to be clear about the gaps. The source does not specify supervisory timelines, the content of Annex 2 in detail, ongoing reporting duties after admission, or how the FMA will treat specific token designs. Anyone building a controls framework should read the guidance in full and treat any summary, including this one, as a starting point. Where we discuss implications below, they are inferences from the structure of the process, not statements of what the FMA requires.

Why this matters for stablecoin accounting

Classification drives treatment

Asset-referenced tokens are one category within the MiCAR framework, and the label a token carries in regulatory terms is a useful signal when you decide how to classify it in the ledger. A token that is formally admitted as an ART has a documented regulatory identity. A token held by your client or your own treasury that carries a different label does not share that identity, even if both are described informally as stablecoins.

The practical lesson for usdc accounting and any broader stablecoin accounting policy is to avoid treating "stablecoin" as a single bucket. Reserve-backed, fiat-referenced tokens, tokens that reference a basket of assets, and algorithmic designs raise different measurement questions and different counterparty risks. Your chart of accounts, your sub-ledger tags and your disclosure notes should be able to distinguish them. A regulatory admission route like this one gives you a reason to formalise that distinction if you have not already.

We are not saying that a particular accounting standard dictates a particular outcome for these tokens. Treatment depends on the reporting framework you apply, the rights the holder has against the issuer, and how the token is used. The point is narrower: the regulatory status of the token should be one documented input to that judgement, and your file should show you considered it.

Evidence and audit trail

A standardised application means that, for tokens that go through this process, there will be a regulatory record of what was offered and by whom. Auditors can use that. If a client holds a token that was admitted through a regulated procedure, the audit file can reference the admission as part of its understanding of the instrument. If a client holds a token that did not go through such a procedure, the file should show why the client is comfortable with the exposure.

This ties directly to how you keep records. Wallet addresses, contract identifiers, issuer names, dates of acquisition and the on-chain transaction trail need to be reconcilable to the books. Crypto accounting software that can tag each position with its issuer and regulatory status, and preserve that tag through the life of the position, reduces the manual effort at year-end and during an audit request. The same applies to crypto bookkeeping software used by smaller practices: if the tool cannot store an issuer and classification field against each asset, you will be rebuilding that context in spreadsheets.

Counterparty and concentration risk

Treasury teams often hold stablecoins as a cash-like balance. A published admission route is a reminder that issuer quality is a real variable. Finance leaders should be able to answer, for each stablecoin balance they hold, who the issuer is, which regime it sits under, and what happens to the balance if redemption is delayed. These are risk questions as much as accounting ones, but they surface in the notes to the financial statements and in the going-concern and liquidity discussion.

What finance teams and firms should do now

For accounting firms and auditors

Start with your client inventory. For every client that holds, issues, or transacts in stablecoins, record the specific token, the issuer, and the jurisdiction in which the token is offered. Where a client operates in or has dealings with Liechtenstein, note that an ART offering or admission there now has a published procedure, and ask whether any of the client's tokens fall into that category.

Then review engagement terms and scoping. If a client plans to offer an ART, your work may touch the regulatory application as well as the accounts, depending on your role and independence position. Make sure the engagement letter says what you are and are not doing, and that any advisory support is separated appropriately from assurance work.

Finally, update your working-paper templates. A short, consistent section on token regulatory status, issuer, redemption rights and custody arrangement will save time and make reviews more consistent across engagements.

For CFOs and treasury teams

Review your stablecoin policy. If it treats all stablecoins the same, break it into categories and set limits for each. Record who approves new token types, what due diligence is performed on the issuer, and how often balances are reconciled to on-chain data and to custodian statements.

If you are a credit institution considering an ART offering, bring finance into the project early. The notification route described by the FMA is a regulatory process, but the instrument will land on your balance sheet or in your off-balance-sheet disclosures, and the accounting policy needs to be settled before launch rather than after. Equally, align the data you will provide in the application form with the data your finance and risk functions already hold. Inconsistent descriptions of the same token across regulatory, accounting and risk documents are an avoidable problem.

A short readiness checklist

The items below are drawn from the structure of the process, not from requirements stated by the FMA. Use them as an internal prompt.

Tax and AML angles to keep in view

Tax treatment is not set by this guidance

The FMA notice concerns market access under MiCAR. It does not address how tokens are taxed, and nothing in it changes the tax position of a holder or issuer. That said, regulatory classification often becomes evidence in tax discussions. If a token's status determines whether a holding is treated like a cash equivalent, a financial instrument or an intangible for tax purposes in a given jurisdiction, then a clear paper trail of that status supports your position. Tax teams should check local rules for each jurisdiction where the entity files and should not read across from this notice.

For B2B readers with cross-border groups, a practical step is to align the tax and accounting token registers. If the tax team and the finance team describe the same token differently, reconciling them later is costly. A shared register with agreed fields avoids that.

AML and sanctions screening still apply

A regulated route for token admission does not replace transaction monitoring. Firms that handle stablecoins still need to screen counterparties and wallets, retain records, and escalate unusual activity. Recent enforcement and threat reporting has shown how quickly stolen funds can be moved through stablecoin rails, which is why issuer freezes and on-chain tracing have become part of incident response. Our earlier coverage of Hong Kong's 24/7 tokenized settlement and stablecoin accounting looked at how round-the-clock settlement raises cut-off and reconciliation questions, and the same operational discipline applies here.

The international picture is also moving. Our piece on Japan FSA stablecoin hearings shows another regulator gathering views on how stablecoin issuers and banks should fit together. Different regimes, similar direction: clearer rules on who may issue, who may distribute, and how they are supervised.

Reporting and data readiness

Whatever the final shape of reporting obligations, the firms that cope best are those that can produce clean, reconciled data on demand. That means a ledger that links on-chain transactions to accounting entries, stores issuer and classification metadata, and keeps a history of changes. Digital asset accounting software with those features turns a regulatory information request from a project into a report. For a broader view of how this fits into reporting obligations, see our pillar on crypto compliance reporting.

Reading the guidance alongside your own position

If you issue or plan to offer an ART

The guidance is directly relevant. Obtain the full FMA text, including Annex 2, and map each question in the form to a source of truth inside your organisation. Decide who signs off the answers, and keep the version you submit under document control. Because the form is standardised, expect the regulator to be able to compare submissions, so internal consistency matters.

If you hold or service tokens issued elsewhere

The notice may not apply to you directly, but it still shapes the market you operate in. As more issuers go through formal procedures, counterparties, auditors and banks will increasingly ask holders to show which tokens they hold and under which regime those tokens were offered. Being able to answer quickly is a competitive advantage in onboarding and in audit.

If you are building or buying software

When you evaluate crypto accounting software, ask practical questions. Can it store an issuer and a regulatory classification against each asset? Can it keep a dated history if that classification changes? Can it export a position listing with those fields for an auditor? Can it reconcile on-chain balances to custodian reports? A tool that answers yes to these will adapt to new procedures more easily than one built only for trade-level tax lots.

Bottom line for finance leaders

The FMA's guidance gives asset-referenced tokens a published, form-based path in Liechtenstein, with a separate notification route for credit institutions. It is a procedural document, and its direct effect falls on issuers and banks. Its indirect effect is on everyone who accounts for stablecoins: regulatory status is becoming a documented attribute of a token, and your books and audit files should reflect it. Build the inventory, split your stablecoin policy by token type, align accounting, tax and compliance records, and read the full guidance before acting on any summary.

FAQ

What is FMA-WL 2026/2?

It is a guidance note from the FMA Liechtenstein on the admission of asset-referenced tokens to a public offer or to trading under MiCAR. It also covers a submission and notification procedure for credit institutions that want to offer such tokens to the public.

Which application form does the FMA use?

According to the source, both procedures use an FMA application form, referred to as Annex 2 of the guidance. The contents of the form are not summarised in the source, so read the full document before preparing a submission.

Does this change how stablecoins are taxed?

No. The guidance concerns market access under MiCAR and does not address taxation. Tax treatment depends on the rules in each jurisdiction where the holder or issuer files, so tax teams should assess it separately.

How does this affect usdc accounting?

The notice does not name specific tokens. The broader lesson for usdc accounting and other stablecoin accounting is to record the issuer, the regulatory regime and the redemption rights for each token, and to avoid treating all stablecoins as one category.

What should crypto accounting software support here?

At minimum, the ability to store issuer and classification data against each asset, keep a dated history of changes, reconcile on-chain balances to custodian statements, and export position listings for auditors.

Source: FMA Liechtenstein