Skip to content

PEPPOL-EN16931-R020: Seller electronic address (BT-34) is missing

Official message

[PEPPOL-EN16931-R020] Seller electronic address MUST be provided

XRechnung (CII) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[PEPPOL-EN16931-R020] Seller electronic address MUST be provided

XRechnung (UBL) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Error The invoice is invalid and may be rejected by the recipient.
Applies to
XRechnung (CII), XRechnung (UBL)

What does this mean?

Seller electronic address MUST be provided: the invoice must contain the seller electronic address (BT-34). It is missing.
The rule originates from Peppol BIS Billing 3.0 and is applied in the XRechnung validation. CII: ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID, UBL: cac:AccountingSupplierParty/cac:Party/cbc:EndpointID.

Typical causes

The seller electronic address was not entered because it is optional in EN 16931.
Only the e-mail address of the contact (BT-43) was given; it does not replace BT-34.

How to fix the error

State BT-34 with an electronic address of the seller, e.g. an e-mail address.
State the matching scheme in BT-34-1 (e.g. EM for an e-mail address; see BR-CL-25).
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form, "Experte" view, section "Verkäufer (BG-4)" (seller), fill in the fields "Elektronische Adresse (BT-34/49)" (electronic address) and "EAS-Schema der elektron. Adresse (BT-34-1/49-1)" (electronic address scheme).

Example

Wrong

<ram:SellerTradeParty>
  <ram:Name>Sample Ltd</ram:Name>
  ...
</ram:SellerTradeParty>

Correct

<ram:SellerTradeParty>
  <ram:Name>Sample Ltd</ram:Name>
  ...
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="EM">invoice@example.com</ram:URIID>
  </ram:URIUniversalCommunication>
</ram:SellerTradeParty>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: ram:SellerTradeParty

ram:URIUniversalCommunication/ram:URIID

XRechnung (UBL) (UBL)

Context: cac:AccountingSupplierParty/cac:Party

cbc:EndpointID

Related validation rules

Last updated:
Explanation of the validation rule, not legal or tax advice.