XRechnung Error Codes: Complete Troubleshooting Guide 2025
In this error guide:
Understanding XRechnung Validation and Error Codes
XRechnung validation occurs at multiple levels: schema validation, business rules (BR), and German-specific rules (BR-DE). Understanding these error codes helps you quickly identify and fix issues before submission.
Error codes follow a structured format:
- BR-XX: European standard business rules from EN 16931
- BR-DE-XX: German-specific business rules
- Schema errors: XML structure and syntax violations
- Validation errors: Data consistency and calculation issues
Business Rule (BR) Errors - European Standard
BR-01: Invoice Number Required
Error Message: "An Invoice shall have an Invoice number (BT-1)."
Cause: Missing invoice number
Solution: Add a unique invoice number in field BT-1
Example: <cbc:ID>RE-2025-001234</cbc:ID>
BR-02: Invoice Issue Date Required
Error Message: "An Invoice shall have an Invoice issue date (BT-2)."
Cause: Missing or invalid invoice date
Solution: Add issue date in YYYY-MM-DD format
Example: <cbc:IssueDate>2025-01-16</cbc:IssueDate>
BR-04: Invoice Type Code Required
Error Message: "An Invoice shall have an Invoice type code (BT-3)."
Cause: Missing invoice type specification
Solution: Add type code (380 for invoice, 381 for credit note)
Example: <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
BR-16: Line Net Amount Required
Error Message: "An Invoice line shall have an Invoice line net amount (BT-131)."
Cause: Missing net amount for invoice line
Solution: Ensure each line has quantity × unit price = line net amount
BR-45: VAT Category Required
Error Message: "Each VAT breakdown shall have a VAT category code (BT-118)."
Cause: Missing VAT category in tax breakdown
Solution: Add appropriate VAT category code (S, AA, Z, E, etc.)
BR-49: Payment Means Required
Error Message: "A Payment instruction shall specify the Payment means type code (BT-81)."
Cause: Missing payment method specification
Solution: Add payment means code (30=credit transfer, 59=SEPA)
German-Specific (BR-DE) Errors
BR-DE-1: Leitweg-ID Required
Error Message: "Das Element 'Buyer reference' (BT-10) muss übermittelt werden (Leitweg-ID)."
Cause: Missing or incorrect Leitweg-ID for B2G invoices
Solution: Add the exact Leitweg-ID provided by the public authority
Critical: Must match exactly, including hyphens and case
BR-DE-2: Seller Electronic Address Required
Error Message: "Das Element 'Seller electronic address' (BT-34) muss übermittelt werden."
Cause: Missing seller's electronic endpoint ID
Solution: Add PEPPOL ID or email address as endpoint
Example: DE:VAT:DE123456789
or invoice@company.de
BR-DE-16: VAT ID Required for Certain Tax Codes
Error Message: "In der Rechnung muss mindestens eines der Elemente 'Seller VAT identifier' (BT-31) oder 'Seller tax registration identifier' (BT-32) übermittelt werden."
Cause: Using tax codes S, Z, E, AE, K, G, L, or M without VAT ID
Solution: Add seller's VAT identifier (USt-IdNr.)
Format: DE123456789
(country code + number)
BR-DE-19: Payment Terms for Skonto
Error Message: "Payment terms (BT-20) shall specify the conditions for a payment discount."
Cause: Offering cash discount without proper terms
Solution: Include discount percentage and period in payment terms
Example: "#SKONTO#TAGE=14#PROZENT=2.00#"
Schema Validation Errors
Invalid XML Structure
Error: "The content of element 'Invoice' is not complete"
Cause: Missing required XML elements or wrong order
Solution: Ensure all mandatory elements are present in correct sequence
- Check namespace declarations
- Verify element order matches schema
- Ensure no missing closing tags
Invalid Data Type
Error: "Invalid content was found starting with element"
Cause: Wrong data type (e.g., text in numeric field)
Solution: Ensure correct data types:
- Amounts: Decimal with max 2 decimals
- Dates: YYYY-MM-DD format
- Codes: Valid code list values only
Namespace Errors
Error: "Cannot find the declaration of element"
Cause: Missing or incorrect namespace declarations
Solution: Verify correct namespaces for UBL or CII syntax
UBL: xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
Calculation and Logic Errors
BR-CO-10: Sum of Line Amounts Error
Error: "Sum of Invoice line net amounts = Invoice total amount without VAT"
Cause: Line items don't add up to subtotal
Solution: Recalculate: Sum of all line net amounts must equal invoice subtotal
Check: Σ(Line amounts) = Invoice subtotal
BR-CO-14: VAT Calculation Error
Error: "Invoice total VAT amount = Σ VAT category tax amounts"
Cause: VAT calculations don't match
Solution: Ensure VAT is calculated correctly for each category
Formula: Taxable amount × VAT rate = VAT amount
BR-CO-15: Invoice Total Error
Error: "Invoice total amount with VAT = Invoice total without VAT + Invoice total VAT"
Cause: Grand total calculation incorrect
Solution: Verify: Subtotal + Total VAT = Grand Total
Format and Data Type Errors
Date Format Errors
Common Issues:
- Wrong format: Must be YYYY-MM-DD (not DD.MM.YYYY)
- Invalid dates: Check for impossible dates (e.g., 2025-13-32)
- Missing leading zeros: Use 2025-01-05, not 2025-1-5
Amount Format Errors
Common Issues:
- Decimal separator: Use period (.) not comma (,)
- Decimal places: Maximum 2 for monetary amounts
- Negative amounts: Use minus sign, not parentheses
Correct: 1234.56
| Wrong: 1.234,56
Code List Errors
Common Issues:
- Invalid currency: Use ISO 4217 codes (EUR, USD, GBP)
- Invalid country: Use ISO 3166-1 Alpha-2 (DE, FR, IT)
- Invalid unit: Use UN/ECE Recommendation 20 codes
Routing and Transmission Errors
Leitweg-ID Not Found
Error: "Die Leitweg-ID konnte nicht zugeordnet werden"
Cause: Unknown or inactive Leitweg-ID
Solution:
- Verify Leitweg-ID with recipient
- Check for typos (case-sensitive!)
- Ensure ID is still active
File Size Exceeded
Error: "Maximum file size exceeded"
Cause: Invoice file too large (usually >15MB)
Solution:
- Remove embedded attachments
- Send attachments separately
- Optimize file structure
Troubleshooting Steps
Step-by-Step Troubleshooting
-
Use Official Validators
- KoSIT Validator for XRechnung compliance
- Portal-specific validators
-
Check Error Hierarchy
- Fix schema errors first
- Then business rule violations
- Finally calculation errors
-
Validate Against Examples
- Compare with working examples
- Use official test cases
-
Test with Minimal Invoice
- Start with mandatory fields only
- Add optional fields gradually
Common Quick Fixes
- ✓ Double-check Leitweg-ID character by character
- ✓ Ensure all dates use YYYY-MM-DD format
- ✓ Verify VAT calculations manually
- ✓ Check currency and country codes
- ✓ Validate seller has electronic address
- ✓ Confirm VAT ID when using taxable categories
Avoid Validation Errors with Our Converter
Our XRechnung converter automatically validates your invoice and provides clear error messages with solutions:
- Real-time validation as you enter data
- Clear error explanations in plain language
- Automatic calculation verification
- Format compliance guaranteed
🚀 Ready to Convert Your Invoices?
Start converting PDF invoices to XRechnung, ZUGFeRD, and other formats today. 3-day free trial included.