Last updated at
September 24, 2026
Learn more about this by booking a demo call with us. Our team will guide you through the process and answer any questions you may have.
Book NowGermany’s mandatory e-invoicing requirement applies mainly to qualifying domestic B2B transactions. Certain transactions are exempt or outside the mandate, while transition provisions temporarily permit other invoice formats for transactions that remain in scope.
Germany’s e-invoicing exemptions apply to specific transaction types and invoice categories. The main exceptions relevant to B2B businesses are VAT-exempt transactions and invoices up to €250.
transactions exempt from VAT under §4 Nos. 8–29 UStG fall outside the mandatory e-invoice requirement. These include financial services, insurance-related services and property rentals.
The exemption must apply to the underlying transaction. It should not be determined solely from the status of the supplier or customer.
Invoices with a total amount of up to €250 may be issued as a small-value invoice under §33 UStDV.
These invoices do not have to meet the full e-invoice requirements under §14 UStG.
The €250 threshold applies to the total invoice amount, including VAT. It is not limited to the taxable portion of the invoice.
Invoice categories are also outside the mandatory e-invoice requirement under specific provisions of German VAT law:
The domestic B2B mandate depends on the status and establishment of the parties and the nature of the transaction.
Germany’s domestic B2B e-invoice mandate does not apply to transactions that do not meet the domestic establishment conditions under §14 UStG.
A foreign supplier or customer may therefore place a transaction outside the German domestic mandate. Other VAT and cross-border invoicing requirements may still apply.
The establishment involved in the transaction matters. A business may have both German and foreign establishments. The e-invoice assessment should therefore consider which establishment is making or receiving the supply.
Group-level classification is not sufficient when different legal entities or establishments operate separate billing flows.
Supplies to legal entities that are not entrepreneurs fall outside the domestic B2B e-invoice requirement.
This category is distinct from B2B transactions between taxable businesses. The customer’s status must therefore be captured in the invoicing process.
Some transactions may appear unusual from a VAT perspective but remain within the e-invoicing requirements.
Reverse-Charge Transactions
Reverse-charge treatment does not itself exempt a transaction from e-invoicing. A domestic B2B transaction subject to §13b UStG can still require an e-invoice when the other scope conditions are met.
The invoice must include the applicable VAT information and reverse-charge indication.
The e-invoice requirement can also apply to transactions subject to special VAT schemes. Special VAT treatment does not, by itself, create an exception to the e-invoicing requirement.
| VAT treatment | Provision | Treatment |
| Agricultural and forestry scheme | §24 UStG | Average-rate VAT scheme |
| Travel services | §25 UStG | Margin-based travel scheme |
| Margin taxation | §25a UStG | VAT is calculated on the resale margin |
An invoice can contain both taxable and VAT-exempt items. The presence of an exempt item does not automatically make the entire invoice exempt from e-invoicing.
Where the transaction falls within the mandatory scope, the structured invoice must contain the required VAT information for the relevant items.
E-invoicing exceptions affect more than the final invoice format. They determine how ERP and billing systems classify, generate, validate and route invoices.
The invoicing system should determine the applicable invoice format based on the transaction’s legal status:
Where an e-invoice is mandatory, the invoice must meet the requirements of §14 UStG.
The structured invoice data must contain the required VAT information. Formats such as XRechnung and compliant ZUGFeRD profiles can satisfy the structured format requirement where they meet the applicable specifications.
Large organisations should implement exception logic at the transaction level.
| Data point | Purpose |
| Legal entity | Determines the applicable invoicing obligation |
| Establishment | Identifies the establishment involved in the supply |
| Customer status | Determines whether the recipient falls within the relevant scope |
| Transaction type | Identifies the nature of the supply |
| VAT treatment | Determines whether an exemption or special treatment applies |
| Invoice amount | Identifies invoices up to €250 |
| Transaction date | Determines applicable transition provisions |
| Invoice format | Controls structured or other permitted invoice output |
Exception handling should occur before invoice generation or transmission. The system should validate the transaction classification first. It can then select the appropriate format and delivery channel.
This avoids treating every invoice as an e-invoice or, conversely, sending a non-structured invoice for a transaction that requires one.
The classification decision should be traceable. Large businesses should retain the relevant transaction data, VAT classification and invoice-format decision within their existing finance controls.
This is particularly important where different legal entities, ERP systems or billing platforms apply different exception scenarios.
Large organisations should apply exemptions through controlled transaction classification rather than manual invoice-by-invoice decisions.
Identify the supplier and customer legal entities involved in the transaction. Do not apply an exception across an entire corporate group without checking the individual entities.
Determine which establishment is involved in the transaction. This is relevant where a business operates through multiple German and foreign establishments.
Identify the underlying supply and its VAT treatment . The exception should relate to the transaction itself, not simply to the invoice format or customer preference.
Check the total invoice amount before applying the small-value invoice exception. The threshold is based on the total invoice value, including VAT.
The system should record why an invoice was treated as exempt, out of scope or subject to another permitted format. This creates a consistent control for finance, tax and audit teams.
An exemption removes a transaction from the mandatory e-invoice requirement. A transition provision keeps the transaction in scope but temporarily allows another invoice format.
The €800,000 threshold applies only to issuing e-invoices. Receiving e-invoices has been mandatory since 1 January 2025.
Under §27(38) UStG, transition provisions continue to permit other invoice formats during the phased implementation period. From 1 January 2028, structured e-invoicing becomes mandatory for in-scope domestic B2B transactions, subject to applicable exceptions.
| Provision | Period | Who can use it | What is permitted | Key condition |
| General transition | 1 Jan 2025 to 31 Dec 2026 | Businesses issuing in-scope B2B invoices | Paper invoices or other non-e-invoice formats | Recipient consent is required for electronic formats such as PDF |
| €800,000 transition | 1 Jan 2027 to 31 Dec 2027 | Businesses with previous-year total turnover of no more than €800,000 | Paper invoices or other permitted non-e-invoice formats | The €800,000 test applies to the invoice issuer |
| EDI transition | Through 31 Dec 2027 | Businesses using qualifying EDI arrangements | Existing EDI processes that meet the transitional conditions | Applies under the specific EDI provision in §27(38) UStG |
| Full obligation | From 1 Jan 2028 | Businesses issuing in-scope domestic B2B invoices | Structured e-invoice required | Subject to statutory exemptions and other applicable provisions |
Conclusion
These statutory exceptions apply only to defined invoice categories and only when their specific legal conditions are met. Businesses should therefore determine exemption eligibility for each transaction before issuing an invoice outside the mandatory e-invoice framework.
The key control is the accurate classification of the transaction, recipient, and applicable statutory provision. Where an exception does not apply, the invoice must follow the applicable German e-invoicing requirements.
Frequently Asked Question
No. The mandate applies to in-scope domestic B2B transactions, subject to statutory exceptions and the transition framework.
Passenger tickets, small-business invoices, and other transactions covered by specific statutory exceptions are excluded where the conditions are met.
Reverse-charge treatment does not itself create an exemption. The underlying transaction must be assessed against the German e-invoicing scope.
The specific German mandate applies to qualifying domestic B2B transactions.
No. It provides an extended transition period for issuing e-invoices; it does not permanently exempt the business.
Quick Navigation
Learn more by booking a demo with our team. We'll guide you step by step.