Valinvo

XRechnung EndpointID: the electronic address in BT-34 and BT-49

An XRechnung needs two electronic addresses: the seller's (BT-34) and the buyer's (BT-49). In UBL each one is a cbc:EndpointID element with a schemeID attribute. Both are required, and an email address with the scheme EM is allowed. That is the short answer; the rest of this page is the detail.

What it is

The electronic address says where a party receives electronic invoices. It has two parts:

It is not a delivery instruction for the file you are creating. An XRechnung that carries buyer@example.de in BT-49 still reaches the buyer the way you send it: by email, through a portal or over the Peppol network.

Where it goes

UBL (Invoice and CreditNote). cbc:EndpointID belongs inside cac:Party, before cac:PartyIdentification and cac:PartyName. In another position the file fails the XML schema.

<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID schemeID="EM">invoices@example-software.de</cbc:EndpointID>
    <cac:PartyName>…</cac:PartyName>
  </cac:Party>
</cac:AccountingSupplierParty>
<cac:AccountingCustomerParty>
  <cac:Party>
    <cbc:EndpointID schemeID="EM">rechnung@beispiel-behoerde.de</cbc:EndpointID>
    <cac:PartyName>…</cac:PartyName>
  </cac:Party>
</cac:AccountingCustomerParty>

CII (UN/CEFACT Cross Industry Invoice). The element is ram:URIUniversalCommunication, after ram:PostalTradeAddress and before ram:SpecifiedTaxRegistration:

<ram:SellerTradeParty>
  …
  <ram:PostalTradeAddress>…</ram:PostalTradeAddress>
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="EM">invoices@example-software.de</ram:URIID>
  </ram:URIUniversalCommunication>
  <ram:SpecifiedTaxRegistration>…</ram:SpecifiedTaxRegistration>
</ram:SellerTradeParty>

ram:BuyerTradeParty takes the same element for BT-49.

Which scheme to use

The scheme must come from the EAS code list (Electronic Address Scheme) of the European Commission. The ones you meet most often in German and neighbouring invoices:

If you send over Peppol, use the identifier under which the receiver is registered there; your access point looks the receiver up by exactly this scheme and value. If you send an XRechnung by email or portal upload, an email address with EM passes the official rules.

Three fields people mix up

The errors you get

We removed or changed the element in an official XRechnung test invoice and validated it against the XRechnung 3.0.2 rules, in UBL and in CII. These are the rule IDs that come back:

The two PEPPOL- rule IDs are not a mistake: XRechnung 3.0 reports the missing address under the same IDs as Peppol BIS.

Two more apply only to Peppol BIS Billing 3.0:

To see which of these your file triggers, drop it into the free validator.

If you don't know the buyer's address

Ask the buyer; it is their identifier, and a guessed one helps nobody. For an XRechnung that you deliver by email or portal, the email address the buyer gave you for invoices, with EM, satisfies the rules. For Peppol, the buyer or their access point tells you the scheme and value, and the public Peppol Directory lists many receivers.

Don't put a placeholder in the field to get past validation. The file would pass, and the buyer's system may still refuse it or file it under the wrong party.

In the Valinvo API

In the JSON invoice both parties have an electronicAddress with the same two parts:

"seller": {
  "name": "Example Software GmbH",
  "electronicAddress": { "scheme": "EM", "value": "invoices@example-software.de" }
},
"buyer": {
  "name": "Beispiel Behörde",
  "electronicAddress": { "scheme": "EM", "value": "rechnung@beispiel-behoerde.de" }
}

If one is missing, the answer is a 400 that names the field (invoice.seller.electronicAddress or invoice.buyer.electronicAddress) before any XML is built. The quickstart has the full example.

Checked in November 2026 against the XRechnung 3.0.2 and Peppol BIS Billing 3.0 rules. We make Valinvo, a validator and API for these formats.

Quickstart · XRechnung validator · Peppol validator · ZUGFeRD / Factur-X validator · ZUGFeRD-csharp: your options · XRechnung from PHP or Node.js · XRechnung in Python · XRechnung EndpointID (BT-34, BT-49) · Error codes