What the rule requires
Attachments in the invoice (BT-125) may only have these file types (attribute mimeCode):
| Type | mimeCode |
|---|---|
application/pdf |
|
| PNG | image/png |
| JPEG | image/jpeg |
| CSV | text/csv |
| Excel (.xlsx) | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet |
| OpenDocument spreadsheet (.ods) | application/vnd.oasis.opendocument.spreadsheet |
According to the XRechnung specification every recipient must be able to accept these types.
Exception: XRechnung extension
With the XRechnung extension (its own identifier in BT-24) XML may be attached as well
(application/xml, rule BR-DEX-01). In the extension KoSIT lowers BR-CL-24 to information.
Common causes
- Attachments as Word (
.docx), ZIP, TXT or XML in a normal XRechnung. - A misspelled type such as
application/PDForpdf.
How to fix it
Convert the attachment to one of the allowed formats (usually PDF) or send it outside the invoice.
Example (CII)
<ram:AdditionalReferencedDocument>
<ram:IssuerAssignedID>Leistungsnachweis</ram:IssuerAssignedID>
<ram:TypeCode>916</ram:TypeCode>
<ram:AttachmentBinaryObject mimeCode="application/pdf" filename="nachweis.pdf">JVBERi0x…</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
Sources: KoSIT, XRechnung specification 3.0.2 (Binary Object, BR-DEX-01); validator configuration XRechnung 3.0.2.