PEPPOL-EN16931-R008 in your own invoice? Upload the file and find every error in seconds.
What does PEPPOL-EN16931-R008 mean?
Empty elements are one of the most common reasons for rejected e-invoices. Peppol forbids them because an empty mandatory field hides a missing entry and disrupts machine processing. This rule often fires several times - once per empty element.
Common causes of PEPPOL-EN16931-R008
- The invoicing software writes out fields even when no value exists (for example empty address or reference fields).
- Optional elements are produced as an empty tag instead of being left out.
- Placeholders or nothing but spaces as content.
How to fix PEPPOL-EN16931-R008
- Find the faulty spot in the XML. Open the XML of the invoice and go to the spot in question along this XPath:
- Apply the fix. Remove empty tags from the XML. An element such as or must either carry a valid value or be removed entirely.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R008 is no longer reported.
Concrete fix
Remove empty tags from the XML. An element such as <ram:Name></ram:Name> or <ram:ID/> must either carry a valid value or be removed entirely.
Frequent questions about PEPPOL-EN16931-R008
Why does the same message appear several times?
The engine reports every single empty element separately. If several fields are empty, you see the message that many times. Our display groups identical messages and counts them.
Does an element holding only a space count as empty?
Yes. An element whose content is nothing but spaces counts as empty and must be removed or filled.
Related error codes
Check PEPPOL-EN16931-R008 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.