What it means
The invoice date (BT-2) must be exactly 10 characters in the form YYYY-MM-DD, and it must be a date that exists. So 2026-11-05 is right, while 05/11/2026, 5.11.2026, 2026-11-5, 20261105 and 2026-02-30 are not. A time or time zone after the date, such as 2026-11-05T10:30:00 or 2026-11-05Z, and spaces around the date also fail. The check is written for every issue date element in the file, so it can also catch the date of a preceding invoice (BT-26).
Why it matters
Romania's e-Factura system reads dates in this one fixed format. A date in any other form, or a date that does not exist, cannot be read as the invoice date, so the invoice is rejected.
How to fix it
Open the invoice date in your invoicing software and check that it holds a real date, chosen in a date field rather than typed as text. If the software exports the file, check the date format in its e-invoice export settings and switch it to year-month-day with hyphens. If the XML is built by a script, write the date as plain text with no time and no time zone.
The rule as published
Un element de tip data (BT-2, BT-27) trebuie sa respecte formatul YYYY-MM-DD #A date (BT-2, BT-27) MUST be formatted YYYY-MM-DD. ( = ' … ') Business terms: BT-2, BT-27
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 |
Check your file
Drop your e-invoice to see whether BR-RO-DT001 still fails, and which other rules do.