Reference
Markdown exportBT-8 VAT point date code
Code that explains how the VAT point date was determined.
Quick answer
Invoice basics
Core document identifiers, dates, process identifiers, and high-level invoice context.
Quick actions
In plain language
Code that explains how the VAT point date was determined.
Code that explains how the VAT point date was determined.
Use this field only when tax law requires the invoice to explain the rule behind the VAT point date.
What you usually enter here
Approved VAT point date code
Typical valid values include: 3, 35
Optional according to EN 16931-1. Use the approved code list when it is present.
What goes wrong often
Avoid values like: VAT date, 03
Examples in context
Use this field only when tax law requires the invoice to explain the rule behind the VAT point date.
Optional according to EN 16931-1. Use the approved code list when it is present.
Valid Examples
- 3
- 35
Invalid Examples
- VAT date
- 03
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-8
Data Type:
code
Cardinality:
0..1
Requirement:
Optional
Max Length:
4 characters
Since Version:
Optional
XML Implementation
/Invoice/cbc:TaxPointDateCode/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:TaxPointDateCodeNext 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 field only when tax law requires the invoice to explain the rule behind the VAT point date.
Legal Requirement
Optional according to EN 16931-1. Use the approved code list when it is present.