Skip to content

Error

FX-SCH-A-000460: Add the format attribute to the invoice period end date

In short

Error: fails the selected checks.

FX-SCH-A-000460 means the invoice period end date (BT-74) is missing the format attribute on udt:DateTimeString. Add the attribute to that element. For a date written as YYYYMMDD, use format 102.

On this page

What it means

Within the invoice period (BG-14), this rule checks for a format attribute on ram:BillingSpecifiedPeriod/ram:EndDateTime/udt:DateTimeString under ram:ApplicableHeaderTradeSettlement. It checks presence only: an empty attribute exists and therefore passes this test. It does not check the format code or date text. FX-SCH-A-000462 covers the start date.

Why it matters

The format attribute declares how the date text is encoded.

How to fix it

Correct the end date's XML representation rather than removing a period that belongs on the invoice. Add format to the affected udt:DateTimeString and make its value match the date text. If you use 102, write the date as YYYYMMDD. Have your software's export corrected if 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

Attribute '@format' is required in this context.

Where this rule applies

Rule set Version
Factur-X 1.09 BASIC WL 1.0.9-2
Factur-X 1.09 BASIC 1.0.9-2
Factur-X 1.09 EN 16931 1.0.9-2
Factur-X 1.09 EXTENDED 1.0.9-2
ZUGFeRD 2.5 BASIC WL 2.5.2
ZUGFeRD 2.5 BASIC 2.5.2
ZUGFeRD 2.5 EN 16931 2.5.2
ZUGFeRD 2.5 EXTENDED 2.5.2
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether FX-SCH-A-000460 still fails, and which other rules do.

Updated 6 November 2026