What it means
This rule checks a non-empty format attribute on ram:BillingSpecifiedPeriod/ram:StartDateTime/udt:DateTimeString under ram:ApplicableHeaderTradeSettlement. Use 102 for YYYYMMDD. It concerns the invoice-level invoicing period (BG-14), not a line period. An empty format value passes this code-list test; it does not check the date itself.
Why it matters
The format code declares how to read the invoicing period start date. This check does not establish whether the period is correct or how a recipient will handle the invoice.
How to fix it
Correct the export of the invoice-level period start date (BT-73). In CII XML, write the intended date as YYYYMMDD in ram:BillingSpecifiedPeriod/ram:StartDateTime/udt:DateTimeString and set format="102". If you cannot control that output, ask your software supplier to correct it. Regenerate and recheck your 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 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-000594 still fails, and which other rules do.
Related rules
- FX-SCH-A-000595 Use a listed invoice currency code
- FX-SCH-A-000596 Use format 102 for the preceding invoice date
- FX-SCH-A-000597 Use a listed payee identifier scheme
- FX-SCH-A-000598 Use a listed payee registration scheme
- FX-SCH-A-000599 Use a listed invoice-level discount VAT category
- FX-SCH-A-000600 Check the tax type for the invoice discount