E-Invoice Error Reference

1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.

86 errors found · Page 2 of 2 for Germany

errorBR-DE-03DEUpeppol-bis-3INPUT

German VAT ID required

German B2B invoices must include the USt-IdNr (VAT identification number) in DE + 9 digits format.

errorBR-DE-CVD-05DEUXRechnung (Germany)INPUT

When CVD standard is referenced in Item Attributes, the attribute values...

Your invoice includes Clean Vehicle Directive (CVD) data, but the vehicle category is not valid. German public procurement invoices for vehicles must specify the correct EU vehicle category (e.g. M1 for passenger cars, N1 for light commercial vehicles).

errorBR-DE-CVD-06-aDEUXRechnung (Germany)INPUT

Vehicle classification code missing or inconsistent

Your invoice includes Clean Vehicle Directive (CVD) data, but the item classification code is either missing or does not match the vehicle category. The classification code must match the vehicle category specified in the CVD properties.

warningBR-DE-TMP-32DEUXRechnung (Germany)INPUT

An invoice should specify when goods were delivered or services performed....

An invoice should specify when goods were delivered or services performed. This can be done via the actual delivery date field, an invoicing period at document level, or invoice line periods on each line item. At least one of these date specifications should be present.

errorBR-DE-CVD-03DEUXRechnung (Germany)INPUT

CVD classification required when clean vehicle attribute present

When an invoice contains a clean vehicle attribute (cva), the invoice must include a CVD (Clean Vehicle Directive) classification. This is required for German public procurement of vehicles under EU Directive 2019/1161.

errorBR-DE-CVD-04DEUXRechnung (Germany)INPUT

CVD classification code must be valid

The CVD (Clean Vehicle Directive) classification code must use a valid value from the allowed code list. This applies to German public procurement of vehicles under EU Directive 2019/1161.

errorDE-R-022DEUPEPPOL_BISCONFIRM

Duplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) i

Duplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) in element BT-125.

errorDE-R-023-2DEUPEPPOL_BISCONFIRM

Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct d

Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct debit (BG-19) groups must not be provided.

errorDE-R-024-2DEUPEPPOL_BISCONFIRM

Conflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and dir

Conflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and direct debit (BG-19) groups must not be provided.

errorDE-R-025-1DEUPEPPOL_BISCONFIRM

If "Payment means type code" (BT-81) contains a code for direct debit (59), "DIRECT DEBIT" (BG-19) shall be provided.

Direct debit details missing. When payment code 59 (direct debit) is used, the Direct Debit group (BG-19) with mandate information must be provided.

errorDE-R-025-2DEUPEPPOL_BISCONFIRM

If "Payment means type code" (BT-81) contains a code for direct debit (59), BG-17 and BG-18 shall not be provided.

Conflicting payment information. When payment code 59 (direct debit) is used, credit transfer (BG-17) and card payment (BG-18) groups must not be provided.

warningDE-R-026DEUPEPPOL_BISCONFIRM

Preceding invoice reference missing. Corrected invoices (type code 384) should reference the original invoice being corr

Preceding invoice reference missing. Corrected invoices (type code 384) should reference the original invoice being corrected in group BG-3.

warningDE-R-027DEUPEPPOL_BISCONFIRM

Invalid phone number format. The seller contact telephone number (BT-42) must contain at least 3 digits to be valid.

Invalid phone number format. The seller contact telephone number (BT-42) must contain at least 3 digits to be valid.

warningDE-R-028DEUPEPPOL_BISCONFIRM

Invalid email format. The seller contact email (BT-43) must contain exactly one @ sign with at least two characters on e

Invalid email format. The seller contact email (BT-43) must contain exactly one @ sign with at least two characters on each side, and no dots at start or end.

errorDE-R-018DEUPEPPOL_BISCONFIRM

Invalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with

Invalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with optional #BASISBETRAG=N#. Must be uppercase with no extra whitespace.

errorBR-DE-01DEUXRechnung (Germany)INPUT

Invalid Leitweg-ID Format

German B2G (Business-to-Government) invoices require a valid Leitweg-ID in the Buyer Reference field (BT-10). The Leitweg-ID is a routing identifier that directs your invoice to the correct government department.

errorBR-DE-3DEUXRechnung (Germany)INPUT

Das Element "Seller city" (BT-37) muss übermittelt werden.

German XRechnung requires Seller City (BT-37). The seller's city must be specified.

errorBR-DE-4DEUXRechnung (Germany)INPUT

Das Element "Seller post code" (BT-38) muss übermittelt werden.

German XRechnung requires Seller Post Code (BT-38). The seller's postal code must be specified.

errorBR-DE-5DEUXRechnung (Germany)INPUT

Das Element "Seller contact point" (BT-41) muss übermittelt werden.

German XRechnung requires Seller Contact Point (BT-41). A contact person or department name must be provided.

errorBR-DE-17DEUXRechnung (Germany)AUTO-FIX

Invalid XRechnung Invoice Type Code

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

errorBR-DE-18DEUXRechnung (Germany)AUTO-FIX

Invalid Skonto (Cash Discount) Format

XRechnung Skonto (early payment discount) lines in PaymentTerms must follow the required format: #SKONTO#TAGE=n#PROZENT=n.nn#BASISBETRAG=n.nn#

errorBR-DE-21DEUXRechnung (Germany)AUTO-FIX

Invalid XRechnung Specification Identifier

The Specification Identifier (BT-24 CustomizationID) must follow the XRechnung URN format: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_X.X

errorBR-DE-15DEUXRechnung (Germany)AUTO-FIX

Buyer reference (Leitweg-ID) mandatory

BuyerReference (BT-10) is mandatory in XRechnung.

errorBR-DE-22DEUXRechnung (Germany)AUTO-FIX

Duplicate Attachment Filenames

XRechnung requires all attachment filenames to be unique. Multiple EmbeddedDocumentBinaryObject elements have the same filename attribute.

errorBR-DE-23-aDEUXRechnung (Germany)AUTO-FIX

Payment code 30 or 58 (bank transfer) requires Credit Transfer details...

Payment code 30 or 58 (bank transfer) requires Credit Transfer details (BG-17). You specified bank transfer but didn't include the bank account.

errorBR-DE-23-bDEUXRechnung (Germany)AUTO-FIX

Payment code 30 or 58 (bank transfer) must not include Card Payment (BG-18)...

Payment code 30 or 58 (bank transfer) must not include Card Payment (BG-18) or Direct Debit (BG-19) sections. Only Credit Transfer should be present.

errorBR-DE-24-aDEUXRechnung (Germany)AUTO-FIX

Payment code 48, 54, or 55 (card payment) requires Card Payment details...

Payment code 48, 54, or 55 (card payment) requires Card Payment details (BG-18). You specified card payment but didn't include card information.

errorBR-DE-24-bDEUXRechnung (Germany)AUTO-FIX

Payment code 48, 54, or 55 (card payment) must not include Credit Transfer...

Payment code 48, 54, or 55 (card payment) must not include Credit Transfer (BG-17) or Direct Debit (BG-19) sections.

errorBR-DE-25-bDEUXRechnung (Germany)AUTO-FIX

Payment code 59 (direct debit) must not include Credit Transfer (BG-17) or...

Payment code 59 (direct debit) must not include Credit Transfer (BG-17) or Card Payment (BG-18) sections. Only Direct Debit Mandate (BG-19) should be present for SEPA direct debit payments.

errorBR-DE-27DEUXRechnung (Germany)AUTO-FIX

Seller Contact Telephone Must Contain At Least Three Digits

Contact telephone numbers must follow proper format guidelines. German XRechnung requires telephone numbers to be properly formatted for machine processing, typically with country code and without invalid characters.

errorBR-DE-CVD-06-bDEUXRechnung (Germany)AUTO-FIX

Missing CVD Classification for Clean Vehicle Attribute

When an invoice line has an AdditionalItemProperty with Name="cva" (clean vehicle attribute), it must also have exactly one CommodityClassification with ItemClassificationCode[@listID="CVD"] containing the vehicle category. This is required for German XRechnung invoices under the Clean Vehicle Directive.

errorBR-DE-28DEUXRechnung (Germany)AUTO-FIX

Seller Contact Email Must Have Valid Format

Contact email addresses must be valid email format. The email must contain proper structure with username, @ symbol, and domain. Invalid email addresses fail schema validation.

errorBR-DEX-10DEUXRechnung (Germany)AUTO-FIX

Missing third party payment type. When using third party payment group...

Missing third party payment type. When using third party payment group (BG-DEX-09), the payment type (BT-DEX-001) is required.

errorBR-DEX-12DEUXRechnung (Germany)AUTO-FIX

Missing third party payment description. When using third party payment...

Missing third party payment description. When using third party payment group (BG-DEX-09), a description (BT-DEX-003) is required.

errorBR-DEX-13DEUXRechnung (Germany)AUTO-FIX

Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party...

Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.

errorBR-DEX-14DEUXRechnung (Germany)AUTO-FIX

Die Währungsangabe von "Third party payment amount" BT-DEX-002 muss BT-5...

Third party payment currency mismatch. The currency of third party payment amount must match the invoice currency (BT-5).

Handle These Errors Automatically in Your Pipeline

The compliance engine auto-remediates validation errors with controlled safety policies and evidence pack generation.

Get API Access