Why does an empty element fail XSD validation?

xsd:minLength counts characters. An empty string has length 0, which is below minLength=1. The element being present in the XML does not change that.

Should I emit a default placeholder like a single space?

No. Whitespace-only values may pass the schema but fail downstream business rules and create noise for human readers. Either supply a real value or omit the element if the CIUS allows it.

Is cvc-minLength-valid auto-fixable?

Removing the element is auto-fixable when the parent allows zero occurrences — Invoice Navigator applies that transformation deterministically. Filling in a real value is not auto-fixable for required fields.

Which EN 16931 fields most commonly trip this error?

BT-22 Invoice note, BT-153 Item description, BT-21/BT-23 Invoice/Subject codes when the ERP exports an empty wrapper, and BT-44 Buyer name when the partner record is incomplete.

Does ZUGFeRD/Factur-X CII have the same issue?

Yes. The CII binding inherits its facets from the same UN/CEFACT XSDs. ram:Content and ram:Name carry the same minLength=1 facet, so empty exports fail identically.

Error codes · xsd

cvc-minLength-validIn your invoicing software

Value is shorter than the minimum length declared in the schema

This is the rejection, word for word: „[cvc-minLength-valid] cvc-minLength-valid is an XSD facet-validation error raised when a string is shorter than the xsd:minLength facet on its simple type. The canonical message reads: "Value 'X' with length = N is not facet-valid with respect to minLength '1' for type 'T'." In EN 16931 invoices the overwhelming majority of cases are minLength=1 violations — i.e. an empty element. The XSD treats the empty string as a structural failure, even though the surrounding element is technically present.“

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doEither delete the empty element where the CIUS allows zero occurrences, or supply a non-empty value from a sibling field; for required fields with no fallback the caller must provide the missing data.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<cbc:Note></cbc:Note>

After

<!-- element removed -->

What the finding looks likeExample

FindingStructure invalid · cvc-minLength-valid

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check