BR-NL-8Credit note sent as an invoice (or the other way round)

ErrorSI-UBL 2.0 / NLCIUSBT-3

Also in:Nederlands

What it means

In SI-UBL 2.0 a credit note (type 381) must be sent as a UBL CreditNote document, and a CreditNote document must have type 381. Invoices (380, 384, 389) use the UBL Invoice document.

Official message

Rejects the invoice (fatal)
[BR-NL-8] If the invoice type code (cbc:InvoiceTypeCode) is 381, the document MUST use the CreditNote scheme

SI-UBL 2.0 (NLCIUS) validation artefacts 2.0.3.13, Peppol Authority NL, released 21 May 2026 · Read the rule at the source

Text compared with the published file on 17 November 2026.

Typical causes

  • The software writes credit notes as an Invoice document with type code 381.
  • A CreditNote document was given the type code 380.

How to fix it

  1. Export credit notes as a CreditNote document with CreditNoteTypeCode 381.
  2. Use the Invoice document for codes 380, 384 and 389.
  3. Check the export setting for credit notes and send the document again.

Check your invoice for BR-NL-8

Open the free validator with BR-NL-8 already explained: paste or upload your XML and the finding, if any, is highlighted with its exact line.

Check my invoice

3 free validations a month without an account. Invoice contents are never stored.

What the rule says (technical)

Type code 381 MUST be sent as a UBL CreditNote, and a UBL CreditNote MUST have type code 381; codes 380, 384 and 389 use the UBL Invoice.

Export credit notes as CreditNote documents (root <CreditNote>, CreditNoteTypeCode 381), or give a normal invoice type code 380.

More errors with a worked fix

Related rules