E-Invoicing in the EU and Germany: XRechnung, ZUGFeRD, and What SMEs Actually Need to Know

The most important mental shift is this: under current EU rules, an e-invoice is not simply an invoice sent electronically. It is an invoice issued in a structured, machine-readable format that conforms to the European norm EN 16931, so that a receiving system can process it without a human reading the document. A plain PDF attached to an email, the format most SMEs have used for years, does not by itself meet that definition, because a PDF is a picture of an invoice, not structured data.

In Germany, the two format names you will encounter everywhere are XRechnung and ZUGFeRD. XRechnung is a pure structured-data format, an XML file designed for machine processing, and it has been the standard for invoicing German public-sector customers for several years. ZUGFeRD is a hybrid: a normal-looking PDF with the structured XML embedded inside it, so humans see a familiar document while systems read the data layer. Recent ZUGFeRD profiles are designed to conform to EN 16931 as well. Both approaches can satisfy the structured-invoice requirement; which one you use often depends on what your customers' systems prefer.

Germany has introduced a domestic B2B e-invoicing obligation that began phasing in from 2025. The phase-in started on the receiving side: as of recent regulation, businesses in Germany need to be able to receive structured e-invoices from other domestic businesses, which in the simplest reading means being able to accept and process an EN 16931-conformant invoice rather than refusing it and demanding a PDF. The obligation to actively issue structured e-invoices follows in later stages, with transition periods that have differed by company size and that phase out over the following years.

The exact cutoff dates, revenue thresholds, and remaining transitional allowances are precisely the kind of detail that shifts with implementing guidance, so treat any specific date you read in a blog post, including this one, as orientation rather than a compliance answer. Verify the current phase-in dates and how they apply to your company with your tax advisor or Steuerberater before making decisions. What is safe to say is the direction: structured e-invoicing in domestic German B2B is moving from optional to mandatory over a multi-year window, and the receiving capability came first.

The regulatory driver is VAT. Tax authorities across the EU are moving toward digital reporting regimes in which invoice data flows to the authorities in structured form, with the stated goal of closing VAT fraud gaps. The EU-level initiative in this direction, often discussed under the name ViDA, points toward structured e-invoicing and digital reporting becoming the norm for more transaction types over time. Germany's domestic mandate is broadly understood as groundwork for that direction of travel.

For an SME, the practical takeaway is that this is not a wave to wait out. But it is also worth seeing the upside: a structured invoice is exactly what automation needs. Once invoices leave and arrive as machine-readable data, automated booking, matching, and payment tracking stop being projects and start being defaults. Companies that treat the mandate purely as a compliance chore typically end up buying a converter and changing nothing; companies that treat it as a forcing function often come out with a faster, cleaner invoicing process than they had before.

Start with receiving, since that obligation came first. Confirm that you have a defined channel where structured e-invoices can arrive, typically an email inbox feeding your accounting tool, and that your accounting or ERP software can actually read XRechnung and ZUGFeRD files rather than just storing them as attachments. Most current versions of common accounting tools in the German market handle this, but verify your specific version rather than assuming.

Then look at issuing. Check whether your invoicing tool can generate EN 16931-conformant output, ask your larger customers which format they prefer, and run a test exchange with one friendly customer before you need it under deadline pressure. Finally, take the occasion to clean your master data: structured formats are stricter about required fields such as tax identifiers and addresses than a free-form PDF ever was, and incomplete master data is the most common source of rejected e-invoices in practice. None of this is legal or tax advice; it is an orientation for the conversation you should have with your tax advisor, who can confirm the current requirements for your specific situation.