# BR-CL-24: Attachment MIME code not allowed

Source: https://veriport.io/einvoice-rules/br-cl-24 (published 2026-11-17)

An attached document, BT-125 (`cbc:EmbeddedDocumentBinaryObject` / `ram:AttachmentBinaryObject`), must declare in `mimeCode` one of the allowed types: application/pdf, image/png, image/jpeg, text/csv, the Excel types (xlsx) and application/vnd.oasis.opendocument.spreadsheet. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CL-24 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-CL-24]-For Mime code in attribute use MIMEMediaType.
```

## What it checks

An attached document, BT-125 (`cbc:EmbeddedDocumentBinaryObject` / `ram:AttachmentBinaryObject`), must declare in `mimeCode` one of the allowed types: application/pdf, image/png, image/jpeg, text/csv, the Excel types (xlsx) and application/vnd.oasis.opendocument.spreadsheet.

## Why invoices fail it

A Word document, a ZIP archive or an XML file is attached, or the MIME type is written in another form (« pdf »).

## How to fix it

Convert the attachment to PDF (or CSV / XLSX for data) and write its exact MIME type.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-CL-24.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CL-24** | error | `/ubl:Invoice/cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject` | For Mime code in attribute use MIMEMediaType. |

```diff
  …
      <cbc:DocumentDescription>Stundennachweis</cbc:DocumentDescription>
      <cac:Attachment>
-       <cbc:EmbeddedDocumentBinaryObject mimeCode="application/msword" filename="stunden-2026-10.csv">RGF0dW07U3R1bmRlbgoyMDI2LTEwLTAxOzgK</cbc:EmbeddedDocumentBinaryObject>
+       <cbc:EmbeddedDocumentBinaryObject mimeCode="text/csv" filename="stunden-2026-10.csv">RGF0dW07U3R1bmRlbgoyMDI2LTEwLTAxOzgK</cbc:EmbeddedDocumentBinaryObject>
      </cac:Attachment>
    </cac:AdditionalDocumentReference>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cbc:EmbeddedDocumentBinaryObject[@mimeCode]
test:    ((@mimeCode = 'application/pdf' or @mimeCode = 'image/png' or @mimeCode = 'image/jpeg' or @mimeCode = 'text/csv' or @mimeCode = 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' or @mimeCode = 'application/vnd.oasis.opendocument.spreadsheet'))
```

```xpath
context: ram:AttachmentBinaryObject[@mimeCode]
test:    ((@mimeCode = 'application/pdf' or @mimeCode = 'image/png' or @mimeCode = 'image/jpeg' or @mimeCode = 'text/csv' or @mimeCode = 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' or @mimeCode = 'application/vnd.oasis.opendocument.spreadsheet'))
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-CL-22: VAT exemption reason code not VATEX](https://veriport.io/einvoice-rules/br-cl-22)
- [BR-CL-23: Unit code not UN/ECE Rec 20 or 21](https://veriport.io/einvoice-rules/br-cl-23)
- [BR-CL-25: Electronic address scheme not in the EAS list](https://veriport.io/einvoice-rules/br-cl-25)
- [BR-CL-26: Delivery location scheme not ISO 6523](https://veriport.io/einvoice-rules/br-cl-26)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
