BR-CL-01:Invalid invoice type code
The invoice type code is not a valid value from the UN/EDIFACT code list 1001. Valid codes include 380 for a standard invoice, 381 for a credit note, 383 for a debit note, 384 for a corrected invoice, 386 for a prepayment invoice, and 389 for a self-billed invoice.
Engine Classification
Normalizes invoice type code using UNTDID 1001 alias mapping and defaults to 380 (Commercial Invoice)
Confidence: 85% · Applied automatically in pipeline
What is BR-CL-01?
BR-CL-01 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoiceTypeCode element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: cbc:InvoiceTypeCode
Why This Error Matters
Invoice rejected. Document type must be a recognized code for automated processing.
BR-CL-01 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-CL-01
- ·Specification: EN 16931
How to Fix It
Identify the document type
Is this a regular invoice (380), credit note (381), corrected invoice (384), or prepayment invoice (386)?
Set the correct code
Replace the invalid type code with the correct numeric code for your document type.
Update your template
If this happens on every invoice, check your ERP or invoicing software template settings.
Before / After
<Invoice> <cbc:DocumentCurrencyCode>INVALID_CODE</cbc:DocumentCurrencyCode> </Invoice>
<Invoice> <cbc:DocumentCurrencyCode>VALID_CODE</cbc:DocumentCurrencyCode> </Invoice>
Technical Reference
cbc:InvoiceTypeCodeCommon Causes
- ·Invoice type code field left empty or set to text like 'Invoice'
- ·Non-standard code used (e.g. 0, 1, or a text value)
- ·ERP system uses internal codes instead of UNTDID 1001
Seeing this in production? The API handles BR-CL-01 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Document type code must be from UNTDID 1001 subset.
Use valid code: 380 (invoice), 381 (credit note), 384 (corrected), etc. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-CL-01 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
Many instances of BR-CL-01 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice type code invalid.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-CL-01 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.