E-Rechnung empfangen: the half of the mandate that already applies

Since January 1, 2025, every business established in Germany must be able to receive electronic invoices for domestic B2B transactions. The sender needs no consent, and the BMF is blunt about exceptions: none are foreseen, because exceptions would only create boundary problems. Kleinunternehmer, landlords with commercial tenants, associations with taxable activity, all of them are on the receiving hook like everyone else.

The formal bar is deliberately low: per the BMF FAQ, an email inbox is sufficient to receive e-invoices. But receiving is the trivial half. The invoice that lands is an XRechnung XML file, a ZUGFeRD hybrid whose legally decisive content is the embedded data record, or a Peppol delivery, and the duty is only useful to you if that file then gets read, validated, booked, and archived correctly. A dedicated invoice inbox that humans actually monitor is the pragmatic minimum; XML attachments dying unread in a shared mailbox is the standard failure mode.

A receiving process that stands up to auditors and to volume does five things in order:

• One intake channel. Route all invoices, email, portal downloads, Peppol delivery, into a single entry point, so nothing depends on who happened to be in copy.
• Format identification. Detect what arrived: XRechnung XML (UBL or CII syntax), ZUGFeRD hybrid, Peppol BIS Billing, plain PDF, or scan. Hybrids must be unpacked so the process works from the XML, which is the legally authoritative layer per the BMF letter of October 15, 2025.
• Validation. Check structured invoices against EN 16931. The BMF’s error taxonomy is your triage: Formatfehler mean the file is no e-invoice at all, Geschäftsregelfehler mean the data contradicts itself, Inhaltsfehler are process questions no validator catches. Reject or clarify before booking, not after.
• Extraction and booking. Map the Business Terms into the structure your ERP or accounting system needs, with amounts, dates, and parties typed and checked rather than re-keyed.
• Archiving. Retain received invoices for eight years under § 14b UStG, with the structured part preserved unaltered in its original form. Printing the PDF layer and filing paper does not satisfy this; the archiving guide covers the GoBD details.

The transition rules guarantee that your inbox stays heterogeneous for years: paper and PDF remain legal with your consent until the end of 2026, for smaller issuers until the end of 2027, and even after 2028 exempt invoice types, small-value invoices up to €250, passenger tickets, invoices from Kleinunternehmer, keep arriving outside the structured world. Whatever you build must handle XML, hybrids, PDFs, and scans side by side, without running two parallel departments.

Two receiving-side details from the BMF guidance are worth knowing. For recurring invoices from continuing obligations, Dauerrechnungen, an initial e-invoice suffices as long as the underlying terms do not change, so do not expect monthly XML for every rent or hosting contract. And where an e-invoice was legally required but something else arrived, tax practitioners point to input-VAT risk in audits; the BMF’s transition guidance moderates this, and the clean answer is process, not panic: request compliant invoices once your suppliers’ duties apply, and document what you receive.

This is the problem Talonic is built for: every incoming format, XRechnung, ZUGFeRD, Peppol invoices, plain PDFs, and paper scans, resolves into the same schema-validated output, with typed fields, a confidence score, and provenance on every value, processed on EU infrastructure in Germany, ready for your ERP or accounting system. The structured formats are parsed, not OCR’d; the unstructured remainder goes through extraction; and your downstream process sees one consistent shape either way.

If you want to see the field model before wiring anything, the free Peppol e-invoice extractor below reads a real e-invoice in the browser, and the invoice parsing page shows the production path.

Reading about formats is one thing; an accounts-payable inbox full of them is another. Two free resources and one production path:

• Peppol e-Invoice Extractor: pull the seller, buyer, line items, VAT breakdown, and totals out of an e-invoice, free in the browser
• Peppol e-invoice extraction guide: the EN 16931 field model (Business Terms) explained field by field
• Invoice parsing with schema validation: process XRechnung, ZUGFeRD, Peppol invoices, PDFs, and paper scans into one validated output schema, with confidence and provenance on every value