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 8 of 27
PEPPOL-EN16931-P0109PEPPOL_BISAUTO-FIXTax Category E MUST be used when exemption reason code is VATEX-EU-F
VAT category E requires exemption reason code VATEX-EU-F when using medical exemption.
PEPPOL-EN16931-P0110PEPPOL_BISAUTO-FIXTax Category E MUST be used when exemption reason code is VATEX-EU-I
VAT category E requires exemption reason code VATEX-EU-I when using insurance exemption.
PEPPOL-EN16931-P0111PEPPOL_BISAUTO-FIXTax Category E MUST be used when exemption reason code is VATEX-EU-J
VAT category E requires exemption reason code VATEX-EU-J when using educational exemption.
PEPPOL-EN16931-P0112PEPPOL_BISInvoice type code 326 or 384 are only allowed when both buyer and seller are German organizations
Invoice type codes 326 (partial invoice) and 384 (corrective invoice) are only allowed between German organizations.
PEPPOL-EN16931-R002PEPPOL_BISAUTO-FIXNo more than one note is allowed on document level, unless both the buyer and seller are German organizations.
Only one note is allowed at document level, unless both buyer and seller are German organizations. PEPPOL limits notes to simplify processing, with an exception for German XRechnung requirements.
PEPPOL-EN16931-R003PEPPOL_BISA buyer reference or purchase order reference MUST be provided.
Either a buyer reference or purchase order reference must be provided. This helps the buyer identify and match the invoice to their internal records or purchase order.
PEPPOL-EN16931-R005PEPPOL_BISAUTO-FIXVAT accounting currency code MUST be different from invoice currency code when provided.
When a VAT accounting currency is provided, it must be different from the invoice currency. If they are the same, the VAT accounting currency field should not be used at all.
PEPPOL-EN16931-R007PEPPOL_BISAUTO-FIXThe business process must follow the specific format "urn:fdc:peppol.eu:2017:poacc:billing:NN:1.0" where NN is the proce
The business process must follow the specific format "urn:fdc:peppol.eu:2017:poacc:billing:NN:1.0" where NN is the process number (01 for standard billing).
PEPPOL-EN16931-R008PEPPOL_BISAUTO-FIXDocument MUST not contain empty elements.
The document must not contain empty XML elements. All elements that are present must have content - empty tags are not allowed in PEPPOL invoices.
PEPPOL-EN16931-R043PEPPOL_BISAUTO-FIXAllowance/charge ChargeIndicator value MUST equal 'true' or 'false'
The ChargeIndicator must be exactly "true" or "false". This indicates whether the entry is a charge (true) or an allowance/discount (false).
PEPPOL-EN16931-R044PEPPOL_BISCharge 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-R051PEPPOL_BISAUTO-FIXAll currency codes in the invoice must match the invoice currency (BT-5), except for the VAT amount in accounting curren
All currency codes in the invoice must match the invoice currency (BT-5), except for the VAT amount in accounting currency (BT-111) which can be different. This ensures monetary consistency.
PEPPOL-EN16931-R053PEPPOL_BISAUTO-FIXOnly one tax total with tax subtotals MUST be provided.
Only one TaxTotal element with tax subtotals (VAT breakdown) is allowed. Multiple VAT breakdowns in the same currency are not permitted.
PEPPOL-EN16931-R054PEPPOL_BISAUTO-FIXOnly one tax total without tax subtotals MUST be provided when tax currency code is provided.
When VAT accounting currency is provided, exactly one TaxTotal without subtotals must exist for that currency. This reports the total VAT in the accounting currency.
PEPPOL-EN16931-R055PEPPOL_BISAUTO-FIXInvoice total VAT amount and Invoice total VAT amount in accounting currency MUST have the same operational sign
The invoice total VAT amount and VAT amount in accounting currency must have the same sign (both positive or both negative). They cannot have opposite signs.
PEPPOL-EN16931-R080PEPPOL_BISOnly one project reference is allowed on document level
Only one project reference is allowed at document level. If multiple projects are involved, they should be handled differently (e.g., separate invoices or line-level references).
PEPPOL-EN16931-R100PEPPOL_BISOnly 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-R101PEPPOL_BISAUTO-FIXElement Document reference can only be used for Invoice line object
Document reference elements at line level can only be used for invoice line object identifiers. Other document references belong at document level.
PEPPOL-EN16931-R110PEPPOL_BISStart 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-R111PEPPOL_BISEnd date of line period MUST be within invoice period.
The end date of a line period must fall within the invoice period. Line periods cannot extend beyond the overall invoice period.
PEPPOL-EN16931-R130PEPPOL_BISAUTO-FIXUnit code of price base quantity MUST be same as invoiced quantity.
The unit code of the price base quantity must match the unit code of the invoiced quantity. You cannot have different units between quantity and base quantity.
SE-R-003SEPEPPOL_BISAUTO-FIXSwedish organisation numbers should be numeric.
Swedish organization numbers must contain only numeric characters. No letters or special characters allowed.
SE-R-004SEPEPPOL_BISAUTO-FIXSwedish organisation numbers consist of 10 characters.
Swedish organization numbers must be exactly 10 digits. This is the standard format assigned by Bolagsverket.
SE-R-005SEPEPPOL_BISAUTO-FIXFor Swedish suppliers, when using Seller tax registration identifier, 'Godkänd för F-skatt' must be stated
Swedish suppliers using tax registration identifier must include the statement "Godkänd för F-skatt" (Approved for F-tax) on their invoices.
SE-R-007SEPEPPOL_BISAUTO-FIXFor Swedish suppliers using Plusgiro, the Account ID must be numeric
Swedish suppliers using Plusgiro must have a numeric account ID. No letters or special characters allowed.
SE-R-008SEPEPPOL_BISAUTO-FIXFor Swedish suppliers using Bankgiro, the Account ID must be numeric
Swedish suppliers using Bankgiro must have a numeric account ID. No letters or special characters allowed.
SE-R-009SEPEPPOL_BISAUTO-FIXFor Swedish suppliers using Bankgiro, the Account ID must have 7-8 characters
Swedish Bankgiro account IDs must be 7-8 characters long. This is the standard Bankgiro format.
SE-R-010SEPEPPOL_BISAUTO-FIXFor Swedish suppliers using Plusgiro, the Account ID must have 2-8 characters
Swedish Plusgiro account IDs must be 2-8 characters long. This is the standard Plusgiro format.
SE-R-011SEPEPPOL_BISAUTO-FIXSwedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30 with FinancialInstitutionBranch ID as SE:BANKG
Swedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30 with FinancialInstitutionBranch ID as SE:BANKGIRO or SE:PLUSGIRO.
SE-R-012SEPEPPOL_BISAUTO-FIXFor domestic transactions between Swedish trading partners, credit transfer should be indicated by PaymentMeansCode="30"
Swedish domestic credit transfers should use PaymentMeansCode 30. This is the standard code for Swedish domestic bank transfers.
SE-R-013SEPEPPOL_BISAUTO-FIXThe last digit of a Swedish organization number must be valid according to the Luhn algorithm.
The last digit of Swedish organization numbers must be valid according to the Luhn algorithm (checksum validation).
UBL-CR-011EN16931AUTO-FIXA UBL invoice should not include the LineCountNumeric
Your invoice contains LineCountNumeric which is not allowed in EN16931 invoices.
UBL-CR-012EN16931AUTO-FIXA UBL invoice should not include the InvoicePeriod StartTime
Your invoice contains InvoicePeriod/StartTime which is not allowed. Only StartDate is permitted.
UBL-CR-013EN16931AUTO-FIXA UBL invoice should not include the InvoicePeriod EndTime
Your invoice contains InvoicePeriod/EndTime which is not allowed. Only EndDate is permitted.
UBL-CR-014EN16931AUTO-FIXA UBL invoice should not include the InvoicePeriod DurationMeasure
Your invoice contains InvoicePeriod/DurationMeasure which is not allowed in EN16931 invoices.
UBL-CR-015EN16931AUTO-FIXA UBL invoice should not include the InvoicePeriod Description
Your invoice contains InvoicePeriod/Description which is not allowed. Use DescriptionCode instead.
UBL-CR-016EN16931AUTO-FIXA UBL invoice should not include the OrderReference CopyIndicator
Your invoice contains OrderReference/CopyIndicator which is not allowed in EN16931 invoices.
UBL-CR-017EN16931AUTO-FIXA UBL invoice should not include the OrderReference UUID
Your invoice contains OrderReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-018EN16931AUTO-FIXA UBL invoice should not include the OrderReference IssueDate
Your invoice contains OrderReference/IssueDate which is not allowed in EN16931 invoices.
UBL-CR-019EN16931AUTO-FIXA UBL invoice should not include the OrderReference IssueTime
Your invoice contains OrderReference/IssueTime which is not allowed in EN16931 invoices.
UBL-CR-020EN16931AUTO-FIXA UBL invoice should not include the OrderReference CustomerReference
Your invoice contains OrderReference/CustomerReference which is not allowed in EN16931 invoices.
UBL-CR-021EN16931AUTO-FIXA UBL invoice should not include the OrderReference OrderTypeCode
Your invoice contains OrderReference/OrderTypeCode which is not allowed in EN16931 invoices.
UBL-CR-022EN16931AUTO-FIXA UBL invoice should not include the OrderReference DocumentReference
Your invoice contains OrderReference/DocumentReference which is not allowed in EN16931 invoices.
UBL-CR-023EN16931AUTO-FIXA UBL invoice should not include the BillingReference CopyIndicator
Your invoice contains BillingReference/CopyIndicator which is not allowed in EN16931 invoices.
UBL-CR-024EN16931AUTO-FIXA UBL invoice should not include the BillingReference UUID
Your invoice contains BillingReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-025EN16931AUTO-FIXA UBL invoice should not include the BillingReference IssueTime
Your invoice contains BillingReference/IssueTime which is not allowed in EN16931 invoices.
UBL-CR-026EN16931AUTO-FIXA UBL invoice should not include the BillingReference DocumentTypeCode
Your invoice contains BillingReference/DocumentTypeCode which is not allowed in EN16931. Only the document ID is permitted for billing references.
UBL-CR-027EN16931AUTO-FIXA UBL invoice should not include the BillingReference DocumentType
Your invoice contains BillingReference/DocumentType which is not allowed in EN16931. Only the document ID is permitted for billing references.
UBL-CR-028EN16931AUTO-FIXA UBL invoice should not include the BillingReference Xpath
Your invoice contains BillingReference/Xpath which is not allowed in EN16931 invoices.
UBL-CR-029EN16931AUTO-FIXA UBL invoice should not include the BillingReference LanguageID
Your invoice contains BillingReference/LanguageID which is not allowed in EN16931 invoices.
Found an error? Fix it automatically
Upload your invoice and we'll fix common errors automatically. No XML editing required.
Fix Your Invoice