Germany Crypto Tax [2026]: Up to 45% FIFO Per Wallet

Germany’s crypto tax rulebook has a quirk that trips up even experienced filers: the tax office does not look at a holder’s entire crypto portfolio as one pool. It looks at each wallet, exchange account, or custody address on its own, running a separate first in, first out calculation for every single one. That wallet by wallet version of FIFO, confirmed again this week by multiple German tax trackers including CryptoTicker, is now the center of renewed attention as more investors juggle coins across several exchanges, hardware wallets, and DeFi addresses heading into the 2026 filing season.

The rule itself is not new. It traces back to guidance from Germany’s Bundesministerium der Finanzen (BMF), the federal finance ministry, issued on 10 May 2022 and updated on 6 March 2025. What has changed is how visible the issue has become as crypto tax software vendors, compliance firms, and financial advisers keep running into the same question from clients: why does moving coins between my own wallets not reset the clock, but selling from the wrong wallet still trigger a bigger tax bill than expected?

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech once in the Google app and our stories appear in your news suggestions.

Add Now

What Germany’s Wallet by Wallet FIFO Rule Actually Says

FIFO stands for first in, first out. Under this method, the crypto units a taxpayer acquired earliest are treated as the units sold first whenever a disposal happens. That sounds simple until multiple wallets enter the picture. German guidance, cited in detail by Waltio’s compliance help center, specifies that FIFO is applied per wallet or per exchange account, not across a person’s total holdings. Coins sitting in a Coinbase account are matched against each other using FIFO independently of coins sitting in a Ledger hardware wallet or a MetaMask address.

That distinction matters enormously for anyone who spreads holdings across several platforms, which describes most active crypto users by 2026. A trader who bought Bitcoin on one exchange in 2021 and bought more on a second exchange in 2024 cannot blend those two purchase batches into a single FIFO queue. Each account keeps its own first in, first out line, and the tax consequence of selling from account A can look completely different from selling the same asset, bought around the same time, from account B.

The German Federal Ministry of Finance states the position directly in its own published guidance: “the analysis is on a wallet-by-wallet basis,” according to the Bundesministerium der Finanzen’s own circular. That single sentence underpins how every German crypto tax calculation has to be structured, and it is the detail that catches out newcomers who assume their tax software will simply average everything together.

Why the Rule Sits Inside Section 23 EStG

Germany taxes private crypto disposals under Section 23 of the Income Tax Act, known as Section 23 EStG, which governs gains from the sale of privately held assets outside a business context. FIFO becomes the default matching method under this provision whenever individual coins or tokens cannot be clearly traced to one specific purchase, a near-universal situation given how fungible crypto units are once they sit in the same address.

Oxford University Press, publisher of a widely cited academic guide on crypto taxation, frames the mechanics plainly: “for valuation purposes, the same result may be achieved by applying the so-called first-in, first-out method (FiFo),” according to its Taxation of Cryptocurrencies guidance. The same publication goes further on the wallet question, noting that “the analysis is conducted on a wallet-by-wallet basis, and the selected method must be retained within each wallet until all units of the same trade name have been fully sold.”

That consistency requirement is easy to overlook. It is not enough to apply FIFO once. Within a given wallet, the taxpayer has to stick with FIFO (or whichever method was validly chosen) until every unit of that specific asset in that specific wallet has been disposed of. Switching methods partway through, or mixing calculation approaches across coins of the same type sitting in the same address, is not permitted under the ministry’s own guidance.

The BMF Guidance Timeline: 2022 to 2025

Two dates anchor this story. The first BMF circular addressing crypto asset tax treatment, including the wallet separation principle, dates to 10 May 2022. Germany’s finance ministry revisited and updated that guidance on 6 March 2025, refining individual points without reversing the core wallet by wallet logic. Both circulars are the documents compliance platforms point back to whenever a client asks why their multi-exchange portfolio cannot simply be pooled into one FIFO ledger.

Date	Source	Key Point
10 May 2022	Bundesministerium der Finanzen	First detailed circular on crypto asset tax treatment under Section 23 EStG, establishing wallet level matching
6 March 2025	Bundesministerium der Finanzen	Updated circular refining crypto guidance while keeping the wallet-by-wallet FIFO default intact
2026 filing season	CryptoTicker, Waltio, KoinX, Blockpit, CoinTracking	Renewed attention from tax trackers and software vendors as multi-wallet crypto activity grows

What stands out is the gap between when this guidance was issued and when the broader crypto-holding public actually started grappling with its implications. Four years passed between the original 2022 circular and the surge of search interest and tax-software commentary seen this week. That lag reflects how much more complex the average German crypto holder’s setup has become, from simple single-exchange accounts around 2021 to sprawling combinations of centralized exchanges, self-custody wallets, and DeFi protocols by 2026.

Wallet Transfers Are Not Disposals, With One Big Exception

One piece of the rule works in taxpayers’ favor. Moving crypto from one wallet a person owns to another wallet that same person owns does not count as a disposal under German guidance. The transferred units keep their original acquisition date and their original cost basis when they land in the new wallet. A coin bought in 2023 and moved from an exchange to a hardware wallet in 2026 still carries its 2023 purchase date for holding period purposes.

That protection only applies to transfers where ownership never changes. The moment coins move to an account controlled by someone else, even briefly through certain wrapping, lending, or liquidity pool mechanics, the disposal question reopens. Tax trackers covering this space have repeatedly flagged that the line between a benign internal transfer and a taxable event is exactly where most filing mistakes happen.

KPMG International’s advisory notes on German crypto tax treatment state plainly how strict the separation really is: “a strict wallet-based approach applies, i.e., crypto assets from different wallets must not be mixed in order to determine a capital gain/loss for tax purposes,” according to KPMG’s flash alert on the subject. That single line explains why a taxpayer cannot simply average cost basis across every platform they use and call it close enough.

When Individual Matching Beats the FIFO Default

FIFO is a fallback, not a mandate. If a taxpayer can specifically identify and document which exact units were sold, that individual allocation takes precedence over the general FIFO assumption. In practice this is rare for most retail holders, since it requires detailed, unit-level record keeping that few people maintain manually. It becomes more realistic for holders using dedicated crypto tax software that logs every transaction with timestamps precise enough to support specific identification.

This is also where the wallet by wallet structure starts to intersect directly with the software tools people use to file. A platform that tracks transactions at the wallet level, rather than lumping everything into one undifferentiated ledger, is the only kind of tool that can actually support either path: a clean FIFO calculation per wallet, or a documented specific identification claim when the records allow it.

How Crypto Tax Software Handles Wallet Separation

The wallet by wallet requirement has shaped how the main crypto tax calculation platforms build their German-market products. Waltio states outright that it “uses FIFO per wallet,” tracking each wallet or exchange separately and preserving acquisition dates across internal transfers, according to its own help documentation. Blockpit publishes a dedicated German-language guide to the Verbrauchsfolgeverfahren, the consumption sequence method, walking through exactly how FIFO and the per-wallet rule interact under current BMF guidance. CoinTracking, KoinX, and CoinTracker all describe similar wallet-isolated FIFO engines in their own German tax guides.

Platform	Wallet-by-Wallet FIFO Support	Internal Transfer Handling	Focus
Waltio	FIFO applied per wallet or exchange, tracked separately	Transferred units keep original acquisition date	German and French compliance guidance
Blockpit	Documents Verbrauchsfolgeverfahren (consumption sequence) under BMF rules	Covered in dedicated German-language guide	German-market tax reporting
CoinTracking	Describes FIFO as the practical default, applied per wallet	Addressed in holding period reform coverage	German holding period and reform tracking
KoinX	FIFO as preferred method under Section 23 EStG	Covered in German tax guide	Section 23 EStG compliance
CoinTracker	Lists wallet-by-wallet FIFO as a defined term in its glossary	Covered in Germany tax guide	Multi-jurisdiction crypto tax reporting

For developers and engineering teams building or evaluating compliance tooling, the practical takeaway is architectural. A crypto tax engine that stores transactions in one flat, cross-wallet ledger cannot correctly reproduce German FIFO outcomes. The data model has to key every lot to its originating wallet or account identifier, preserve that identifier through internal transfers, and run FIFO matching scoped to that identifier alone. A simplified version of that logic looks like this:

for wallet in wallets:
    lots = sorted(wallet.acquisitions, key=lambda l: l.date)
    for disposal in wallet.disposals:
        remaining = disposal.quantity
        while remaining > 0 and lots:
            oldest = lots[0]
            matched = min(oldest.quantity, remaining)
            disposal.cost_basis += matched * oldest.unit_cost
            oldest.quantity -= matched
            remaining -= matched
            if oldest.quantity == 0:
                lots.pop(0)

Running that loop once per wallet, rather than once across a merged transaction history, is the entire difference between a compliant calculation and a wrong one under German guidance.

Historical Context: How Germany Got Here

Germany has treated privately held crypto under Section 23 EStG for years, applying the same general framework used for other private asset disposals. What made crypto different, and eventually required dedicated guidance, was the sheer scale of fragmentation in how people hold it. A stock portfolio typically sits with one or two brokers. A crypto portfolio by 2026 might span a centralized exchange, a self-custody hardware wallet, a software wallet for daily use, and several DeFi protocol positions, each technically a separate address with its own transaction history.

The 2022 circular was the ministry’s attempt to give that fragmented reality a consistent rulebook. The 2025 update refined specific points without changing the underlying structure. CoinTracking’s own coverage of the broader holding period debate, tracked in its German Crypto Holding Period Reform 2026 status report, notes that FIFO determines both whether a sale falls within Germany’s holding period and the specific size of any taxable gain, tying the wallet separation question directly to one of the most consequential variables in a German crypto tax bill.

That holding period debate is still unresolved heading into 2026, according to CoinTracking’s tracking of the reform conversation, which means the wallet by wallet FIFO mechanics described here remain the operative rule for now, even as policymakers discuss whether the broader framework around it should change.

Market Impact for German Crypto Holders and Platforms

The practical fallout from this rule shows up in three places: individual tax bills, the design priorities of compliance software, and the behavior incentives it creates around where people choose to hold assets. On tax bills, the wallet by wallet structure means two investors with identical total holdings and identical total purchase history can owe meaningfully different amounts depending purely on which wallet they happened to sell from. Selling the oldest coins from a wallet that happens to hold newer, higher-cost-basis lots at the front of its FIFO queue produces a different gain than selling from a wallet where the oldest lots are genuinely old.

On compliance software, the rule effectively forces every serious German-market crypto tax product to build wallet-aware data models from day one, rather than retrofitting that structure later. That has become a competitive differentiator among platforms like Waltio, Blockpit, KoinX, CoinTracking, and CoinTracker, all of which publish detailed German-specific documentation precisely because generic, pooled-portfolio tax engines built for other markets do not transfer cleanly to German requirements.

On behavior, the rule creates a quiet incentive to consolidate rather than fragment holdings, since fewer wallets mean fewer separate FIFO queues to track and fewer chances to accidentally trigger a larger gain by selling from the wrong address. That runs somewhat against the broader self-custody trend encouraged by security-conscious investors in the wake of incidents like the hardware wallet implant case that spread across Europe and the earlier 86 million dollar Ledger hack that prompted warnings from exchange executives, both of which pushed some holders toward spreading assets across more wallets, not fewer, for security reasons.

How Germany’s Approach Compares to Other Tax Methods

FIFO is only one of several cost basis methods used around the world for crypto taxation, alongside approaches like specific identification and average cost. What sets the German approach apart is not the choice of FIFO itself, which is common, but the strictness of the per-wallet scoping. KPMG’s international guidance on the subject makes clear that German authorities expect crypto assets from different wallets not to be mixed when calculating gains or losses, a stricter line than some other cost-basis frameworks draw.

That strictness has real consequences for anyone whose crypto activity spans jurisdictions, including users of global exchanges and cross-border DeFi protocols, since a method that works cleanly for a pooled-portfolio tax regime elsewhere may need a full re-architecture to satisfy German wallet-level requirements. It is also why German-focused tax software vendors treat the wallet separation rule as a headline feature rather than a footnote, actively marketing their per-wallet FIFO engines as a point of differentiation.

Reporting and Audit Exposure for Multi-Wallet Holders

Crypto exchanges report gross transaction amounts, not calculated profit, to German tax authorities, according to CryptoTicker’s coverage of exchange reporting obligations. That distinction matters because it leaves the burden of correctly applying wallet by wallet FIFO squarely on the taxpayer rather than the exchange. If a filer reports gains using a pooled, cross-wallet calculation instead of the required per-wallet approach, the gap between what the exchange reported and what the taxpayer calculated can become a flag for further review.

CryptoTicker’s guidance stresses that the tax administration expects a method applied uniformly, both per wallet and consistently across tax years, reinforcing that this is not a one-time calculation choice but an ongoing discipline. Holders who switch tax software providers, or who manually track some wallets while letting software handle others, risk breaking that consistency requirement without realizing it.

This growing compliance complexity sits alongside a broader wave of scrutiny on how crypto-adjacent infrastructure gets secured and regulated across Europe, from the European Union’s expanding sanctions regime targeting technology supply chains to ongoing debate about how exchanges and custodians should be supervised as crypto activity scales. Multi-wallet tax complexity is one more layer in that same push toward tighter, more granular oversight of how digital assets move.

What Software Developers Building Tax Tools Should Prioritize

For engineering teams working on crypto accounting products, Germany’s rule is a useful stress test of data architecture. A system needs to tag every acquisition and disposal event with a durable wallet or account identifier, preserve that identifier through internal transfers without treating them as disposals, and support an audit trail precise enough to justify a specific identification claim when a user’s records allow one. Teams that build a single global FIFO queue first and try to bolt on wallet segmentation later tend to discover the retrofit touches nearly every part of the cost basis engine.

It also means international products entering the German market cannot simply localize the user interface and tax forms. The underlying calculation logic has to change. That is a large part of why the platforms named earlier Maintain dedicated German guides rather than translating a single global tax explainer, and it is a pattern likely to repeat as more jurisdictions formalize their own wallet-level or account-level matching rules. For a broader look at how developer and compliance tooling is evolving across the software category this year, the wallet separation requirement is a small but telling case study in domain-specific engineering.

Password and key management tooling intersects here too. Holders juggling several wallets for tax-isolation or security reasons increasingly lean on dedicated credential managers to keep track of seed phrases and exchange logins without duplicating risk, a pattern covered in detail in a self-hosted password manager setup guide and in broader comparisons of the best password manager options for 2026.

Predictions: Where This Rule Goes From Here

Crypto tax software vendors will keep expanding dedicated German-market documentation and wallet-isolated calculation engines as the user base of multi-wallet holders grows through 2026 and into 2027.
The unresolved debate over Germany’s one-year holding period, actively tracked by compliance platforms like CoinTracking, will likely surface again in policy discussions before the rule itself changes in any formal way.
More investors who previously spread assets across many wallets for security reasons, including in response to hardware wallet incidents across Europe, will face growing pressure to consolidate holdings or adopt more sophisticated per-wallet tracking tools.
Specific identification claims, currently rare among retail filers, will likely become more common as tax software improves transaction-level record keeping precise enough to support them.
Expect continued scrutiny of the gap between gross exchange reporting and taxpayer-calculated gains, as German authorities lean on that mismatch as an audit signal for incorrect wallet-by-wallet FIFO application.

The Bottom Line for German Crypto Filers

Germany’s wallet by wallet FIFO rule is not a new policy shock. It is a years-old piece of BMF guidance that is only now getting the attention it deserves as the average crypto holder’s setup has grown too complex to ignore it safely. The core mechanics are straightforward once understood: FIFO applies inside each wallet independently, internal transfers between a person’s own wallets preserve cost basis and acquisition date, and specific identification can override FIFO only when the records genuinely support it.

What makes the rule consequential is scale, not novelty. Anyone holding crypto across more than one wallet, exchange, or custody arrangement, which by 2026 describes the large majority of active holders, needs tooling or discipline precise enough to track FIFO separately for every single one of those accounts. Getting that structure wrong does not just risk an incorrect tax bill. It risks a mismatch between what an exchange reports and what a taxpayer claims, exactly the kind of gap that invites a closer look.

Frequently Asked Questions

What does FIFO mean for German crypto taxes?
FIFO stands for first in, first out. It means the crypto units a taxpayer acquired earliest are treated as the units sold first whenever a disposal occurs, under Section 23 EStG.

Why is FIFO applied per wallet instead of across a whole portfolio in Germany?
German Federal Ministry of Finance guidance specifies that the FIFO analysis is conducted on a wallet-by-wallet basis, meaning each wallet or exchange account runs its own independent FIFO calculation rather than being pooled with holdings elsewhere.

Does moving crypto between my own wallets trigger a taxable event in Germany?
Generally no. Transfers between a taxpayer’s own wallets are not treated as disposals, and the transferred units keep their original acquisition date and cost basis.

When does German guidance on this rule date from?
The core guidance comes from Bundesministerium der Finanzen circulars dated 10 May 2022 and updated 6 March 2025.

Can I choose a method other than FIFO for my German crypto taxes?
If specific units can be individually matched to a specific acquisition through detailed records, that individual allocation takes precedence over the general FIFO assumption. Otherwise, FIFO applies by default.

Do crypto exchanges calculate my taxable gain for me in Germany?
No. Exchanges report gross transaction amounts to tax authorities, not calculated profit, which means the burden of correctly applying wallet by wallet FIFO falls on the taxpayer.

Which crypto tax software supports Germany’s wallet by wallet FIFO rule?
Platforms including Waltio, Blockpit, CoinTracking, KoinX, and CoinTracker all publish dedicated German guidance describing wallet-isolated FIFO calculation engines built around Section 23 EStG.

What happens if I apply FIFO across my whole portfolio instead of per wallet by mistake?
It risks an incorrect tax filing that does not match the gross amounts exchanges report to German authorities, creating a discrepancy that can draw further review.

Germany Crypto FIFO Rule: 5 Tax Tools Track Wallets [2026]