PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

XRechnung buyer reference missing

German XRechnung flows commonly reject invoices missing the buyer reference. Learn how to spot the issue fast and avoid another failed submission.

German document rejection Belgium-first Self-serve remediation
Symptoms

What this usually looks like

XRechnung rejectionBuyer reference missingXML otherwise looks valid
Likely cause

What is usually actually broken

The recipient expects a buyer reference for processing and routing within their workflow.

Next steps

Do these before you resend

  1. Obtain the exact buyer reference from the recipient.
  2. Inject it in the source system before regenerating the file.
  3. Resend only after re-running the diagnosis.

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.

Open prefilled diagnosis See the fix pack
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

Can the invoice look valid otherwise?

Yes. Buyer-reference errors often appear in otherwise well-formed XRechnung XML.

Where should the buyer reference come from?

From the recipient's procurement or accounts-payable workflow, not from guesswork in your ERP.

Operator guides

Go one level deeper before you resend

Fixing missing Peppol profile fields before delivery fails

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