errorEN 16931

BR-CL-24:For Mime code in attribute use MIMEMediaType (IANA media types).

An attached document has an invalid MIME type code. MIME types must follow the standard format (type/subtype), such as application/pdf for PDF files, image/png for PNG images, or text/csv for CSV files.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
90%
Category
codelist

Engine Classification

Maps file extensions and common invalid MIME types to valid IANA media types

Confidence: 90% · Applied automatically in pipeline

What is BR-CL-24?

BR-CL-24 is a fatal validation rule defined in the EN 16931 specification. It validates the @mimeCode element under Attachment > EmbeddedDocumentBinaryObject 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: cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@mimeCode

Why This Error Matters

Invoice rejected. Attachments must have valid MIME types for proper handling.

BR-CL-24 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-24
  • ·Specification: EN 16931

How to Fix It

1.

Identify the file type

What kind of file is attached? PDF, PNG, XML, CSV, etc.

2.

Use the correct MIME type

Common types: application/pdf, image/png, image/jpeg, text/csv, application/xml, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet (for Excel).

3.

Update the mimeCode attribute

Set the mimeCode attribute on the EmbeddedDocumentBinaryObject to the correct MIME type.

Before / After

Failing XML
<cbc:EmbeddedDocumentBinaryObject>
  <@mimeCode>INVALID_CODE</@mimeCode>
</cbc:EmbeddedDocumentBinaryObject>
Corrected XML
<cbc:EmbeddedDocumentBinaryObject>
  <@mimeCode>VALID_CODE</@mimeCode>
</cbc:EmbeddedDocumentBinaryObject>

Technical Reference

XPathcac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@mimeCode
SpecEN 16931
Operationlookup
StrategyMaps file extensions and common invalid MIME types to valid IANA media types

Common Causes

  • ·MimeCode set to file extension instead of MIME type (e.g. 'pdf' instead of 'application/pdf')
  • ·MIME type misspelled or using non-standard format
  • ·MimeCode attribute left empty

Seeing this in production? The API handles BR-CL-24 automatically. See the fix response →

Commonly Seen In

All invoicing software

Frequently Asked Questions

BR-CL-24 occurs when an attachment's MIME type code is not valid. Valid codes include application/pdf, image/png, image/jpeg, text/csv, and other IANA registered media types.

Update the mimeCode attribute in the EmbeddedDocumentBinaryObject element to use a valid IANA media type that matches your file format.

Yes, BR-CL-24 is a code list violation that will cause invoice rejection. Attachments must have valid MIME types for proper processing.

In some cases. Invoice Navigator can detect common file extensions and suggest the correct MIME type, but manual verification is recommended for unusual file formats.

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-CL-24 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.