Stablecoin Accounting in Germany: The 2026 Guide
More and more companies receive payments in USDC or EURC: from international customers, from crypto-native business partners, and increasingly in ordinary B2B trade. For accounting purposes such a payment is not a special case with rules of its own. It is a business receipt like any other: it has to be valued, booked, classified for VAT, and documented. The difference is not whether but how: the source document is not a bank statement but a public blockchain transaction, and a few intermediate steps a bank normally provides have to be produced by the company itself.
This guide walks the whole path: from legal classification through valuation, journal entry and VAT to the GoBD audit trail and the handoff to your tax firm. It is written for companies that keep German books, whatever country the group sits in, and for the firms that keep those books.
1. Legal classification: what is a stablecoin, for accounting purposes?
For tax purposes the question has been settled since March 2025. The BMF memorandum of 6 March 2025 (IV C 1 - S 2256/00042/064/043), which supersedes the version of 10 May 2022, explicitly does not classify crypto-assets as foreign currency but as a category of their own: other economic assets. That holds for stablecoins too, even though they are economically pegged to a currency. Legal classification and practical valuation are two different things here: valuation still works much like it would for a foreign currency, in euros at the moment of receipt with a documented source. It is only the legal consequences of a foreign-currency classification that do not apply.
On the regulatory side, much has moved in parallel: under MiCA, stablecoins like USDC and EURC are regulated as e-money tokens, with authorised issuers and reserve requirements. As of early 2026, seven euro stablecoins are authorised as e-money tokens. The point that matters for accounting: MiCA authorisation is supervisory law. It changes nothing about the tax classification as an other economic asset.
2. Valuation: the euro value at the moment of receipt
What matters is the rate at the moment of receipt, not the daily closing rate and not a figure rounded after the fact. A documented reference rate works well as the source, for example the ECB reference rate or an exchange rate with a timestamp, each recorded with its source directly on the entry. What matters is not which source you choose, but that the choice is documented and applied consistently over time.
An example using an actual rate:
Receipt: 12,500.00 USDC
Rate: 0.876808 EUR/USDC
Source: ECB reference rate 14.07.2026 (1 EUR = 1.1405 USD), timestamp 09:41
Euro equivalent: 10,960.10 EUR
The amounts do not come out round, and that is normal: a real reference rate does not produce round numbers. An example that does usually reveals a rate someone picked rather than looked up.
The rate source belongs on the entry even for EURC, a euro stablecoin. The value sits practically at one to one, but "practically one to one" is not a documentation entry. What gets recorded is the source and the timestamp, even when the result is unspectacular.
3. The journal entry
Booking follows normal double-entry bookkeeping: an increase to an asset account, a revenue posting, and, where applicable, VAT. In SKR03 it can look like this:
1370 Crypto clearing D 10,960.10
8400 Revenue 19% VAT C 9,210.17
1776 VAT 19% C 1,749.93
Net and VAT are rounded so that debit and credit match exactly: the net amount commercially, VAT as the difference from the gross. Rounding both figures independently produces cent differences that accumulate visibly across a batch.
Two notes on the choice of accounts. First, there is no single, binding standard for where the crypto receipt goes: in practice it is booked sometimes through a clearing account, sometimes through an account for other assets, sometimes through a custom account created for the purpose. The account number in the example is for illustration, not a fixed recommendation. Second, the same logic applies in SKR04 with the corresponding accounts; the concrete mapping in either chart of accounts should be confirmed with your own tax firm before it is used in production.
The step-by-step walkthrough with all the details is in Booking a USDC payment in DATEV.
4. VAT: two levels that keep getting mixed up
The VAT assessment has two separate levels, and most of the confusion comes from mixing them.
Level one is the underlying supply of goods or services. It follows the same rules as with any other payment: who the customer is, where they sit, whether it is B2B or B2C, whether reverse charge applies. The payment method changes none of that. A software service to a German B2B customer remains a software service to a German B2B customer, whether the money arrives by bank transfer or in USDC.
Level two is the payment transaction itself. If the stablecoin payment is accepted by both sides purely as a means of payment and serves no other purpose, that exchange or payment transaction is itself exempt from VAT (ECJ, Case C-264/14 "Hedqvist", 22 October 2015, Art. 135(1)(e) of the VAT Directive). It is the same logic that applies to exchanging Bitcoin for euros. The exemption covers only the payment itself, not the VAT on the underlying supply, which is due as normal.
The most common mistake in practice is not bad tax logic, though. It is more banal: under time pressure, the classification simply never happens, and the payment ends up incomplete or missing from the books entirely.
5. Fees, partial payments, held balances
Network fees. Whoever initiates transactions pays network fees. They are business expenses in principle; the concrete account mapping (for example as ancillary costs of payment transactions) belongs, like the account choice generally, in the conversation with your tax firm.
Multiple payments on the same day. Each receipt is valued individually at its own moment in time, not at an averaged daily rate, unless your own tax firm explicitly specifies a different, documented method.
Balances held across the balance sheet date. A company that holds stablecoins rather than converting them promptly faces a valuation question at the balance sheet date: acquisition cost, possible write-downs, the handling of rate movements. Because the BMF explicitly does not classify crypto-assets as foreign currency, the familiar rules of foreign-currency translation cannot simply be carried over. This point belongs squarely in the conversation with your own tax firm before year-end facts are created. For companies that convert incoming stablecoin payments promptly, the question does not arise with this sharpness.
6. GoBD: the audit trail behind every entry
Under the GoBD, an entry must be documented in a traceable, unalterable way. For an on-chain payment that means four pieces of information have to come together:
- The transaction: hash, sender, timestamp.
- The rate source: which rate, from where, with what timestamp.
- The mapping: by what rule, or on what basis, the account and the tax rate were chosen.
- The approval: who approved the entry, and when.
These four together are what a tax auditor will want to see years later. A blockchain explorer link covers only the first. A spreadsheet missing the other three is nearly impossible to reconstruct after the fact, and exactly that reconstruction is the most expensive part of many crypto engagements.
Unalterability also means: later corrections are recorded as new, marked entries, not by silently overwriting the old ones. That is no different for crypto payments than for anything else, but it surfaces faster there, because the blockchain side of the data can be independently checked by anyone at any time.
7. DAC8: from 2027, the tax office already has the data
Since 1 January 2026, crypto service providers have reported their customers' transaction data to Germany's Federal Central Tax Office. The basis is the EU directive DAC8, implemented in Germany as the Kryptowerte-Steuertransparenzgesetz. The key dates:
- The first reporting period is calendar year 2026.
- Existing customers must provide their service providers with a tax self-disclosure by 1 January 2027.
- The first filing with the Federal Central Tax Office is due by 31 July 2027.
- Automatic exchange between EU tax authorities begins on 30 September 2027.
- Violations can carry fines of up to 50,000 euros.
For accounting, that means one simple but far-reaching shift: from autumn 2027, the tax office can reconcile a company's own books against externally reported data. Traceable valuation and documentation stops being good practice and becomes the baseline such a reconciliation assumes. A company accepting stablecoin payments today sensibly builds the audit trail now, not retroactively in 2027.
8. The handoff to your tax firm
At the end of the month or quarter, your tax firm does not need wallet exports or explorer links. It needs what it gets from every other client: a posting batch. The open EXTF format is the established route; the firm imports the file like any other batch, with no new tool and no new process. Alongside it go the reconciliation report (totals per account, open items) and, on request, the audit trail for any individual entry.
Organising this handoff cleanly removes the basis for the most common objection tax firms raise against crypto engagements. The objection is rarely "the tax treatment is unclear". It is almost always "the data arrives unusable".
Frequently asked questions
Is a stablecoin a foreign currency for tax purposes? No. The BMF memorandum of 6 March 2025 classifies crypto-assets, stablecoins included, as other economic assets. Valuation runs much like it would for a foreign currency, but the legal classification is different. The classification in a specific case belongs with your own tax firm.
Does a rate need to be documented for EURC as well? Yes. The value sits practically at one to one with the euro, but the source document needs a source and a timestamp, not an assumption. For a euro stablecoin the documentation is quickly done, but it does not fall away.
Does a stablecoin's MiCA authorisation change anything for the books? No. MiCA is supervisory law and governs issuers and reserves. The tax classification as an other economic asset and the GoBD requirements are untouched by it.
What about stablecoins that are held rather than converted? Then a valuation question arises at the balance sheet date, and it cannot simply be answered with foreign-currency translation rules, precisely because no foreign currency exists for tax purposes. This case belongs in the conversation with your tax firm before the year-end close.
Is a blockchain explorer link enough as a source document? It is one building block, but not a complete source document. Without a documented rate source, mapping basis, and approval, it is missing the context the GoBD requires.
If your problem is not the company's books but a bank asking where your own crypto proceeds came from: the free source-of-funds check reviews your history entirely in your browser.
This guide is no substitute for tax advice in a specific case. Account choice, VAT classification, and the treatment of held balances belong in the conversation with your own tax firm.