E-Invoice Error Reference
1369+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
755 errors found · Page 2 of 16 in Format Rules
UBL-CR-034UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference Attachment
Your invoice contains BillingReference/Attachment which is not allowed. Attachments belong in AdditionalDocumentReference, not BillingReference.
UBL-CR-358UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation ValidityPeriod
Your invoice contains a DeliveryLocation ValidityPeriod element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-036UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference IssuerParty
Your invoice contains BillingReference/IssuerParty which is not allowed in EN16931 invoices.
FORMAT-001internalBLOCKEDUnrecognized invoice format
Your file was read successfully as XML, but it does not contain a recognized e-invoice structure. Supported formats are UBL 2.1 Invoice, UBL 2.1 CreditNote, and UN/CEFACT Cross-Industry Invoice (CII D16B). The file may have been exported in the wrong format, or it may be a different type of XML document (such as an order or dispatch advice).
UBL-CR-037UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference ResultOfVerification
Your invoice contains BillingReference/ResultOfVerification which is not allowed in EN16931 invoices.
UBL-CR-038UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference...
Your invoice contains BillingReference/SelfBilledInvoiceDocumentReference which is not allowed in EN16931 invoices.
UBL-CR-040UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference...
Your invoice contains BillingReference/SelfBilledCreditNoteDocumentReference which is not allowed in EN16931 invoices.
UBL-CR-041UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference DebitNoteDocumentReference
Your invoice contains BillingReference/DebitNoteDocumentReference which is not allowed in EN16931 invoices.
UBL-SR-49EN16931CONFIRMValue tax point date shall occur maximum once
Your invoice contains multiple Value tax point date elements (TaxPointDate). EN16931 allows only one tax point date per invoice.
UBL-CR-046UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference UUID
Your invoice contains DespatchDocumentReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-622UBL 2.1AUTO-FIXA UBL invoice should not include the InvoiceLine Item ItemInstance
UBL 2.1 Invoice schema does not include `cac:Item/cac:ItemInstance`. This element must be removed for EN 16931 compliance.
UBL-SR-50EN16931CONFIRMItem description shall occur maximum once
Your invoice line Item contains multiple Description elements. EN16931 allows only one item description per line.
UBL-CR-006UBL 2.1AUTO-FIXDisallowed element: cbc:IssueTime
UBL 2.1 Invoice schema does not include `cbc:IssueTime`. This element must be removed for EN 16931 compliance.
FORMAT-002factur-xBLOCKEDPDF must be PDF/A format
Factur-X requires PDF/A-3 base document.
IN-PAYABLE-POSITIVEpeppol-bis-3BLOCKEDPayable amount should be positive
The amount due for payment (PayableAmount) should typically be a positive value.
IN-PRICE-POSITIVEpeppol-bis-3BLOCKEDItem price should be positive
Item price (PriceAmount) should typically be a positive value.
IN-QUANTITY-POSITIVEpeppol-bis-3BLOCKEDLine quantity should be positive
Invoice line quantity (InvoicedQuantity) should typically be a positive value.
UBL-CR-411UBL 2.1AUTO-FIXA UBL invoice should not include the PaymentMeans ID
Your invoice contains a PaymentMeans ID element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-055UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference...
Your invoice contains DespatchDocumentReference/DocumentStatusCode which is not allowed in EN16931 invoices.
UBL-CR-024UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference UUID
Your invoice contains BillingReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-009UBL 2.1AUTO-FIXDisallowed element: cbc:PaymentAlternativeCurrencyCode
UBL 2.1 Invoice schema does not include `cbc:PaymentAlternativeCurrencyCode`. This element must be removed for EN 16931 compliance.
UBL-CR-412EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans PaymentDueDate
Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.
PEPPOL-EN16931-CL002PEPPOL_BISAUTO-FIXReason code MUST be according to subset of UNCL 5189 D.16B.
The allowance reason code must be from the UNCL 5189 D.16B subset. This code explains why a discount or allowance is being applied.
PEPPOL-EN16931-CL003PEPPOL_BISAUTO-FIXReason code MUST be according to UNCL 7161 D.16B.
The charge reason code must be from the UNCL 7161 D.16B list. This code explains why a surcharge or additional charge is being applied.
UBL-CR-027UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference DocumentType
Your invoice contains BillingReference/DocumentType which is not allowed in EN16931. Only the document ID is permitted for billing references.
UBL-CR-025UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference IssueTime
Your invoice contains BillingReference/IssueTime which is not allowed in EN16931 invoices.
SIZE-001BLOCKEDInvoice file too large to process
Your invoice file exceeds the 10MB size limit and cannot be validated or processed. This usually happens when large attachments (PDFs, images) are embedded directly in the XML file.
IN-ALLOWANCE-AMOUNT-REQUIREDpeppol-bis-3INPUTAllowance/Charge amount required
AllowanceCharge elements must have an Amount element specified.
IN-TAX-TOTAL-AMOUNTpeppol-bis-3INPUTTax total amount required
Invoice must have a total VAT amount in the TaxTotal element.
UBL-SR-45EN16931CONFIRMDue Date shall occur maximum once
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
UBL-SR-11EN16931CONFIRMSeller legal registration identifier shall occur maximum once
Your invoice contains multiple Seller legal registration identifiers (PartyLegalEntity/CompanyID). EN16931 allows only one legal registration ID per seller.
UBL-SR-14EN16931CONFIRMSeller additional legal information shall occur maximum once
Your invoice contains multiple Seller additional legal information elements (PartyLegalEntity/CompanyLegalForm). EN16931 allows only one.
UBL-SR-17EN16931CONFIRMBuyer legal registration identifier shall occur maximum once
Your invoice contains multiple Buyer legal registration identifiers (PartyLegalEntity/CompanyID). EN16931 allows only one legal registration ID per buyer.
UBL-SR-19EN16931CONFIRMPayee name shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee name elements (PayeeParty/PartyName/Name). EN16931 allows only one payee name.
UBL-SR-20EN16931CONFIRMPayee identifier shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee identifier elements (PayeeParty/PartyIdentification/ID). EN16931 allows only one payee identifier.
UBL-SR-21EN16931CONFIRMPayee legal registration identifier shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee legal registration identifiers (PayeeParty/PartyLegalEntity/CompanyID). EN16931 allows only one.
UBL-SR-22EN16931CONFIRMSeller tax representative name shall occur maximum once, if the Seller has a tax representative
Your invoice contains multiple Tax representative name elements (TaxRepresentativeParty/PartyName/Name). EN16931 allows only one.
UBL-SR-24EN16931CONFIRMDeliver to information shall occur maximum once
Your invoice contains multiple Delivery location elements. EN16931 allows only one Delivery element per invoice.
UBL-SR-26EN16931CONFIRMPayment reference shall occur maximum once
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
UBL-SR-29EN16931CONFIRMBank creditor reference shall occur maximum once
Your invoice contains multiple Bank creditor reference elements (PaymentMeans/PayeeFinancialAccount/ID with creditor reference). EN16931 allows only one.
UBL-SR-31EN16931CONFIRMDocument level charge reason shall occur maximum once
Your invoice contains multiple Document level charge reason texts (AllowanceCharge/AllowanceChargeReason). EN16931 allows only one reason per charge.
UBL-SR-32EN16931CONFIRMVAT exemption reason text shall occur maximum once
Your invoice contains multiple VAT exemption reason texts (TaxCategory/TaxExemptionReason). EN16931 allows only one exemption reason per VAT category.
UBL-SR-33EN16931CONFIRMSupporting document description shall occur maximum once
Your invoice contains multiple Supporting document description elements (AdditionalDocumentReference/DocumentDescription). EN16931 allows only one description per document.
UBL-DT-20EN16931BLOCKEDList uri attribute should not be present
Your invoice contains the listURI attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
UBL-SR-34EN16931CONFIRMInvoice line note shall occur maximum once
Your invoice line contains multiple Note elements (InvoiceLine/Note). EN16931 allows only one note per invoice line.
UBL-SR-35EN16931CONFIRMReferenced purchase order line identifier shall occur maximum once
Your invoice line contains multiple Referenced purchase order line identifiers (OrderLineReference/LineID). EN16931 allows only one per line.
UBL-SR-36EN16931CONFIRMInvoice line period shall occur maximum once
Your invoice line contains multiple Invoice line period elements (InvoiceLine/InvoicePeriod). EN16931 allows only one period per line.
UBL-SR-39EN16931CONFIRMProject reference shall occur maximum once.
Your invoice contains multiple Project reference elements (ProjectReference/ID). EN16931 allows only one project reference per invoice.
UBL-SR-40EN16931CONFIRMBuyer trade name shall occur maximum once
Your invoice contains multiple Buyer trade name elements (AccountingCustomerParty/Party/PartyName). EN16931 allows only one buyer trading name.
UBL-SR-42EN16931CONFIRMParty tax scheme shall occur maximum twice in accounting supplier party
Your seller party (AccountingSupplierParty) contains more than two PartyTaxScheme elements. EN16931 allows maximum two (one VAT scheme and optionally one other tax scheme).
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→