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:
- the value, for example an email address, a VAT number or a Leitweg-ID,
- the scheme, a code that says what kind of value it is.
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:
| Scheme | Value | Typical use |
|---|---|---|
EM | Email address | XRechnung sent by email or uploaded to a portal. Not accepted in Peppol BIS. |
9930 | German VAT number, e.g. DE123456789 | German companies on the Peppol network. |
0204 | Leitweg-ID | German public bodies on the Peppol network. |
0088 | GLN (Global Location Number) | Companies that already use GLNs in EDI. |
0208 | Belgian enterprise number, 10 digits | Belgian companies on Peppol. |
0106, 0190 | Dutch KvK number, Dutch OIN | Dutch companies and public bodies. |
0009, 0225 | French SIRET, French e-invoicing address | French companies. |
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
- BT-49, buyer electronic address (
cbc:EndpointID): this page. - BT-10, buyer reference (
cbc:BuyerReference): for German public buyers this holds the Leitweg-ID. It is a separate, required field. A Leitweg-ID in BT-10 does not fill BT-49, and the other way round. - BT-43, seller contact email (
cac:Contact/cbc:ElectronicMail): the address of a person or team for questions. It may be the same mailbox as BT-34, but both elements must be there.
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:
| Rule | Message | Cause | Fix |
|---|---|---|---|
PEPPOL-EN16931-R020 | Seller electronic address MUST be provided | BT-34 is missing. | Add the seller's cbc:EndpointID with a schemeID. |
PEPPOL-EN16931-R010 | Buyer electronic address MUST be provided | BT-49 is missing. | Add the buyer's cbc:EndpointID with a schemeID. |
BR-62 | The Seller electronic address (BT-34) shall have a Scheme identifier. | The element is there, the schemeID attribute is not. | Add schemeID, e.g. schemeID="EM". |
BR-63 | The Buyer electronic address (BT-49) shall have a Scheme identifier. | Same, on the buyer's side. | Add schemeID. |
BR-CL-25 | Endpoint identifier scheme identifier MUST belong to the CEF EAS code list | The scheme is not a code from the list, for example EMAIL or email instead of EM. | Use the exact code. Codes are case-sensitive. |
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:
| Rule | Cause | Fix |
|---|---|---|
PEPPOL-EN16931-CL008 | The scheme is not in Peppol's own, shorter list. EM is the usual case: email addresses are not Peppol addresses. | Use the receiver's Peppol identifier, e.g. 9930 or 0208. |
PEPPOL-COMMON-R043 | Scheme 0208 with a value that is not a valid Belgian enterprise number. | Ten digits, no BE prefix, no dots; the last two digits are a check number. |
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