E-Invoice Error Reference
1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
345 errors found · Page 3 of 7 in Business Rules
BR-CO-03EN 16931AUTO-FIXVAT 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.
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-K-01en16931BLOCKEDIntra-community supply VAT treatment
VAT category K (intra-community) requires zero VAT and both party VAT numbers.
BR-CO-06EN 16931AUTO-FIXSurcharge 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.
BR-G-01EN 16931BLOCKEDExport VAT category requirements
VAT category G (export) requires exemption reason and must have zero VAT.
BR-CO-08EN 16931AUTO-FIXLine 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.
BR-CO-09EN 16931AUTO-FIXVAT 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.
BR-CO-19EN 16931AUTO-FIXInvoice 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.
PEPPOL-EN16931-CL001Peppol BIS 3.0AUTO-FIXMime 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.
BR-CO-20EN 16931AUTO-FIXInvoice 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.
BR-AE-07EN 16931AUTO-FIXDocument 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.
BR-CO-21EN 16931AUTO-FIXDocument 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.
BR-CO-22EN 16931AUTO-FIXDocument 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.
BR-IC-08EN 16931BLOCKEDThe taxable amount for this VAT category must equal the sum of line amounts...
The taxable amount for this VAT category must equal the sum of line amounts minus allowances plus charges for this category (applies to `cac:TaxSubtotal`, rule BR-IC-08).
BR-AE-09EN 16931AUTO-FIXReverse 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.
BR-CO-23EN 16931AUTO-FIXInvoice 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.
BR-DEC-21en16931BLOCKEDTax total: max 2 decimals
TaxTotal/TaxAmount allows maximum 2 decimal places.
BR-S-01EN 16931BLOCKEDStandard rate must be in VAT breakdown
If any line uses VAT category S, VAT breakdown must include S category.
BR-CO-24EN 16931AUTO-FIXInvoice 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.
BR-O-01EN 16931BLOCKEDOut of scope VAT category requirements
VAT category O (out of scope) must not have a VAT percentage.
BR-O-11EN 16931BLOCKEDMixed VAT categories with "Not subject to VAT". When using VAT category O...
Mixed VAT categories with "Not subject to VAT". When using VAT category O (Not subject to VAT), no other VAT categories are allowed on the invoice.
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.
BR-O-12EN 16931BLOCKEDInconsistent 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".
BR-O-13EN 16931BLOCKEDInconsistent allowance VAT with "Not subject to VAT". Document allowances...
Inconsistent allowance VAT with "Not subject to VAT". Document allowances must use VAT category O when the invoice uses "Not subject to VAT".
BR-E-06EN 16931AUTO-FIXExempt VAT must be zero
VAT amount for category E must be zero.
BR-DEC-01EN 16931AUTO-FIXDocument allowance: max 2 decimals
Document level allowance amount allows maximum 2 decimal places.
BR-O-14EN 16931BLOCKEDInconsistent 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".
BR-E-07EN 16931AUTO-FIXExempt requires exemption reason
VAT category E must have exemption reason.
BR-DEC-02EN 16931AUTO-FIXDocument allowance base: max 2 decimals
Document level allowance base amount allows max 2 decimals.
BR-DEC-05EN 16931AUTO-FIXDocument level charge: max 2 decimals
Document level charge amount (BT-99) allows max 2 decimal places.
BR-DEC-06EN 16931AUTO-FIXDocument level charge base: max 2 decimals
Document level charge base amount (BT-100) allows max 2 decimal places.
BR-DEC-09EN 16931AUTO-FIXSum 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.
BR-DEC-10EN 16931AUTO-FIXThe 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.
BR-DEC-11EN 16931AUTO-FIXThe allowed maximum number of decimals for the Sum of charges on document...
The sum of document level charges has too many decimal places. This total must have a maximum of 2 decimal places.
BR-DEC-12EN 16931AUTO-FIXInvoice total amount without VAT: max 2 decimals
The Invoice total amount without VAT (TaxExclusiveAmount, BT-109) allows a maximum of 2 decimal places.
BR-DEC-13EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice total VAT amount...
The invoice total VAT amount has too many decimal places. The total tax amount must have a maximum of 2 decimal places.
BR-DEC-14EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice total amount with VAT...
The invoice total amount with VAT (tax inclusive amount) has too many decimal places. This grand total must have a maximum of 2 decimal places.
BR-DEC-15EN 16931AUTO-FIXAccounting 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.
BR-DEC-17EN 16931AUTO-FIXRounding amount: max 2 decimals
The rounding adjustment amount has too many decimal places. Rounding amounts must have a maximum of 2 decimal places.
BR-DEC-18EN 16931AUTO-FIXPayable amount: max 2 decimals
PayableAmount allows maximum 2 decimal places.
BR-DEC-19EN 16931AUTO-FIXVAT 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.
BR-DEC-20EN 16931AUTO-FIXVAT tax amount: max 2 decimals
TaxSubtotal/TaxAmount allows maximum 2 decimal places.
BR-DEC-23EN 16931AUTO-FIXLine net amount: max 2 decimals
InvoiceLine/LineExtensionAmount (BT-131) allows maximum 2 decimal places.
BR-DEC-24EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line allowance amount...
The invoice line allowance amount has too many decimal places. Line-level allowance amounts must have a maximum of 2 decimal places.
BR-DEC-25EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line allowance base...
The invoice line allowance base amount has too many decimal places. The base amount for calculating line allowances must have a maximum of 2 decimal places.
BR-DEC-27EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line charge amount...
The invoice line charge amount has too many decimal places. Line-level charge amounts must have a maximum of 2 decimal places.
BR-DEC-28EN 16931AUTO-FIXThe allowed maximum number of decimals for the Invoice line charge base...
The invoice line charge base amount has too many decimal places. The base amount for calculating line charges must have a maximum of 2 decimal places.
BR-AF-10EN 16931AUTO-FIXIGIC VAT breakdown must not have exemption reason
An IGIC VAT breakdown must NOT have a VAT exemption reason code or text. IGIC is a positive tax (like standard VAT), so exemption reasons are not applicable.
BR-AE-01EN 16931BLOCKEDMissing reverse charge VAT summary
Your invoice has line items marked as reverse charge (VAT category AE), but the VAT summary section is missing the corresponding reverse charge breakdown. When any item uses the reverse charge mechanism, the invoice must include a VAT breakdown line showing the reverse charge totals with a zero tax amount.
BR-03EN 16931AUTO-FIXInvoice must have an issue date
Every invoice must contain an issue date indicating when the invoice was created.
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→