What it means
This rule checks the format attribute on udt:DateTimeString inside rsm:ExchangedDocument/ram:IssueDateTime against the EN 16931 profile's permitted date-format codes for Factur-X and ZUGFeRD. An empty value passes this particular test. It does not check the date text or require the invoice date; BR-03 addresses the date's presence separately.
Why it matters
The format code describes how to interpret the invoice date text. The code and text need to describe the same date representation.
How to fix it
Check the invoice date in your source invoice. In rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString, write the full date as YYYYMMDD without separators and set format to 102. Correct the exporter if it generates a different code, then export and check the new 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 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000554 still fails, and which other rules do.
Related rules
- FX-SCH-A-000555 Use a permitted invoice type code
- FX-SCH-A-000556 Use a permitted specification identifier
- FX-SCH-A-000557 Give the invoiced-object reference one identifier
- FX-SCH-A-000558 Keep one type code in the invoiced-object reference
- FX-SCH-A-000559 A reference to the invoiced object must use the type code 130
- FX-SCH-A-000560 A tender or lot reference needs exactly one identifier