Skip to content

PEPPOL-EN16931-R010: Buyer electronic address (BT-49) is missing

Official message

[PEPPOL-EN16931-R010] Buyer electronic address MUST be provided

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

[PEPPOL-EN16931-R010] Buyer 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?

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

Typical causes

The buyer electronic address was not entered because it is optional in EN 16931.
The Leitweg-ID was only given as buyer reference (BT-10).

How to fix the error

State BT-49 with the electronic address at which the buyer receives invoices, e.g. their Leitweg-ID or an e-mail address.
State the matching scheme in BT-49-1 (e.g. 0204 for a Leitweg-ID, 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 "Käufer (BG-7)" (buyer), 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:BuyerTradeParty>
  <ram:Name>City of Sampletown</ram:Name>
  ...
</ram:BuyerTradeParty>

Correct

<ram:BuyerTradeParty>
  <ram:Name>City of Sampletown</ram:Name>
  ...
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="0204">04011000-12350-85</ram:URIID>
  </ram:URIUniversalCommunication>
</ram:BuyerTradeParty>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: ram:BuyerTradeParty

ram:URIUniversalCommunication/ram:URIID

XRechnung (UBL) (UBL)

Context: cac:AccountingCustomerParty/cac:Party

cbc:EndpointID

Related validation rules

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