errorbusinessEN 16931

`BR-52`:Each Additional supporting document (BG-24) shall contain a Supporting...

Fix: This requires user input to resolve. Provide the correct value for `cac:AdditionalDocumentReference` (BG-24). Provide the required value in the free validator.

InvoiceTypeCode must be a valid UNTDID 1001 document type code.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

INPUT REQUIRED

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 rejected by Peppol access points and never reaches the buyer.

Target path: XPath: /Invoice/cbc:InvoiceTypeCode

Fix this error

Why This Error Matters

Invoice rejected. Supporting documents must be identifiable for audit and reference purposes.

BR-52 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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

Failing XML

<Invoice>
  <cac:AdditionalDocumentReference><!-- invalid or missing value --></cac:AdditionalDocumentReference>
</Invoice>

Corrected XML

<Invoice>
  <cac:AdditionalDocumentReference>correct-value</cac:AdditionalDocumentReference>
</Invoice>

Technical Reference

XPathXPath: /Invoice/cbc:InvoiceTypeCode

SpecEN 16931

StrategyRequires user input: Document reference number or identifier. Cannot auto-generate because references often follow organizational naming conventions.

Code 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

All invoicing software

Frequently Asked Questions

InvoiceTypeCode must be a valid UNTDID 1001 document type code.

This requires user input to resolve. Provide the correct value for `cac:AdditionalDocumentReference` (BG-24). Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.

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.

BR-52 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.

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

BR-04Missing invoice type code

Validate your invoice

Drop your XML here to check for BR-52

Upload XML

Fix BR-52 with guided input

Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.

Fix it now Automate via API

BR-52:Each Additional supporting document (BG-24) shall contain a Supporting...