What the rule requires
The invoice must not contain empty elements: no element without content, such as <cbc:Note/>,
<cbc:Telephone></cbc:Telephone> or an element holding only spaces. Attributes do not count as
content: <cbc:ItemClassificationCode listID="IB"/> is empty too.
Leave a field without a value out of the XML altogether. The validator reports each empty element separately; the message gives its location.
Exceptions in the validator configuration: in UBL the order reference cac:OrderReference/cbc:ID
may be empty, in CII the element ram:ApplicableHeaderTradeDelivery.
Common causes
- The program fills a fixed template and writes every element, even when the field is empty in the master data.
- Empty seller contact details are typical: then the rules of the fields come on top of R008 — BR-DE-5 (contact point), BR-DE-6 (telephone), BR-DE-7 (e-mail).
How to fix it
- Fill in the fields your program outputs empty — for mandatory fields that is the only way.
- For optional fields the program should leave empty elements out. If that cannot be set, it is a bug in the program; report it to the vendor with the check report.
Source: KoSIT, XRechnung validator configuration 3.0.2 (rule PEPPOL-EN16931-R008 in the UBL and CII rules); XRechnung specification 3.0.2 (list of the Peppol rules).