PEPPOL-EN16931-R010Buyer electronic address MUST be provided
Official rule text
The buyer electronic address (BT-49) must be provided — the identifier the invoice is technically delivered to, such as an email address. The scheme that goes with it is BR-63's requirement, not this rule's.
- Severity
- Error
- Applies to
- CII, UBL
- Rule set
- v2026-08-31
- Checked on
Written and checked against the official KoSIT rule set by Dmytro Yalanskyi, NormAPI.
Why does PEPPOL-EN16931-R010 happen?
The address belongs to the transport rather than to the invoice, so it lives in the sending system and not in the invoice record. It is then missing when the document is built, even though the transport knows it. All that is checked is that the element is there: an empty cbc:EndpointID satisfies this rule and is caught instead by PEPPOL-EN16931-R008, which forbids empty elements anywhere in the document.
What the validator checks
The expression the official KoSIT rule set evaluates — not paraphrased, but read from the Schematron file it ships. UBL and CII address different document trees, so the same rule reads differently in each.
- UBL
cbc:EndpointID- CII
ram:URIUniversalCommunication/ram:URIID
Source: rule set v2026-08-31
How do you fix PEPPOL-EN16931-R010?
Set BT-49 with its scheme attribute: cbc:EndpointID with schemeID under cac:AccountingCustomerParty/cac:Party in UBL, ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID in CII. EM denotes an email address, 0204 the German Leitweg-ID — the formerly common 9958 is no longer in the list BR-CL-25 checks.
In the XML
A UBL fragment. The CII path is named above — same change, different element names.
<cac:AccountingCustomerParty>
<cac:Party>
<cac:PartyName>
<cbc:Name>Behörde Bonn</cbc:Name>
</cac:PartyName>
</cac:Party>
</cac:AccountingCustomerParty><cac:AccountingCustomerParty>
<cac:Party>
<cbc:EndpointID schemeID="EM">rechnung@behoerde-bonn.de</cbc:EndpointID>
<cac:PartyName>
<cbc:Name>Behörde Bonn</cbc:Name>
</cac:PartyName>
</cac:Party>
</cac:AccountingCustomerParty>Related rules
NormAPI provides technical validation, not tax or legal advice.