Skip to content

Fatal

BR-RO-DT002: VAT point date must be written as YYYY-MM-DD

In short

Fatal: fails the selected checks.

BR-RO-DT002 means the VAT point date (BT-7) 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 VAT point date (BT-7), the date the VAT becomes due, 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-05T00:00:00 and 2026-02-30 fail, as do spaces before or after the date. The rule only applies when the invoice gives a VAT point date.

Why it matters

The VAT point date decides which VAT period the VAT falls in, so the system has to be able to read it. A date in another format, or one that does not exist, is rejected, and the invoice with it.

How to fix it

Find the VAT point date in your invoicing software, where it may be called the tax point date, VAT date or date of supply for VAT. Re-enter it with the date picker, then check the date format used in the e-invoice export. It must come out as year, month, day with hyphens, with no time and no time zone.

The rule as published

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

Business terms: BT-7

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

Updated 6 November 2026