BR-52:Each Additional supporting document (BG-24) shall contain a Supporting...
InvoiceTypeCode must be a valid UNTDID 1001 document type code.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Invoice Type Code
What is BR-52?
BR-52 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoiceTypeCode element under Invoice 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: XPath: /Invoice/cbc:InvoiceTypeCode
Why This Error Matters
Invoice rejected. Supporting documents must be identifiable for audit and reference purposes.
BR-52 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.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-52
- ·Specification: EN 16931
How to Fix It
Common codes
380=invoice, 381=credit note, 384=corrected, 389=self-billing
Check document
Match code to actual document type
CreditNote separate
Credit notes use CreditNote root, not InvoiceTypeCode=381
Before / After
<Invoice> <cac:AdditionalDocumentReference><!-- invalid or missing value --></cac:AdditionalDocumentReference> </Invoice>
<Invoice> <cac:AdditionalDocumentReference>correct-value</cac:AdditionalDocumentReference> </Invoice>
Technical Reference
XPath: /Invoice/cbc:InvoiceTypeCodeCode Example
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<!-- For credit notes, use CreditNote document type -->Common 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
Seeing this in production? The API handles BR-52 automatically. See the fix response →
Commonly Seen In
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.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-52 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.