E-Invoice Error Reference
1369+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1369 errors found · Page 12 of 28
UBL-SR-09ubl-2.1CONFIRMInvalid boolean value
Boolean elements must be true or false.
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.
FR-01FRACIUS-FR (France)BLOCKEDFrench sellers should include SIRET number
French sellers should include SIRET number. This validation rule ensures Invoice compliance with CIUS-FR (France).
UBL-SR-03ubl-2.1CONFIRMUBL element order incorrect
UBL elements must follow schema-defined order.
UBL-SR-10ubl-2.1CONFIRMInvalid decimal format
Decimal numbers must use period as separator.
DK-R-007DNKOIOUBL (Denmark)INPUTFor Danish suppliers PaymentMandate/ID and PayerFinancialAccount/ID are...
Danish suppliers using payment means 49 (direct debit) must provide both PaymentMandate/ID and PayerFinancialAccount/ID. These identify the mandate agreement and account to debit.
DK-R-011DNKOIOUBL (Denmark)INPUTDanish suppliers using FIK payment with 71# or 75# prefix must include a...
Danish suppliers using FIK payment with 71# or 75# prefix must include a 15-16 digit instruction ID in the PaymentID.
GR-S-008-1GRCCIUS-GR (Greece)INPUTWhen Supplier is Greek, there should be one invoice url
Greek supplier invoices should include one invoice URL for accessing the invoice document. This is a recommendation for better accessibility.
IS-R-002ISLCIUS-IS (Iceland)INPUTIcelandic suppliers must provide their Icelandic legal ID (kennitala). This...
Icelandic suppliers must provide their Icelandic legal ID (kennitala). This 10-digit identifier is mandatory for Icelandic business invoices.
IS-R-003ISLCIUS-IS (Iceland)INPUTIcelandic suppliers must provide complete address with street name and...
Icelandic suppliers must provide complete address with street name and postal code. This is mandatory for Icelandic invoices.
IS-R-004ISLCIUS-IS (Iceland)INPUTWhen both seller and buyer are Icelandic, the buyer's kennitala must be...
When both seller and buyer are Icelandic, the buyer's kennitala must be provided. This is required for domestic Icelandic transactions.
IS-R-005ISLCIUS-IS (Iceland)INPUTWhen both seller and buyer are Icelandic, the buyer's address must include...
When both seller and buyer are Icelandic, the buyer's address must include street name and postal code. Complete address is required for domestic transactions.
IS-R-009ISLCIUS-IS (Iceland)INPUTIcelandic invoices with EINDAGI (final due date) must also have a regular...
Icelandic invoices with EINDAGI (final due date) must also have a regular due date (BT-9). The due date is required when EINDAGI is present.
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.
DE-R-022DEUPEPPOL_BISCONFIRMDuplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) i
Duplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) in element BT-125.
DE-R-023-2DEUPEPPOL_BISCONFIRMConflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct d
Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct debit (BG-19) groups must not be provided.
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.
DE-R-024-2DEUPEPPOL_BISCONFIRMConflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and dir
Conflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and direct debit (BG-19) groups must not be provided.
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.
DE-R-025-1DEUPEPPOL_BISCONFIRMIf "Payment means type code" (BT-81) contains a code for direct debit (59), "DIRECT DEBIT" (BG-19) shall be provided.
Direct debit details missing. When payment code 59 (direct debit) is used, the Direct Debit group (BG-19) with mandate information must be provided.
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.
DE-R-025-2DEUPEPPOL_BISCONFIRMIf "Payment means type code" (BT-81) contains a code for direct debit (59), BG-17 and BG-18 shall not be provided.
Conflicting payment information. When payment code 59 (direct debit) is used, credit transfer (BG-17) and card payment (BG-18) groups must not be provided.
DE-R-026DEUPEPPOL_BISCONFIRMPreceding invoice reference missing. Corrected invoices (type code 384) should reference the original invoice being corr
Preceding invoice reference missing. Corrected invoices (type code 384) should reference the original invoice being corrected in group BG-3.
PEPPOL-EN16931-R043Peppol BIS 3.0AUTO-FIXAllowance/charge ChargeIndicator value MUST equal "true" or "false"
The ChargeIndicator on one of your discounts or surcharges is not in the correct format. It must be exactly "true" (for a surcharge) or "false" (for a discount), in lowercase.
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.
IN-PAYMENT-MEANS-CODESPeppol BIS 3.0BLOCKEDPayment means codes validation
Payment means codes should be from recommended UNCL4461 subset
DE-R-027DEUPEPPOL_BISCONFIRMInvalid phone number format. The seller contact telephone number (BT-42) must contain at least 3 digits to be valid.
Invalid phone number format. The seller contact telephone number (BT-42) must contain at least 3 digits to be valid.
DE-R-028DEUPEPPOL_BISCONFIRMInvalid email format. The seller contact email (BT-43) must contain exactly one @ sign with at least two characters on e
Invalid email format. The seller contact email (BT-43) must contain exactly one @ sign with at least two characters on each side, and no dots at start or end.
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).
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.
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→