E-Invoice Error Reference

1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.

31 errors found in Syntax Errors

errorcvc-complex-type.2.4.bxsdBLOCKED

Required element is missing from invoice XML

Your invoice is missing a required XML element. The error message from the validator identifies which element is expected and where it should appear. This is an XML Schema (XSD) validation error — the file structure itself is incomplete, which is different from a business rule violation where the structure is correct but values are wrong.

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

Invoice field value does not match the required data format

A value in your invoice does not match the data format required by the XML Schema. This typically means a number, date, or other value is formatted incorrectly — for example, using a comma instead of a dot for decimals (1.234,56 instead of 1234.56), or a date in DD/MM/YYYY format instead of the required YYYY-MM-DD (ISO 8601).

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-05ubl-2.1CONFIRM

ID elements must be unique

ID elements within scope must have unique values.

errorUBL-SR-09ubl-2.1CONFIRM

Invalid boolean value

Boolean elements must be true or false.

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.

errorCII-SR-04cii-d16bBLOCKED

SupplyChainTradeTransaction required

CII must have main trade transaction element.

Handle These Errors Automatically in Your Pipeline

The compliance engine auto-remediates validation errors with controlled safety policies and evidence pack generation.

Get API Access