Fehlercodes · xsd

cvc-complex-type.2.4.bIm Rechnungssystem

Required XML element is missing (XSD content model incomplete)

So lautet die Ablehnung wörtlich: „[cvc-complex-type.2.4.b] cvc-complex-type.2.4.b is an XML Schema (XSD) validation error meaning an element's content is incomplete: the schema requires a child element that is not present. The message reads "The content of element 'X' is not complete. One of {'Y'} is expected." Unlike a business rule (BR-*) violation, this is a structural failure — the document does not conform to the UBL or CII schema, so it fails before any EN 16931 business rules are evaluated.“

The XSD content model defines a required sequence of child elements and the validator reached the end of an element while a mandatory child was still expected. Common triggers: AccountingSupplierParty/AccountingCustomerParty missing cac:Party; cac:PostalAddress missing cac:Country; cac:LegalMonetaryTotal missing a required amount; cac:TaxTotal missing cbc:TaxAmount; elements emitted out of the UBL sequence order; or a namespace prefix typo (cbc vs cac) that makes a present element appear absent.

Was Sie bereithaltenNichts. Die Datei muss im Rechnungssystem neu erzeugt werden; wir prüfen sie danach erneut.
Was wir tunRead the message: the element after 'content of element' is the incomplete parent and the names in curly braces are what the schema expected next. Add the missing mandatory child with a real value from your system (it cannot be invented), or, if the element exists but is out of order, reorder it (UBL is sequence-sensitive; cbc: before cac:). Check for a wrong namespace prefix (cbc vs cac). Re-validate against the XSD before the business rules run.
Wenn Sie es selbst im Rechnungssystem eintragen
Vorher
<cac:AccountingSupplierParty><cac:Party><cac:PostalAddress><cbc:StreetName>Keizersgracht 1</cbc:StreetName><cbc:CityName>Amsterdam</cbc:CityName><cbc:PostalZone>1015 CW</cbc:PostalZone><!-- cac:Country missing --></cac:PostalAddress></cac:Party></cac:AccountingSupplierParty>
Nachher
<cac:AccountingSupplierParty><cac:Party><cac:PostalAddress><cbc:StreetName>Keizersgracht 1</cbc:StreetName><cbc:CityName>Amsterdam</cbc:CityName><cbc:PostalZone>1015 CW</cbc:PostalZone><cac:Country><cbc:IdentificationCode>NL</cbc:IdentificationCode></cac:Country></cac:PostalAddress></cac:Party></cac:AccountingSupplierParty>

Die Reihenfolge ist Teil der Regel: steht das Element an der falschen Stelle, lehnt der Validator mit cvc-complex-type.2.4.b ab.

So sieht der Befund ausBeispiel
BefundAufbau fehlerhaft · cvc-complex-type.2.4.b
Von IhnenNeu exportierte Datei
DanachNeu exportieren
NachweisSHA-256 und /verify-Link nach der Prüfung
Tritt oft zusammen auf
cvc-complex-type.2.2Invoice XML elements are in the wrong ordercvc-complex-type.2.4.aInvoice XML structure does not match the required schemacvc-complex-type.4Required attribute is missing from an invoice element