Error Guide

🇩🇪 BR-DE-17: Invalid XRechnung Invoice Type Code in Germany

ErrorMandatoryAuto-fixable

XRechnung only allows specific Invoice Type Codes: 326 (partial), 380 (commercial), 381 (credit note), 384 (corrected), 389 (self-billed), 875-877 (construction invoices).

Quick Facts

Severity

Error (rejection)

Ruleset

XRechnung (Germany)

Fix Confidence

80%

Mandate

B2B Mandatory

Fix Type

Automatic

Why This Matters in Germany

Germany requires e-invoicing using XRechnung (UBL), XRechnung (CII), ZUGFeRD 2.x. Invoices with this error will be rejected. They cannot be processed for Germany compliance.

Invoice Navigator automatically fixes this error. No manual intervention needed.

Invoice Navigator covers 147 XRechnung 3.0.2 rules for Germany. Auto-remediates 89% of top rejection errors.

How to Fix BR-DE-17

1
Identify invoice purpose
Determine if this is a standard invoice, credit note, or correction
2
Set valid type code
Use 380 (commercial), 381 (credit), 384 (corrected), 389 (self-billed), or 326 (partial)

Example: Before & After

Before (invalid)

<cac:PartyTaxScheme>
  <cbc:CompanyID>INVALID_CODE</cbc:CompanyID>
</cac:PartyTaxScheme>

After (fixed)

<cac:PartyTaxScheme>
  <cbc:CompanyID>VALID_CODE</cbc:CompanyID>
</cac:PartyTaxScheme>

Germany E-Invoicing Requirements

Phase

Status

Scope

B2G

Live (Nov 2020)

All federal suppliers

B2B receiving

Live (Jan 2025)

All German businesses

B2B sending

Jan 2027

>€800K annual revenue

B2B sending

Jan 2028

All businesses

Common Causes

•Invalid invoice type code for XRechnung
•BT-3 uses code not allowed in German invoices
•Only 326/380/384/389/381/875/876/877 permitted
•Legacy invoice type code not mapped to German subset
•Construction invoice codes not properly assigned

Fix BR-DE-17 automatically

Upload your invoice and let Invoice Navigator auto-remediate this error.

Try the Validator Germany Guide →