EN 16931 · PEPPOL 3.0.17 CERTIFIED ENGINE
Pay-As-You-Go API Credits ($0.05/op) →
InvoiceSpec / Rules Registry / peppol-bis-3 / DE-R-017
warning ASSERTION · DE-R-017 Peppol BIS Billing 3.0 (UBL-2.1) Jurisdiction: EU

DE-R-017: If both supplier and customer are located in Germany, the element "Invoice type code" (BT-3) should only contain the following values from code list UNTDID 1001: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

Official Peppol BIS Billing 3.0 Spec ↗
01. Technical Specification & XPath Evaluation Context

This rule (DE-R-017) is a German-specific Peppol BIS Billing 3.0 Schematron assertion that applies when both the supplier (BG-5) and customer (BG-7) are located in Germany. The context XPath selects either an Invoice or CreditNote document where the variables $supplierCountryIsDE and $customerCountryIsDE evaluate to true. These variables are defined elsewhere in the Schematron and check the country code (BT-40 for supplier, BT-55 for customer) against 'DE'. The rule then asserts that the Invoice type code (BT-3), which is mandatory and taken from UNTDID 1001, must be one of the listed values: 326, 380, 384, 389, 381, 875, 876, or 877. If the code is not in this set, the assertion fails, triggering a warning. The XPath test likely checks the value of cbc:InvoiceTypeCode or cbc:CreditNoteTypeCode against the allowed list. This rule ensures compliance with German e-invoicing requirements, particularly for construction invoices and credit notes.

Evaluated XPath Location:
(/ubl-invoice:Invoice | /ubl-creditnote:CreditNote)[$supplierCountryIsDE and $customerCountryIsDE]
Deterministic Remediation Steps

1. Identify the Invoice type code (BT-3) in your UBL document: it is the value of cbc:InvoiceTypeCode (for Invoice) or cbc:CreditNoteTypeCode (for CreditNote). 2. Check if both supplier and customer country codes (BT-40 and BT-55) are 'DE'. If not, this rule does not apply. 3. If both are 'DE', ensure the Invoice type code is one of: 326, 380, 384, 389, 381, 875, 876, 877. 4. If the current code is not in the list, replace it with an appropriate allowed code. For a standard commercial invoice, use 380. For a credit note, use 381. For construction invoices, use 875, 876, or 877 as applicable. 5. Validate the document again to ensure the warning is resolved.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (DE-R-017) FAIL
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
2 <!-- ... other elements ... -->
3 - <cbc:InvoiceTypeCode>388</cbc:InvoiceTypeCode> <!-- DE-R-017: Invoice type code 388 (tax invoice) is not allowed when both parties are in Germany -->
4 <!-- ... -->
5 </Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID) PASS
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
2 <!-- ... other elements ... -->
3 + <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode> <!-- Compliant: 380 (commercial invoice) is allowed -->
4 <!-- ... -->
5 </Invoice>
03. Interactive Peppol BIS Billing 3.0 Validation & Auto-Fix Workbench
BALANCE:3 CREDITS
invoice.xmlUBL-2.1
ORIGINCustom ERP / Billing Engine
BT-131 LINE SUM0.00 EUR
BT-106 HEADER0.00 EUR
STATUS: FAIL (1 FATAL, 1 WARN)· 1ms
Peppol BIS Billing 3.0
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Spec & Diff
xpath: /ubl:Invoice/cbc:CustomizationID

Missing <cbc:CustomizationID> or value does not declare EN 16931 CIUS compliance.

fix: Insert <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>.

BR-DE-15Buyer reference / Leitweg-ID (BT-10) is missing
Spec & Diff
xpath: /ubl:Invoice/cbc:BuyerReference

No <cbc:BuyerReference> (BT-10) found. Mandatory in XRechnung 3.0 (BR-DE-15) and required in Peppol BIS 3.0 (PEPPOL-EN16931-R003) when OrderReference is absent.

fix: Insert <cbc:BuyerReference>991-12849-74</cbc:BuyerReference> in the document header.

Deploy Direct Custom ERP / Billing Engine → Peppol BIS Billing 3.0 AP Bridge

Automated Peppol Access Point & ZUGFeRD delivery without manual XML maintenance

04. Adjacent Peppol BIS Billing 3.0 Assertions Browse All 1,145 Rules →