Skip to content

Fatal

BR-NL-9: A corrective invoice must refer to the invoice it corrects

In short

Fatal: fails the selected checks.

BR-NL-9 means the document is a corrective invoice (type code 384) but does not say which earlier invoice it corrects. Fix it by adding the invoice number of the original invoice as the preceding invoice reference.

On this page

What it means

When the document type code (BT-3) is 384, the file must contain a reference to the earlier invoice (BT-25), which is its invoice number. The check only looks that the reference is present. It does not check that the number exists.

Why it matters

A correction only makes sense next to the invoice it corrects. Without the reference the recipient cannot link it to the original, so the file fails the check and the invoice is rejected.

How to fix it

In your invoicing software, create the correction from the original invoice so the link is carried over, or fill in the field for the original invoice number. You do not need the date of the original invoice, see BR-NL-24. If you are not correcting an earlier invoice, type 384 is the wrong choice: use 380 for a new invoice or 381 for a credit note.

The rule as published

For suppliers in the Netherlands, if the document is a corrective invoice (cbc:InvoiceTypeCode = 384), the document MUST contain an invoice reference (cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID)

Where this rule applies

Rule set Version
SI-UBL 2.0 / NLCIUS (invoice) 2.0.3.13
SI-UBL 2.0 / NLCIUS (credit note) 2.0.3.13
NLCIUS (CII) 1.0.3.13
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether BR-NL-9 still fails, and which other rules do.

Updated 6 November 2026