Skip to content

Fatal

BR-NL-7: Use an allowed document type code: 380, 381, 384 or 389

In short

Fatal: fails the selected checks.

BR-NL-7 means the document type code is not one of 380, 381, 384 or 389. Fix it by setting the document type to an invoice (380), credit note (381), corrective invoice (384) or self-billed invoice (389).

On this page

What it means

The document type code (BT-3) must be 380 (invoice), 381 (credit note), 384 (corrective invoice) or 389 (self-billed invoice). In a UBL file it sits in the invoice type code or the credit note type code. In the CII rule set the same four values are checked in the type code of the CII document.

Why it matters

The type code tells the recipient how to book the document. The Dutch NLCIUS rules accept only these four, so any other code, even one that other rule sets accept, fails the check and the invoice is rejected.

How to fix it

Check the document type in your invoicing software. A normal invoice should be 380 and a credit note 381. If your software lets you set the code by hand, change it to one of the four. If it is a document that is not an invoice at all, it should not be sent as an e-invoice.

The rule as published

The invoice or credit note type code (cbc:InvoiceTypeCode/cbc:CreditNoteTypeCode) MUST have one of the following values: 380, 381, 384, 389

Where NLCIUS (CII) run it, the rule reads:

The invoice type code (ram:TypeCode) MUST have one of the following values: 380, 381, 384, 389

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

Updated 6 November 2026