Skip to content
Theme
English

Fatal

BR-RO-DT003_CN: Payment due date must be written as YYYY-MM-DD

In short

Fatal: fails the selected checks.

BR-RO-DT003_CN means the payment due date, which is the due date (BT-9) in the payment details, 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) given as the payment due date in the payment details must be exactly 10 characters in the form YYYY-MM-DD, and it must be a date that exists. This is the element where a UBL credit note carries its due date, while BR-RO-DT003 covers the due date element used on invoices. 2026-12-05 passes, while 05/12/2026, 2026-12-5, 2026-12-05T00:00:00 and 2026-11-31 fail.

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 document, so it is rejected.

How to fix it

Open the payment details of the credit note and check the payment due date, or due date, in your software. Make sure it holds a real date and that the e-invoice export writes it as year-month-day with hyphens, with no time or time zone. If invoices pass but credit notes fail, ask your software supplier to check the credit note export, because it writes the date in a different element.

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

Updated 6 November 2026