The element <name/> "Attached Document" (BT-125) uses an impermissible MIME code: <value-of select="@mimeCode"/>. In the case of an extension, the MIME code application/xml may additionally be used in addition to the list of MIME codes (defined in section 8.2, "Binary Object").
The value of mimeCode in ram:AttachmentBinaryObject is not one of the MIME codes allowed by this rule. For an extension, application/xml is also allowed in addition to the listed document types.
The MIME code describes the format of the attached document. An allowed code identifies the content as a supported format.
The MIME code for the attached document in ram:AttachmentBinaryObject is not accepted by this rule. You can replace it with one of the allowed codes.
- Check the value of
mimeCodeforAdditionalReferencedDocument.AttachmentBinaryObject. - Choose one of the allowed codes, such as
application/pdfor, for an extension,application/xml. - Check the call to
AddAdditionalReferencedDocument(...). - Regenerate the invoice and validate it again.
<ram:AttachmentBinaryObject mimeCode="application/octet-stream">...</ram:AttachmentBinaryObject>
<ram:AttachmentBinaryObject mimeCode="application/pdf">...</ram:AttachmentBinaryObject>
AdditionalReferencedDocument.AttachmentBinaryObject(BT-125)AdditionalReferencedDocument.Filename(BT-125-2)FacturXInvoice.AddAdditionalReferencedDocument(id, typeCode, issueDateTime, name, referenceTypeCode, attachmentBinaryObject, filename, uriID)(attachmentBinaryObject: BT-125)
Technical details
The test compares @mimeCode directly with the allowed values: PDF, PNG, JPEG, CSV, two spreadsheet formats, and application/xml.
The rule applies to ram:AttachmentBinaryObject for an extension. It checks the mimeCode attribute of the attached document.
rule/@context)assert/@test)- 2024-10-312024-10-31 · AddedCustom level for BR-CL-24 in CII Extension to support BR-DEX-01