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

DE-R-001: If both supplier and customer are located in Germany, an invoice shall contain information on "PAYMENT INSTRUCTIONS" (BG-16).

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

This fatal rule (DE-R-001) enforces the German national requirement that when both the supplier (BG-5) and customer (BG-7) are located in Germany (country code 'DE' in their respective postal addresses), the invoice must contain payment instructions (BG-16). The context XPath selects Invoice or CreditNote documents where the variables $supplierCountryIsDE and $customerCountryIsDE are true. These variables are defined in the Schematron to check the CountryID (BT-40 for supplier, BT-55 for customer) in the PostalAddress (BG-5, BG-7). The rule then asserts that the PaymentMeans (BG-16) element exists. If missing, the assertion fails with the given message. The rule is fatal, meaning the invoice is non-compliant and must be rejected.

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

To fix the violation, ensure that the invoice contains at least one cac:PaymentMeans element (BG-16) when both supplier and customer are in Germany. Steps: 1. Check the supplier's country code (BT-40) in cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode. 2. Check the customer's country code (BT-55) similarly. 3. If both are 'DE', add a cac:PaymentMeans element with required sub-elements: cbc:PaymentMeansCode (BT-81) and optionally payment account details (BG-17). 4. Validate against the Peppol BIS Billing 3.0 Schematron to ensure compliance.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (DE-R-001) FAIL
1 <!-- Supplier and customer are both in Germany, but no PaymentMeans (BG-16) is provided -->
2 <ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
3 <cac:AccountingSupplierParty>
4 <cac:Party>
5 <cac:PostalAddress>
6 <cac:Country>
7 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
8 </cac:Country>
9 </cac:PostalAddress>
10 </cac:Party>
11 </cac:AccountingSupplierParty>
12 <cac:AccountingCustomerParty>
13 <cac:Party>
14 <cac:PostalAddress>
15 <cac:Country>
16 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
17 </cac:Country>
18 </cac:PostalAddress>
19 </cac:Party>
20 </cac:AccountingCustomerParty>
21 <!-- Missing cac:PaymentMeans (BG-16) -->
22 </ubl:Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID) PASS
1 <ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
2 <cac:AccountingSupplierParty>
3 <cac:Party>
4 <cac:PostalAddress>
5 <cac:Country>
6 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
7 </cac:Country>
8 </cac:PostalAddress>
9 </cac:Party>
10 </cac:AccountingSupplierParty>
11 <cac:AccountingCustomerParty>
12 <cac:Party>
13 <cac:PostalAddress>
14 <cac:Country>
15 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
16 </cac:Country>
17 </cac:PostalAddress>
18 </cac:Party>
19 </cac:AccountingCustomerParty>
20 + <cac:PaymentMeans>
21 + <cbc:PaymentMeansCode>30</cbc:PaymentMeansCode>
22 + <cac:PayeeFinancialAccount>
23 + <cbc:ID>DE12345678901234567890</cbc:ID>
24 + </cac:PayeeFinancialAccount>
25 + </cac:PaymentMeans>
26 </ubl: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 →