What it means
In the Basic WL profiles of Factur-X and ZUGFeRD, this rule checks the format code on ram:BillingSpecifiedPeriod/ram:EndDateTime/udt:DateTimeString under ram:ApplicableHeaderTradeSettlement against the profile's date-format list. An empty code value passes this test. FX-SCH-A-000460 checks whether the attribute exists, not whether it is filled in.
Why it matters
The profile defines which format codes you can use to describe the date representation. This check does not establish whether a recipient could otherwise interpret the date.
How to fix it
Use a date-format code allowed by Basic WL and make the date text follow that format. If you use 102, write the date as YYYYMMDD without separators. Correct both the attribute and the date text where necessary, then export and recheck the invoice.
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 WL | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000461 still fails, and which other rules do.
Related rules
- FX-SCH-A-000462 Add the format attribute to the invoice period start date
- FX-SCH-A-000463 Use an allowed format for the invoice period start date
- FX-SCH-A-000464 Use an allowed invoice currency code
- FX-SCH-A-000465 Add the format attribute to the earlier invoice date
- FX-SCH-A-000466 Use an allowed format for the earlier invoice date
- FX-SCH-A-000467 Keep at most one ram:ID for the payee