Peppol BIS Billing 3.0 · rule
UBL-DT-18
What does UBL-DT-18 mean? Name attribute should not be present
Why did my invoice fail UBL-DT-18?
The name attribute should not be present on code elements in an EN 16931 UBL invoice. The code value itself is sufficient; a human-readable name attribute is outside the core model and triggers a warning. Remove it.
Official rule text
Name attribute should not be present
Common causes
- Generator adds name="..." as a label next to each code
- Note: the one exception in Peppol usage is DocumentTypeCode/related patterns defined by the specification itself — generic codes must not carry name
How do I fix it?
<cbc:PaymentMeansCode>30</cbc:PaymentMeansCode>
Related rules
UBL-DT-01 · UBL-DT-06 · UBL-DT-07 · UBL-DT-08 · UBL-DT-09 · UBL-DT-10 · UBL-DT-11 · UBL-DT-12
Check your invoice against this rule
Paste it into the live demo, or call POST /v1/validate. See the quickstart.