E-Invoice Error Reference
1375+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1375 errors found · Page 2 of 28
DE-R-008DEUEN 16931AUTO-FIXThe element "Buyer city" (BT-52) shall be provided.
Buyer city is missing. German invoices must include the buyer's city in the address (BT-52).
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.
UBL-CR-048UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference IssueTime
Your invoice contains DespatchDocumentReference/IssueTime which is not allowed in EN16931 invoices.
CII-DT-037cii-d16bAUTO-FIXTax category TypeCode must be 'VAT'
CII-DT-037 is a fatal EN 16931 datatype assertion on the CII binding. It restricts ram:TypeCode inside ram:ApplicableTradeTax and ram:CategoryTradeTax to the literal value 'VAT'. EN 16931 is a VAT-centric standard and rejects every other UN/EDIFACT 5153 tax type.
UBL-CR-023UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference CopyIndicator
Your invoice contains BillingReference/CopyIndicator which is not allowed in EN16931 invoices.
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.
UBL-CR-053UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference LocaleCode
Your invoice contains DespatchDocumentReference/LocaleCode which is not allowed in EN16931 invoices.
BR-47EN 16931AUTO-FIXLine allowance amount required
Line-level AllowanceCharge must include the Amount element.
UBL-CR-054UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference VersionID
Your invoice contains DespatchDocumentReference/VersionID which is not allowed in EN16931 invoices.
UBL-CR-057UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference Attachment
Your invoice contains DespatchDocumentReference/Attachment which is not allowed. Attachments belong in AdditionalDocumentReference.
PEPPOL-EN16931-CL006PEPPOL_BISBLOCKEDInvoice period description code must be according to UNCL 2005 D.16B.
The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).
BR-CL-26EN 16931AUTO-FIXDelivery location identifier scheme identifier MUST belong to the ISO 6523...
A Delivery Location Identifier scheme is not a valid ISO 6523 ICD code. Location identifiers need proper scheme codes.
BR-AF-01EN 16931BLOCKEDWhen an invoice contains items, allowances, or charges with VAT category...
When an invoice contains items, allowances, or charges with VAT category "IGIC" (Canary Islands indirect tax), the VAT breakdown must include at least one entry with the IGIC VAT category code.
CII-SR-462cii-d16bINPUTOnly one DueDateTypeCode may be present across all tax breakdown entries
CII-SR-462 is a fatal EN 16931 syntax rule on the CII binding. It asserts that across every ram:ApplicableTradeTax block in the document, either no ram:DueDateTypeCode is present, or every DueDateTypeCode carries the same value. The XPath test is count(//ram:ApplicableTradeTax/ram:DueDateTypeCode)=0 or count(distinct-values(//ram:ApplicableTradeTax/ram:DueDateTypeCode))=1.
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.
UBL-CR-058UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference ValidityPeriod
Your invoice contains DespatchDocumentReference/ValidityPeriod which is not allowed in EN16931 invoices.
UBL-CR-060UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference...
Your invoice contains DespatchDocumentReference/ResultOfVerification which is not allowed in EN16931 invoices.
UBL-DT-12EN16931BLOCKEDFormat attribute should not be present
Your invoice contains the format attribute on an element. This attribute is not allowed in EN16931 and must be removed.
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.
PEPPOL-EN16931-CL007PEPPOL_BISBLOCKEDCurrency code must be according to ISO 4217:2005
Currency codes must be valid ISO 4217:2005 codes. Only standard 3-letter currency codes like EUR, USD, GBP are accepted.
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-O-11EN 16931BLOCKEDMixed VAT categories with "Not subject to VAT". When using VAT category O...
Mixed VAT categories with "Not subject to VAT". When using VAT category O (Not subject to VAT), no other VAT categories are allowed on the invoice.
BR-O-13EN 16931BLOCKEDInconsistent allowance VAT with "Not subject to VAT". Document allowances...
Inconsistent allowance VAT with "Not subject to VAT". Document allowances must use VAT category O when the invoice uses "Not subject to VAT".
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-011UBL 2.1AUTO-FIXA UBL invoice should not include the LineCountNumeric
Your invoice contains LineCountNumeric which is not allowed in EN16931 invoices.
BR-DEC-11EN 16931AUTO-FIXThe allowed maximum number of decimals for the Sum of charges on document...
The sum of document level charges has too many decimal places. This total must have a maximum of 2 decimal places.
BR-DEC-13EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice total VAT amount...
The invoice total VAT amount has too many decimal places. The total tax amount must have a maximum of 2 decimal places.
BR-DEC-14EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice total amount with VAT...
The invoice total amount with VAT (tax inclusive amount) has too many decimal places. This grand total must have a maximum of 2 decimal places.
BR-DEC-24EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line allowance amount...
The invoice line allowance amount has too many decimal places. Line-level allowance amounts must have a maximum of 2 decimal places.
BR-DEC-25EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line allowance base...
The invoice line allowance base amount has too many decimal places. The base amount for calculating line allowances must have a maximum of 2 decimal places.
BR-DEC-27EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line charge amount...
The invoice line charge amount has too many decimal places. Line-level charge amounts must have a maximum of 2 decimal places.
BR-DEC-28EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line charge base...
The invoice line charge base amount has too many decimal places. The base amount for calculating line charges must have a maximum of 2 decimal places.
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.
UBL-CR-359UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation Address ID
Your invoice contains a DeliveryLocation Address ID element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-385UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery CarrierParty
Your invoice contains a CarrierParty element which is not allowed in EN16931 invoices. This element must be removed.
DE-R-017DEUEN 16931AUTO-FIXInvalid invoice type code. German invoices only allow specific type codes:...
Invalid invoice type code. German invoices only allow specific type codes: 326 (partial), 380 (commercial), 384 (corrected), 389 (self-billed), 381 (credit note), 875-877 (construction).
DE-R-019DEUEN 16931AUTO-FIXInvalid IBAN format. When payment means code 58 (SEPA credit transfer) is...
Invalid IBAN format. When payment means code 58 (SEPA credit transfer) is used, the payment account (BT-84) must contain a valid IBAN.
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.
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.
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→