Skip to content

Fatal

BR-RO-DT004: Delivery date must be written as YYYY-MM-DD

In short

Fatal: fails the selected checks.

BR-RO-DT004 means the delivery date (BT-72) 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-05 for 5 November 2026.

On this page

What it means

The delivery date (BT-72), the date the goods were delivered or the services supplied, must be exactly 10 characters in the form YYYY-MM-DD, and it must be a date that exists. 2026-11-05 passes, while 05.11.2026, 2026-11-5, 2026-11-05T08:00:00 and 2026-02-30 fail, as do spaces around the date. The rule only applies when the invoice gives a delivery date.

Why it matters

The delivery date records when the supply took place, so the system needs a date it can read. A date in another format, or one that does not exist, is rejected, and the invoice with it.

How to fix it

Find the delivery date on the invoice. Your software may call it the date of supply, service date or ship date. Re-enter it with the date picker and check that the e-invoice export writes it as year-month-day with hyphens and nothing after the day.

The rule as published

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

Business terms: BT-72, BT-73, BT-134

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-DT004 still fails, and which other rules do.

Updated 6 November 2026