errorpeppol-bis-3
BR-52:Invalid invoice type code
InvoiceTypeCode must be a valid UNTDID 1001 document type code.
We can help you fix this
NEEDS INPUTRequires user input: Document reference number or identifier. Cannot auto-generate because references often follow organizational naming conventions.
Simple form - we handle the XML for you
Upload and Answer QuestionsWhy This Error Matters
Invoice rejected. Supporting documents must be identifiable for audit and reference purposes.
How to Fix It
1
Common codes
380=invoice, 381=credit note, 384=corrected, 389=self-billing
2
Check document
Match code to actual document type
3
CreditNote separate
Credit notes use CreditNote root, not InvoiceTypeCode=381
Code Example
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<!-- For credit notes, use CreditNote document type -->Technical Details
XPath: /Invoice/cbc:InvoiceTypeCodeCommon Causes
- Supporting document added without reference ID
- AdditionalDocumentReference/ID not mapped
- Attachment uploaded without document number
- Template missing document reference field
- Reference generated but not included in export
Commonly Seen In
All invoicing software
Frequently Asked Questions
InvoiceTypeCode must be a valid UNTDID 1001 document type code.
Use valid invoice type code. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-52 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-52 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid invoice type code.
BR-52 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Last updated: 18 January 2026
Share this guide: