E-Invoice Error Reference
1350+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
223 errors found · Page 1 of 5 in Country-Specific
PL-R-007POLubl-2.1INPUTSplit payment annotation required
High-value Polish invoices may require split payment notation.
BR-FR-01FRApeppol-bis-3INPUTSIRET number format
French invoices must include SIRET (14 digits) with schemeID="0009" for company identification. SIRET is mandatory for all French business invoices.
KSEF-010POLKSeFBLOCKEDKSeF XML schema validation failed
Invoice XML must conform exactly to the FA schema version (FA/1 or FA/2). Even minor deviations cause rejection.
PEPPOL-SDI-01ITAPeppol-SDIBLOCKEDPeppol to SDI conversion error
When Peppol invoices enter Italy via the SDI gateway, they must be converted to FatturaPA format. Conversion issues are common with complex invoices.
PT-R-003PRTubl-2.1BLOCKEDSAF-T compliance recommended
Portuguese invoices should be SAF-T (PT) compliant for reporting.
PL-R-003POLubl-2.1BLOCKEDKSeF submission required
Polish invoices must be submitted to KSeF (Krajowy System e-Faktur).
KSEF-009POLKSeFBLOCKEDBank account not on VAT white list
For split payment (podzielona płatność) invoices, the seller bank account must be registered on the VAT white list (biała lista VAT).
PL-R-004POLubl-2.1BLOCKEDKSeF session token invalid
KSeF API requires valid authentication token.
PL-R-005POLubl-2.1INPUTInvalid Polish NIP format
Polish NIP must be 10 digits with valid checksum.
BR-BE-01BELpeppol-bis-3INPUTEnterprise Number Recommended
Belgian invoices should include the 10-digit enterprise number (ondernemingsnummer) formatted as 0XXX.XXX.XXX.
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.
FI-R-001FINpeppol-bis-3INPUTFinnish Business ID required
Finnish invoices must include Y-tunnus (business ID).
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.
PT-R-001PRTubl-2.1INPUTPortuguese NIF required
Portuguese invoices must include NIF (Numero de Identificacao Fiscal).
IT-R-005ITAubl-2.1INPUTInvalid PEC email format
Italian PEC email must be valid certified email address.
PT-R-002PRTubl-2.1INPUTAT document codes required
Portuguese invoices need AT (Autoridade Tributaria) document codes.
DK-R-006DNKOIOUBL (Denmark)BLOCKEDFor Danish suppliers bank account and registration account is mandatory if...
Danish suppliers using payment means 31 (credit transfer) or 42 (payment to bank account) must provide both bank account number and registration number.
PT-R-004PRTubl-2.1BLOCKEDATCUD validation code required
Portuguese invoices require ATCUD (unique document code).
RO-R-001ROUubl-2.1INPUTRomanian CIF/CUI required
Romanian invoices must include CIF or CUI number.
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.
RO-R-004ROUubl-2.1BLOCKEDRON conversion may be required
Romanian tax reporting requires RON amounts.
HU-R-001HUNnavINPUTHungarian tax number required
Hungarian invoices must include adószám (tax number).
HU-R-002HUNnavBLOCKEDNAV Online Invoice reporting required
Hungarian invoices over HUF 100k must be reported to NAV.
HU-R-003HUNnavBLOCKEDNAV technical user required
NAV reporting requires registered technical user.
HU-R-004HUNnavINPUTHungarian VAT code required
NAV requires Hungarian-specific VAT category codes.
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.
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.
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.
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.
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.
BR-DE-07DEUxrechnungINPUTGerman postal code format
German postal codes should be 5 digits.
BR-DE-13DEUxrechnungINPUTDelivery date or period required
XRechnung requires delivery date or period.
BR-DE-25DEUxrechnungBLOCKEDXRechnung invoice type restriction
XRechnung restricts allowed invoice type codes.
BR-DE-29DEUxrechnungINPUTSEPA direct debit mandate required
SEPA direct debit requires mandate reference.
BR-DE-20DEUXRechnung (Germany)BLOCKEDThe Debited Account (BT-91) should contain a valid IBAN for SEPA direct...
The Debited Account (BT-91) should contain a valid IBAN for SEPA direct debit. The current value doesn't match IBAN format.
CZ-R-001CZEubl-2.1INPUTCzech DIČ required
Czech invoices must include DIČ (tax identification number).
CZ-R-002CZEubl-2.1INPUTCzech IČO recommended
Czech business ID (IČO) recommended for identification.
CZ-R-003CZEisdocBLOCKEDISDOC format for Czech domestic
Czech domestic invoices may use ISDOC format.
BR-IT-02ITApeppol-bis-3INPUTMissing Codice Destinatario
Italian B2B invoices require a 7-character Codice Destinatario (recipient code) for SDI routing, or a PEC email address.
DK-R-001DNKoioublINPUTDanish CVR number required
Danish invoices must include 8-digit CVR number.
ES-R-002ESPfacturaeBLOCKEDInvalid FacturaE format
Spanish B2G invoices must use FacturaE 3.2.x format.
BR-DE-04DEUxrechnungBLOCKEDInvalid XRechnung CustomizationID
XRechnung invoices must use the correct specification identifier for the version.
ES-R-003ESPfacturaeINPUTFACe routing codes required
Spanish B2G invoices need OC (oficina contable), OG (organo gestor), UT (unidad tramitadora).
BR-BE-02BELpeppol-bis-3INPUTBelgian VAT number recommended
Belgian invoices should include the BTW/TVA number in format BE + 10 digits.
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→