E-Invoice Error Reference
1374+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1374 errors found · Page 13 of 28
CII-FIX-LINE-AMOUNTScii-d16bCONFIRMCII line total amount recalculation
Each invoice line total (ram:LineTotalAmount) must equal the unit price times quantity, plus charges minus allowances. When the declared amount differs from the calculated amount by more than 1 cent, the system can recalculate it. This changes a financial value and requires your confirmation.
CII-FIX-TAX-AMOUNTScii-d16bCONFIRMCII tax amount recalculation
Each tax breakdown amount (ram:CalculatedAmount) must equal the taxable amount times the tax rate. When the declared tax amount differs from the calculated amount by more than 1 cent, the system can recalculate it. This changes a financial value and requires your confirmation.
UBL-SR-43EN16931AUTO-FIXScheme identifier shall only be used for invoiced object (document type code with value 130 or 50)
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). Scheme identifiers are only valid for these document types.
CII-FIX-TOTALScii-d16bCONFIRMCII invoice totals recalculation
The invoice header totals must be internally consistent: LineTotalAmount must equal the sum of line totals, TaxBasisTotalAmount must equal LineTotalAmount + charges - allowances, GrandTotalAmount must equal TaxBasisTotalAmount + TaxTotalAmount, and DuePayableAmount must equal GrandTotalAmount - prepaid amounts. This recalculates the entire cascade and requires your confirmation because it modifies financial values.
UBL-SR-15EN16931CONFIRMBuyer name shall occur maximum once
Your invoice contains multiple Buyer name elements (AccountingCustomerParty/Party/PartyName/Name). EN16931 allows only one buyer name.
UBL-SR-51EN16931CONFIRMAn address can only have one third line.
Duplicate address line 3. An address can have at most one additional address line (third line).
UBL-SR-52EN16931CONFIRMDocument reference shall occur maximum once
Duplicate document reference. Document reference can only appear once in the specified context.
DE-R-018DEUPEPPOL_BISCONFIRMInvalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with
Invalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with optional #BASISBETRAG=N#. Must be uppercase with no extra whitespace.
UBL-SR-18EN16931CONFIRMBuyer VAT identifier shall occur maximum once
Your invoice contains multiple Buyer VAT identifiers (PartyTaxScheme with VAT scheme). EN16931 allows only one VAT identifier per buyer.
UBL-SR-37EN16931CONFIRMItem price discount shall occur maximum once
Your invoice line contains multiple Item price discount elements (Price/AllowanceCharge). EN16931 allows only one discount per price.
IT-01ITACIUS-IT (Italy)BLOCKEDItalian sellers should include Codice Fiscale or Partita IVA
Italian sellers should include Codice Fiscale or Partita IVA. This validation rule ensures Invoice compliance with CIUS-IT (Italy).
UBL-CR-029UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference LanguageID
Your invoice contains BillingReference/LanguageID which is not allowed in EN16931 invoices.
UBL-SR-47EN 16931AUTO-FIXMultiple different payment methods on one invoice
Your invoice has multiple payment means sections with different payment method codes. The UBL standard requires that all payment means on a single invoice use the same payment method code.
UBL-CR-031UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference VersionID
Your invoice contains BillingReference/VersionID which is not allowed in EN16931 invoices.
PEPPOL-COMMON-R046Peppol BIS 3.0AUTO-FIXTax Code (Codice Fiscale) must be stated in the correct format
Italian Tax Code (Codice Fiscale) must follow the correct format. This validation applies to a different location in the invoice where tax codes appear.
PEPPOL-COMMON-R044Peppol BIS 3.0AUTO-FIXItalian office code (IPA) has wrong format
The Italian IPA code (Codice Univoco Unità Organizzativa) on your invoice is not in the correct format. It must be exactly 6 uppercase letters and/or digits.
BR-01EN 16931AUTO-FIXInvoice must have specification identifier
Every Peppol BIS invoice must include a specification identifier (CustomizationID) that indicates which profile the invoice conforms to.
BR-23EN 16931AUTO-FIXMissing unit of measure code
Each Invoice line shall have an Invoiced quantity unit of measure code (BT-130). This identifies the unit of measure for the invoiced quantity using UN/ECE Recommendation 20 codes.
UBL-CR-665EN16931AUTO-FIXA UBL invoice should not include the AdditionalDocumentReference ID schemeID unless the DocumentTypeCode equals '130'
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
PEPPOL-EN16931-R008Peppol BIS 3.0AUTO-FIXDocument MUST not contain empty elements.
The document must not contain empty XML elements. All elements that are present must have content - empty tags are not allowed in PEPPOL invoices.
BR-30EN 16931AUTO-FIXInvoice line period end date before start date
If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the end date shall be later or equal to the start date.
UBL-CR-680EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans/PayerFinancialAccount
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-CR-681EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans InstructionNote
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-CR-682EN16931AUTO-FIXA UBL invoice should not include the Delivery DeliveryAddress
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
BR-51EN 16931AUTO-FIXPayment card primary account number not masked
The invoice contains a full credit card number (BT-87), which violates PCI security standards. Only the first 6 and last 4 digits should be shown.
UBL-DT-13EN16931BLOCKEDUnit code list identifier attribute should not be present
Your invoice contains the unitCodeListID attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-SR-12EN 16931AUTO-FIXSeller VAT identifier shall occur maximum once
Your invoice contains multiple Seller VAT identifiers (PartyTaxScheme with VAT scheme). EN16931 allows only one VAT identifier per seller.
BR-05EN 16931AUTO-FIXMissing document currency code
An Invoice shall have an Invoice currency code (BT-5). This specifies the currency used for all monetary amounts in the invoice using ISO 4217 three-letter codes.
PEPPOL-COMMON-R049Peppol BIS 3.0AUTO-FIXInvalid Swedish organization number
A Swedish organization number (organisationsnummer) in this invoice is not correctly formatted. Swedish org numbers must be exactly 10 digits and include a valid check digit calculated using the Luhn algorithm. This applies to any identifier using scheme 0007, including seller and buyer endpoint addresses, company registration numbers, and party identifiers.
UBL-DT-26EN16931BLOCKEDEncodingCode attribute should not be present
Your invoice contains the encodingCode attribute on a binary object element. This attribute is not allowed in EN16931 and must be removed.
BR-42EN 16931AUTO-FIXInvoice line allowance reason required
An invoice line allowance (BG-27) is missing both a reason text (BT-139) and reason code (BT-140). At least one must be provided to explain this line discount.
UBL-DT-27EN16931BLOCKEDScheme Agency ID attribute should not be present
Your invoice contains the schemeAgencyID attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-SR-16EN16931CONFIRMBuyer identifier shall occur maximum once
Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier.
BR-AG-05EN 16931AUTO-FIXIPSI invoice line VAT rate must be 0% or positive
When an invoice line uses the IPSI VAT category (M for Ceuta/Melilla indirect tax), the VAT rate must be 0 or greater than zero.
PEPPOL-EN16931-R101Peppol BIS 3.0AUTO-FIXInvoice line document reference has wrong type code
A document reference on one of your invoice lines uses the wrong type code. Line-level document references in Peppol invoices must use code "130", which means "invoice line object identifier".
UBL-SR-23EN16931CONFIRMSeller tax representative VAT identifier shall occur maximum once, if the Seller has a tax representative
Your invoice contains multiple Tax representative VAT identifiers (TaxRepresentativeParty/PartyTaxScheme). EN16931 allows only one.
UBL-SR-25EN16931CONFIRMDeliver to party name shall occur maximum once
Your invoice contains multiple Deliver to party name elements (Delivery/DeliveryParty/PartyName/Name). EN16931 allows only one.
BR-CL-13EN 16931AUTO-FIXInvalid product classification scheme
A line item's classification code uses an invalid scheme identifier. The classification listID must be from the UNTDID 7143 code list. Common valid schemes include STI for UNSPSC, EN for eCl@ss, and CPV for EU public procurement.
UBL-SR-30EN16931CONFIRMDocument level allowance reason shall occur maximum once
Your invoice contains multiple Document level allowance reason texts (AllowanceCharge/AllowanceChargeReason). EN16931 allows only one reason per allowance.
PEPPOL-COMMON-R041Peppol BIS 3.0AUTO-FIXNorwegian organization number MUST be stated in the correct format.
Norwegian organization numbers must follow the correct format. The organization number is a 9-digit identifier assigned by Brønnøysund Register Centre.
PEPPOL-COMMON-R042Peppol BIS 3.0AUTO-FIXDanish organization number (CVR) MUST be stated in the correct format.
Danish organization numbers (CVR) must follow the correct format. CVR is an 8-digit identifier assigned by the Danish Business Authority.
PEPPOL-COMMON-R043Peppol BIS 3.0AUTO-FIXBelgian enterprise number MUST be stated in the correct format.
Belgian enterprise numbers must follow the correct format. The enterprise number is a 10-digit identifier (0XXX.XXX.XXX format) assigned by the Crossroads Bank for Enterprises.
PEPPOL-COMMON-R045Peppol BIS 3.0AUTO-FIXTax Code (Codice Fiscale) must be stated in the correct format
Italian Tax Code (Codice Fiscale) must follow the correct format. For individuals, this is a 16-character alphanumeric code; for companies, it may be an 11-digit VAT number.
UBL-SR-46EN16931CONFIRMPayment means text shall occur maximum once
Your invoice contains multiple Payment means instruction text elements. EN16931 allows only one instruction note per payment means.
PEPPOL-EN16931-R053Peppol BIS 3.0AUTO-FIXOnly one tax total with tax subtotals MUST be provided.
Only one TaxTotal element with tax subtotals (VAT breakdown) is allowed. Multiple VAT breakdowns in the same currency are not permitted.
SE-R-001Peppol BIS 3.0AUTO-FIXSwedish organization number required
Swedish invoices must include 10-digit organization number.
BR-CL-24EN 16931AUTO-FIXFor Mime code in attribute use MIMEMediaType (IANA media types).
An attached document has an invalid MIME type code. MIME types must follow the standard format (type/subtype), such as application/pdf for PDF files, image/png for PNG images, or text/csv for CSV files.
SE-R-002Peppol BIS 3.0AUTO-FIXFor Swedish suppliers, Swedish VAT-numbers must have the trailing 12...
Swedish invoices to public sector should be Svefaktura compliant.
UBL-SR-53EN16931CONFIRMCompanyID (VAT Identifier) must be stated when providing the PartyTaxScheme/TaxScheme/ID.
Missing VAT ID with tax scheme. When providing TaxScheme/ID, the CompanyID (VAT identifier) must also be provided.
SE-R-004Peppol BIS 3.0AUTO-FIXSwedish organisation number has wrong length
The seller's Swedish organisation number (organisationsnummer) does not have the required 10 characters. Swedish org numbers are always exactly 10 digits, typically written as XXXXXX-XXXX but stored without the hyphen.
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→