Skip to content

Fatal

BR-RO-DT006: Period end date must be written as YYYY-MM-DD

In short

Fatal: fails the selected checks.

BR-RO-DT006 means a period end date (BT-74 or BT-135) is not written as YYYY-MM-DD, or is not a real calendar date. Fix it by writing it as year, month and day with hyphens, for example 2026-11-30 for 30 November 2026.

On this page

What it means

The end date of the invoice period (BT-74), or of the period of a single line (BT-135), must be exactly 10 characters in the form YYYY-MM-DD, and it must be a date that exists. 2026-11-30 passes, while 30/11/2026, 2026-11-3, 2026-11-30T00:00:00 and 2026-11-31 fail, as do spaces around the date. The rule only applies when the invoice or a line gives a period end date.

Why it matters

The period tells the buyer which stretch of time the invoice or line covers. If the system cannot read the end date, the invoice is rejected.

How to fix it

Find the period end on the invoice, or on the line if the period is set per line. It may be called the billing period to, service end or period end date in your software. Re-enter it as a real date, then check that the e-invoice export writes it as year-month-day with hyphens, with no time or time zone.

The rule as published

Un element de tip data (BT-74, BT-135) trebuie sa respecte formatul YYYY-MM-DD #A date (BT-74, BT-135) MUST be formatted YYYY-MM-DD. ( = ' … ')

Business terms: BT-74, BT-135

Where this rule applies

Rule set Version
CIUS-RO UBL Invoice 1.0.9 1.0.9
CIUS-RO UBL Credit Note 1.0.9 1.0.9
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether BR-RO-DT006 still fails, and which other rules do.

Updated 6 November 2026