E-Invoice Error Reference
1326+ documented errors for Peppol, UBL, CII, and EN16931 validation errors. Find the fix for any error code.
1326 errors found • Page 23 of 27
UBL-SR-39EN16931AUTO-FIXProject reference shall occur maximum once.
Your invoice contains multiple Project reference elements (ProjectReference/ID). EN16931 allows only one project reference per invoice.
UBL-SR-40EN16931AUTO-FIXBuyer trade name shall occur maximum once
Your invoice contains multiple Buyer trade name elements (AccountingCustomerParty/Party/PartyName). EN16931 allows only one buyer trading name.
UBL-SR-42EN16931AUTO-FIXParty tax scheme shall occur maximum twice in accounting supplier party
Your seller party (AccountingSupplierParty) contains more than two PartyTaxScheme elements. EN16931 allows maximum two (one VAT scheme and optionally one other tax scheme).
UBL-SR-43EN16931AUTO-FIXScheme identifier shall only be used for invoiced object (document type code with value 130 or 50)
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). Scheme identifiers are only valid for these document types.
UBL-SR-44EN16931An Invoice may only have one unique PaymentID, but the PaymentID may be used for multiple PaymentMeans
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-45EN16931AUTO-FIXDue Date shall occur maximum once
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
UBL-SR-46EN16931AUTO-FIXPayment means text shall occur maximum once
Your invoice contains multiple Payment means instruction text elements. EN16931 allows only one instruction note per payment means.
UBL-SR-47EN16931When there are more than one payment means code, they shall be equal
Your invoice has multiple payment means with different PaymentMeansCode values. When multiple payment means exist in EN16931, they must all use the same payment method code.
UBL-SR-48EN16931Invoice lines shall have one and only one classified tax category.
Your invoice line has an incorrect number of ClassifiedTaxCategory elements. Each invoice line must have exactly one tax category classification - not zero, not multiple.
UBL-SR-49EN16931AUTO-FIXValue tax point date shall occur maximum once
Your invoice contains multiple Value tax point date elements (TaxPointDate). EN16931 allows only one tax point date per invoice.
UBL-SR-50EN16931AUTO-FIXItem description shall occur maximum once
Your invoice line Item contains multiple Description elements. EN16931 allows only one item description per line.
UBL-SR-51EN16931AUTO-FIXAn address can only have one third line.
Duplicate address line 3. An address can have at most one additional address line (third line).
UBL-SR-52EN16931AUTO-FIXDocument reference shall occur maximum once
Duplicate document reference. Document reference can only appear once in the specified context.
UBL-SR-53EN16931AUTO-FIXCompanyID (VAT Identifier) must be stated when providing the PartyTaxScheme/TaxScheme/ID.
Missing VAT ID with tax scheme. When providing TaxScheme/ID, the CompanyID (VAT identifier) must also be provided.
BR-01peppol-bis-3Invoice must have specification identifier
Every Peppol BIS invoice must include a specification identifier (CustomizationID) that indicates which profile the invoice conforms to.
BR-23peppol-bis-3AUTO-FIXMissing unit of measure code
Each Invoice line shall have an Invoiced quantity unit of measure code (BT-130). This identifies the unit of measure for the invoiced quantity using UN/ECE Recommendation 20 codes.
BR-30peppol-bis-3AUTO-FIXInvoice line period end date before start date
If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the end date shall be later or equal to the start date.
BR-38peppol-bis-3AUTO-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.
BR-AG-02EN16931NEEDS INPUTWhen using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
BR-AG-03EN16931NEEDS INPUTWhen using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
BR-44peppol-bis-3AUTO-FIXInvoice line charge reason required
An invoice line charge (BG-28) is missing both a reason text and reason code. At least one must be provided to explain this line surcharge.
BR-51peppol-bis-3AUTO-FIXPayment card primary account number not masked
The invoice contains a full credit card number (BT-87), which violates PCI security standards. Only the first 6 and last 4 digits should be shown.
BR-05peppol-bis-3AUTO-FIXMissing document currency code
An Invoice shall have an Invoice currency code (BT-5). This specifies the currency used for all monetary amounts in the invoice using ISO 4217 three-letter codes.
BR-21peppol-bis-3AUTO-FIXMissing invoice line identifier
Each Invoice line shall have an Invoice line identifier (BT-126). This is a unique sequential number identifying each line item on the invoice.
BR-29peppol-bis-3AUTO-FIXInvoice period end date before start date
The Invoicing Period End Date (BT-74) is before the Start Date (BT-73). The end date must be on or after the start date.
BR-33peppol-bis-3AUTO-FIXDocument level allowance reason required
A document level allowance (discount) is missing both a reason text (BT-97) and reason code (BT-98). At least one must be provided to explain why this discount exists.
BR-42peppol-bis-3AUTO-FIXInvoice line allowance reason required
An invoice line allowance (BG-27) is missing both a reason text (BT-139) and reason code (BT-140). At least one must be provided to explain this line discount.
BR-66EN16931AUTO-FIXAn Invoice shall contain maximum one Payment Card account (BG-18).
The invoice contains multiple Payment Card accounts (BG-18). Only one card payment method is allowed per invoice.
BR-67EN16931AUTO-FIXAn Invoice shall contain maximum one Payment Mandate (BG-19).
The invoice contains multiple Payment Mandates (BG-19). Only one direct debit mandate is allowed per invoice.
BR-AE-05EN16931AUTO-FIXReverse 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.
BR-AE-06en16931AUTO-FIXDocument level allowance with reverse charge must have 0% VAT rate
When a document level allowance uses the reverse charge VAT category, the VAT rate must be 0%. Allowances in reverse charge scenarios follow the same zero-rate rule.
BR-AE-09en16931AUTO-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-AE-10EN16931AUTO-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-AF-10EN16931AUTO-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-AG-01EN16931AUTO-FIXIPSI VAT breakdown required when IPSI used on lines
When using the IPSI VAT category (M) on invoice lines, allowances, or charges, you must have exactly one matching VAT breakdown section for IPSI.
BR-AG-05EN16931AUTO-FIXIPSI invoice line VAT rate must be 0% or positive
When an invoice line uses the IPSI VAT category (M for Ceuta/Melilla indirect tax), the VAT rate must be 0 or greater than zero.
BR-AG-07EN16931AUTO-FIXIPSI document level charge VAT rate must be 0% or positive
When a document level charge uses the IPSI VAT category (M for Ceuta/Melilla indirect tax), the VAT rate must be 0 or greater than zero.
BR-AG-09EN16931AUTO-FIXIPSI VAT breakdown tax amount must be calculated correctly
The tax amount for the IPSI VAT category in the VAT breakdown must be calculated based on the taxable amount and rate.
BR-AG-08EN16931AUTO-FIXIPSI taxable amount calculation error
The IPSI taxable amount in the VAT breakdown does not match the calculated sum of line amounts plus charges minus allowances for the IPSI category.
BR-CL-07en16931AUTO-FIXObject identifier scheme MUST be from UNTDID 1153
An Object Identifier scheme is not a valid UNTDID 1153 code. This identifies what type of reference the object ID represents.
BR-CL-08en16931AUTO-FIXInvoice note subject code must be from UNCL 4451
An Invoice Note subject code is not a valid UNCL 4451 code. Note subject codes categorize the type of note (e.g., AAI=general information, REG=regulatory, SUR=surcharge).
BR-AG-04EN16931NEEDS INPUTWhen using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
BR-CL-10en16931AUTO-FIXInvalid identifier scheme (ISO 6523 ICD)
Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list.
BR-CL-13EN16931AUTO-FIXInvalid item classification scheme
Item classification identifier identification scheme identifier (listID) MUST be coded using one of the UNTDID 7143 list. This applies to the ItemClassificationCode@listID attribute in CommodityClassification.
BR-CL-19EN16931AUTO-FIXInvalid allowance reason code
Coded allowance reasons MUST belong to the UNCL 5189 code list. This applies to AllowanceChargeReasonCode for allowances (ChargeIndicator=false).
BR-DEC-05en16931AUTO-FIXDocument level charge: max 2 decimals
Document level charge amount (BT-99) allows max 2 decimal places.
BR-B-02EN16931NEEDS INPUTWhen using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
When using this VAT category, the seller must have a VAT identifier, tax registration, or tax representative.
BR-CO-03en16931AUTO-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-06en16931AUTO-FIXCharge reason and code must match
Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge. The reason text must semantically match the UNTDID 7161 code.
BR-CO-07en16931AUTO-FIXLine allowance reason and code must match
Invoice line allowance reason code (BT-140) and Invoice line allowance reason (BT-139) shall indicate the same type of allowance reason. The reason text must semantically match the UNTDID 5189 code.
Found an error? Fix it automatically
Upload your invoice and we'll fix common errors automatically. No XML editing required.
Fix Your Invoice