E-Invoice Error Reference
1359+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1359 errors found · Page 6 of 28
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.
UBL-CR-359UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation Address ID
Your invoice contains a DeliveryLocation Address ID element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-385UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery CarrierParty
Your invoice contains a CarrierParty element which is not allowed in EN16931 invoices. This element must be removed.
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.
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.
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-CO-04EN 16931AUTO-FIXInvoice currency must be valid ISO 4217
Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151).. This applies to the `cac:InvoiceLine` element in the invoice XML.
DE-R-014DEUEN 16931AUTO-FIXThe element "VAT category rate" (BT-119) shall be provided.
The element VAT category rate (BT-119) shall be provided.. This applies to the `cbc:Percent` element in the invoice XML.
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.
DE-R-017DEUEN 16931AUTO-FIXInvalid invoice type code. German invoices only allow specific type codes:...
Invalid invoice type code. German invoices only allow specific type codes: 326 (partial), 380 (commercial), 384 (corrected), 389 (self-billed), 381 (credit note), 875-877 (construction).
DE-R-019DEUEN 16931AUTO-FIXInvalid IBAN format. When payment means code 58 (SEPA credit transfer) is...
Invalid IBAN format. When payment means code 58 (SEPA credit transfer) is used, the payment account (BT-84) must contain a valid IBAN.
DE-R-020DEUEN 16931AUTO-FIXDebited account identifier (BT-91) should contain a valid IBAN if code 59...
Invalid debit IBAN format. When payment means code 59 (SEPA direct debit) is used, the debited account (BT-91) must contain a valid IBAN.
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.
DE-R-024-1DEUEN 16931AUTO-FIXPayment card details missing. When payment code 48, 54, or 55 (payment card)...
Payment card details missing. When payment code 48, 54, or 55 (payment card) is used, the Payment Card Information group (BG-18) 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.
PEPPOL-EN16931-R004EN 16931AUTO-FIXThe specification identifier must be exactly...
The specification identifier must be exactly "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0". This identifies the invoice as PEPPOL BIS Billing 3.0 compliant.
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.
PEPPOL-EN16931-R100EN 16931AUTO-FIXOnly one invoiced object is allowed pr line
Only one invoiced object identifier is allowed per invoice line. Each line can reference at most one object (contract, order, etc.).
PEPPOL-EN16931-R110EN 16931AUTO-FIXStart date of line period MUST be within invoice period.
The start date of a line period must fall within the invoice period. Line periods cannot extend before the overall invoice period begins.
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-CL008EN 16931AUTO-FIXElectronic address identifier scheme must be from the codelist "Electronic...
The electronic address identifier scheme must be from the PEPPOL Electronic Address Identifier Scheme codelist. This identifies what type of endpoint ID is being used (GLN, PEPPOL ID, etc.).
UBL-SR-44EN 16931AUTO-FIXAn Invoice may only have one unique PaymentID, but the PaymentID may be used...
Your invoice has multiple different PaymentID values across PaymentMeans elements. EN16931 allows only one unique payment reference value, though it can be repeated across multiple payment means.
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.
DE-R-031DEUEN 16931AUTO-FIXIf the group "DIRECT DEBIT" (BG-19) is delivered, the element "Debited...
Debited account missing. When direct debit (BG-19) is used, the debited account identifier (BT-91) containing the buyer's IBAN is required.
PEPPOL-EN16931-P0112EN 16931AUTO-FIXInvoice type code 326 or 384 are only allowed when both buyer and seller are...
Invoice type codes 326 (partial invoice) and 384 (corrective invoice) are only allowed between German organizations.
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.
PEPPOL-EN16931-CL002PEPPOL_BISAUTO-FIXReason code MUST be according to subset of UNCL 5189 D.16B.
The allowance reason code must be from the UNCL 5189 D.16B subset. This code explains why a discount or allowance is being applied.
PEPPOL-EN16931-CL003PEPPOL_BISAUTO-FIXReason code MUST be according to UNCL 7161 D.16B.
The charge reason code must be from the UNCL 7161 D.16B list. This code explains why a surcharge or additional charge is being applied.
BR-26EN 16931BLOCKEDEach Invoice line (BG-25) shall contain the Item net price (BT-146).
Each Invoice line (BG-25) shall contain the Item net price (BT-146).. This applies to the `cbc:PriceAmount` element in the invoice XML.
BR-31EN 16931BLOCKEDEach Document level allowance (BG-20) shall have a Document level allowance...
Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92).. Check the `cac:AllowanceCharge` element in your invoice XML.
BR-36EN 16931BLOCKEDTax total amount required
Each Document level charge (BG-21) shall have a Document level charge amount (BT-99).. Check the `cac:AllowanceCharge` element in your invoice XML.
BR-41EN 16931BLOCKEDEach Invoice line allowance (BG-27) shall have an Invoice line allowance...
Seller should provide contact details for invoice queries.
BR-43EN 16931BLOCKEDAllowance/charge reason required
Each Invoice line charge (BG-28) shall have an Invoice line charge amount (BT-141).. Check the `cac:AllowanceCharge` element in your invoice XML.
BR-CO-16EN 16931AUTO-FIXPayable amount calculation error
Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) - Paid amount (BT-113) + Rounding amount (BT-114).. This applies to the `cbc:PayableAmount` element in the invoice XML.
BR-AE-08EN 16931AUTO-FIXReverse charge taxable amount doesn't add up
The taxable amount in the reverse charge VAT breakdown does not match the sum of reverse charge line items, charges, and allowances. The taxable base must equal: sum of line amounts with category AE, plus charges with category AE, minus allowances with category AE.
BR-50EN 16931BLOCKEDA Payment account identifier (BT-84) shall be present if Credit transfer...
A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided.. This applies to the `cbc:ID` element in the invoice XML.
BR-56EN 16931BLOCKEDEach Seller tax representative party (BG-11) shall have a Seller tax...
Invoice line allowance must have either reason code or text explanation.
UBL-DT-01EN16931AUTO-FIXAmounts shall be decimal up to two fraction digits
Your invoice contains amount values with more than 2 decimal places. EN16931 requires all monetary amounts to have maximum 2 decimal digits (e.g., 100.00 not 100.001).
PEPPOL-EN16931-R041EN 16931AUTO-FIXDiscount or surcharge is missing the base amount
When you specify a percentage for a discount or surcharge, you must also provide the base amount that the percentage applies to. For example, if you give a 10% discount, the invoice must state what the 10% is calculated on.
BR-61EN 16931BLOCKEDIf the Payment means type code (BT-81) means SEPA credit transfer, the...
If the Payment means type code (BT-81) means SEPA credit transfer, the Payment account identifier (BT-84) shall be an IBAN.. This applies to the `cbc:PaymentMeansCode` element in the invoice XML.
UBL-DT-06EN 16931AUTO-FIXBinary object elements shall contain the mime code attribute
Your invoice contains an embedded attachment (EmbeddedDocumentBinaryObject) but the mimeCode attribute is missing. The MIME type (e.g., application/pdf, image/png) must be specified.
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→