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

NL-R-002: For suppliers in the Netherlands the supplier's address (cac:AccountingSupplierParty/cac:Party/cac:PostalAddress) MUST contain street name (cbc:StreetName), city (cbc:CityName) and post code (cbc:PostalZone)

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

NL-R-002 is a fatal Peppol BIS Billing 3.0 Schematron rule that enforces the Dutch national requirement for a complete supplier postal address when the supplier is established in the Netherlands. The rule is evaluated in the context of cac:AccountingSupplierParty/cac:Party/cac:PostalAddress, but only when the predicate [$supplierCountryIsNL] is true. That predicate is defined elsewhere in the Schematron (typically as a variable that checks cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'NL'). The assertion requires the presence of three Business Terms: BT-35 (cbc:StreetName), BT-37 (cbc:CityName), and BT-38 (cbc:PostalZone). In EN 16931 terms, these correspond to BG-5 (Seller postal address) child elements. The XPath test fails if any of the three elements is absent or empty. Because the rule is fatal, a missing element causes the entire invoice to be rejected by the receiving Access Point. The rule does not apply to suppliers in other countries, even though Peppol BIS Billing 3.0 generally allows a more flexible address structure (e.g., address lines instead of street name). For Dutch suppliers, the street name, city, and post code are mandatory.

Evaluated XPath Location:
cac:AccountingSupplierParty/cac:Party/cac:PostalAddress[$supplierCountryIsNL]
Deterministic Remediation Steps

1. Locate the supplier postal address block: cac:AccountingSupplierParty/cac:Party/cac:PostalAddress. 2. Verify that the country code in cac:Country/cbc:IdentificationCode is 'NL'. If it is not 'NL', this rule does not apply. 3. Ensure that the following three elements are present and non-empty: - cbc:StreetName (BT-35) - cbc:CityName (BT-37) - cbc:PostalZone (BT-38) 4. If any of these elements are missing, add them with the correct values from the supplier's official address. 5. Do not use cbc:AddressLine as a substitute for cbc:StreetName for Dutch suppliers; the rule explicitly requires cbc:StreetName. 6. Re-validate the invoice 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 (NL-R-002) FAIL
1 <cac:AccountingSupplierParty>
2 <cac:Party>
3 <cac:PostalAddress>
4 - <!-- ERROR: cbc:StreetName is missing; cbc:CityName and cbc:PostalZone are present but the rule requires all three -->
5 <cbc:CityName>Amsterdam</cbc:CityName>
6 <cbc:PostalZone>1012AB</cbc:PostalZone>
7 <cac:Country>
8 <cbc:IdentificationCode>NL</cbc:IdentificationCode>
9 </cac:Country>
10 </cac:PostalAddress>
11 </cac:Party>
12 </cac:AccountingSupplierParty>
+++ b/invoice-compliant.xml (EN 16931 VALID) PASS
1 <cac:AccountingSupplierParty>
2 <cac:Party>
3 <cac:PostalAddress>
4 + <cbc:StreetName>Damrak</cbc:StreetName>
5 <cbc:CityName>Amsterdam</cbc:CityName>
6 <cbc:PostalZone>1012AB</cbc:PostalZone>
7 <cac:Country>
8 <cbc:IdentificationCode>NL</cbc:IdentificationCode>
9 </cac:Country>
10 </cac:PostalAddress>
11 </cac:Party>
12 </cac:AccountingSupplierParty>
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 (2 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>.

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 →