erroren16931

BR-CL-01:Invoice type code invalid

Document type code must be from UNTDID 1001 subset.

We can fix this automatically

AUTO-FIX

Auto-fix: Map common variations to standard UNTDID 1001 codes. "invoice"→380, "credit"→381. If unrecognizable, default to 380 for standard invoices.

No manual changes needed
Upload and Fix Now

Why This Error Matters

Invoice rejected. Document type must be a recognized code for automated processing.

How to Fix It

1

Check type code

Find InvoiceTypeCode value

2

Use valid code

380, 381, 383, 384, 385, 386, 389, 390 are common

Technical Details

XPath: /Invoice/cbc:InvoiceTypeCode

Common Causes

  • Invoice type code not from UNTDID 1001 list
  • Custom document type code used instead of standard
  • Type code stored as text description not numeric code
  • Credit note using invoice code or vice versa
  • Legacy system type codes not mapped to UNTDID 1001

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

EN 16931 Validator

Check your invoice now

Related Errors

BR-CO-03

VAT point date and VAT point date code are mutually exclusive

Last updated: 16 January 2026

Share this guide: