BR-NL-8: The type code and the UBL layout must agree: 381 is a credit note

What it means

UBL has two layouts, Invoice and CreditNote, each with its own top-level element. The rule checks that a document with document type code (BT-3) 381 uses the CreditNote layout. The variant in the same rule sets checks the other direction: a document with code 380, 384 or 389 must use the Invoice layout, not the CreditNote layout.

Why it matters

The layout and the code are two statements about the same document. When they disagree, the recipient cannot tell whether the document adds to or reduces the amount owed. The file fails the check and the invoice is rejected.

How to fix it

If it is a credit note, create it as a credit note in your invoicing software and export it as a UBL credit note. A common cause is a credit note that went through the invoice template. If it is an invoice, change the type code to 380, or to 384 for a correction.

The rule as published

If the invoice type code (cbc:InvoiceTypeCode) is 381, the document MUST use the CreditNote scheme

Where SI-UBL 2.0 / NLCIUS (invoice), SI-UBL 2.0 / NLCIUS (credit note) run it, the rule reads:

If the credit note type code (cbc:CreditNoteTypeCode) is 380, 384 or 389, the document MUST use the Invoice scheme

Where this rule applies