Common E-Invoice Mistakes German Freelancers Make (and How to Avoid Them)
Germany's e-invoicing mandate is straightforward in principle but has several common failure points in practice. Most mistakes are avoidable once you know what to look for, and catching them before submission saves the delay and rework of a rejection.
1. Missing or wrong Leitweg-ID
The Leitweg-ID is the routing identifier for the receiving government entity. Getting it wrong or leaving it out is the single most common cause of rejection. Always confirm the exact Leitweg-ID with your client before submitting, not from memory or assumption.
2. Submitting a PDF scan instead of structured data
A PDF image of an invoice is not an e-invoice. An e-invoice must be a structured XML file (XRechnung) or a hybrid PDF with embedded XML (ZUGFeRD/Factur-X). Many freelancers new to the mandate submit scanned PDFs and receive immediate rejections.
3. Wrong VAT category code
Germany's reverse charge rules and VAT exemptions require specific coded values. Using the wrong code, or omitting it, produces an invalid invoice. The most common mix-up is using the standard rated code on a reverse-charge transaction or a small-business exemption invoice.
4. Missing mandatory fields
- Seller and buyer names, addresses and tax identifiers.
- Invoice number (must be unique within your sequence).
- Invoice date and due date.
- Line-item descriptions, quantities, unit prices and line totals.
- VAT rate and amount per line item.
- Payment details (IBAN for bank transfer).
5. Not validating before sending
Most e-invoice portals will reject a malformed file immediately. Running the invoice through a validator (the official KoSIT Validator or a tool that applies the same rules) catches structural errors before the recipient ever sees them.
6. Assuming the same process applies to all public clients
Federal, state and municipal agencies may use different portals (OZG-RE, Peppol network, email) and may require slightly different profiles. Confirm the submission channel with each new public client, not just the invoice format.
This article is general information, not tax or legal advice. For your specific situation, consult a Steuerberater or legal professional. The E-Rechnung app creates both XRechnung XML and ZUGFeRD PDFs with all required fields validated as you type, reducing the chance of a rejectable error. For profile-level questions, see the guide to ZUGFeRD profile types.
Common questions
- Why is my XRechnung being rejected?
- The most common causes are a missing or incorrect Leitweg-ID, wrong VAT codes, missing mandatory fields, or a malformed XML structure. Validate the file with the KoSIT Validator before resubmitting.
- Do I need to validate an e-invoice before sending?
- It is strongly advisable. Validation catches structural and content errors before submission, avoiding rejection delays. Several free online validators apply the EN 16931 rules.
- Is a signed PDF an e-invoice under German law?
- No. A signed or scanned PDF is not a structured e-invoice. You need an XRechnung XML file or a ZUGFeRD hybrid PDF with embedded structured XML.