Invoice error guide · Supported local check

PEPPOL-EN16931-R008: UBL invoice contains empty elements

Understand PEPPOL-EN16931-R008, review an example and inspect your invoice XML locally. Check the underlying invoice values before applying a correction.

Last updated: 14 November 2026

  • No invoice uploads. The studio processes XML in your browser.
  • A resolved check is not full invoice compliance.

What this check means

Peppol Billing disallows empty elements. The local check looks for leaf elements whose text is empty or whitespace, including self-closing tags.

Example

An empty optional note can be removed. An empty required identifier needs its real value; simply deleting it does not make the invoice valid.

How to investigate and repair

Use the reported path to find the element in the XML editor. Fill required data or remove an optional empty element, then inspect again. The studio deliberately does not delete empty elements automatically.

Open E-invoice Studio, import the original XML or the hybrid PDF and choose Inspect invoice. The check shows the path of the affected element. Correct the value in the software that created the invoice or in the XML editor, then inspect again. Keep the original for your records.

Validation coverage

The studio implements a bounded subset of checks for mapped UBL and CII fields. It is not a complete XSD or Schematron validator. The empty-element rule is applied only to UBL. Signed XML cannot be repaired, and unsupported precision or ambiguous amounts prevent affected arithmetic checks.

Validate the complete document against the exact invoice profile and national requirements before sending it. The studio does not transmit through Peppol.

Tools and sources

Frequently asked questions

Can the studio automatically fix PEPPOL-EN16931-R008?

No. It reports the affected element and explains the rule. The correct value depends on your records, so you enter it yourself; nothing is deleted or invented automatically.

Does passing this rule mean my invoice is compliant?

No. One arithmetic or structural check cannot verify all required fields, tax treatment, code lists, country rules, PDF/XML agreement or delivery requirements. Full profile validation remains necessary.