E-Invoice Error Reference
1375+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1375 errors found · Page 5 of 28
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.
PL-R-004POLubl-2.1BLOCKEDKSeF session token invalid
KSeF API requires valid authentication token.
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.
SDI-00200ITAFatturaPABLOCKEDDuplicate invoice number
Invoice number + year combination must be unique per sender. SDI maintains a registry and rejects duplicates within the same fiscal year.
PL-R-006POLubl-2.1BLOCKEDCurrency must be PLN for KSeF
Invoices to Polish KSeF typically require PLN amounts.
UBL-SR-50EN16931CONFIRMItem description shall occur maximum once
Your invoice line Item contains multiple Description elements. EN16931 allows only one item description per line.
BR-G-02EN 16931INPUTWhen using this VAT category, the seller must have a VAT identifier, tax...
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative (applies to `cac:InvoiceLine`, rule BR-G-02).
BR-IC-07EN 16931AUTO-FIXIntra-community requires reason
VAT category K must have exemption reason.
GR-R-003GRCCIUS-GR (Greece)AUTO-FIXGreek invoice type code required
myDATA requires specific Greek invoice type classification.
CII-SR-03cii-d16bBLOCKEDExchangedDocument element required
CII must have ExchangedDocument with ID and TypeCode.
BR-CO-05EN 16931AUTO-FIXDiscount reason text does not match the reason code
The allowance reason code and the reason text on your invoice describe different types of discounts. For example, code 95 means "Discount" but the text says something else. These must match.
BR-37EN 16931AUTO-FIXEach Document level charge (BG-21) shall have a Document level charge VAT...
Each Document level charge (BG-21) shall have a Document level charge VAT category code (BT-102). Check the `cac:AllowanceCharge` element in your invoice XML.
BR-IC-10EN 16931AUTO-FIXThis VAT category requires an exemption reason code or text explaining why...
This VAT category requires an exemption reason code or text explaining why no tax is charged (applies to `cac:TaxSubtotal`, rule BR-IC-10).
FI-R-002FINfinvoiceBLOCKEDFinvoice format for Finnish B2B
Finnish domestic B2B may prefer Finvoice format.
FR-R-007FRAfactur-xBLOCKEDFactur-X XML must be embedded in PDF
Factur-X requires XML to be embedded as PDF attachment.
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.
PT-R-004PRTubl-2.1BLOCKEDATCUD validation code required
Portuguese invoices require ATCUD (unique document code).
BR-IC-11EN 16931AUTO-FIXMissing delivery date for intra-community supply. Invoices with VAT category...
Missing delivery date for intra-community supply. Invoices with VAT category "Intra-community supply" (K) must have either a delivery date (BT-72) or invoicing period (BG-14).
RO-R-002ROUubl-2.1BLOCKEDe-Factura submission required
Romanian B2B/B2G invoices must go through e-Factura (SPV).
RO-R-003ROUcius-roBLOCKEDCIUS-RO format required
Romanian e-invoices must use CIUS-RO profile.
BR-IC-12EN 16931AUTO-FIXMissing delivery country for intra-community supply. Invoices with VAT...
Missing delivery country for intra-community supply. Invoices with VAT category "Intra-community supply" (K) must specify the delivery country code (BT-80).
RO-R-004ROUubl-2.1BLOCKEDRON conversion may be required
Romanian tax reporting requires RON amounts.
HU-R-002HUNnavBLOCKEDNAV Online Invoice reporting required
Hungarian invoices over HUF 100k must be reported to NAV.
BR-TMP-2EN 16931AUTO-FIXBT-124 "External document location" muss eine absolute URL mit gültigem...
Invalid external document URL. The external document location (BT-124) must be an absolute URL with a valid scheme (http/https).
BR-O-04EN 16931AUTO-FIXSurcharge marked as not subject to VAT but seller has a VAT number
One of your document-level surcharges uses VAT category "O" (Not subject to VAT), but the seller has a VAT identification number. These contradict each other — if the surcharge is not subject to VAT, the seller should not have a VAT ID on this invoice.
BR-O-05EN 16931AUTO-FIXAn Invoice line (BG-25) where the VAT category code (BT-151) is "Not subject...
VAT amount for category O must be zero.
BR-O-06EN 16931AUTO-FIXA Document level allowance (BG-20) where VAT category code (BT-95) is "Not...
VAT category O must have exemption reason.
BR-O-07EN 16931AUTO-FIXWhen using this VAT category, the VAT rate must be 0 (zero). This category...
When using this VAT category, the VAT rate must be 0 (zero). This category does not have a positive tax rate (applies to `cac:AllowanceCharge`, rule BR-O-07).
BR-48EN 16931INPUTDocument allowance tax category required
Document-level allowances/charges must specify the VAT category.
BR-CO-15EN 16931AUTO-FIXTax exclusive amount calculation error
Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).. This applies to the `cbc:TaxInclusiveAmount` element in the invoice XML.
BR-O-09EN 16931AUTO-FIXOut of scope must be only category
If O is used, only O category allowed on invoice.
HU-R-003HUNnavBLOCKEDNAV technical user required
NAV reporting requires registered technical user.
BR-DEC-08en16931BLOCKEDAllowance total: max 2 decimals
AllowanceTotalAmount allows max 2 decimal places.
XML-003ubl-2.1BLOCKEDXML encoding declaration recommended
XML should declare character encoding.
BR-AE-10EN 16931AUTO-FIXReverse charge VAT breakdown must include exemption reason
A reverse charge VAT breakdown must include either a VAT exemption reason code meaning "Reverse charge" or exemption text stating "Reverse charge" (or equivalent). This explains why no VAT is charged.
XML-005ubl-2.1BLOCKEDXML schema validation failed
Document does not conform to XSD schema.
XML-006en16931BLOCKEDSchematron validation failed
Document failed business rule validation.
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.
BR-CL-03EN 16931AUTO-FIXcurrencyID MUST be coded using ISO code list 4217 alpha-3
A currency attribute (currencyID) contains an invalid ISO 4217 code. Currency codes must be 3-letter codes like EUR, USD, GBP.
BR-AG-01EN 16931BLOCKEDIPSI VAT breakdown required when IPSI used on lines
When using the IPSI VAT category (M) on invoice lines, allowances, or charges, you must have exactly one matching VAT breakdown section for IPSI.
BR-CL-05EN 16931AUTO-FIXTax currency code MUST be coded using ISO code list 4217 alpha-3
The Tax Currency Code (BT-6) is not a valid ISO 4217 code. If using a different currency for tax accounting, it must be a valid 3-letter code.
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.
BR-FR-02FRApeppol-bis-3INPUTSIREN vs SIRET confusion
SIREN (9 digits) identifies the company, SIRET (14 digits) identifies the specific establishment. French e-invoices require the full 14-digit SIRET.
BR-E-02EN 16931INPUTWhen using this VAT category, the seller must have a VAT identifier, tax...
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative (applies to `cac:InvoiceLine`, rule BR-E-02).
BR-DE-25DEUxrechnungBLOCKEDXRechnung invoice type restriction
XRechnung restricts allowed invoice type codes.
BR-IC-03EN 16931INPUTWhen using this VAT category, the seller must have a VAT identifier, tax...
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative (applies to `cac:AllowanceCharge`, rule BR-IC-03).
BR-CL-06EN 16931AUTO-FIXValue added tax point date code MUST be coded using a restriction of UNTDID...
The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date).
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→