Reference
Markdown exportBT-58 Buyer contact email address
Email address for the buyer contact point.
Quick answer
Buyer details
Who receives the invoice and which buyer records or routing data must match.
Quick actions
In plain language
This helps invoice follow-up reach the right mailbox when the buyer processes invoices centrally.
What you usually enter here
Email address
Typical valid values include: ap@buyer.example
Optional according to EN 16931-1.
Where the field sits
- Invoice
- cac:AccountingCustomerParty
- cac:Party
- cac:Contact
- cbc:ElectronicMailBT-58
- rsm:CrossIndustryInvoice
- rsm:SupplyChainTradeTransaction
- ram:ApplicableHeaderTradeAgreement
- ram:BuyerTradeParty
- ram:DefinedTradeContact
- ram:EmailURIUniversalCommunication
- ram:URIIDBT-58
What goes wrong often
Avoid values like: not-an-email
Valid Examples
- ap@buyer.example
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-58
Data Type:
text
Cardinality:
0..1
Requirement:
Optional
Max Length:
100 characters
XML Implementation
/Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication/ram:URIIDNext step
Create an XRechnung from your PDF
The converter reads the invoice and shows the fields it found before download, so you can check and correct the values. No PDF? Fill in the XRechnung directly in the form.
Download requires an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.