E-Invoice Error Reference

1375+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.

1375 errors found · Page 14 of 28

errorBR-CL-24EN 16931AUTO-FIX

For Mime code in attribute use MIMEMediaType (IANA media types).

An attached document has an invalid MIME type code. MIME types must follow the standard format (type/subtype), such as application/pdf for PDF files, image/png for PNG images, or text/csv for CSV files.

errorSE-R-002Peppol BIS 3.0AUTO-FIX

For Swedish suppliers, Swedish VAT-numbers must have the trailing 12...

Swedish invoices to public sector should be Svefaktura compliant.

errorUBL-SR-53EN16931CONFIRM

CompanyID (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.

errorSE-R-004Peppol BIS 3.0AUTO-FIX

Swedish organisation number has wrong length

The seller's Swedish organisation number (organisationsnummer) does not have the required 10 characters. Swedish org numbers are always exactly 10 digits, typically written as XXXXXX-XXXX but stored without the hyphen.

errorSE-R-013Peppol BIS 3.0AUTO-FIX

Swedish organisation number has wrong check digit

The seller's Swedish organisation number (organisationsnummer) has an incorrect check digit. The last digit of a 10-digit Swedish org number is calculated using the Luhn algorithm. This rule checks the seller's company registration number specifically.

errorPEPPOL-EN16931-P0100Peppol BIS 3.0AUTO-FIX

Wrong invoice type code for Peppol

Peppol Invoice documents must use type code 380 (Commercial Invoice). A different or missing type code was found.

errorPEPPOL-COMMON-R047Peppol BIS 3.0AUTO-FIX

Italian VAT Code (Partita Iva) must be stated in the correct format

Italian VAT Code (Partita IVA) must follow the correct format. This is an 11-digit number prefixed with "IT" for international use.

errorPEPPOL-COMMON-R048Peppol BIS 3.0AUTO-FIX

Italian VAT Code (Partita Iva) must be stated in the correct format

Italian VAT Code (Partita IVA) must follow the correct format. This validation applies to another field where Italian VAT numbers appear.

errorPEPPOL-EN16931-P0105Peppol BIS 3.0AUTO-FIX

Tax category and exemption reason code do not match

Your invoice has a VAT breakdown where the tax category and the exemption reason code do not match. For example, category "O" (Not subject to VAT) requires exemption code "VATEX-EU-O", but a different code was found.

errorPEPPOL-COMMON-R050Peppol BIS 3.0AUTO-FIX

Australian Business Number (ABN) MUST be stated in the correct format.

Australian Business Numbers (ABN) must follow the correct format. ABN is an 11-digit identifier with a specific check digit algorithm.

errorBR-DE-01DEUXRechnung (Germany)INPUT

Invalid Leitweg-ID Format

German B2G (Business-to-Government) invoices require a valid Leitweg-ID in the Buyer Reference field (BT-10). The Leitweg-ID is a routing identifier that directs your invoice to the correct government department.

errorBR-DEC-16EN 16931AUTO-FIX

Paid amount: max 2 decimals

The Paid amount (BT-113, also known as prepaid amount) must have a maximum of 2 decimal places. This represents amounts already paid toward the invoice.

warningIN-PROFILE-FORMATPeppol BIS 3.0AUTO-FIX

ProfileID format recommendation

ProfileID should have the standard Peppol value

errorPEPPOL-EN16931-R130Peppol BIS 3.0AUTO-FIX

Unit 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.

errorPEPPOL-EN16931-R055Peppol BIS 3.0AUTO-FIX

Invoice total VAT amount and Invoice total VAT amount in accounting currency...

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.

errorUBL-CR-360UBL 2.1AUTO-FIX

A UBL invoice should not include the Delivery DeliveryLocation Address...

Your invoice contains a DeliveryLocation Address AddressTypeCode element which is not allowed in EN16931 invoices. This element must be removed.

errorUBL-CR-361UBL 2.1AUTO-FIX

A UBL invoice should not include the Delivery DeliveryLocation Address...

Your invoice contains a DeliveryLocation Address AddressFormatCode element which is not allowed in EN16931 invoices. This element must be removed.

errorUBL-CR-362UBL 2.1AUTO-FIX

A UBL invoice should not include the Delivery DeliveryLocation Address Postbox

Your invoice contains a DeliveryLocation Address Postbox element which is not allowed in EN16931 invoices. This element must be removed.

errorUBL-CR-137UBL 2.1AUTO-FIX

A UBL invoice should not include the Signature

Your invoice contains a Signature element which is not allowed in EN16931. Digital signatures should be applied at transport level, not in the invoice XML.

errorUBL-CR-294UBL 2.1AUTO-FIX

A UBL invoice should not include the BuyerCustomerParty

Your invoice contains a BuyerCustomerParty element which is not allowed in EN16931 invoices. Use AccountingCustomerParty instead.

errorPEPPOL-EN16931-R054Peppol BIS 3.0AUTO-FIX

Only one tax total without tax subtotals MUST be provided when tax currency...

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.

errorPEPPOL-EN16931-F001Peppol BIS 3.0AUTO-FIX

A date MUST be formatted YYYY-MM-DD.

A date MUST be formatted YYYY-MM-DD. This validation rule ensures Invoice compliance with Peppol BIS 3.0.

errorSE-R-005Peppol BIS 3.0AUTO-FIX

For Swedish suppliers, when using Seller tax registration identifier,...

Swedish suppliers using tax registration identifier must include the statement "Godkänd för F-skatt" (Approved for F-tax) on their invoices.

errorSE-R-007Peppol BIS 3.0AUTO-FIX

For 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.

errorSE-R-008Peppol BIS 3.0AUTO-FIX

For 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.

errorSE-R-009Peppol BIS 3.0AUTO-FIX

For 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.

errorSE-R-010Peppol BIS 3.0AUTO-FIX

For 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.

errorSE-R-011Peppol BIS 3.0AUTO-FIX

Swedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30...

Swedish suppliers using Bankgiro or Plusgiro must use PaymentMeansCode 30 with FinancialInstitutionBranch ID as SE:BANKGIRO or SE:PLUSGIRO.

warningSE-R-012Peppol BIS 3.0AUTO-FIX

For domestic transactions between Swedish trading partners, credit transfer...

Swedish domestic credit transfers should use PaymentMeansCode 30. This is the standard code for Swedish domestic bank transfers.

errorPEPPOL-EN16931-P0104Peppol BIS 3.0AUTO-FIX

Tax Category G MUST be used when exemption reason code is VATEX-EU-G

VAT category G (Export) requires exemption reason code VATEX-EU-G. The category and exemption must match.

errorPEPPOL-EN16931-P0101Peppol BIS 3.0BLOCKED

Credit note type code MUST be set according to the profile.

The Credit Note Type Code does not match the Peppol profile. Use 381 for credit notes in Peppol BIS 3.0.

errorPEPPOL-EN16931-P0106Peppol BIS 3.0AUTO-FIX

Tax Category K MUST be used when exemption reason code is VATEX-EU-IC

VAT category K (Intra-community) requires exemption reason code VATEX-EU-IC. IC supplies must use correct code.

errorPEPPOL-EN16931-P0107Peppol BIS 3.0AUTO-FIX

Tax Category AE MUST be used when exemption reason code is VATEX-EU-AE

VAT category AE (Reverse charge) requires exemption reason code VATEX-EU-AE. Reverse charge must use correct code.

errorPEPPOL-EN16931-P0108Peppol BIS 3.0AUTO-FIX

Tax Category E MUST be used when exemption reason code is VATEX-EU-D

VAT category E requires exemption reason code VATEX-EU-D when using this specific exemption. Category E covers various exemptions.

errorPEPPOL-EN16931-P0109Peppol BIS 3.0AUTO-FIX

Tax 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.

errorPEPPOL-EN16931-P0110Peppol BIS 3.0AUTO-FIX

Tax 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.

errorPEPPOL-EN16931-P0111Peppol BIS 3.0AUTO-FIX

Tax 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.

errorBR-DE-18DEUXRechnung (Germany)AUTO-FIX

Invalid Skonto (Cash Discount) Format

XRechnung Skonto (early payment discount) lines in PaymentTerms must follow the required format: #SKONTO#TAGE=n#PROZENT=n.nn#BASISBETRAG=n.nn#

errorBR-DE-17DEUXRechnung (Germany)INPUT

Seller contact information (name, phone, email) required in XRechnung

BR-DE-17 fires when an XRechnung invoice's seller party (cac:AccountingSupplierParty/cac:Party) does not carry a complete cac:Contact block containing the seller contact point name (BT-41, cbc:Name), telephone (BT-42, cbc:Telephone) and email (BT-43, cbc:ElectronicMail). XRechnung makes all three contact fields mandatory; Peppol BIS Billing 3.0 makes them optional, so an invoice that validates against Peppol can still fail KoSIT XRechnung validation with BR-DE-17.

errorUBL-CR-629UBL 2.1AUTO-FIX

A UBL invoice should not include the InvoiceLine Item Price ValidityPeriod

UBL 2.1 Invoice schema does not include `cac:Price/cac:ValidityPeriod`. This element must be removed for EN 16931 compliance.

errorBR-DE-21DEUXRechnung (Germany)AUTO-FIX

Invalid XRechnung Specification Identifier

The Specification Identifier (BT-24 CustomizationID) must follow the XRechnung URN format: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_X.X

errorUBL-CR-295UBL 2.1AUTO-FIX

A UBL invoice should not include the SellerSupplierParty

Your invoice contains a SellerSupplierParty element which is not allowed in EN16931 invoices. Use AccountingSupplierParty instead.

errorBR-DE-15DEUXRechnung (Germany)AUTO-FIX

Buyer reference (Leitweg-ID) mandatory

BuyerReference (BT-10) is mandatory in XRechnung.

errorBR-DE-22DEUXRechnung (Germany)AUTO-FIX

Duplicate Attachment Filenames

XRechnung requires all attachment filenames to be unique. Multiple EmbeddedDocumentBinaryObject elements have the same filename attribute.

errorBR-DE-3DEUXRechnung (Germany)INPUT

Das Element "Seller city" (BT-37) muss übermittelt werden.

German XRechnung requires Seller City (BT-37). The seller's city must be specified.

errorBR-G-03EN 16931INPUT

When 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:AllowanceCharge`, rule BR-G-03).

errorBR-09EN 16931INPUT

Seller country code missing

Your invoice has a seller postal address but is missing the country code. Every invoice must include the seller's country as a two-letter ISO code (e.g. DE for Germany, NL for Netherlands).

errorBR-DE-4DEUXRechnung (Germany)INPUT

Das Element "Seller post code" (BT-38) muss übermittelt werden.

German XRechnung requires Seller Post Code (BT-38). The seller's postal code must be specified.

errorBR-S-03EN 16931INPUT

When 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:AllowanceCharge`, rule BR-S-03).

errorBR-11EN 16931INPUT

Buyer country code is mandatory

The Buyer postal address (BG-8) shall contain a Buyer country code (BT-55) using ISO 3166-1 alpha-2.

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