Reference
Markdown exportBT-56 Buyer contact point
Contact person or department on the buyer side.
Quick answer
Buyer details
Who receives the invoice and which buyer records or routing data must match.
Quick actions
In plain language
Contact person or department on the buyer side.
Contact person or department on the buyer side.
Use this when the invoice needs to name the operational recipient instead of only the legal buyer entity.
What you usually enter here
Person or department name
Typical valid values include: AP Team
Optional according to EN 16931-1.
What goes wrong often
Avoid values like:
Examples in context
Use this when the invoice needs to name the operational recipient instead of only the legal buyer entity.
Optional according to EN 16931-1.
Valid Examples
- AP Team
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-56
Data Type:
text
Cardinality:
0..1
Requirement:
Optional
Max Length:
100 characters
Since Version:
Optional
XML Implementation
/Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:Name/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:PersonNameNext 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.
Why the standard cares about this field
Business Context
Use this when the invoice needs to name the operational recipient instead of only the legal buyer entity.
Legal Requirement
Optional according to EN 16931-1.