XRechnung 6 min readPublished

XRechnung Electronic Address: BT-34, BT-49 and EAS Scheme IDs

XRechnung electronic address explained: how to fill BT-34 and BT-49 with scheme IDs EM, 0204 or 9930, with UBL and CII snippets, the exact rules and common errors.

docutools.pro Editorial TeamEditorial Team

Key takeaways

  • Since XRechnung 3.0, the seller electronic address (BT-34) and buyer electronic address (BT-49) are mandatory, enforced by PEPPOL-EN16931-R020 and R010.
  • Every electronic address needs an EAS scheme ID, such as EM for e-mail, 0204 for a Leitweg-ID or 9930 for a German VAT ID.
  • In the KoSIT configuration 2026-08-31, rule BR-CL-25 accepts exactly 104 scheme codes; spellings such as EMAIL or SMTP fail validation.
  • BT-34 does not replace the seller contact BG-6: the contact e-mail BT-43 is still required by BR-DE-7.
On this page

The XRechnung electronic address consists of two mandatory fields: BT-34 for the seller and BT-49 for the buyer. Each needs a scheme ID from the Electronic Address Scheme (EAS) code list, such as EM for an e-mail address or 0204 for a Leitweg-ID. If either field is missing, the KoSIT validator rejects an XRechnung 3.0.2 invoice.

This guide is for developers, ERP teams and foreign suppliers who generate XRechnung files or maintain customer master data. It gives copy-ready UBL and CII snippets, the scheme IDs you will meet in German invoices, and the validation rules with their exact message text.

When do you need BT-34 and BT-49?

Whenever the invoice is meant to be an XRechnung. Both fields came with the harmonisation of XRechnung and Peppol BIS Billing. The version history of the XRechnung 3.0.2 specification (opens in a new tab) lists the adoption of PEPPOL-EN16931-R010 and R020 under version 3.0.0. The German federal e-invoicing service (opens in a new tab) presents BT-23, BT-34 and BT-49 as the new required fields of version 3.0.1.

The obligation does not depend on who the buyer is. It applies to an invoice to a federal ministry and to an XRechnung sent to a wholesaler alike. What decides is the specification identifier in BT-24:

InvoiceIdentifier in BT-24BT-34 / BT-49
XRechnung 3.0 (CIUS)urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0both mandatory (R020, R010)
Extension XRechnungCIUS identifier plus #conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0both mandatory, extra codes XR01 to XR03 allowed
EN 16931 only, e.g. ZUGFeRD EN 16931 profileurn:cen.eu:en16931:2017optional in the KoSIT validator's EN 16931 scenario; if present, it needs a scheme ID

The last row follows from the rule files. R010 and R020 exist only in the XRechnung Schematron, not in the CEN rules for EN 16931. There, BR-62 and BR-63 only check that an address which is present carries a scheme ID.

For a foreign supplier this matters in practice: R010 and R020 are Peppol BIS Billing 3.0 rules that KoSIT adopted, so an invoice that passes Peppol BIS validation already carries both addresses. An invoice exported from a domestic template in another country may not.

The template: UBL and CII

Example: Muster GmbH invoices Beispiel AG with invoice RE-2026-0042. Both use an e-mail address as their electronic address. UBL excerpt, abridged to the relevant elements:

<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID schemeID="EM">rechnung@muster-gmbh.de</cbc:EndpointID>  <!-- BT-34 -->
    <cac:PartyName><cbc:Name>Muster GmbH</cbc:Name></cac:PartyName>
    <!-- PostalAddress, PartyTaxScheme, PartyLegalEntity, Contact ... -->
  </cac:Party>
</cac:AccountingSupplierParty>
<cac:AccountingCustomerParty>
  <cac:Party>
    <cbc:EndpointID schemeID="EM">eingangsrechnungen@beispiel-ag.de</cbc:EndpointID>  <!-- BT-49 -->
    <cac:PartyName><cbc:Name>Beispiel AG</cbc:Name></cac:PartyName>
  </cac:Party>
</cac:AccountingCustomerParty>

In cac:Party, cbc:EndpointID comes before cac:PartyIdentification and cac:PartyName; only the rarely used cbc:WebsiteURI and cbc:LogoReferenceID may precede it. Put it further down and the XML Schema check fails before any business rule runs.

The same values in CII (Cross Industry Invoice), also abridged:

<ram:SellerTradeParty>
  <ram:Name>Muster GmbH</ram:Name>
  <!-- DefinedTradeContact, PostalTradeAddress ... -->
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="EM">rechnung@muster-gmbh.de</ram:URIID>  <!-- BT-34 -->
  </ram:URIUniversalCommunication>
  <!-- SpecifiedTaxRegistration ... -->
</ram:SellerTradeParty>
<ram:BuyerTradeParty>
  <ram:Name>Beispiel AG</ram:Name>
  <!-- PostalTradeAddress ... -->
  <ram:URIUniversalCommunication>
    <ram:URIID schemeID="EM">eingangsrechnungen@beispiel-ag.de</ram:URIID>  <!-- BT-49 -->
  </ram:URIUniversalCommunication>
</ram:BuyerTradeParty>

In CII the electronic address sits after ram:PostalTradeAddress and before ram:SpecifiedTaxRegistration. For namespaces and the overall document layout, see XRechnung XML structure. A complete sample file is available as an XRechnung example.

Field by field

FieldUBL pathCII pathMeaning per the specificationRules
BT-34cac:AccountingSupplierParty/cac:Party/cbc:EndpointIDram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIIDSeller address to which an application-level response to the invoice can be sentPEPPOL-EN16931-R020, BR-62, BR-CL-25
BT-49cac:AccountingCustomerParty/cac:Party/cbc:EndpointIDram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIIDBuyer address to which the invoice should be sentPEPPOL-EN16931-R010, BR-63, BR-CL-25
Scheme IDattribute @schemeIDattribute @schemeIDHow the address is formed: a code from the EAS list maintained by the Connecting Europe FacilityBR-62, BR-63, BR-CL-25

Both fields have cardinality 1 in XRechnung 3.0.2: exactly one address per party. For the scheme ID, the specification references EAS code list version 9.0 (XRepository identifier urn:xoev-de:kosit:codeliste:eas_5).

The rules, word for word

This is how the rules read in the Schematron of KoSIT validator configuration 2026-08-31 (XRechnung 3.0.2). All five have level "fatal", so a single hit makes the file invalid:

RuleMessage in the validation report
PEPPOL-EN16931-R010Buyer electronic address MUST be provided
PEPPOL-EN16931-R020Seller electronic address MUST be provided
BR-62The Seller electronic address (BT-34) shall have a Scheme identifier.
BR-63The Buyer electronic address (BT-49) shall have a Scheme identifier.
BR-CL-25Endpoint identifier scheme identifier MUST belong to the CEF EAS code list

If one of these messages is on your screen right now, the guide to fixing XRechnung validation errors covers the other frequent rejections as well.

Variants: which scheme ID for which case?

Rule BR-CL-25 in the CEN Schematron 1.3.16 shipped with configuration 2026-08-31 accepts exactly 104 codes: four-digit numbers such as 0088 or 9930, plus the letter codes AN, AQ, AS, AU and EM. These are the ones you will meet most in German invoices:

Scheme IDWhat goes in the elementTypical useExample value
EMe-mail addressB2B invoice sent by e-mail, invoice intake mailboxrechnung@muster-gmbh.de
0204Leitweg-ID without prefixinvoice to a German authority, buyer BT-4904011000-1234512345-06
9930German VAT IDcompany sending or receiving via PeppolDE123456789
0088Global Location Number (GLN)retail and manufacturing with GLN master data13-digit GLN
0060D-U-N-S numbergroups that manage suppliers by D-U-N-S9-digit number
XR01 to XR03identifiers for digital health applications (DiGA) and healthcare providers under German social law (SGB V)Extension XRechnung onlyas specified by the recipient

The names of 0204 ("Peppol-Leitweg-ID"), 9930 ("Germany VAT number"), 0088 and 0060 come from the EAS code list published by OpenPEPPOL (opens in a new tab); the federal e-invoicing service names EM and 0204 explicitly. Codes XR01 to XR03 are defined by the XRechnung specification itself: in the Extension, rule BR-DEX-07 replaces the BR-CL-25 check and adds these three values. That is why the KoSIT configuration lowers BR-CL-25 to "information" in the Extension scenarios.

Which variant should you choose?

  1. The customer specifies one: use exactly that value and scheme ID. Authorities usually give a Leitweg-ID (buyer reference, BT-10); groups connected to Peppol give their Peppol ID.
  2. No instruction, delivery by e-mail: EM with the address you actually send the invoice to. For BT-34, use your own mailbox for responses about invoices.
  3. Delivery via Peppol: the participant ID on the envelope and the electronic address in the invoice should match. How Peppol IDs relate to the Leitweg-ID is explained in Germany Peppol ID vs Leitweg-ID.

Common errors and how to fix them

ErrorSymptom in the reportFix
Buyer has no electronic addressPEPPOL-EN16931-R010ask the customer for their intake address and put it in BT-49
cbc:EndpointID without schemeIDBR-62 (seller) or BR-63 (buyer)add the scheme ID, e.g. EM
Scheme ID written as EMAIL, SMTP or emBR-CL-25write exactly EM in capitals
schemeID="0204" with value 0204:04011000-…no rule fires, but the address is wrongremove the prefix from the value; it belongs in the attribute only
9930 with a German tax number (Steuernummer) instead of the VAT IDno rule fires, but the address cannot be resolveduse 9930 only with the VAT ID in the format DE123456789
Company e-mail only in BT-34, no contactBR-DE-2 (seller contact BG-6 missing)add a contact with name, phone and e-mail BT-43

The last row is a frequent mix-up. The XRechnung specification separates the delivery address BT-34 from the contact e-mail BT-43 in group BG-6: BR-DE-2 requires the seller contact group and BR-DE-7 the contact e-mail inside it. The same address may appear in both places, but it has to appear twice.

All other required fields with path and rule are listed in XRechnung mandatory fields.

How to check the electronic address with docutools.pro

  1. Generate the invoice. To create an XRechnung, fill in the "Company" step. The seller's "Email (electronic address)" field is required and becomes BT-34 with scheme ID EM. For the buyer, the generator writes the e-mail with EM into BT-49; if it is empty, it uses the buyer's VAT ID with 9930. Leave both empty and BT-49 is missing. A Leitweg-ID entered under "Buyer reference / Leitweg-ID" goes into BT-10, not BT-49. Under "Export", choose "XRechnung XML".
  2. Validate the file. Upload the XML to the XRechnung validator. The file is sent to our server and checked the way the KoSIT validator does with configuration 2026-08-31. A missing address or scheme ID shows up as R010, R020, BR-62, BR-63 or BR-CL-25, and the result reads "Not KoSIT-conformant". The free plan allows 2 uploads per day up to 500 KB; the Pro plan removes the limits.
  3. Fix it at the source. Smart Repair in the viewer does not edit electronic addresses. Correct the master data in your invoicing software and export the file again. Explanations of other messages are collected in our XRechnung error codes reference.

More guides on fields, portals and versions are in the XRechnung category.

Sources

Last reviewed: November 2026

This article is general information, not tax or legal advice.

Tags:XRechnungBT-34BT-49EAS code listUBL

Tools for this article

Frequently asked questions

What scheme ID should I use for an e-mail address in XRechnung?

Use the scheme ID EM. In UBL that is cbc:EndpointID with the attribute schemeID set to EM, which is the example the German federal e-invoicing service gives for BT-34 and BT-49. EM is on the EAS code list that KoSIT rule BR-CL-25 checks. Other spellings such as EMAIL, MAIL or SMTP are not on the list and make the invoice fail validation.

Is the buyer electronic address mandatory for B2B invoices in Germany?

Yes, if the invoice is an XRechnung. Rule PEPPOL-EN16931-R010 applies to every XRechnung 3.0.2 invoice, whether the buyer is a public authority or a private company. Ask your customer for their invoice intake address. In the plain EN 16931 scenario of the KoSIT validator, for example for a ZUGFeRD invoice in the EN 16931 profile, BT-49 is optional.

How do I fix the error Seller electronic address MUST be provided?

Add cbc:EndpointID as one of the first children of cac:Party inside cac:AccountingSupplierParty, with a scheme ID such as EM and your invoicing mailbox as the value. In CII, add ram:URIUniversalCommunication with ram:URIID to ram:SellerTradeParty. Fix it in your invoicing software's master data, then generate the file again and re-validate it.

Can a Peppol participant ID be used as the electronic address?

Yes. The electronic address is designed for that: scheme ID plus identifier. A German company reachable on Peppol with its VAT ID uses scheme 9930 and the value DE123456789, without the 9930 prefix and colon in the element text. A German authority on the federal OZG-RE portal is addressed with scheme 0204 and its Leitweg-ID. Use the value your customer gives you.

Topic hubMore on XRechnungStructure, mandatory fields, Leitweg-ID and submission of XRechnung, Germany's standard for structured e-invoices.