UBL-DT-06:Binary object elements shall contain the mime code attribute
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (UBL-DT-06). Upload your invoice to fix this automatically.
Your invoice contains an embedded attachment (EmbeddedDocumentBinaryObject) but the mimeCode attribute is missing. The MIME type (e.g., application/pdf, image/png) must be specified.
Engine Classification
Add default mimeCode attribute (application/pdf) to embedded binary objects
Confidence: 80% · Applied automatically in pipeline
What is UBL-DT-06?
UBL-DT-06 is a fatal validation rule defined in the EN 16931 specification. It validates the @mimeCode element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: //cbc:EmbeddedDocumentBinaryObject/@mimeCode
Why This Error Matters
Invoice will be rejected. Receiving systems need the MIME type to properly display or process the attachment.
UBL-DT-06 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
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: UBL-DT-06
- ·Specification: EN 16931
How to Fix It
Find the missing or empty field
Check @mimeCode at //cbc:EmbeddedDocumentBinaryObject/@mimeCode. This field is required but is either missing or empty.
Set the required value
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (UBL-DT-06).
Re-validate your invoice
Upload the corrected invoice to confirm UBL-DT-06 is resolved.
Before / After
<Invoice> <!-- Issue: Binary object elements shall contain the mime code attribute --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
//cbc:EmbeddedDocumentBinaryObject/@mimeCodeCommon Causes
- ·Attachment added without specifying the file type
- ·ERP export omitted the MIME type attribute
- ·Binary content copied without metadata
- ·Template missing mimeCode attribute on attachment element
- ·File uploaded without extension or type detection
Seeing this in production? The API handles UBL-DT-06 automatically. See the fix response →
Frequently Asked Questions
Your invoice contains an embedded attachment (EmbeddedDocumentBinaryObject) but the mimeCode attribute is missing. The MIME type (e.g., application/pdf, image/png) must be specified.
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (UBL-DT-06). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-DT-06 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-DT-06 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for UBL-DT-06
Auto-fix UBL-DT-06 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.