What it means
This rule checks a non-empty format attribute on udt:DateTimeString within the delivery event against the profile's date-format code list. Format 102 denotes a year, month and day without separators or a time. The test does not check the date text or whether it is a valid calendar date.
Why it matters
The format code describes how software should interpret the delivery date's text.
How to fix it
On ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString under ram:ApplicableHeaderTradeDelivery, set format to 102 and ensure the date text uses YYYYMMDD. If you cannot control this XML attribute, give the field and rule id to your software supplier so they can check the export. Recheck the corrected file.
Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta
The rule as published
Value of '@format' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000505 still fails, and which other rules do.
Related rules
- FX-SCH-A-000506 Check the delivery location identifier's scheme
- FX-SCH-A-000507 Use an allowed country code for the delivery address
- FX-SCH-A-000508 Use an allowed VAT category code
- FX-SCH-A-000509 Use 5, 29 or 72 for the VAT point date code
- FX-SCH-A-000510 Use an allowed VAT exemption reason code
- FX-SCH-A-000511 Use VAT as the tax type code