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

DE-R-015: If both supplier and customer are located in Germany, the element "Buyer reference" (BT-10) shall be provided.

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

This rule enforces the German national requirement (from the Peppol BIS Billing 3.0 DE extension) that when both the supplier (BG-4, BT-27 country) and customer (BG-7, BT-55 country) are located in Germany, the Buyer reference (BT-10) must be provided. The Schematron context selects Invoice or CreditNote documents where the variables $supplierCountryIsDE and $customerCountryIsDE evaluate to true. These variables are defined elsewhere in the Schematron to check the country codes in the supplier and customer postal addresses (cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode and cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode) for the value 'DE'. The assertion test then checks for the presence of the Buyer reference element (cbc:BuyerReference) in the document. If it is absent, the rule fails with fatal severity, as BT-10 is mandatory in this scenario.

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

1. Ensure that the invoice or credit note includes the element cbc:BuyerReference (BT-10) at the document level (as a direct child of Invoice or CreditNote). 2. The value should be a string that identifies the buyer's reference, such as a purchase order number or a unique identifier assigned by the buyer. 3. If the document is generated programmatically, add logic to include this element when both supplier and customer country codes are 'DE'. 4. Validate the updated XML against the Peppol BIS Billing 3.0 Schematron to confirm compliance.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (DE-R-015) FAIL
1 <!-- Invoice with both supplier and customer in Germany, but missing BuyerReference -->
2 <Invoice xmlns="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 <!-- ... other elements ... -->
6 <cac:AccountingSupplierParty>
7 <cac:Party>
8 <cac:PostalAddress>
9 <cac:Country>
10 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
11 </cac:Country>
12 </cac:PostalAddress>
13 </cac:Party>
14 </cac:AccountingSupplierParty>
15 <cac:AccountingCustomerParty>
16 <cac:Party>
17 <cac:PostalAddress>
18 <cac:Country>
19 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
20 </cac:Country>
21 </cac:PostalAddress>
22 </cac:Party>
23 </cac:AccountingCustomerParty>
24 <!-- Missing cbc:BuyerReference element -->
25 </Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID) PASS
1 <Invoice xmlns="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 <!-- ... other elements ... -->
5 <cac:AccountingSupplierParty>
6 <cac:Party>
7 <cac:PostalAddress>
8 <cac:Country>
9 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
10 </cac:Country>
11 </cac:PostalAddress>
12 </cac:Party>
13 </cac:AccountingSupplierParty>
14 <cac:AccountingCustomerParty>
15 <cac:Party>
16 <cac:PostalAddress>
17 <cac:Country>
18 <cbc:IdentificationCode>DE</cbc:IdentificationCode>
19 </cac:Country>
20 </cac:PostalAddress>
21 </cac:Party>
22 </cac:AccountingCustomerParty>
23 + <cbc:BuyerReference>REF-12345</cbc:BuyerReference>
24 </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 →