E-Invoice Error Reference

1369+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.

1369 errors found · Page 7 of 28

errorBR-CL-11EN 16931AUTO-FIX

Invalid registration identifier scheme

Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. This applies to the PartyLegalEntity/CompanyID@schemeID attribute.

errorBR-Z-01EN 16931BLOCKED

An Invoice that contains an Invoice line (BG-25), a Document level allowance...

When using VAT category Z (zero rate), an exemption reason code or text must be provided.

errorBR-AE-05EN 16931AUTO-FIX

Reverse charge invoice line must have 0% VAT rate

When an invoice line uses the reverse charge VAT category, the VAT rate must be 0%. Reverse charge means the buyer accounts for VAT, so seller charges zero VAT.

errorUBL-CR-009UBL 2.1AUTO-FIX

Disallowed element: cbc:PaymentAlternativeCurrencyCode

UBL 2.1 Invoice schema does not include `cbc:PaymentAlternativeCurrencyCode`. This element must be removed for EN 16931 compliance.

errorBR-CL-19EN 16931AUTO-FIX

Invalid allowance reason code

Coded allowance reasons MUST belong to the UNCL 5189 code list. This applies to AllowanceChargeReasonCode for allowances (ChargeIndicator=false).

errorBR-CL-21EN 16931AUTO-FIX

Invalid product identifier scheme

A line item's standard product identifier uses an invalid scheme code. The most common standard identifier is a GTIN (barcode number), which should use scheme code 0160. Other valid schemes include ISO 6523 ICD codes for industry-specific numbering systems.

errorBR-ES-02ESPverifactuBLOCKED

Missing VeriFACTU hash chain

Spanish VeriFACTU invoices must include the hash chain for audit trail.

errorGR-R-002GRCubl-2.1BLOCKED

myDATA reporting required

Greek invoices must be reported to myDATA (AADE).

errorBR-CO-03EN 16931AUTO-FIX

VAT point date and VAT point date code are mutually exclusive

Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive. You cannot specify both - use one or the other to indicate when VAT becomes due.

errorBR-CO-05EN 16931AUTO-FIX

Discount 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.

errorBR-K-01en16931BLOCKED

Intra-community supply VAT treatment

VAT category K (intra-community) requires zero VAT and both party VAT numbers.

errorBR-CO-06EN 16931AUTO-FIX

Surcharge reason text does not match the reason code

The surcharge (extra charge) reason code and the reason text on your invoice describe different types of charges. For example, code FC means "Freight" but the text says something else. These must match.

errorBR-G-01EN 16931BLOCKED

Export VAT category requirements

VAT category G (export) requires exemption reason and must have zero VAT.

warningBR-CO-08EN 16931AUTO-FIX

Line charge reason and code must match

Invoice line charge reason code (BT-145) and Invoice line charge reason (BT-144) shall indicate the same type of charge reason. The reason text must semantically match the UNTDID 7161 code.

errorBR-CO-09EN 16931AUTO-FIX

VAT number is missing the country code

A VAT identification number in this invoice does not start with a valid two-letter country code. European VAT numbers must be prefixed with the country code (e.g. DE for Germany, NL for the Netherlands, SE for Sweden). Greece may use EL instead of GR.

errorBR-CO-19EN 16931AUTO-FIX

Invoice period must have at least one date

If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both.

errorPEPPOL-EN16931-CL001Peppol BIS 3.0AUTO-FIX

Mime code must be according to subset of IANA code list.

Mime code must be according to subset of IANA code list.. This validation rule ensures Invoice compliance with Peppol BIS 3.0.

errorBR-CO-20EN 16931AUTO-FIX

Invoice line period dates required

If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both.

errorcvc-complex-type.2.4.axsdBLOCKED

Invoice XML structure does not match the required schema

Your invoice file has a structural problem — required data elements are missing, in the wrong position, or unexpected elements are present. This is an XML Schema validation error, which means the basic structure of the file does not conform to the e-invoicing standard (UBL 2.1 or CII D16B). This is different from a business rule error: business rules check whether the data makes sense, while this error means the file format itself is wrong.

errorBR-AE-07EN 16931AUTO-FIX

Document level charge with reverse charge must have 0% VAT rate

When a document level charge uses the reverse charge VAT category, the VAT rate must be 0%. Charges in reverse charge scenarios follow the same zero-rate rule.

errorBR-CO-21EN 16931AUTO-FIX

Document allowance reason required

Each Document level allowance (BG-20) shall contain a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98), or both.

errorBR-CO-22EN 16931AUTO-FIX

Document charge reason required

Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.

errorBR-AE-09EN 16931AUTO-FIX

Reverse charge VAT breakdown tax amount must be zero

The VAT category tax amount for reverse charge must be 0. Since reverse charge means buyer accounts for VAT, the seller's VAT amount is always zero.

errorBR-CO-23EN 16931AUTO-FIX

Invoice Line Allowance Reason Required

Each Invoice line allowance (BG-27) shall contain an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140), or both.

errorBR-DEC-21en16931BLOCKED

Tax total: max 2 decimals

TaxTotal/TaxAmount allows maximum 2 decimal places.

errorBR-S-01EN 16931BLOCKED

Standard rate must be in VAT breakdown

If any line uses VAT category S, VAT breakdown must include S category.

errorBR-B-02EN 16931INPUT

When 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-B-02).

errorBR-CO-24EN 16931AUTO-FIX

Invoice Line Charge Reason Required

Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both.

errorBR-O-01EN 16931BLOCKED

Out of scope VAT category requirements

VAT category O (out of scope) must not have a VAT percentage.

errorBR-AE-10EN 16931AUTO-FIX

Reverse 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.

errorBR-O-12EN 16931BLOCKED

Inconsistent line VAT with "Not subject to VAT". All invoice lines must use...

Inconsistent line VAT with "Not subject to VAT". All invoice lines must use VAT category O when the invoice VAT breakdown uses "Not subject to VAT".

errorBR-E-06EN 16931AUTO-FIX

Exempt VAT must be zero

VAT amount for category E must be zero.

errorBR-DEC-01EN 16931AUTO-FIX

Document allowance: max 2 decimals

Document level allowance amount allows maximum 2 decimal places.

errorBR-O-14EN 16931BLOCKED

Inconsistent charge VAT with "Not subject to VAT". Document charges must use...

Inconsistent charge VAT with "Not subject to VAT". Document charges must use VAT category O when the invoice uses "Not subject to VAT".

errorSDI-00311ITAFatturaPABLOCKED

Ritenuta d'acconto calculation error

Withholding tax (ritenuta d'acconto) amount must exactly match the base amount × declared rate calculation. Any discrepancy causes rejection.

errorSDI-00400ITAFatturaPABLOCKED

XML schema validation failure

FatturaPA XML must conform exactly to the official XSD schema published by Agenzia delle Entrate. Any structural deviation causes rejection.

errorBR-E-07EN 16931AUTO-FIX

Exempt requires exemption reason

VAT category E must have exemption reason.

errorBR-DEC-02EN 16931AUTO-FIX

Document allowance base: max 2 decimals

Document level allowance base amount allows max 2 decimals.

errorBR-DEC-05EN 16931AUTO-FIX

Document level charge: max 2 decimals

Document level charge amount (BT-99) allows max 2 decimal places.

errorBR-DEC-06EN 16931AUTO-FIX

Document level charge base: max 2 decimals

Document level charge base amount (BT-100) allows max 2 decimal places.

errorBR-DEC-09EN 16931AUTO-FIX

Sum of line amounts: max 2 decimals

Sum of Invoice line net amount (BT-106) allows max 2 decimal places. This is the LineExtensionAmount in LegalMonetaryTotal.

errorBR-DEC-10EN 16931AUTO-FIX

The allowed maximum number of decimals for the Sum of allowanced on document...

The sum of document level allowances has too many decimal places. This total must have a maximum of 2 decimal places.

errorBR-DEC-12EN 16931AUTO-FIX

Invoice total amount without VAT: max 2 decimals

The Invoice total amount without VAT (TaxExclusiveAmount, BT-109) allows a maximum of 2 decimal places.

errorBR-DEC-15EN 16931AUTO-FIX

Accounting currency VAT amount: max 2 decimals

When a tax/accounting currency is specified (BT-6), the Invoice total VAT amount in accounting currency (BT-111) must have a maximum of 2 decimal places.

errorBR-DEC-17EN 16931AUTO-FIX

Rounding amount: max 2 decimals

The rounding adjustment amount has too many decimal places. Rounding amounts must have a maximum of 2 decimal places.

errorBR-DEC-18EN 16931AUTO-FIX

Payable amount: max 2 decimals

PayableAmount allows maximum 2 decimal places.

errorBR-DEC-19EN 16931AUTO-FIX

VAT taxable amount: max 2 decimals

The allowed maximum number of decimals for the VAT category taxable amount (BT-116) is 2. This applies to the `cbc:TaxableAmount` element in the invoice XML.

errorBR-DEC-20EN 16931AUTO-FIX

VAT tax amount: max 2 decimals

TaxSubtotal/TaxAmount allows maximum 2 decimal places.

errorBR-DEC-23EN 16931AUTO-FIX

Line net amount: max 2 decimals

InvoiceLine/LineExtensionAmount (BT-131) allows maximum 2 decimal places.

warningUBL-CR-412EN16931AUTO-FIX

A UBL invoice should not include the PaymentMeans PaymentDueDate

Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.

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