Practical Germany E-Rechnung exceptions checklist for SMEs: low-value invoices, tickets, B2B scope, ZUGFeRD/XRechnung, software rules and audit evidence.
Germany’s E-Rechnung rules are usually discussed as if every invoice has the same workflow. In practice, finance teams also handle small receipts, travel tickets, B2C sales, foreign customers, public-sector invoices and edge cases. If these are not classified early, software demos look successful but month-end work stays manual.
Start with invoices for transactions between domestic entrepreneurs. The BMF FAQ describes the mandatory E-Rechnung rules for domestic B2B transactions from 2025 with transition rules for issuing. Treat B2B, B2C, B2G, intra-EU, export, self-billing, credit notes and employee expenses as separate lanes.
German guidance discusses exceptions such as small-value invoices and certain travel tickets. Do not turn that into a blanket exemption. Decide who checks the amount, document type, customer status and VAT treatment, then confirm with official guidance or your adviser before excluding a flow from structured processing.
Ask whether the tool can tag invoice scope, create and receive ZUGFeRD and XRechnung, display XML safely, keep the original structured file, archive small receipts separately, route exceptions to accounting and report which invoices were excluded from E-Rechnung handling.
Use one normal German B2B invoice, one B2C invoice, one low-value receipt, one travel ticket, one public-sector XRechnung, one credit note, one foreign customer invoice and one incoming supplier XML. The provider should show classification, validation, archive and accountant export for each scenario.
Do not assume every PDF is still acceptable because transition rules exist. Do not let sales choose the format case by case without accounting rules. Do not archive only the visual PDF if the structured XML is the invoice evidence. Do not ignore incoming supplier E-Rechnungen.
Prefer software that makes scope visible, explains validation errors, supports EN 16931 formats, keeps audit evidence, provides DATEV or accounting export, separates exceptions cleanly and gives accountants access to the original invoice data.
Build a one-page E-Rechnung scope register. List invoice type, customer type, likely format, exception reason, software owner, archive location and source used. Review it with accounting before buying or reconfiguring a tool.
List domestic B2B, B2C, B2G, cross-border, credit note and expense flows
Mark possible low-value invoice and ticket exceptions
Confirm ZUGFeRD/XRechnung support for normal B2B invoices
Keep original XML or hybrid file where structured invoice data applies
Define who approves exception classification
Test incoming supplier E-Rechnungen, not only outgoing invoices
Document official source date and adviser review
Compare software on archive, validation, export and exception reporting
German guidance refers to exceptions for certain small-value invoices, but the practical answer depends on amount, document type, parties and VAT treatment. Do not rely on a generic exemption: classify the flow and confirm against BMF guidance or a qualified adviser.
Certain tickets can have special treatment, but finance teams should still document how travel, expense and supplier documents are stored, read and booked. A ticket exception is not a reason to leave all supplier invoices unmanaged.
For affected E-Rechnung flows, a normal PDF is not the same as structured invoice data. ZUGFeRD and XRechnung are the practical format terms to test with software and customers.
Usually no. Even if some documents are outside the structured invoice path, normal domestic B2B invoices, incoming supplier invoices, validation and archive evidence still need a reliable process.
Yes. A scope register lets you compare providers using the same cases and avoids buying a tool that handles perfect invoices but not real operational edge cases.
Ask them to review B2B scope, low-value and ticket handling, credit notes, incoming invoices, archive evidence, DATEV or accounting export and how exceptions are documented.
Public-sector/B2G invoicing can have XRechnung-specific requirements and should be separated from general B2B and B2C flows in your register.
No. This is practical readiness guidance. Confirm scope, VAT treatment and retention rules with official sources and qualified advisers.
Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.
We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.
E-Invoice Finder
