My German Accountant Just Emailed Me About XRechnung. I Have Never Felt More European.

The email arrived on a Tuesday. Subject line: "XRechnung – bitte lesen". My accountant, Horst, sends me maybe three emails a year. This was one of them.

I opened it expecting something about my tax return. Instead I got four paragraphs, a link to a BMF document, and the phrase "ab Januar 2025 empfangspflichtig" which Google Translate told me meant "receiving mandatory from January 2025."

I stared at this for approximately 45 seconds and then did what any reasonable adult does when confronted with German financial regulation: I made a coffee and opened Reddit.

Reddit was not helpful. The e-invoicing subreddit exists but it is mostly Germans discussing specific namespace issues in UBL 2.1 syntax, which is its own kind of horror. I ended up on a Wikipedia rabbit hole that went:

- XRechnung → EN 16931 → CEN/TC 434 → European Committee for Standardisation → Vienna Agreement → wait why am I reading about the Vienna Agreement

Eventually I found an article (possibly this one, ironically) that explained it in normal human words: Germany now requires that all businesses be able to receive structured electronic invoices. Not paper. Not PDF. An XML file with specific fields in specific positions, validated against a published standard.

Here is the embarrassing part: basically nothing. My accountant already uses DATEV. DATEV supports XRechnung. My clients who invoice me are mostly small studios and agencies — they use Lexware or sevDesk — they also support it. The whole infrastructure was already there. I just needed to know it existed.

I did download one XRechnung XML file out of curiosity. I opened it in a text editor. I read the line "380" and thought: 380. Is that the right code? Who decided 380? I spent 20 minutes learning that 380 is the UN/EDIFACT standard code for a commercial invoice, which dates back to the 1980s, which means this piece of XML I received about my February graphic design work is carrying the ghost of Cold War-era trade documentation standards.

I find this genuinely delightful.

The point of all this — the XRechnung, the ZUGFeRD, the EN 16931, the whole apparatus — is that when both sides of a transaction send and receive structured data, the VAT gap (the difference between VAT owed and VAT actually collected) shrinks. Italy proved it. After their FatturaPA mandate launched in 2019, the Italian government recovered billions in previously evaded VAT. Not because anyone was being audited harder. Just because the data was there, automatically, in a format a computer could read.

Horst didn't mention any of this in his email. He just said "empfangspflichtig." But I think about it sometimes when I open an XML invoice in a text editor at 11pm for no reason.

If you are a freelancer in Germany: 1. Your accounting software almost certainly already handles this 2. If you don't have accounting software, you need it anyway (GoBD compliance is separate and also a thing) 3. The XML files are actually readable and kind of interesting if you like Cold War trade documentation history