Skip to content

Fatal

BR-RO-DT003: Due date must be written as YYYY-MM-DD

In short

Fatal: fails the selected checks.

BR-RO-DT003 means the due date (BT-9) 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-12-05 for 5 December 2026.

On this page

What it means

The due date (BT-9), the last day for payment, must be exactly 10 characters in the form YYYY-MM-DD, and it must be a date that exists. 2026-12-05 passes, while 05/12/2026, 5 Dec 2026, 2026-12-5 and 2026-11-31 fail. A time, a time zone or spaces around the date make the text longer than 10 characters and fail too. This rule checks the due date element used on invoices; BR-RO-DT003_CN checks the one used on credit notes.

Why it matters

The due date tells the buyer when to pay. If the system cannot read it as a date, it cannot accept the invoice, so the invoice is rejected.

How to fix it

Check the due date on the invoice. If your software works it out from the payment terms, for example the invoice date plus 30 days, make sure the result is a real date and that the e-invoice export writes it as year-month-day with hyphens. If the export adds a time or time zone after the date, ask your software supplier for the e-invoice date setting.

The rule as published

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

Business terms: BT-9

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

Updated 6 November 2026