Back to Compliance Hub
Critical

SCHEMA-003

XSD Schema Violation: Element Missing, Misplaced or Not Allowed (No Rule ID)

What This Error Means

SCHEMA-003 is not an official rule ID; docutools.pro uses it as a label for XML schema (XSD) errors. After selecting a scenario, the KoSIT validator checks the file against the UBL 2.1 or CII D16B schema. If that fails, the Schematron steps are not run at all, so the report shows only schema messages such as 'Invalid content was found starting with element cbc:IssueDate. One of cbc:ProfileID, cbc:ID ... is expected.' The result is reject.

How to Fix It

Read the schema message: it names the element where the problem was found and what was expected there. UBL prescribes a fixed order of elements, and a few are mandatory in the schema itself, such as cbc:ID, cbc:IssueDate, both parties, cac:LegalMonetaryTotal and at least one cac:InvoiceLine. Move or add the element and validate again.

XML Example
<!-- UBL header in schema order -->
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
<cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
<cbc:ID>RE-2026-4711</cbc:ID>
<cbc:IssueDate>2026-07-15</cbc:IssueDate>
<cbc:DueDate>2026-07-29</cbc:DueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<cbc:Note>Projekt Alpha</cbc:Note>
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<cbc:BuyerReference>04011000-1234512345-06</cbc:BuyerReference>

Fix Automatically

Upload your invoice to our Smart Repair engine. It checks the file against the full KoSIT rule set, including SCHEMA-003, and corrects supported fields with a GoBD audit trail.

Open Smart Repair

Related Errors

Other commonly encountered validation errors

SCHEMA-001XML Not Well-Formed (Parser Error, No Rule ID)SCHEMA-002Wrong Root Element or Namespace (No Matching Scenario, No Rule ID)BR-2Invoice Number Missing (BT-1)BR-DE-1Payment Instructions Missing (BG-16)