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-002
fatal ASSERTION · DE-R-002 Peppol BIS Billing 3.0 (UBL-2.1) Jurisdiction: EU

DE-R-002: If both supplier and customer are located in Germany, the group "SELLER CONTACT" (BG-6) shall be provided.

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

This rule enforces the German national requirement (DE-R-002) that when both the supplier (BG-4) and customer (BG-7) are located in Germany (BT-40 and BT-55 equal 'DE'), the seller contact group (BG-6) must be present. The context XPath selects the AccountingSupplierParty element of an Invoice or CreditNote, but only when the variables $supplierCountryIsDE and $customerCountryIsDE are true. These variables are defined elsewhere in the Schematron and evaluate the country codes from the supplier's and customer's postal addresses (BT-40 and BT-55). The rule then checks that the cac:SellerContact element exists within the AccountingSupplierParty. If it is missing, the assertion fails with a fatal error. The rule applies to both UBL Invoice and CreditNote documents.

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

1. Verify that both the supplier's country (BT-40) and the customer's country (BT-55) are set to 'DE' in the respective PostalAddress elements. 2. If both are 'DE', ensure that the AccountingSupplierParty/Party contains a cac:SellerContact element (BG-6). 3. Populate the SellerContact with at least one of the following: cbc:Name (BT-41), cbc:Telephone (BT-42), or cbc:ElectronicMail (BT-43). It is recommended to provide all three for completeness. 4. If the countries are not both 'DE', this rule does not apply, and SellerContact is optional. 5. Re-validate the document against the Peppol BIS Billing 3.0 Schematron to confirm the error is resolved.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (DE-R-002) FAIL
1 <!-- Supplier and customer are both in Germany, but SellerContact is missing -->
2 <ubl-invoice:Invoice xmlns:ubl-invoice="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
3 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
4 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
5 <cac:AccountingSupplierParty>
6 <cac:Party>
7 <cac:PostalAddress>
8 <cbc:CountrySubentity>Berlin</cbc:CountrySubentity>
9 <cac:Country>
10 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
11 </cac:Country>
12 </cac:PostalAddress>
13 <!-- Missing cac:SellerContact element -->
14 </cac:Party>
15 </cac:AccountingSupplierParty>
16 <cac:AccountingCustomerParty>
17 <cac:Party>
18 <cac:PostalAddress>
19 <cbc:CountrySubentity>Munich</cbc:CountrySubentity>
20 <cac:Country>
21 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
22 </cac:Country>
23 </cac:PostalAddress>
24 </cac:Party>
25 </cac:AccountingCustomerParty>
26 <!-- ... rest of invoice ... -->
27 </ubl-invoice:Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID) PASS
1 <ubl-invoice:Invoice xmlns:ubl-invoice="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
2 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
3 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
4 <cac:AccountingSupplierParty>
5 <cac:Party>
6 <cac:PostalAddress>
7 <cbc:CountrySubentity>Berlin</cbc:CountrySubentity>
8 <cac:Country>
9 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
10 </cac:Country>
11 </cac:PostalAddress>
12 + <cac:SellerContact>
13 + <cbc:ID>12345</cbc:ID>
14 + <cbc:Name>John Doe</cbc:Name>
15 + <cbc:Telephone>+49 30 1234567</cbc:Telephone>
16 + <cbc:ElectronicMail>john.doe@example.com</cbc:ElectronicMail>
17 + </cac:SellerContact>
18 </cac:Party>
19 </cac:AccountingSupplierParty>
20 <cac:AccountingCustomerParty>
21 <cac:Party>
22 <cac:PostalAddress>
23 <cbc:CountrySubentity>Munich</cbc:CountrySubentity>
24 <cac:Country>
25 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
26 </cac:Country>
27 </cac:PostalAddress>
28 </cac:Party>
29 </cac:AccountingCustomerParty>
30 <!-- ... rest of invoice ... -->
31 </ubl-invoice: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 (3 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>.

PEPPOL-EN16931-R020Seller electronic address (BT-34) MUST be provided with a valid EAS @schemeID
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

Missing <cbc:EndpointID schemeID="..."> inside <cac:AccountingSupplierParty>/<cac:Party>.

fix: Add <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID> as the first child of Seller <cac:Party>.

PEPPOL-EN16931-R010Buyer electronic address (BT-49) MUST include a valid EAS @schemeID attribute
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

Buyer <cbc:EndpointID> is either missing or lacks the mandatory EAS @schemeID attribute.

fix: Add schemeID="9930" (or "0088" for GLN / "0204" for Leitweg-ID) to Buyer <cbc:EndpointID>.

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 →