E-Invoice Error Reference
1374+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1374 errors found · Page 3 of 28
DE-R-020DEUEN 16931AUTO-FIXDebited account identifier (BT-91) should contain a valid IBAN if code 59...
Invalid debit IBAN format. When payment means code 59 (SEPA direct debit) is used, the debited account (BT-91) must contain a valid IBAN.
DE-R-024-1DEUEN 16931AUTO-FIXPayment card details missing. When payment code 48, 54, or 55 (payment card)...
Payment card details missing. When payment code 48, 54, or 55 (payment card) is used, the Payment Card Information group (BG-18) must be provided.
PEPPOL-EN16931-R004EN 16931AUTO-FIXThe specification identifier must be exactly...
The specification identifier must be exactly "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0". This identifies the invoice as PEPPOL BIS Billing 3.0 compliant.
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.
PEPPOL-EN16931-R100EN 16931AUTO-FIXOnly one invoiced object is allowed pr line
Only one invoiced object identifier is allowed per invoice line. Each line can reference at most one object (contract, order, etc.).
PEPPOL-EN16931-R110EN 16931AUTO-FIXStart date of line period MUST be within invoice period.
The start date of a line period must fall within the invoice period. Line periods cannot extend before the overall invoice period begins.
cvc-complex-type.2.1xsdCONFIRMElement 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."
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.
cvc-enumeration-validxsdINPUTValue is not in the declared enumeration (invalid code list entry)
cvc-enumeration-valid is an XSD facet-validation error raised when the value of an element or attribute does not appear in the enumeration the schema declares. The canonical message reads: "Value X is not facet-valid with respect to enumeration [A, B, C ...]. It must be a value from the enumeration." In EN 16931 invoices it fires on unit codes, currency codes, document type codes, and tax category codes.
BR-AG-07EN 16931AUTO-FIXIPSI document level charge VAT rate must be 0% or positive
When a document level charge uses the IPSI VAT category (M for Ceuta/Melilla indirect tax), the VAT rate must be 0 or greater than zero.
BR-AG-09EN 16931AUTO-FIXIPSI VAT breakdown tax amount must be calculated correctly
The tax amount for the IPSI VAT category in the VAT breakdown must be calculated based on the taxable amount and rate.
UBL-CR-016UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference CopyIndicator
Your invoice contains OrderReference/CopyIndicator which is not allowed in EN16931 invoices.
UBL-CR-356UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation InformationURI
Your invoice contains a DeliveryLocation InformationURI element which is not allowed in EN16931 invoices. This element must be removed.
UBL-SR-44EN 16931AUTO-FIXAn Invoice may only have one unique PaymentID, but the PaymentID may be used...
Your invoice has multiple different PaymentID values across PaymentMeans elements. EN16931 allows only one unique payment reference value, though it can be repeated across multiple payment means.
DE-R-031DEUEN 16931AUTO-FIXIf the group "DIRECT DEBIT" (BG-19) is delivered, the element "Debited...
Debited account missing. When direct debit (BG-19) is used, the debited account identifier (BT-91) containing the buyer's IBAN is required.
BR-AG-10EN 16931AUTO-FIXIPSI VAT breakdown must NOT have exemption reason
An IPSI VAT breakdown must NOT have a VAT exemption reason code or text. IPSI is a positive tax (like standard VAT), so exemption reasons are not applicable.
PEPPOL-EN16931-P0112EN 16931AUTO-FIXInvoice type code 326 or 384 are only allowed when both buyer and seller are...
Invoice type codes 326 (partial invoice) and 384 (corrective invoice) are only allowed between German organizations.
UBL-DT-06EN 16931AUTO-FIXBinary object elements shall contain the mime code attribute
Your invoice contains an embedded attachment (EmbeddedDocumentBinaryObject) but the mimeCode attribute is missing. The MIME type (e.g., application/pdf, image/png) must be specified.
UBL-DT-01EN16931AUTO-FIXAmounts shall be decimal up to two fraction digits
Your invoice contains amount values with more than 2 decimal places. EN16931 requires all monetary amounts to have maximum 2 decimal digits (e.g., 100.00 not 100.001).
BR-AF-07EN 16931BLOCKEDWhen a document level charge uses the IGIC VAT category, the VAT rate must...
When a document level charge uses the IGIC VAT category, the VAT rate must be 0% or greater.
BR-AF-08EN 16931BLOCKEDFor each IGIC VAT rate, the taxable amount must equal the sum of line net...
For each IGIC VAT rate, the taxable amount must equal the sum of line net amounts plus charges minus allowances where all use IGIC with that same rate. This is a calculation consistency check.
BR-AF-09EN 16931BLOCKEDThe VAT category tax amount for IGIC must equal the taxable amount...
The VAT category tax amount for IGIC must equal the taxable amount multiplied by the IGIC rate. This verifies the tax calculation is mathematically correct.
UBL-DT-08EN16931BLOCKEDScheme name attribute should not be present
Your invoice contains the schemeName attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-09EN16931BLOCKEDScheme agency name attribute should not be present
Your invoice contains the schemeAgencyName attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-CR-020UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference CustomerReference
Your invoice contains OrderReference/CustomerReference which is not allowed in EN16931 invoices.
UBL-DT-10EN16931BLOCKEDScheme data uri attribute should not be present
Your invoice contains the schemeDataURI attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
BR-AG-08EN 16931AUTO-FIXIPSI taxable amount calculation error
The IPSI taxable amount in the VAT breakdown does not match the calculated sum of line amounts plus charges minus allowances for the IPSI category.
UBL-DT-11EN16931BLOCKEDScheme uri attribute should not be present
Your invoice contains the schemeURI attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-14EN16931BLOCKEDUnit code list agency identifier attribute should not be present
Your invoice contains the unitCodeListAgencyID attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-15EN16931BLOCKEDUnit code list agency name attribute should not be present
Your invoice contains the unitCodeListAgencyName attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-CR-357UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation Name
Your invoice contains a DeliveryLocation Name element which is not allowed in EN16931 invoices. This element must be removed.
UBL-DT-16EN16931BLOCKEDList agency name attribute should not be present
Your invoice contains the listAgencyName attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-17EN16931BLOCKEDList name attribute should not be present
Your invoice contains the listName attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-18EN16931BLOCKEDName attribute should not be present
Your invoice contains the name attribute on an element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-21EN16931BLOCKEDList scheme uri attribute should not be present
Your invoice contains the listSchemeURI attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-22EN16931BLOCKEDLanguage local identifier attribute should not be present
Your invoice contains the languageLocaleID attribute on a text element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-23EN16931BLOCKEDUri attribute should not be present
Your invoice contains the uri attribute on an element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-24EN16931BLOCKEDCurrency code list version id should not be present
Your invoice contains the currencyCodeListVersionID attribute on a currency code. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-25EN16931BLOCKEDCharacterSetCode attribute should not be present
Your invoice contains the characterSetCode attribute on a binary object element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-28EN16931BLOCKEDList Agency ID attribute should not be present
Your invoice contains the listAgencyID attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
CII-SR-01cii-d16bAUTO-FIXCII namespace declaration required
Cross Industry Invoice must declare RSM namespace.
BR-S-08EN 16931AUTO-FIXStandard rated VAT amount doesn't add up
The taxable amount in the VAT breakdown for standard-rated items does not match the sum of the corresponding line items, charges, and allowances. For each VAT rate (e.g. 25%, 21%, 19%), the taxable base in the VAT summary must equal: sum of line amounts at that rate, plus charges at that rate, minus allowances at that rate.
CII-FIX-DATEcii-d16bAUTO-FIXCII date format must use format code 102
All dates in CII invoices must use format code 102 (YYYYMMDD) in the udt:DateTimeString element. ISO 8601 dates with hyphens (YYYY-MM-DD) are not valid in CII — the hyphens must be removed and the @format attribute set to "102".
CII-FIX-CURRENCYcii-d16bAUTO-FIXCII currency codes must be uppercase
All currency codes in CII invoices must be uppercase ISO 4217 codes. This includes the @currencyID attribute on amount elements and the ram:InvoiceCurrencyCode element. Lowercase currency codes like "eur" are invalid.
UBL-CR-028UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference Xpath
Your invoice contains BillingReference/Xpath which is not allowed in EN16931 invoices.
BR-S-10EN 16931AUTO-FIXStandard rate must not have exemption reason
VAT category S must not have exemption reason.
CII-FIX-VATEXcii-d16bAUTO-FIXCII VAT exemption reason code normalization
CII invoices with VAT categories O (Outside scope), E (Exempt), AE (Reverse charge), G (Export), or K (Intra-community) require a valid VATEX exemption reason code. This fix normalizes the ExemptionReasonCode at header level and propagates it to line-level tax breakdowns that are missing it.
BR-DEX-09DEUXRechnung (Germany)BLOCKEDThird party payment calculation error. Amount due must equal: Total with VAT...
Third party payment calculation error. Amount due must equal: Total with VAT - Paid amount + Rounding + Sum of third party payments.
BE-01BELCIUS-BE (Belgium)BLOCKEDBelgian B2B invoices should use Peppol BIS Billing 3.0
Belgian B2B invoices should use Peppol BIS Billing 3.0. This validation rule ensures Invoice compliance with CIUS-BE (Belgium).
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→