Symptoms
What this usually looks like
CustomizationID missingXML opens but tooling rejects itProfile-related export confusion
Missing CustomizationID in a Peppol invoice
A Peppol invoice can contain the business data and still fail because the export is missing the profile marker tools expect to classify it correctly.
Likely cause
What is usually actually broken
The ERP exported invoice data without the Peppol BIS customization or profile metadata that downstream systems rely on.
Next steps
Do these before you resend
- Check whether the source export is actually producing a Peppol BIS profile.
- Fix the export template or connector rather than patching the final XML by hand.
- Generate a fresh file and re-run the diagnosis before sending.
The fastest path from this page is a prefilled diagnosis. It opens the analyzer with this exact issue pattern already loaded and immediately prepares the EUR 9 fix-pack preview when the route looks blocked or risky.
Direct help
Buy the rescue kit for this exact issue
If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.
FAQ
What people ask right before they get blocked
Yes. The file can still be readable XML while failing stricter Peppol or validator workflows.
At the ERP export or connector layer, so every regenerated invoice carries the correct metadata.
Operator guides
Go one level deeper before you resend
A practical guide for missing CustomizationID, profile markers, and other export-level metadata that leave XML looking valid but unusable in Peppol workflows.
Read the guide Related issues
Similar failure patterns worth checking
Passing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.
Open issue page