E-Invoice Error Reference
1375+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1375 errors found · Page 7 of 28
BR-B-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-B-02).
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-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".
IT-R-003ITACIUS-IT (Italy)INPUTNatura code required for zero VAT
Italian invoices with zero VAT must specify Natura code.
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".
DE-R-016DEUEN 16931AUTO-FIXVAT identifier is missing. German invoices using VAT codes S, Z, E, AE, K,...
VAT identifier is missing. German invoices using VAT codes S, Z, E, AE, K, G, L, or M must include either Seller VAT ID (BT-31), Tax registration ID (BT-32), or Tax Representative.
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.
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.
PEPPOL-EN16931-R007Peppol BIS 3.0AUTO-FIXBusiness process identifier has wrong format
The ProfileID in your invoice does not follow the required Peppol format. It must be "urn:fdc:peppol.eu:2017:poacc:billing:01:1.0" for standard billing.
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-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-CL-08EN 16931AUTO-FIXInvoice note has an invalid subject code
One of the notes on your invoice uses a subject code that is not in the official UN/CEFACT code list (UNCL 4451). The subject code indicates the type of note — for example, general information, regulatory, or surcharge.
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-38EN 16931AUTO-FIXDocument level charge reason required
A document level charge is missing both a reason text (BT-104) and reason code (BT-105). At least one must be provided to explain what this charge is for.
UBL-CR-412EN16931AUTO-FIXA 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.
DE-R-003DEUEN 16931INPUTThe element "Seller city" (BT-37) shall be provided.
Seller city is missing. German invoices must include the seller's city in the address (BT-37).
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.
DE-R-005DEUEN 16931INPUTSeller contact name required (XRechnung)
German XRechnung invoices must include a contact person name (BT-41) in the Seller Contact group (BG-6).
DE-R-006DEUEN 16931INPUTSeller contact telephone required (XRechnung)
German XRechnung invoices must include a telephone number (BT-42) for the seller contact person in the Seller Contact group (BG-6).
DE-R-007DEUEN 16931INPUTSeller contact email required (XRechnung)
German XRechnung invoices must include an email address (BT-43) for the seller contact person in the Seller Contact group (BG-6).
DE-R-010DEUEN 16931INPUTThe element "Deliver to city" (BT-77) shall be provided if the group...
Delivery city is missing. When a delivery address is provided in German invoices, the delivery city (BT-77) is required.
DE-R-011DEUEN 16931INPUTThe element "Deliver to post code" (BT-78) shall be provided if the group...
Delivery postal code is missing. When a delivery address is provided in German invoices, the delivery postal code (BT-78) is required.
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.
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.
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-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-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.
DE-R-023-1DEUEN 16931AUTO-FIXCredit transfer details missing. When payment code 30 or 58 (credit...
Credit transfer details missing. When payment code 30 or 58 (credit transfer) is used, the Credit Transfer group (BG-17) with bank account details must be provided.
PEPPOL-EN16931-R001Peppol BIS 3.0AUTO-FIXBusiness process identifier required
Business process MUST be provided. Check the `cbc:ProfileID` element in your invoice XML.
BR-CO-07EN 16931AUTO-FIXLine item discount reason text does not match the reason code
On one of your invoice lines, the discount reason code and the reason text describe different types of discounts. For example, code 95 means "Discount" but the text says something else. These must match.
PEPPOL-EN16931-R044EN 16931AUTO-FIXCharge on price level is NOT allowed. Only value 'false' allowed.
Price level allowances/charges must be allowances only (ChargeIndicator = false). Surcharges at the item price level are not allowed in PEPPOL - they must be at line or document level.
DK-R-014DNKOIOUBL (Denmark)AUTO-FIXDanish company registration number has wrong scheme code
Your Danish company registration number (CVR) is present but uses the wrong scheme identifier. Danish suppliers must use scheme code 0184 to indicate a CVR number.
BR-10EN 16931INPUTBuyer must have postal address
An Invoice shall contain the Buyer postal address (BG-8). At minimum, the country code is required.
PEPPOL-EN16931-R111EN 16931AUTO-FIXInvoice line billing period extends beyond invoice dates
One of your invoice lines has a billing period end date that falls outside the overall invoice period. For example, the invoice covers January but a line item says it ends in February.
PEPPOL-EN16931-R080EN 16931BLOCKEDToo many project references
The invoice has more than one project reference at the document level. Peppol allows only a single project reference per invoice. If your invoice relates to multiple projects, use only the primary one at the document level.
BR-12EN 16931BLOCKEDInvoice total with VAT required
The invoice must contain the total amount including VAT (TaxInclusiveAmount).
UBL-SR-48EN 16931AUTO-FIXInvoice line has wrong number of tax categories
Each invoice line must have exactly one tax category classification. One of your lines has either no tax category or multiple tax categories, which is not allowed.
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→