Check embedded PDF attachments in UBL invoices
Paste your UBL XML to inspect AdditionalDocumentReference attachments. We decode base64 locally, check for the %PDF- header, and explain common problems.
Paste or load UBL XML
About embedded PDFs in UBL
- EmbeddedDocumentBinaryObject carries an attached file inline in the XML.
- Base64 converts a binary PDF into safe ASCII characters that fit inside XML.
- UBL invoices commonly include a human-readable PDF next to the structured XML.
- The XML is for software; the PDF is for people. Both should describe the same invoice.
Related tools
UBL Validator and Error Explainer
Find missing fields, structural problems and Peppol issues, and read plain-English explanations.
UBL Viewer
Render a UBL XML invoice as a readable invoice summary.
UBL totals checker
Verify line, tax and payable totals against LegalMonetaryTotal.
UBL VAT checker
Compare declared and calculated VAT per category.
UBL field explainer
Search UBL fields and read what each XML path means.
Peppol BIS Billing checker
Check common Peppol BIS Billing 3.0 invoice issues.
Frequently asked questions
›What is EmbeddedDocumentBinaryObject?
It is the UBL element used to carry an embedded file (typically a PDF) inside the invoice XML. The file content is encoded as a base64 string and accompanied by mimeCode and filename attributes.
›What is Base64?
Base64 is a way to represent binary data (like a PDF) using only printable ASCII characters. It makes it safe to embed binary files inside XML.
›Why include a PDF in a UBL invoice?
The XML is for automated processing; a human-readable PDF helps people read the invoice. Many regulations (and Peppol practice) recommend including a visual PDF alongside the structured data.
›Structured XML versus PDF — what's the difference?
The structured XML is what software reads to book the invoice automatically. The PDF is what humans look at. Both should describe the same invoice.