What the field is for
The specification's description (above, in German) translates as: "The seller's electronic
address, to which the application-level response to an invoice can be sent." BT-34 is the address
to which the buyer or the buyer's system can reply to the invoice — with a message that it was
received or rejected, for example. Every address has a scheme (attribute schemeID) that says
what kind of address it is.
In XRechnung, BT-34 is mandatory (rule PEPPOL-EN16931-R020); in EN 16931 and in ZUGFeRD in the EN 16931 profile it is optional. The buyer's counterpart is BT-49.
The scheme
The scheme comes from the EAS code list (Electronic Address Scheme) of the Connecting Europe Facility. Common in Germany:
| Scheme | Meaning |
|---|---|
EM |
email address |
9930 |
German VAT identification number |
0088 |
GLN (EAN Location Code) |
For a shop that sends its invoices by email, an email address with EM is the simplest way. A
seller who receives through Peppol uses the Peppol identifier.
Which rules check the field
| Rule | What it requires | Level in XRechnung |
|---|---|---|
| PEPPOL-EN16931-R020 | BT-34 is there | error |
| BR-62 | BT-34 has a scheme (schemeID) |
error |
| BR-CL-25 | the scheme is in the EAS code list | error; in the XRechnung extension only information, where BR-DEX-07 checks a longer list |
Where the field is in the file
| Syntax | Element |
|---|---|
| CII | ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID with schemeID |
| UBL | cac:AccountingSupplierParty/cac:Party/cbc:EndpointID with schemeID |
Common mistakes
- The field is missing → PEPPOL-EN16931-R020, the invoice is rejected.
- An address without a scheme → BR-62. For an email address:
schemeID="EM". - A made-up scheme (
email,mail) → BR-CL-25. The codes are fixed and in capitals. - The email is only in the contact (BT-43), not in BT-34.
Example
<!-- CII -->
<ram:SellerTradeParty>
...
<ram:URIUniversalCommunication>
<ram:URIID schemeID="EM">rechnung@example.com</ram:URIID> <!-- BT-34 -->
</ram:URIUniversalCommunication>
...
</ram:SellerTradeParty>
<!-- UBL -->
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="EM">rechnung@example.com</cbc:EndpointID>
...
Sources: KoSIT, XRechnung specification 3.0.2 (BT-34, section 11.28, BR-62, PEPPOL-EN16931-R020, BR-DEX-07); XRechnung 3.0.2 validator configuration (BR-CL-25 and the codes of the EAS list); code lists for EN 16931 v17b in the Factur-X 1.09.2 / ZUGFeRD 2.5.2 package (meaning of the EAS codes).