Reference
Markdown exportBT-43 Seller contact email address
Email address for the seller contact point.
Quick answer
Seller details
Who issued the invoice and how the recipient can identify that business reliably.
Quick actions
In plain language
This address routes invoice questions to the seller contact.
What you usually enter here
Email address
Typical valid values include: billing@example.com
Optional in base EN 16931. XRechnung requires seller contact group BG-6 through BR-DE-2 and requires BT-43 through BR-DE-7.
Where the field sits
- Invoice
- cac:AccountingSupplierParty
- cac:Party
- cac:Contact
- cbc:ElectronicMailBT-43
- rsm:CrossIndustryInvoice
- rsm:SupplyChainTradeTransaction
- ram:ApplicableHeaderTradeAgreement
- ram:SellerTradeParty
- ram:DefinedTradeContact
- ram:EmailURIUniversalCommunication
- ram:URIIDBT-43
What goes wrong often
Avoid values like: not-an-email
Relevant rule codes: BR-DE-2, BR-DE-7
Valid Examples
- billing@example.com
Invalid Examples
- not-an-email
XML mapping and field facts
Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.
Field ID:
BT-43
Data Type:
text
Cardinality:
1..1
Requirement:
Mandatory
Max Length:
100 characters
Since Version:
XRechnung 1.0+
XML Implementation
/Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication/ram:URIIDValidation Rules
BR-DE-2
BR-DE-2
BR-DE-7
BR-DE-7
Next step
Check whether your XRechnung sets BT-43 correctly
Upload the XML file to the free validator. It applies the KoSIT rules for XRechnung 3.0 and names each finding with its rule ID, for this field for example BR-DE-2, BR-DE-7. Creating a new invoice instead? The converter checks the invoice against the same rules and shows the findings before download.
Free, no account needed. XML file up to 2 MB.