E-Invoice Error Reference
1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1359 errors found · Page 15 of 28
FORMAT-003factur-xBLOCKEDIncorrect XML attachment filename
Factur-X XML must be named correctly.
FORMAT-004zugferdBLOCKEDInvalid ZUGFeRD profile
ZUGFeRD documents must specify valid profile.
BR-DE-27DEUXRechnung (Germany)AUTO-FIXSeller Contact Telephone Must Contain At Least Three Digits
Contact telephone numbers must follow proper format guidelines. German XRechnung requires telephone numbers to be properly formatted for machine processing, typically with country code and without invalid characters.
IN-ISSUE-DATE-REQUIREDpeppol-bis-3INPUTIssue date required
Invoice must have an issue date specified.
IN-TAX-SUBTOTAL-AMOUNTpeppol-bis-3INPUTTax subtotal amount required
Each VAT breakdown (TaxSubtotal) must have a tax amount specified.
KSEF-001POLKSeFINPUTNIP validation failed
Polish NIP (tax identification number) must be 10 digits with valid checksum. Both seller and buyer NIP are required for B2B invoices. Leading zeros are significant.
BR-DE-CVD-06-bDEUXRechnung (Germany)AUTO-FIXMissing CVD Classification for Clean Vehicle Attribute
When an invoice line has an AdditionalItemProperty with Name="cva" (clean vehicle attribute), it must also have exactly one CommodityClassification with ItemClassificationCode[@listID="CVD"] containing the vehicle category. This is required for German XRechnung invoices under the Clean Vehicle Directive.
BR-DE-28DEUXRechnung (Germany)AUTO-FIXSeller Contact Email Must Have Valid Format
Contact email addresses must be valid email format. The email must contain proper structure with username, @ symbol, and domain. Invalid email addresses fail schema validation.
BR-DEX-10DEUXRechnung (Germany)AUTO-FIXMissing third party payment type. When using third party payment group...
Missing third party payment type. When using third party payment group (BG-DEX-09), the payment type (BT-DEX-001) is required.
BR-DEX-12DEUXRechnung (Germany)AUTO-FIXMissing third party payment description. When using third party payment...
Missing third party payment description. When using third party payment group (BG-DEX-09), a description (BT-DEX-003) is required.
BR-DEX-13DEUXRechnung (Germany)AUTO-FIXDie maximale Anzahl zulässiger Nachkommastellen für das Element "Third party...
Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.
UBL-CR-630UBL 2.1AUTO-FIXA UBL invoice should not include the InvoiceLine Item Price PriceList
UBL 2.1 Invoice schema does not include `cac:Price/cac:PriceList`. This element must be removed for EN 16931 compliance.
BR-DEX-14DEUXRechnung (Germany)AUTO-FIXDie Währungsangabe von "Third party payment amount" BT-DEX-002 muss BT-5...
Third party payment currency mismatch. The currency of third party payment amount must match the invoice currency (BT-5).
NL-R-009NLDNLCIUS (Netherlands)AUTO-FIXDutch suppliers using order line references must also have an order...
Dutch suppliers using order line references must also have an order reference at document level. Line-level order refs require a document-level order reference.
BE-03BELCIUS-BE (Belgium)BLOCKEDBelgian VAT numbers must be in correct format
Belgian VAT numbers must be in correct format. This validation rule ensures Invoice compliance with CIUS-BE (Belgium).
NL-R-003NLDNLCIUS (Netherlands)AUTO-FIXFor suppliers in the Netherlands, the legal entity identifier MUST be either...
Dutch suppliers must use either KVK number (scheme 0106) or OIN number (scheme 0190) as their legal entity identifier.
NL-R-005NLDNLCIUS (Netherlands)AUTO-FIXFor suppliers in the Netherlands, if the customer is in the Netherlands, the...
When both parties are Dutch, the buyer must use KVK (scheme 0106) or OIN (scheme 0190) as legal entity identifier.
NL-R-008NLDNLCIUS (Netherlands)AUTO-FIXFor Dutch domestic invoices, payment means code must be one of: 30, 48, 49,...
For Dutch domestic invoices, payment means code must be one of: 30, 48, 49, 57, 58, or 59. Other codes are not accepted.
IT-R-001ITACIUS-IT (Italy)AUTO-FIXItalian suppliers must have a tax registration identifier (BT-32) between 11...
Italian suppliers must have a tax registration identifier (BT-32) between 11 and 16 characters. This accommodates both Partita IVA (11 digits) and Codice Fiscale (16 characters).
ES-01ESPCIUS-ES (Spain)BLOCKEDSpanish sellers should include NIF/CIF
Spanish sellers should include NIF/CIF. This validation rule ensures Invoice compliance with CIUS-ES (Spain).
PL-01POLCIUS-PL (Poland)BLOCKEDPolish sellers should include NIP number
Polish sellers should include NIP number. This validation rule ensures Invoice compliance with CIUS-PL (Poland).
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-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-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-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-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.
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.
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→