For an early-stage founder building a digital-asset business, the VAT treatment of crypto services is rarely the first question on the whiteboard — but it consistently becomes one of the most expensive questions left unanswered. A token launch structured without reference to VAT exposure in the issuing jurisdiction, the user-base jurisdiction and the treasury jurisdiction can create obligations that dwarf the cost of getting it right at the outset. Personal tax residency and corporate structure must be decided together, or the decision effectively defaults to the worst available answer.
This page sets out the regulated basis for VAT analysis on crypto services, the common structural errors early-stage founders make, the cross-border interaction between entity domicile and founder residence, and the practical process for building a VAT-clean structure before a token event or a fundraise.
Why does VAT exposure catch early-stage crypto founders off guard?
VAT on digital services does not wait for profitability. It attaches to supplies made in the course of an economic activity, often before a founder has drawn a salary or closed a round. For a token issuer, the question of whether a token sale constitutes a VAT-able supply of services, a transfer of property, a financial service exempt from VAT, or something outside the scope entirely, turns on the rights the token confers – not on the label the white paper assigns to it.
Across the European Union, the principle established under MiCA (the Markets in Crypto-Assets Regulation), enforced by national competent authorities under ESMA oversight, is that substance governs classification. A token marketed as a utility instrument but conferring rights resembling an e-money token or a security will be assessed accordingly. The VAT analysis follows the same logic: the supply is characterised by what the buyer actually receives.
In our practice, we see founders make a structurally identical error. They treat the token-issuing entity's domicile as the only relevant VAT jurisdiction, ignoring the place-of-supply rules that attach to digital services supplied to customers in other member states or other VAT territories. A British Virgin Islands entity issuing tokens to EU-resident buyers may still trigger VAT registration obligations in one or more EU member states, depending on the characterisation of the supply and the applicable threshold rules in each territory.
The cross-border reality is this: the entity's registered address determines which regime governs the issuer's own compliance obligations. It does not determine where VAT obligations arise in relation to each supply. Those two questions have different answers, and conflating them is the most common structural gap we identify at the intake stage.
The process above describes the standard analytical path. Your facts — the token design, the user base geography, the treasury entity and the founder's own residence — change the analysis materially. For a scoped assessment of your current or planned structure, contact OBOLUS at info@oboluslaw.com.
How are different crypto service supplies classified for VAT purposes?
VAT classification of a crypto supply depends first on whether the supply is within scope, and second on whether it qualifies for an exemption — most commonly the financial-services exemption that applies in the EU and in the United Kingdom under the respective regimes.
The core categories, as they are treated across the major VAT territories, run broadly as follows.
- Exchange and conversion services: the supply of intermediation in converting one crypto-asset into another, or into fiat currency, is generally treated as a financial service. In the EU, the Court of Justice's reasoning in the Hedqvist matter established that bitcoin exchange falls within the financial-services exemption. Subsequent guidance from national tax authorities has extended that principle, with varying scope, to other fungible crypto-assets. The exemption typically does not extend to the platform fee charged for the service, which remains taxable in some territories.
- Token sales at issuance: the VAT treatment of an initial token offering turns on the token's classification. A payment token or a currency-like token issued at par tends to follow the Hedqvist logic. A utility token conferring access to future services is more likely to be treated as a prepayment for a taxable supply, triggering VAT at the point of sale or at redemption, depending on the jurisdiction's voucher rules. An asset-referenced token or security token may fall outside the financial-services exemption altogether.
- Staking and validation services: where a founder or a treasury entity provides staking services to third parties in exchange for a fee, that supply is generally taxable. The characterisation of staking rewards received by the entity as a network participant — as distinct from a service provider — is treated differently across the EU member states and the UK, and national guidance diverges.
- Custody and safekeeping: regulated as a service in most flagship regimes, the fee charged for custody is typically a taxable supply. The VAT-registration threshold in each jurisdiction where customers are located governs whether registration is required.
- Advisory and development services: fees for smart-contract development, tokenomics advisory, or legal and compliance work are standard business-to-business services. They follow the general place-of-supply rules and, in a cross-border context, typically shift the VAT obligation to the business recipient under the reverse-charge mechanism.
The practical consequence for a founder is that a single product — say, a platform offering exchange, custody and staking — may generate two or three VAT treatments operating simultaneously. Building that analysis into the entity structure before launch costs a fraction of what a retrospective compliance review costs after users have been onboarded across multiple territories.
How does the holding structure affect the group's VAT position?
The holding entity's domicile determines which regime governs the group's intra-group supplies, the recovery of input VAT on professional fees and technology costs, and the reporting obligations on supplies made to third-party customers. Getting the domicile decision right requires mapping the VAT consequences alongside the direct-tax consequences — they are not the same analysis and do not always point to the same jurisdiction.
A founder choosing between a Malta entity under the MFSA's VFA-to-MiCA transition, a Singapore entity under the MAS Payment Services Act regime, or a BVI entity under the BVI FSC's VASP Act 2022 is making three structurally different VAT decisions. Malta is an EU member state, so the entity is within the EU VAT system. Singapore imposes GST on supplies of digital services with its own registration thresholds. The BVI has no VAT, but the BVI entity supplying services to EU customers may still trigger EU VAT obligations under the non-established supplier rules.
The interaction between the holding structure and the founder's own tax residency adds a further layer. An Irish-domiciled founder who incorporates in Singapore but remains habitually resident in Ireland may create an Irish tax presence through the management-and-control rules — which in turn affects the entity's exposure to Irish VAT. A common assumption we encounter is that relocating personally is sufficient to change the group's tax position. It is not. Personal relocation affects the founder's income-tax position. The entity's VAT and direct-tax obligations depend on where the entity itself is managed and controlled, where its customers are located, and where its supplies are treated as made.
In a recent structuring matter, a two-founder team at the pre-token stage had incorporated a Cayman entity for the treasury and a BVI subsidiary for development. They had not analysed whether the management functions being performed from a European city created a taxable presence there. On review, those management activities were triggering corporate-tax exposure in the founders' city of residence and, separately, creating a risk that supplies made by the BVI entity were being treated as made from that city for VAT purposes. Restructuring at that stage — before the token sale — was straightforward. Addressing the same issue after a public token event would have been materially more complex.
What cross-border VAT obligations arise when your users are global?
A digital-asset platform with users across the EU, the UK, Singapore and the Gulf faces VAT obligations that are structurally impossible to manage from a single jurisdiction without deliberate structural planning. Each territory's rules on non-established digital-services suppliers create registration thresholds, reporting requirements and reverse-charge interactions that operate independently of one another.
Within the EU, the One Stop Shop (OSS) mechanism allows a non-established supplier of digital services to register in a single member state and account for VAT due in all other member states through that single registration. This mechanism is available to entities established outside the EU that supply digital services to EU consumers. The threshold for triggering EU VAT registration as a non-established digital-services supplier is lower than many founders expect – and importantly it applies on a cumulative cross-EU basis, not per member state.
The UK operates its own regime following the departure from the EU VAT area. Supplies of digital services to UK consumers by a non-UK entity trigger UK VAT registration and reporting obligations independently of any EU OSS registration. A founder who has managed EU exposure through OSS may still have an unaddressed UK registration obligation.
Singapore's GST regime for overseas digital-services suppliers applies to B2C supplies above the applicable registration threshold. The AIFC jurisdiction in Kazakhstan does not impose VAT on most financial services originating within the free zone. The UAE, under VARA's remit for Dubai, operates a federal VAT regime administered separately from VARA's licensing function – VAT compliance there is a Federal Tax Authority matter, and it interacts with VARA licensing in ways that are not always visible in the licensing process alone.
The practical takeaway: a global user base means multiple potential VAT registration obligations, each governed by the rules of the user's jurisdiction, not the entity's jurisdiction. Mapping that exposure early, and structuring supply flows to use available exemptions and registration mechanisms efficiently, is a core part of what we do for founders at the pre-token and post-seed stages.
If a prior compliance gap has already been identified – or if a tax authority in a user jurisdiction has raised an inquiry – a structured review can surface the exposure and the options. Write to OBOLUS at info@oboluslaw.com or message us via t.me/oboluslaw to map your current position.
How does founder tax residency interact with the entity's VAT and direct-tax position?
A founder's personal tax residency affects the entity's tax position in two distinct ways that are often treated as a single question. They are not. Conflating them is one of the more expensive structural errors we see at the mid-raise stage.
The first interaction is through management-and-control rules. In most common-law and civil-law jurisdictions, a company is resident for tax purposes where its central management and control is exercised. If a founder who is the sole director makes all material decisions from their home jurisdiction, the entity may be treated as tax-resident in that jurisdiction regardless of where it is incorporated. That tax residence determination then anchors the entity's VAT obligations in that territory.
The second interaction is through personal income on distributions, carried interest and token allocations. A founder who relocates to a territorial-tax jurisdiction — Singapore, the UAE, Portugal under its applicable regime — may reduce personal income-tax exposure on distributions. But that personal benefit does not flow to the entity. The entity's own obligations depend on the entity's own residence, the character of its supplies and the rules of each territory where it operates.
We align founder residency planning with the holding structure and the exit plan as a single exercise. The reason is straightforward: a VAT-clean entity structure and a director-level residency arrangement that is not coordinated will eventually conflict. The conflict typically becomes visible at the first institutional due-diligence process, when a fund's tax counsel asks for the group's tax-residency analysis and finds that none exists as a coherent document.
The decision matrix for early-stage founders runs broadly as follows. A founder who is personally mobile and is building a B2B infrastructure product with no consumer-facing token sale faces a different residency-and-structure decision than a founder building a consumer exchange with EU and UK retail users. The former can often optimise around a territorial-tax jurisdiction for the founder and a low-VAT-cost domicile for the entity. The latter needs to account for the EU CASP authorisation requirements under MiCA, the OSS VAT registration mechanism, and the interaction between the entity's VAT obligations and the founder's own residence.
What are the most common VAT and tax-structure mistakes early-stage founders make?
Based on the structuring work we do at the pre-token and post-incorporation stages, several errors recur with enough frequency that we treat them as structural failure modes rather than isolated mistakes.
Treating incorporation as a tax decision. Incorporation in a zero-tax jurisdiction does not create a zero-tax outcome if the founders, the servers, the customers or the IP are located elsewhere. The entity's domicile is the starting point for the tax analysis, not the end point.
Ignoring VAT on the assumption that the business is not yet profitable. VAT attaches to turnover, not to profit. A token sale generating significant revenue in a jurisdiction where the issuer has not registered for VAT creates an immediate liability, regardless of whether the business has broken even.
Separating the IP-holding structure from the token-issuance entity without mapping the VAT consequences of intra-group IP licences. Where the operating entity pays a royalty to an IP-holding entity for the use of the protocol, that payment may be a taxable supply. If the IP-holding entity is in a jurisdiction with no VAT, the supply may still trigger a reverse-charge obligation in the operating entity's jurisdiction.
Failing to document the basis for a VAT exemption claim. The financial-services exemption for crypto-exchange and conversion services is not self-executing. Many jurisdictions require the entity to file for the exemption, maintain evidence of how each supply qualifies, and update that analysis as the product evolves. A platform that adds a new service without reviewing its VAT classification may inadvertently apply an exemption to a supply that no longer qualifies.
Treating the Travel Rule and AML compliance as separate from the VAT structure. They are. But a VAT registration in a new jurisdiction may trigger AML registration requirements under that jurisdiction's VASP regime, and vice versa. The two analyses need to be run in parallel, not sequentially.
Self-assessment: is your current structure VAT-clean?
Before engaging counsel, a founder can run a preliminary self-assessment against the following indicators. If the answer to two or more of these questions is uncertain, the structure warrants a scoped legal review.
- Has the entity's legal team characterised each token type issued — payment, utility, ART, EMT — and documented the VAT treatment for each, jurisdiction by jurisdiction?
- Is there a live map of the user base by territory, and has that map been compared against each territory's VAT registration threshold for non-established digital-services suppliers?
- Has the intra-group supply chain — IP licences, management fees, development services — been reviewed for VAT on a per-supply, per-territory basis?
- Does the founder's personal tax-residency arrangement reflect the current state of the entity's management-and-control reality, not the state at incorporation?
- Has the basis for any VAT-exemption claim been documented and filed where required by the relevant jurisdiction?
- Has the group's structure been reviewed since the last material change to the product — new service line, new jurisdiction, new token — to confirm that existing VAT and direct-tax positions still hold?
A "no" or "uncertain" answer to any of the above indicates a gap that is typically cheaper to address pre-token than post-token. The cost of retrospective compliance — back-registration, interest, penalties and the professional cost of reconstructing transaction records — consistently exceeds the cost of proactive structuring.
Related at OBOLUS
- Tax and Cross-border Structuring for Digital Asset Businesses – the full practice overview for cross-border tax, holding structures and entity domicile decisions.
- Tax Treatment of Tokens in Singapore – how MAS and the Singapore tax authority approach token classification, GST and direct-tax obligations for digital-asset entities.
- VAT Treatment of Crypto Services – Legal Counsel for Digital Asset Firms – the broader firm service page covering VAT analysis and compliance strategy for operating digital-asset businesses.
FAQ
Where should a token-issuing entity be domiciled?
There is no single answer. The right domicile depends on the token type, the user-base geography, the regulatory licensing requirements, and the founder's own residency. A MiCA-regulated CASP authorisation requires an EU entity. A payment-token issuer targeting the Gulf may prefer a VARA or ADGM structure. A utility-token issuer with a global user base may find a Singapore MAS-licensed entity or a Cayman-BVI structure more practical. Each scenario carries distinct VAT and direct-tax consequences that must be mapped before incorporation.
How are staking rewards taxed?
Treatment varies by jurisdiction and by the staking model. Rewards received by an entity as a network participant — rather than as a fee for providing staking services to third parties — are generally treated as income at the point of receipt in most common-law jurisdictions, though the precise characterisation differs. The VAT treatment also diverges: passive protocol rewards are typically outside the scope of VAT, while fee-based staking services to third parties are more likely to constitute a taxable supply. National guidance in the EU member states and the UK has evolved on this point and continues to develop.
Does remote working create tax residency risk?
Yes, in two distinct ways. A founder who performs management functions remotely from a jurisdiction where the entity is not registered may create a taxable presence — a permanent establishment or a tax-residency trigger — for the entity in that jurisdiction. Separately, the founder's own personal tax residency may be affected if they spend sufficient time in a jurisdiction with residency-based taxation. Both risks are functions of the actual facts of day-to-day activity, not of where the entity is incorporated or where the founder is nominally domiciled.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance structures that sit around them. Digital assets are the whole of our practice. We align founder residency with the holding structure and the exit plan as a single coordinated exercise — because the two decisions made separately almost always conflict by the time institutional capital arrives. To discuss your structure, contact info@oboluslaw.com.
By Lydia Brennan, Tax & Structuring Analyst — specialising in VAT analysis, holding-structure design and cross-border tax coordination for digital-asset founders and token issuers.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.