MiCA (MiCAR) explained

MiCA is the EU's comprehensive crypto regulation — a single rulebook for crypto-asset markets across all member states. It's now in force, and while it's primarily about authorisation and conduct, it also shapes how crypto-assets are classified for accounting and reporting. This page explains the essentials.

General information, not legal or tax advice. Confirm your specific obligations against the regulation and a qualified advisor.

What MiCA is

MiCA — the Markets in Crypto-Assets Regulation (Regulation (EU) 2023/1114, often "MiCAR") — creates a harmonised EU framework for issuing and providing services in crypto-assets, covering authorisation of crypto-asset service providers (CASPs), conduct and transparency rules, and requirements for stablecoin issuers.

The token classes

MiCA classifies crypto-assets into three broad groups, which determine the rules that apply:

• Asset-Referenced Tokens (ARTs) — tokens referencing a basket of assets, currencies, or commodities to stabilise value.
• E-Money Tokens (EMTs) — tokens referencing a single official currency (euro-stablecoins are the common example).
• Other crypto-assets — everything else in scope (e.g. utility tokens), excluding assets already covered by other EU financial law and excluding NFTs in most cases.

This classification matters beyond licensing: it can affect tax treatment too — for example, some jurisdictions give MiCAR-compliant euro-stablecoins distinct tax treatment.

What's in force

MiCA applies in stages: the rules for stablecoins (ARTs and EMTs) applied from mid-2024, and the broader rules for CASPs applied from end-2024 — so MiCA is now substantially in force across the EU, with transitional arrangements in some member states.

Why it matters for accounting

Correctly classifying each token under MiCAR — and tracking which assets are MiCAR-compliant euro-stablecoins versus other types — feeds both your regulatory position and, in some jurisdictions, the tax treatment of those assets.

How CryptaCount helps

• Classifies crypto-assets with MiCAR classification attributes, so each asset is tagged correctly
• Applies the right tax treatment where MiCAR status changes it (e.g. euro-stablecoin carve-outs)
• Keeps classification consistent across your books, with a full audit trail

Compliance & reporting → · The crypto sub-ledger →

General information, not legal or tax advice. Verify against the regulation and a qualified advisor.

What MiCA governs, and why accounting teams still care

MiCA is primarily a markets regulation — about who may issue crypto-assets and provide crypto services in the EU, and how they must conduct themselves — rather than an accounting or tax standard. So why does it land on a finance team's desk at all? Because the regulation's classification of each asset, set out on the page above as the ART / EMT / other-crypto-asset split, is a label that travels downstream. The category an asset falls into can influence how it is treated for regulatory and, in some jurisdictions, tax purposes, which means the classification has to be captured accurately and consistently in your books rather than assessed informally.

Who MiCA applies to is, at the general level, issuers and crypto-asset service providers operating in or into the EU. For a business keeping crypto accounts, the practical takeaway is narrower: regardless of whether you are the regulated entity, the assets you hold and transact carry MiCA classifications, and getting those tags right keeps your records aligned with the regulatory reality around them. The precise authorisation and conduct obligations that apply to your organisation are matters to confirm against the regulation and your advisor.

How MiCA classification reaches into your books

Classification is only useful if it is attached to the asset everywhere it appears. If a euro-referencing e-money token is tagged correctly in one report but treated as a generic crypto-asset elsewhere, your records contradict themselves — and any downstream treatment that depends on the classification inherits the error. The cleanest way to avoid that is to hold the MiCA classification as an attribute of the asset in your crypto sub-ledger →, so every movement, balance, and report that touches it carries the same correct label automatically rather than relying on someone remembering to apply it.

Where classification changes a downstream treatment — for example, jurisdictions that give MiCAR-compliant euro-stablecoins distinct handling — the tag has to flow through to the journal entries → and onward into the figures, not sit as a note on the side. That is the difference between classification as paperwork and classification as something that actually drives your accounting. The measurement of the asset itself still follows your accounting framework under IFRS → or US GAAP →; MiCA classification sits alongside that, informing treatment where the rules make it relevant.

The data and audit trail MiCA classification depends on

Defensible classification needs more than a category flag — it needs the basis for that flag preserved. An auditor or regulator looking at why an asset was treated as an EMT rather than an ART, or as an other-crypto-asset rather than out of scope, will expect to see the reasoning and the attributes that supported it, captured at the point of classification and kept consistent thereafter. Because classifications can be revisited as an asset's status or the guidance around it evolves, the trail also has to record changes with their justification.

• Per-asset classification attribute — the MiCA category attached to the asset itself, so it propagates to every movement and report.
• Classification rationale — the basis on which each category was assigned, preserved for audit and review.
• Compliance status detail — for example, whether a euro-stablecoin is MiCAR-compliant, where that distinction drives downstream treatment.
• Change history — any reclassification with its date and reasoning, so a later treatment difference reads as a tracked decision.
• Consistency linkage — assurance that the same asset carries the same classification everywhere it appears in the books.

The reconciliation challenge MiCA adds

MiCA's contribution to the reconciliation problem is consistency at scale. A business may hold dozens of distinct tokens across many wallets and venues, some of which look superficially similar — several euro-referencing stablecoins, for instance — but carry different regulatory status. Reconciliation here is not only about recognising each movement once and stripping internal transfers; it is about ensuring that the classification is applied uniformly to every instance of an asset, so the same token is never an EMT in one corner of the books and an undifferentiated crypto-asset in another.

When classification is held as an asset-level attribute on a reconciled ledger, this consistency comes almost for free: classify the asset once and every balance and movement inherits it. When it is applied manually, asset by asset and report by report, it becomes a recurring source of drift — exactly the kind of inconsistency that undermines confidence in the figures. Reconciling holdings and anchoring classification to the asset are two halves of the same discipline.

How a crypto sub-ledger supports MiCA compliance

A crypto sub-ledger supports MiCA by treating classification as first-class data rather than an afterthought. It tags each asset with its MiCAR classification, applies the corresponding treatment where the classification changes it — such as euro-stablecoin carve-outs in jurisdictions that recognise them — and keeps that classification consistent across every report and posting, with a full audit trail behind each decision. Because the classification lives with the asset in a reconciled store, the compliance and reporting → outputs that depend on it stay coherent automatically.

It also keeps MiCA in its proper relationship to the rest of your obligations. Classification under MiCA is distinct from your measurement under IFRS or US GAAP and from your reporting under DAC8 → or CARF →, but all of them draw on the same underlying assets. Holding one reconciled dataset, with MiCA classification attached at the asset level, means each of these layers reads from a single consistent foundation rather than from separate, divergent copies.

Scope and timing, at a general level

The page above already sets out that MiCA applies in stages and is now substantially in force, with stablecoin rules and the broader CASP rules having come into effect and transitional arrangements in some member states. The safe generalisation beyond that is simply that MiCA is a live, phased regime, and the precise authorisation requirements, transitional windows, and obligations that apply to your activities are matters to confirm against the regulation and your advisor rather than infer from the broad shape.

On scope, the practical question for a finance team is which of your assets fall into which MiCA category and which sit outside the regulation altogether — for instance, assets already covered by other EU financial law, or NFTs in most cases. Because those boundaries can be finely balanced for novel instruments, documenting why each asset was classified as it was belongs in the audit trail next to the figures. A defensible classification rationale is part of the record, not an optional extra.

Common pitfalls under MiCA

• Treating classification as a one-off note. A MiCA category that is not attached to the asset itself drifts out of date and contradicts the rest of the books.
• Conflating similar stablecoins. Several euro-referencing tokens can carry different status; lumping them together loses the distinction that drives downstream treatment.
• Assuming classification changes measurement. Measurement still follows your accounting framework; MiCA classification informs treatment where the rules make it relevant, but it does not replace IFRS or US GAAP.
• No rationale on file. A classification without its supporting basis is hard to defend if questioned.
• Ignoring reclassification. As status or guidance evolves, a stale classification with no change history misstates the asset.
• Inconsistent application across reports. The same asset classified differently in different places undermines confidence in every figure that touches it.

How CryptaCount helps with MiCA

CryptaCount makes MiCA classification durable and consistent. It tags each crypto-asset with its MiCAR classification as an attribute of the asset, applies the corresponding treatment where the classification changes it — such as euro-stablecoin carve-outs in jurisdictions that recognise them — and keeps that classification uniform across every balance, movement, and report, with a full audit trail behind each decision. Because the classification lives in one reconciled crypto sub-ledger alongside the assets themselves, it propagates everywhere automatically rather than being reapplied by hand, and it sits coherently beside your measurement under IFRS or US GAAP and your reporting under DAC8 and CARF. The precise authorisation obligations and category boundaries for your business remain matters to confirm against the regulation and your advisor.

Does MiCA change how we measure crypto in our accounts?

Not directly. Measurement follows your accounting framework — IFRS → or US GAAP →. MiCA's role is classification, which can influence downstream treatment in some jurisdictions, particularly for MiCAR-compliant euro-stablecoins. The two work together: measurement from your framework, classification from MiCA, both drawing on the same reconciled sub-ledger →.

Why does it matter which stablecoins are MiCAR-compliant?

Because some jurisdictions give MiCAR-compliant euro-stablecoins distinct treatment, the compliance status is not a cosmetic label — it can drive how the asset is handled downstream. Capturing that status as an attribute of the asset, rather than assessing it ad hoc, is what keeps the treatment correct and consistent everywhere the asset appears.

How do we keep MiCA classifications consistent across hundreds of transactions?

By anchoring the classification to the asset rather than to individual transactions. When the MiCA category is an attribute held once in a reconciled sub-ledger →, every movement and report involving that asset inherits the same label automatically, which removes the manual reapplication that is the usual source of drift.

Is MiCA relevant to us if we aren't a regulated CASP?

Potentially, in the narrower sense that the crypto-assets you hold still carry MiCA classifications that can affect their treatment, even if your organisation is not the regulated entity. Whether any authorisation or conduct obligations apply to your activities specifically is a separate question to confirm against the regulation and your advisor.