E-Invoice Error Reference
1350+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1350 errors found · Page 15 of 27
AT-R-003AUTCIUS-AT (Austria)INPUTAustrian postal code format
Austrian postal codes should be 4 digits.
DK-R-014DNKOIOUBL (Denmark)AUTO-FIXDanish company registration number has wrong scheme code
Your Danish company registration number (CVR) is present but uses the wrong scheme identifier. Danish suppliers must use scheme code 0184 to indicate a CVR number.
DK-R-003DNKOIOUBL (Denmark)AUTO-FIXIf ItemClassification is provided from Danish suppliers, UNSPSC version...
Danish suppliers using item classification must use UNSPSC version 19.05.01 or 26.08.01. Other UNSPSC versions are not accepted for Danish e-invoicing.
DK-R-002DNKOIOUBL (Denmark)INPUTDanish seller Peppol address missing
Danish suppliers must include a NemHandel (Peppol) electronic address with their CVR number. This is your company's identifier on the Danish invoicing network.
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.
DK-R-008DNKOIOUBL (Denmark)AUTO-FIXDanish suppliers using Giro payment (code 50) must provide PaymentID...
Danish suppliers using Giro payment (code 50) must provide PaymentID starting with 01#, 04#, or 15# and a 7-8 digit Giro account number.
DK-R-010DNKOIOUBL (Denmark)AUTO-FIXDanish suppliers using FIK payment (code 93) must provide PaymentID starting...
Danish suppliers using FIK payment (code 93) must provide PaymentID starting with 71#, 73#, or 75# and an exactly 8-character creditor number.
DK-R-013DNKOIOUBL (Denmark)AUTO-FIXDanish suppliers must specify the schemeID when using PartyIdentification/ID...
Danish suppliers must specify the schemeID when using PartyIdentification/ID for either supplier or customer. The scheme identifies what type of ID is being used.
DK-R-016DNKOIOUBL (Denmark)BLOCKEDFor Danish Suppliers, a Credit note cannot have a negative total (PayableAmount)
Danish credit notes cannot have a negative PayableAmount. Credit notes should have positive amounts representing the credit being issued.
UBL-CR-257UBL 2.1AUTO-FIXA UBL invoice should not include the AccountingCustomerParty Party Person
Your invoice contains a Person element in the buyer party which is not allowed in EN16931 invoices. This element must be removed.
NO-R-001NOREHF (Norway)AUTO-FIXNorwegian organization number required
Norwegian invoices must include 9-digit organization number.
NO-R-002NOREHF (Norway)AUTO-FIXFor Norwegian suppliers (AS, ASA, or foreign branch), the word...
Norwegian B2G invoices must use EHF (Elektronisk Handelsformat).
GR-R-009GRCCIUS-GR (Greece)AUTO-FIXGreek suppliers must use their correct TIN as the electronic address for...
Greek suppliers must use their correct TIN as the electronic address for PEPPOL (scheme 9933). This ensures proper routing on the PEPPOL network.
GR-S-011GRCCIUS-GR (Greece)AUTO-FIXGreek suppliers must provide their Seller Tax Registration Number, prefixed...
Greek suppliers must provide their Seller Tax Registration Number with the country code prefix. This is the VAT identification for Greek tax purposes.
GR-R-010GRCCIUS-GR (Greece)AUTO-FIXWhen Greek suppliers send invoices to Greek buyers via PEPPOL, the buyer...
When Greek suppliers send invoices to Greek buyers via PEPPOL, the buyer must also use their TIN as electronic address (scheme 9933).
GR-R-008-2GRCCIUS-GR (Greece)AUTO-FIXWhen Supplier is Greek, there should be no more than one invoice url
Greek supplier invoices should have no more than one invoice URL. Multiple URLs are not allowed in Greek e-invoicing.
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.
GR-R-004-2GRCCIUS-GR (Greece)AUTO-FIXWhen Supplier is Greek, the MARK Number must be a positive integer
The Greek MARK number must be a positive integer. MARK is a sequential number assigned by myDATA and cannot be zero, negative, or contain decimals.
GR-R-001-2GRCCIUS-GR (Greece)AUTO-FIXThe first segment of Greek invoice ID must be a valid TIN matching the...
The first segment of Greek invoice ID must be a valid TIN matching the supplier or tax representative. This links the invoice to the correct Greek tax entity.
UBL-CR-398UBL 2.1AUTO-FIXA UBL invoice should not include the DeliveryParty Contact
Your invoice contains a DeliveryParty Contact element which is not allowed in EN16931 invoices. This element must be removed.
GR-R-001-1GRCCIUS-GR (Greece)AUTO-FIXWhen the Supplier is Greek, the Invoice Id should consist of 6 segments
Greek supplier invoices must have an Invoice ID consisting of 6 segments. This special format is required for Greek tax authority (AADE) reporting.
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-008ISLCIUS-IS (Iceland)AUTO-FIXWhen Icelandic invoices include EINDAGI (final due date) in supporting...
When Icelandic invoices include EINDAGI (final due date) in supporting documents, the date must be in YYYY-MM-DD format.
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.
IS-R-001ISLCIUS-IS (Iceland)AUTO-FIXIcelandic suppliers can only issue invoice type 380 (invoice) or 381 (credit...
Icelandic suppliers can only issue invoice type 380 (invoice) or 381 (credit note). Other document types are not supported for Icelandic e-invoicing.
IS-R-010ISLCIUS-IS (Iceland)AUTO-FIXWhen EINDAGI (final due date) is provided, it must be the same as or later...
When EINDAGI (final due date) is provided, it must be the same as or later than the regular due date. EINDAGI cannot be before the due date.
IS-R-006ISLCIUS-IS (Iceland)BLOCKEDIcelandic suppliers using payment means code 9 (claim/krafa) must provide a...
Icelandic suppliers using payment means code 9 (claim/krafa) must provide a 12-digit account ID consisting of bank number, ledger 66, and account number.
IS-R-007ISLCIUS-IS (Iceland)BLOCKEDIcelandic suppliers using payment means code 42 (bank transfer) must provide...
Icelandic suppliers using payment means code 42 (bank transfer) must provide a 12-digit bank account number.
UBL-CR-001UBL 2.1AUTO-FIXDisallowed element: ext:UBLExtensions
UBL 2.1 Invoice schema does not include `ext:UBLExtensions`. This element must be removed for EN 16931 compliance.
UBL-CR-404UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery NotifyParty
Your invoice contains a Delivery NotifyParty element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-003UBL 2.1AUTO-FIXDisallowed element: cbc:ProfileExecutionID
Each invoice line must have a unique ID within the invoice. Duplicate IDs found.
UBL-CR-004UBL 2.1AUTO-FIXDisallowed element: cbc:CopyIndicator
UBL 2.1 Invoice schema does not include `cbc:CopyIndicator`. This element must be removed for EN 16931 compliance.
UBL-CR-005UBL 2.1AUTO-FIXDocument MUST NOT contain cbc:UUID
Required elements must not be empty or contain only whitespace.
UBL-CR-007UBL 2.1AUTO-FIXDisallowed element: cbc:PricingCurrencyCode
UBL invoices should have at most two TaxTotal elements (document and optional tax currency).
UBL-CR-008UBL 2.1AUTO-FIXDisallowed element: cbc:PaymentCurrencyCode
TaxTotal element must contain at least one TaxSubtotal.
UBL-CR-010UBL 2.1AUTO-FIXDisallowed element: cbc:AccountingCostCode
UBL 2.1 Invoice schema does not include `cbc:AccountingCostCode`. This element must be removed for EN 16931 compliance.
UBL-CR-410UBL 2.1AUTO-FIXA UBL invoice should not include the DeliveryTerms
Your invoice contains a DeliveryTerms element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-490UBL 2.1AUTO-FIXA UBL invoice should not include the TaxExchangeRate
Your invoice contains a TaxExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-492UBL 2.1AUTO-FIXA UBL invoice should not include the PaymentExchangeRate
Your invoice contains a PaymentExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-513UBL 2.1AUTO-FIXA UBL invoice should not include the WithholdingTaxTotal
Your invoice contains a WithholdingTaxTotal element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-013UBL 2.1AUTO-FIXA UBL invoice should not include the InvoicePeriod EndTime
Your invoice contains InvoicePeriod/EndTime which is not allowed. Only EndDate is permitted.
UBL-CR-018UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference IssueDate
Your invoice contains OrderReference/IssueDate which is not allowed in EN16931 invoices.
UBL-CR-021UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference OrderTypeCode
Your invoice contains OrderReference/OrderTypeCode which is not allowed in EN16931 invoices.
UBL-CR-022UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference DocumentReference
Your invoice contains OrderReference/DocumentReference which is not allowed in EN16931 invoices.
UBL-CR-026UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference DocumentTypeCode
Your invoice contains BillingReference/DocumentTypeCode which is not allowed in EN16931. Only the document ID is permitted for billing references.
UBL-CR-030UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference LocaleCode
Your invoice contains BillingReference/LocaleCode which is not allowed in EN16931 invoices.
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→