Booking a USDC Payment in DATEV: Step by Step

A USDC payment is valued, booked, and documented in euros like any other business receipt, except the source document isn't a bank, it's a public blockchain transaction. The process breaks down into five clear steps: valuation, booking, VAT treatment, audit trail documentation, batch export. This article walks through each one concretely.

What happens when a USDC payment arrives?

A wallet delivers a transaction: a hash, an amount, a timestamp. No bank statement. No ERP and no bank generates a document for this automatically. Anyone who wants to book the payment correctly has to produce, themselves, three things a bank normally provides: a euro equivalent, a journal entry, and a traceable source document.

Step 1: Value the payment in euro

What matters is the rate at the exact moment of receipt, not the daily rate or a rounded figure applied afterward. For USDC and EURC, a documented reference rate works well, for example the ECB reference rate or an exchange rate with a timestamp, each with its source recorded directly on the entry. What matters isn't which source is chosen, but that the choice is documented and applied consistently over time. An entry with no identifiable rate source is the most common weak point in a later audit.

Step 2: Create the journal entry

The journal entry follows normal double-entry bookkeeping: an increase to an asset account, a revenue posting, and, where applicable, VAT. As 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

1370  Crypto clearing            D   10,960.10
8400  Revenue 19% VAT            C    9,210.17
1776  VAT 19%                    C    1,749.93

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. Net and VAT are rounded so that debit and credit match exactly: the net amount is rounded commercially, and VAT is derived as the difference from the gross. Rounding both figures independently instead produces cent differences that accumulate visibly across a batch.

A note on account number 1370: in practice, the crypto receipt gets booked differently from firm to firm, sometimes through a clearing account as in the example, sometimes through an account for other assets, sometimes through a custom account created for the purpose. There's no single, binding standard for this. The account number in the example was chosen for illustration, not as a fixed recommendation. Anyone using this article for their own bookkeeping should confirm the specific account with their own tax firm before using it in production.

Step 3: Apply VAT correctly

The VAT treatment of the underlying supply of goods or services depends, as with any other payment, on the supply relationship: who the customer is, where they're located, whether it's B2B or B2C, whether reverse charge applies. The payment method doesn't change any of that.

Separately, a distinct rule applies to the payment mechanism 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), the same logic that applies to exchanging Bitcoin for euros. This exemption covers only the payment itself, not the VAT owed on the underlying supply of goods or services, which is still due as normal.

The most common mistake in practice isn't incorrect VAT logic anyway, it's that crypto payments simply don't get processed in time due to time pressure, and the payment ends up incomplete or missing entirely from the books.

Step 4: Document the audit trail (GoBD)

Under the GoBD, an entry must be documented in a traceable, unalterable way. For an on-chain payment, that means concretely: the transaction (hash, sender, timestamp), the rate source with timestamp, the rule applied or the basis for the account mapping, and who approved the entry and when. These four pieces of information together are what a tax auditor will want to see years later. A spreadsheet without this information is nearly impossible to reconstruct after the fact.

Step 5: Export the batch

At the end sits an EXTF batch, the open import format every tax firm already knows. The firm imports the file like any other batch, no new tool and no new process required.

Why this matters more now

Since January 2026, crypto service providers have reported transaction data to Germany's Federal Central Tax Office (DAC8, implemented in Germany as the Kryptowerte-Steuertransparenzgesetz). The first reporting period is calendar year 2026; the first filing is due by 31 July 2027, and automatic exchange between EU tax authorities begins on 30 September 2027. From that point on, the tax office can reconcile a company's own books against externally reported data. A traceable valuation and documentation stops being a nice-to-have and becomes the baseline a reconciliation assumes.

Frequently asked questions

Does every single payment need to be booked immediately on the day it arrives? The rate has to be documented at the moment of receipt. The actual booking can happen as part of regular bookkeeping, the same as with any other document, as long as the rate source and the timestamp are correctly recorded.

Which rate applies for multiple partial 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.

Is USDC treated like a foreign currency for tax purposes, then? Not legally. The BMF's 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 their own category: other economic assets. In practice, the valuation still works similarly to a foreign currency, in euros at the moment of receipt with a documented source. Legal classification and practical valuation are two different things here, and only the former is actually different from a foreign currency. The precise tax classification for a specific case should be confirmed with your own tax firm.

Is a blockchain explorer link enough as a source document? It's one building block, but not a complete source document. Without a documented rate source, rule mapping, and approval, it's missing the context the GoBD requires.