Country-Specific Errors
National e-invoicing rules (BR-DE, BR-FR, BR-IT, etc.) that apply on top of the EU standard for specific countries.
100 errors documented
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.
BR-IT-03ITApeppol-bis-3INPUTMissing Regime Fiscale
Italian invoices must specify the tax regime (Regime Fiscale) code.
ES-R-004ESPfacturaeBLOCKEDDigital signature required
Spanish FacturaE invoices require XAdES digital signature.
BR-ES-01ESPpeppol-bis-3INPUTSpanish NIF/CIF required
Spanish invoices must include the NIF (individuals) or CIF (companies) tax identifier.
ES-R-005ESPubl-2.1INPUTSII reporting reference
Invoices reported to Spanish SII should include reporting reference.
ES-R-006ESPubl-2.1INPUTRecargo de equivalencia for retailers
Spanish retail sales may require equivalence surcharge.
FR-R-004FRAfactur-xINPUTChorus Pro engagement number required
French B2G invoices require engagement juridique (purchase order reference).
FR-R-005FRAfactur-xINPUTChorus Pro structure code required
French B2G invoices need Code Structure (SIRET of receiving entity).
FR-R-006FRAfactur-xBLOCKEDInvalid Factur-X profile identifier
Factur-X invoices must have valid profile in CustomizationID.
FR-R-008FRAfactur-xINPUTInvalid French VAT number format
French TVA intracommunautaire must be FR + 11 characters.
FR-R-009FRAfactur-xINPUTRCS registration recommended
French commercial invoices should include RCS registration.
FR-R-010FRAfactur-xINPUTShare capital recommended on invoices
French SARL/SA invoices should show capital social.
BR-DE-06DEUxrechnungINPUTGerman invoice should include payment terms
German invoices should specify payment terms including any early payment discount (Skonto).
BR-IT-04ITAfatturapaINPUTMissing Codice Destinatario
Italian FatturaPA invoices require the 7-character recipient code (Codice Destinatario).
GR-R-001GRCubl-2.1INPUTGreek AFM (VAT number) required
Greek invoices must include 9-digit AFM.
BR-ES-02ESPverifactuBLOCKEDMissing VeriFACTU hash chain
Spanish VeriFACTU invoices must include the hash chain for audit trail.
GR-R-002GRCubl-2.1BLOCKEDmyDATA reporting required
Greek invoices must be reported to myDATA (AADE).
BR-AT-01AUTpeppol-bis-3INPUTAustrian UID number required
Austrian invoices must include the UID-Nummer (VAT ID) in ATU + 8 digits format.
BR-PT-01PRTpeppol-bis-3INPUTPortuguese NIF required
Portuguese invoices must include the 9-digit NIF (tax number).
GR-R-004GRCubl-2.1INPUTGreek VAT category code required
myDATA requires Greek-specific VAT category codes.
IT-R-006ITAubl-2.1INPUTBollo stamp duty may be required
Italian invoices over threshold with no VAT require bollo.
IT-R-007ITAubl-2.1INPUTRegime fiscale code required
Italian invoices must specify the seller tax regime.
BR-DEX-03DEUXRechnung (Germany)AUTO-FIXEine Sub Invoice Line (BG-DEX-01) muss genau eine "SUB INVOICE LINE VAT...
Missing sub-line VAT info. Each Sub Invoice Line (BG-DEX-01) must contain exactly one VAT information group (BG-DEX-06).
IT-R-008ITAubl-2.1INPUTCIG/CUP codes for public contracts
Italian B2G invoices require CIG and/or CUP codes.
AT-R-004AUTerbBLOCKEDERB (e-Rechnung Bund) compliance required
Austrian B2G invoices must comply with ERB requirements.
BR-DEX-11DEUXRechnung (Germany)AUTO-FIXMissing third party payment amount. When using third party payment group...
Missing third party payment amount. When using third party payment group (BG-DEX-09), the amount (BT-DEX-002) is required.
GR-R-003GRCCIUS-GR (Greece)AUTO-FIXGreek invoice type code required
myDATA requires specific Greek invoice type classification.
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.
SDI-00001ITAFatturaPAINPUTCodice Destinatario missing or invalid
Each invoice must specify how to reach the recipient: 7-character SDI code, PEC email, or "0000000" for B2C consumers. This is required for all Italian e-invoices.
SDI-00002ITAFatturaPAINPUTPartita IVA format invalid
Italian VAT number (Partita IVA) must be exactly 11 digits for domestic invoices, or prefixed with IT for cross-border invoices.
SDI-00305ITAFatturaPAINPUTCodice Fiscale validation failed
Codice Fiscale must pass checksum validation. It should be 16 characters for individuals (alphanumeric) or 11 digits for businesses (same as Partita IVA).
SDI-00311ITAFatturaPABLOCKEDRitenuta d'acconto calculation error
Withholding tax (ritenuta d'acconto) amount must exactly match the base amount × declared rate calculation. Any discrepancy causes rejection.
SDI-00400ITAFatturaPABLOCKEDXML schema validation failure
FatturaPA XML must conform exactly to the official XSD schema published by Agenzia delle Entrate. Any structural deviation causes rejection.
KSEF-005POLKSeFBLOCKEDVAT rate invalid for item type
Polish VAT rates (23%, 8%, 5%, 0%, ZW-exempt, NP-not subject) must match item classification rules per Polish VAT law and PKWiU classification.
KSEF-006POLKSeFINPUTUnit code not recognized
Unit of measure must be from Polish classification. Common codes include szt. (piece), kg, m, l, usł. (service).
KSEF-007POLKSeFBLOCKEDDate format invalid
All dates in KSeF invoices must be in YYYY-MM-DD (ISO 8601) format. Other formats are rejected.
KSEF-008POLKSeFINPUTGTU code missing
Certain goods/services require GTU (Grupy Towarów i Usług) classification codes. Required for alcohol (GTU_01), fuel (GTU_02), heating oil (GTU_03), tobacco (GTU_04), and other specific categories.
SII-001ESPSIIINPUTClave de régimen especial missing
SII requires a regime key (clave de régimen especial) for each invoice indicating the type of operation: 01=General, 02=Export, 03=Gold operations, etc.
DK-R-004DNKOIOUBL (Denmark)INPUTWhen specifying non-VAT Taxes for Danish customers, Danish suppliers MUST...
Your Danish invoice includes non-VAT taxes (such as environmental levies or municipal charges) but is missing the reason code. Danish regulations require a reason code that explains the type of non-VAT tax.
DK-R-005DNKOIOUBL (Denmark)INPUTPayment method not allowed for Danish invoices
Your invoice uses a payment method code that is not accepted for Danish suppliers. Denmark only allows specific payment codes on Peppol invoices.
DE-R-018DEUPEPPOL_BISCONFIRMInvalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with
Invalid Skonto format. Cash discount terms in German invoices must follow the format: #SKONTO#TAGE=N#PROZENT=N.NN# with optional #BASISBETRAG=N#. Must be uppercase with no extra whitespace.
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).
IT-01ITACIUS-IT (Italy)BLOCKEDItalian sellers should include Codice Fiscale or Partita IVA
Italian sellers should include Codice Fiscale or Partita IVA. This validation rule ensures Invoice compliance with CIUS-IT (Italy).
GR-R-004-1GRCPEPPOL_BISINPUTWhen Supplier is Greek, there must be one MARK Number
Greek supplier invoices must include one MARK (Μοναδικός Αριθμός Καταχώρησης) number. This is the unique registration number from the Greek myDATA system.
GR-R-006GRCCIUS-GR (Greece)INPUTGreek Suppliers must provide the VAT number of the buyer, if the buyer is Greek
When both supplier and buyer are Greek, the buyer's VAT number must be provided. This is required for domestic Greek transactions.
BR-DE-01DEUXRechnung (Germany)INPUTInvalid Leitweg-ID Format
German B2G (Business-to-Government) invoices require a valid Leitweg-ID in the Buyer Reference field (BT-10). The Leitweg-ID is a routing identifier that directs your invoice to the correct government department.
BR-DE-1DEUXRechnung (Germany)INPUTEine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...
German XRechnung requires Payment Instructions (BG-16). You must specify how the invoice should be paid.
BR-DE-02DEUXRechnung (Germany)INPUTPayment terms text recommended
German invoices should include payment terms text (Zahlungsbedingungen) for clarity.
BR-DE-2DEUXRechnung (Germany)INPUTDie Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.
German XRechnung requires a Seller Contact section (BG-6). Contact details for the seller must be provided.
BR-DE-05DEUXRechnung (Germany)INPUTSeller contact email is required for German B2G invoices
XRechnung to German public sector requires valid Leitweg-ID as buyer reference.
BR-DE-3DEUXRechnung (Germany)INPUTDas Element "Seller city" (BT-37) muss übermittelt werden.
German XRechnung requires Seller City (BT-37). The seller's city must be specified.
PL-R-007POLubl-2.1INPUTSplit payment annotation required
High-value Polish invoices may require split payment notation.
Handle Country-Specific Errors in Your Pipeline
The compliance engine auto-remediates country-specific errors with controlled safety policies.
Get API Access