What it means
In the Basic profiles of Factur-X and ZUGFeRD, this rule checks the format code on rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString against the profile's date format code list. An empty checked value passes. This test does not check the date text or require the format attribute to exist.
Why it matters
The format code identifies how your invoice date is encoded. This check does not determine the bookkeeping period or whether the date itself is valid.
How to fix it
Use a date format permitted by Basic and write the invoice date in that format. For YYYYMMDD, set format="102" on the udt:DateTimeString inside ram:IssueDateTime. If your software writes an unsupported code, ask its supplier to correct the export, then export and recheck.
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-000491 still fails, and which other rules do.
Related rules
- FX-SCH-A-000492 Use an allowed invoice type code (Basic)
- FX-SCH-A-000493 Use a specification identifier allowed by Basic
- FX-SCH-A-000494 Use an allowed buyer identifier scheme (Basic)
- FX-SCH-A-000495 Use an allowed buyer country code (Basic)
- FX-SCH-A-000496 Use an allowed buyer registration scheme (Basic)
- FX-SCH-A-000497 Use an allowed buyer tax registration scheme (Basic)