What Is LTU? The Obligation Token Explained
A complete, plain-language explanation of what LTU is, what it is not, and how it is treated under EU VAT law (including the ECJ case law that means VAT applies only at the burn/redemption event), US securities regulation, and MiCA. Written for users, accountants, and regulators alike.
Start here: the simplest version
When you work within this platform and earn LTU, you have not been paid. You have been given a record — a precise, traceable record — that the productive economy around you owes you something back.
When you commit LTU to a new contract, you are making the same kind of promise in the other direction: you owe a future performance. The LTU sits in escrow until you deliver.
Nothing is settled. Nothing is taxed. Nothing is consumed. The system is working.
Settlement — the moment where value is actually realised — happens once: when you burn your LTU to access something real. A property lease. An expert service. A hotel room built by the same network you contributed to. At that point, an invoice is generated, VAT is applied, and revenue is recognised. For the first time in the whole chain, a consumption event has occurred.
Everything before that burn was production. And in production, the same rules apply as they do inside any company: people work toward a shared outcome, obligations are passed down the chain, and no tax event occurs at each internal handoff.
What LTU is not
Before going further, let's clear the most common misconceptions:
- Not a cryptocurrency. LTU does not exist to appreciate in price. There is no speculation, no mining, no open market where you can sell it to a stranger for profit.
- Not a stablecoin. LTU is not pegged to any currency and makes no price stability promise.
- Not equity. LTU carries no ownership of the platform, no governance votes over the company, and no share of its profits.
- Not a gift card. A gift card is bought with cash by the person who wants to receive services. LTU is earned by the person who delivers services. The direction is opposite.
- Not wages. Wages are settled at the time of work. LTU is a deferred claim — it only becomes realisable when it is burned for something real.
- Not money. LTU cannot be redeemed for cash from the platform. Its value lives only within the network of obligations it represents.
The hotel construction analogy
Imagine a hotel is being built. The project involves a wood cutter, a woodworker, a contractor, and a developer. None of them is billing the next person in the chain. They are all contributing toward the same thing: a finished hotel.
When the hotel opens, guests pay to stay. That is when revenue is recognised. That is when VAT is collected. That is the consumption event.
Now imagine those same four people will be entitled to stay in the hotel themselves once it opens — their contribution earns them access to the output they helped create. The wood cutter cuts trees. The woodworker shapes them. The contractor assembles. Each passes the obligation forward. Each holds a record of their contribution. None of them has been "paid" in the moment. None of them has consumed anything.
That is exactly how LTU works.
The burn event — redeeming LTU for a hotel stay, a lease, an expert service — is the moment the wood cutter finally stays in the room they helped build. Revenue is recognised at that moment. An invoice is generated. Tax applies.
Everything before it was internal to the productive chain.
The legal precedent: this is not a new idea
This model is not novel. It has been operating legally in multiple jurisdictions for nearly a century.
The WIR Bank (Switzerland, 1934 — present)
The Swiss WIR Bank issues WIR Francs — a complementary currency circulating among approximately 60,000 Swiss businesses. WIR is not redeemable for Swiss Francs from the issuer. It circulates purely as a bilateral trade credit: I do work for you, you pay me in WIR, I spend WIR with someone else for their services.
Swiss authorities have consistently treated WIR as a unit of account for contractual obligations — not as money, not as a security. It is taxable as barter income when received as compensation for services rendered. It has never attracted financial regulation as a deposit or a security. It has operated continuously under this framework for over ninety years.
LTU is structurally similar, with one important distinction: LTU transfers within the platform during production are not intended as compensation between parties. They are internal obligation transfers within a cooperative chain — closer to a company allocating internal costs than to businesses billing each other.
Time banking (US, UK, EU)
Time banking systems — operated by hOurworld, TimeBanks USA, Timebanking UK, and hundreds of local networks — exchange time credits between members: one hour of service earns one credit, redeemable for one hour of another member's time.
In the UK, HMRC has confirmed that where time banking operates through a not-for-profit intermediary and credits are not used commercially, VAT does not apply to the exchanges. In the US, the IRS has generally treated community time banking as outside normal tax reporting, though commercial platforms attract higher scrutiny.
The key precedent from both models: when an instrument circulates within a defined community toward a shared productive purpose, regulators have consistently distinguished it from commercial cash-equivalent transactions.
Why VAT does not apply to intermediate LTU transfers
This is the part most accountants will want to understand. The short version: VAT applies once — at the burn event. Not at every transfer in between. Here is why, with the legal basis for each argument.
Argument 1: There is no bilateral supply between participants
EU VAT law requires a direct link between a service provided and the consideration received for VAT to apply. This was established by the European Court of Justice in Tolsma v Inspecteur der Omzetbelasting (Case C-16/93, 1994) and confirmed in Mohr v Finanzamt Bad Segeberg (Case C-215/94, 1996): a payment only attracts VAT if there is a legal relationship between provider and recipient in which reciprocal performance is exchanged.
When the wood cutter passes LTU obligations down the chain to the woodworker, the woodworker is not paying the wood cutter for services. Both are contributing to the same project. The LTU moves because the collective obligation moves — not because one party is compensating the other directly. The direct bilateral link that VAT requires does not exist at each intermediate transfer.
Argument 2: LTU is a Multi-Purpose Voucher under EU Directive 2016/1065
The EU Voucher Directive, which came into force across all member states from 2019, introduced a specific VAT framework for instruments accepted as consideration for a future supply. It distinguishes two types:
- A Single-Purpose Voucher (SPV): the goods or services and the VAT rate are known at the time of issue. VAT is charged on issue.
- A Multi-Purpose Voucher (MPV): what will be supplied — and therefore the VAT rate and place of supply — is not known at the time of issue. VAT is charged only at the point of redemption, not at any earlier transfer.
LTU is an MPV. When LTU is minted, it is not known whether it will be redeemed for a hotel stay, a legal consultation, an expert adjudication service, a property lease, or another category of service — each of which may attract a different VAT rate in a different jurisdiction.
The consequence under EU law is unambiguous: every intermediate transfer of an MPV is outside VAT scope. The wood cutter passing LTU to the woodworker — not a VAT event. The woodworker passing it to the contractor — not a VAT event. The contractor redeeming it for a hotel stay — VAT event, applied at the rate applicable to that service on the date of redemption.
This is not a workaround. It is the explicit design of the Voucher Directive, applying precisely as intended.
Argument 3: The single enterprise principle — internal transfers are not supplies
EU VAT law has long recognised that where legally separate parties operate as a single economic unit toward a common purpose, their internal transactions are not separate supplies for VAT purposes.
In Polysar Investments Netherlands BV v Inspecteur der Invoerrechten en Accijnzen (Case C-60/90, 1991), the ECJ established that transactions between parties forming part of the same economic whole can fall outside the scope of VAT. This is extended by Article 11 of the VAT Directive, which allows member states to recognise VAT groups — clusters of parties treated as a single taxable person — for whom internal transactions are transparent to VAT entirely.
When a group of contractors is building a hotel together, passing LTU obligations between themselves as they go, they are functioning as a single enterprise working toward one output. The supply to the outside world — to the guest who stays in the hotel, to the person who redeems LTU for a service — is the only transaction that crosses the enterprise boundary. That is where VAT is collected. That is where it should be collected.
Argument 4: VAT is a tax on consumption, not on production
The fundamental policy purpose of VAT, established in the First VAT Directive and confirmed across decades of ECJ jurisprudence, is to tax consumption — the final use of a good or service by an end user — not the intermediate stages of production.
Applying VAT to every LTU transfer during production would create exactly the cascading tax effect that VAT was designed to eliminate. A wood cutter passing obligations to a woodworker, both of whom are working toward the same hotel, has not consumed anything. No consumption event has occurred. Taxing that transfer would mean the same underlying value is taxed multiple times before it reaches the end consumer — precisely what the input tax credit mechanism of VAT was built to prevent.
The correct and legally sound position: VAT applies at the burn event, once, on the value of the service or access redeemed. The invoice generated at burn is the VAT document. It is the record that consumption occurred, who consumed it, what was received, and what tax is due.
The tax picture — clearly stated
| Event | Who | What happens |
|---|---|---|
| LTU minted on contract completion | You (the service provider) | You hold a deferred claim. No immediate cash received. Keep records of the FMV at this point for your accountant. |
| LTU transferred between participants during production | Both parties | Outside VAT scope — MPV intermediate transfer rules apply (Directive 2016/1065) and/or single enterprise principle (Polysar, C-60/90). No tax event. |
| LTU committed to escrow | Both parties | A conditional commitment. No settlement, no tax event. |
| LTU burned — redeemed for services or access | Redeemer | Consumption event. Invoice generated. VAT applies at the rate for the service received. For businesses, this may be a deductible expense. |
| Service provider receives LTU at burn completion | Provider | Income recognition at the point of delivery and burn. |
| Platform fee taken at burn | Platform | Standard revenue recognition — VAT on the platform's fee. |
The difference between earning LTU and earning Euros
If a contractor pays you €100 for a day's work, you have received money. It is income on the day you receive it. Income tax applies. If you are VAT-registered, a supply has occurred.
If the same contractor acknowledges your day's work with LTU within this platform, no settlement has occurred. The LTU records an obligation. You have not received anything realisable yet. The tax event occurs when you burn that LTU — when you redeem it for something real: a hotel stay, a service, a lease. At that point, an invoice is generated and the appropriate tax applies.
This is not a tax avoidance structure. It is a timing alignment: the tax event matches the consumption event, because no consumption occurs until burn. This is how every sound accounting framework — from EU VAT rules to US revenue recognition standards — is designed to work when applied correctly to deferred obligation instruments.
Is LTU a security? The US position
Under the Howey test — the US Supreme Court's 1946 framework for identifying securities, confirmed in SEC v W.J. Howey Co. — an investment contract requires: an investment of money, in a common enterprise, with an expectation of profits from the efforts of others.
LTU fails on two counts. First, LTU is primarily earned through performance, not purchased with money. Second, LTU promises no profit: it carries no yield, no appreciation right, and no share of the platform's revenue. The value of an LTU is the right to have equivalent work performed in return — which is the definition of a contractual right, not an investment.
The SEC's 2025 framework for digital assets acknowledges that most tokens performing a practical function — granting access to something specific without investor profit-sharing — are not securities. LTU is more conservatively structured than most tokens in this category: it has no secondary market by design.
The risk area to monitor: if LTU were to develop a liquid open market where it could be bought and sold freely for cash, regulators would revisit the classification. The platform's structural design — no cash redemption from the platform, no open exchange listing — is what maintains this position.
The EU and MiCA position
MiCA (the EU's Markets in Crypto-Assets Regulation, fully in force from December 2024) defines utility tokens as crypto-assets granting "access to a good or service supplied by the issuer." LTU does not grant access to a service supplied by the platform — it grants a claim on another participant's future performance. The issuer is not the ultimate service provider.
The honest position: LTU does not fit neatly into any of MiCA's three regulated categories — e-money tokens, asset-referenced tokens, or utility tokens as classically defined. It may fall outside MiCA's scope entirely as a contractual rights instrument rather than a crypto-asset.
If the platform were to publicly offer LTU or list it on an exchange, the safest compliance position would be to treat it as a utility token and publish a crypto-asset whitepaper — not because the classification is precise, but because it is the closest available framework and regulators would apply it by analogy in the absence of clearer guidance.
What LTU definitively is not under MiCA:
- Not an e-money token. It is not pegged to fiat. The platform is not an e-money institution and no ECB licence is required.
- Not an asset-referenced token. It is not backed by a basket of assets. Reserve requirements do not apply.
The structural features that protect this classification
Three architectural decisions keep LTU outside financial regulation and ensure its legal character remains clear:
- No cash redemption. The platform does not redeem LTU for fiat currency at any price. There is no exit to cash through the platform.
- No passive yield. Holding LTU generates nothing. Value is only realised through active participation in new contracts or redemption for real services.
- Traceable obligation origin. Every LTU has a recorded origin — which contract or activity created it, who earned it, who holds it. It is not an anonymous bearer instrument. This traceability is what makes the audit trail clean for accountants and for any regulatory inquiry.
None of these are accidental. They are the deliberate design decisions that give LTU its legal character. If any of them were changed — particularly introducing cash redemption or a yield mechanism — the regulatory classification would need to be reassessed immediately.
For your accountant
When presenting LTU transactions to your accountant or tax adviser, communicate these points:
- LTU is a deferred obligation instrument, not cash or a cash equivalent
- Intermediate transfers during production are not supplies for VAT purposes — cite the Voucher Directive (2016/1065) MPV framework and Tolsma (C-16/93) on the direct link requirement
- The tax event is the burn/redemption — the invoice generated at burn is your VAT document and your income recognition document
- Keep records of LTU balances, transfer history, and the fair market value at the time of any burn event — the platform provides exportable transaction history for this purpose
- Always obtain independent advice in your specific jurisdiction, as treatment varies across member states and outside the EU
This article is for informational and educational purposes. It does not constitute legal or tax advice. The legal analysis presented represents the platform's interpretation of applicable frameworks. Individual circumstances vary and you should obtain independent professional advice before relying on any characterisation described here.
Community Endorsement
1 endorsement · 1.0 IA weight
🔏 Attributed IP Proof
SHA-256: b1fb87dde751ff4c1266059c02785d9c43f13c2e1cfa2b7f96516f919899062b
This hash is a cryptographic fingerprint of the original published content, author, and timestamp. It cannot be changed retroactively. Being cited by others generates IA signals for the author.