Syntax Errors Errors

XML structure and schema validation errors that occur when the invoice format doesn't match UBL or CII specifications.

37 errors documented

Other categoriesBusiness Rules Format Rules Country-Specific

errorcvc-complex-type.4xsdBLOCKED

Required attribute is missing from an invoice element

An XML element in your invoice is missing a required attribute. In Peppol and UBL invoices, this typically means a monetary amount is missing its currencyID attribute, or an identifier is missing its schemeID. The element itself is present, but it lacks required metadata that receiving systems need to process it correctly.

errorcvc-datatype-valid.1.2.1xsdAUTO-FIX

Value does not match the required XML datatype format

cvc-datatype-valid.1.2.1 is an XML Schema (XSD) validation error meaning a value does not satisfy the lexical rules of its declared simple type. The message reads "'X' is not a valid value for 'Y'." In e-invoicing this usually means a number, date, or boolean is formatted in a locale or style the schema does not allow — a comma decimal separator, a DD/MM/YYYY date, or 'Yes'/'No' for a boolean.

errorcvc-complex-type.2.4.bxsdINPUT

Required XML element is missing (XSD content model incomplete)

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.

errorcvc-complex-type.2.2xsdAUTO-FIX

Invoice XML elements are in the wrong order

The elements in your invoice XML are in the wrong order. UBL 2.1 and CII D16B schemas use strict element ordering (xs:sequence), which means child elements must appear in a specific order. Even if all the right elements are present with correct values, having them in the wrong order causes a schema validation failure.

errorPEPPOL-EN16931-R102Peppol BIS 3.0AUTO-FIX

Document Reference Only Allowed for Invoice Line Object

PEPPOL-EN16931-R102 fires when a DocumentReference element is used at the wrong level in the invoice. The cac:DocumentReference element can only be used to reference an invoiced object at the line level, not at the document header level.

errorZUG-XMP-001zugferdBLOCKED

ZUGFeRD/Factur-X PDF Missing or Invalid XMP Metadata

The ZUGFeRD or Factur-X PDF is missing required XMP metadata properties in the fx namespace.

errorZUG-FILENAME-001zugferdBLOCKED

ZUGFeRD/Factur-X Wrong Embedded XML Filename

The embedded XML in your ZUGFeRD/Factur-X PDF has the wrong filename. It must be exactly factur-x.xml since ZUGFeRD 2.1.

errorCII-SR-02cii-d16bBLOCKED

CII GuidelineSpecifiedDocumentContextParameter required

CII must specify guideline identifier.

errorXML-002ubl-2.1BLOCKED

Malformed XML structure

XML document is not well-formed.

errorXML-004ubl-2.1BLOCKED

Invalid XML characters

Document contains invalid XML characters.

errorUBL-SR-06ubl-2.1CONFIRM

Invalid date format

UBL dates must use YYYY-MM-DD format.

errorUBL-SR-08ubl-2.1CONFIRM

Quantity missing unit code

Quantity elements must have unitCode attribute.

errorCII-SR-01cii-d16bAUTO-FIX

CII namespace declaration required

Cross Industry Invoice must declare RSM namespace.

errorCII-SR-002cii-d16bBLOCKED

Missing ExchangedDocument context

CII documents must include the ExchangedDocumentContext header.

errorCII-SR-03cii-d16bBLOCKED

ExchangedDocument element required

CII must have ExchangedDocument with ID and TypeCode.

warningXML-003ubl-2.1BLOCKED

XML encoding declaration recommended

XML should declare character encoding.

errorXML-005ubl-2.1BLOCKED

XML schema validation failed

Document does not conform to XSD schema.

errorXML-006en16931BLOCKED

Schematron validation failed

Document failed business rule validation.

errorCII-SR-001cii-d16bBLOCKED

Invalid CII namespace

CII (Cross Industry Invoice) documents must use the correct namespace declaration.

errorUBL-CR-002ubl-2.1AUTO-FIX

Invalid or Missing Namespace

The UBL invoice must use the correct XML namespaces for UBL 2.1.

errorcvc-complex-type.2.4.axsdBLOCKED

Invoice XML structure does not match the required schema

Your invoice file has a structural problem — required data elements are missing, in the wrong position, or unexpected elements are present. This is an XML Schema validation error, which means the basic structure of the file does not conform to the e-invoicing standard (UBL 2.1 or CII D16B). This is different from a business rule error: business rules check whether the data makes sense, while this error means the file format itself is wrong.

errorCII-SR-05cii-d16bBLOCKED

ApplicableHeaderTradeAgreement required

CII must specify seller and buyer.

errorCII-SR-003cii-d16bINPUT

Invalid document type code

CII TypeCode must be valid UNTDID 1001 code (380=Invoice, 381=Credit Note).

errorUBL-SR-01ubl-2.1CONFIRM

UBL namespace declaration required

UBL documents must declare correct namespace.

errorUBL-SR-02ubl-2.1CONFIRM

CAC/CBC namespace declarations required

UBL requires Common Aggregate and Basic Component namespaces.

warningUBL-SR-04ubl-2.1CONFIRM

Empty elements should be removed

UBL elements with no content should be omitted.

errorUBL-SR-09ubl-2.1CONFIRM

Invalid boolean value

Boolean elements must be true or false.

errorUBL-SR-05ubl-2.1CONFIRM

ID elements must be unique

ID elements within scope must have unique values.

errorUBL-SR-03ubl-2.1CONFIRM

UBL element order incorrect

UBL elements must follow schema-defined order.

errorUBL-SR-10ubl-2.1CONFIRM

Invalid decimal format

Decimal numbers must use period as separator.

errorcvc-complex-type.2.4.dxsdBLOCKED

Unexpected child element in invoice XML

cvc-complex-type.2.4.d is an XSD schema-validation error raised by Xerces-based parsers when the invoice contains an element the schema does not allow at that position. The parser has finished accepting the declared children for the current parent and encountered one more element it was not expecting.

errorcvc-complex-type.2.3xsdCONFIRM

Text content inside an element-only element

cvc-complex-type.2.3 is an XSD error raised when an element declared as element-only has non-whitespace text inside it. Mixing text and structural children is not allowed for that complex type.

errorCII-SR-046cii-d16bINPUT

GlobalID present without schemeID attribute

CII-SR-046 is a fatal EN 16931 Schematron assertion on the CII binding used by ZUGFeRD and Factur-X. If ram:GlobalID is present, it must carry a schemeID attribute. Formal test: not(ram:GlobalID) or (ram:GlobalID/@schemeID).

errorXML-001ubl-2.1BLOCKED

Invoice file is not well-formed XML

XML-001 is raised when the invoice file fails XML well-formedness before any schema or Schematron rule can apply. The parser cannot build a DOM tree because the bytes do not conform to XML 1.0 grammar.

errorCII-DT-018cii-d16bAUTO-FIX

TypeCode should not be present on this element

CII-DT-018 is an EN 16931 datatype assertion on the CII binding. It forbids a ram:TypeCode child on any element except ram:AdditionalReferencedDocument, and even there restricts the value to UNTDID 1001 codes 50 (price/sales catalogue), 130 (invoicing data sheet), or 916 (related document).

errorcvc-complex-type.2.1xsdCONFIRM

Element declared as empty contains character or child content

cvc-complex-type.2.1 is an XSD schema-validation error raised by Xerces-based parsers when an element whose content type is declared as empty contains character data or child elements. The canonical message reads: "Element X must have no character or element information item [children], because the type's content type is empty."

errorCII-SR-04cii-d16bBLOCKED