E-Invoice Error Reference
1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1359 errors found · Page 1 of 28
cvc-complex-type.2.4.bxsdBLOCKEDRequired 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.
cvc-complex-type.4xsdBLOCKEDRequired 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.
cvc-datatype-valid.1.2.1xsdAUTO-FIXInvoice 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).
BR-03EN 16931AUTO-FIXInvoice must have an issue date
Every invoice must contain an issue date indicating when the invoice was created.
cvc-complex-type.2.2xsdAUTO-FIXInvoice 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.
BR-04EN 16931AUTO-FIXMissing invoice type code
An Invoice shall have an Invoice type code (BT-3). The most common value is 380 for a standard commercial invoice.
PEPPOL-EN16931-R102Peppol BIS 3.0AUTO-FIXDocument 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.
KSEF-440PLksefBLOCKEDKSeF Duplicate Invoice Rejection (HTTP 440)
The KSeF system rejected your invoice because it detected a duplicate submission. KSeF checks the combination of seller NIP, invoice number, and invoice date against all invoices submitted in the last 10 years. If a match is found, the API returns HTTP status 440 and the invoice is not accepted.
PEPPOL-COMMON-R052DKPeppol BIS 3.0AUTO-FIXDanish Chamber of Commerce P-Number Format Invalid
PEPPOL-COMMON-R052 validates that a Danish chamber of commerce production unit number (P-number) is in the correct format. The P-number must consist of exactly 10 digits. This rule fires when a party identifier uses scheme 0198 but the value does not meet the format requirements.
UBL-CR-077UBL 2.1AUTO-FIXA UBL invoice should not include the StatementDocumentReference
Your invoice contains StatementDocumentReference which is not allowed in EN16931 invoices. Statement references are not supported.
ZUG-XMP-001zugferdBLOCKEDZUGFeRD/Factur-X PDF Missing or Invalid XMP Metadata
The ZUGFeRD or Factur-X PDF is missing required XMP metadata properties in the fx namespace.
BR-18EN 16931INPUTInvoice line price required
Each invoice line must have a price amount (item net price).
ZUG-FILENAME-001zugferdBLOCKEDZUGFeRD/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.
CII-SR-02cii-d16bBLOCKEDCII GuidelineSpecifiedDocumentContextParameter required
CII must specify guideline identifier.
PEPPOL-EN16931-R040EN 16931AUTO-FIXDiscount or surcharge amount doesn't match the calculation
A discount or surcharge amount does not match its base amount multiplied by the percentage. When all three values are provided (amount, base amount, and percentage), they must be consistent: amount = base amount × percentage ÷ 100.
PEPPOL-EN16931-R061Peppol BIS 3.0INPUTMissing direct debit mandate reference
When payment is by direct debit (SEPA or other), the invoice must include the mandate reference number. This is the unique identifier of the agreement that authorizes the seller to collect payment from the buyer's bank account.
UBL-CR-470UBL 2.1AUTO-FIXA UBL invoice should not include the PrepaidPayment
Your invoice contains a PrepaidPayment element which is not allowed in EN16931 invoices. This element must be removed.
XML-002ubl-2.1BLOCKEDMalformed XML structure
XML document is not well-formed.
UBL-CR-491UBL 2.1AUTO-FIXA UBL invoice should not include the PricingExchangeRate
Your invoice contains a PricingExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
XML-004ubl-2.1BLOCKEDInvalid XML characters
Document contains invalid XML characters.
BR-21EN 16931AUTO-FIXMissing invoice line identifier
Each Invoice line shall have an Invoice line identifier (BT-126). This is a unique sequential number identifying each line item on the invoice.
PT-R-001PRTubl-2.1INPUTPortuguese NIF required
Portuguese invoices must include NIF (Numero de Identificacao Fiscal).
UBL-CR-079UBL 2.1AUTO-FIXA UBL invoice should not include the OriginatorDocumentReference UUID
Your invoice contains OriginatorDocumentReference/UUID which is not allowed in EN16931 invoices.
UBL-SR-06ubl-2.1CONFIRMInvalid date format
UBL dates must use YYYY-MM-DD format.
UBL-SR-08ubl-2.1CONFIRMQuantity missing unit code
Quantity elements must have unitCode attribute.
PT-R-002PRTubl-2.1INPUTAT document codes required
Portuguese invoices need AT (Autoridade Tributaria) document codes.
BR-25EN 16931INPUTInvoice line item name required
Each Invoice line shall contain the Item name (BT-153). This describes the goods or services being invoiced.
UBL-CR-017UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference UUID
Your invoice contains OrderReference/UUID which is not allowed in EN16931 invoices.
BR-29EN 16931AUTO-FIXInvoice period end date before start date
The Invoicing Period End Date (BT-74) is before the Start Date (BT-73). The end date must be on or after the start date.
BR-32EN 16931AUTO-FIXEach Document level allowance (BG-20) shall have a Document level allowance...
Each Document level allowance (BG-20) shall have a Document level allowance VAT category code (BT-95). Check the `cac:AllowanceCharge` element in your invoice XML.
BR-33EN 16931AUTO-FIXDocument level allowance reason required
A document level allowance (discount) is missing both a reason text (BT-97) and reason code (BT-98). At least one must be provided to explain why this discount exists.
BR-38EN 16931AUTO-FIXDocument level charge reason required
A document level charge is missing both a reason text (BT-104) and reason code (BT-105). At least one must be provided to explain what this charge is for.
BR-44EN 16931AUTO-FIXInvoice line charge reason required
An invoice line charge (BG-28) is missing both a reason text and reason code. At least one must be provided to explain this line surcharge.
BR-CO-15EN 16931AUTO-FIXTax exclusive amount calculation error
Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).. This applies to the `cbc:TaxInclusiveAmount` element in the invoice XML.
UBL-CR-493UBL 2.1AUTO-FIXA UBL invoice should not include the PaymentAlternativeExchangeRate
Your invoice contains a PaymentAlternativeExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
BR-47EN 16931AUTO-FIXLine allowance amount required
Line-level AllowanceCharge must include the Amount element.
BR-55EN 16931INPUTPrepayment should reference prepayment invoice
When PrepaidAmount is used, reference the prepayment invoice.
UBL-SR-13EN16931CONFIRMSeller tax registration shall occur maximum once
Your invoice contains multiple Seller tax registration elements (PartyTaxScheme). EN16931 allows maximum one tax registration per seller.
BR-62EN 16931AUTO-FIXThe Seller electronic address (BT-34) shall have a Scheme identifier.
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?
BR-64EN 16931AUTO-FIXItem standard identifier needs scheme
If item has standard identifier, scheme must be specified.
BR-65EN 16931AUTO-FIXBuyer item identifier should be unique
The Item classification identifier (BT-158) shall have a Scheme identifier.
BR-DEC-03en16931BLOCKEDDocument charge: max 2 decimals
Document level charge amount allows max 2 decimal places.
BR-66EN 16931AUTO-FIXAn Invoice shall contain maximum one Payment Card account (BG-18).
The invoice contains multiple Payment Card accounts (BG-18). Only one card payment method is allowed per invoice.
BR-67EN 16931AUTO-FIXAn Invoice shall contain maximum one Payment Mandate (BG-19).
The invoice contains multiple Payment Mandates (BG-19). Only one direct debit mandate is allowed per invoice.
UBL-CR-015UBL 2.1AUTO-FIXA UBL invoice should not include the InvoicePeriod Description
Your invoice contains InvoicePeriod/Description which is not allowed. Use DescriptionCode instead.
BR-AE-06EN 16931AUTO-FIXDocument level allowance with reverse charge must have 0% VAT rate
When a document level allowance uses the reverse charge VAT category, the VAT rate must be 0%. Allowances in reverse charge scenarios follow the same zero-rate rule.
UBL-SR-27EN16931AUTO-FIXPayment means text shall occur maximum once
Your invoice contains multiple Payment means text elements (PaymentMeans/InstructionNote). EN16931 allows only one instruction note.
UBL-SR-28EN16931AUTO-FIXMandate reference identifier shall occur maximum once
Your invoice contains multiple Mandate reference identifiers (PaymentMandate/ID). EN16931 allows only one direct debit mandate reference.
BR-AG-06EN 16931AUTO-FIXIPSI document level allowance VAT rate must be 0% or positive
When a document level allowance uses the IPSI VAT category (M for Ceuta/Melilla indirect tax), the VAT rate must be 0 or greater than zero.
UBL-CR-353UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation CountrySubentity
Your invoice contains a DeliveryLocation CountrySubentity element which is not allowed in EN16931 invoices. This element must be removed.
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→