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 24 of 27

warningBR-CO-21en16931AUTO-FIX

Document allowance reason required

Each Document level allowance (BG-20) shall contain a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98), or both.

View fix
errorBR-CO-20en16931AUTO-FIX

Invoice line period dates required

If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both.

View fix
errorBR-DE-9DEXRECHNUNGNEEDS INPUT

Das Element "Buyer post code" (BT-53) muss übermittelt werden.

German XRechnung requires Buyer Post Code (BT-53). The buyer's postal code must be specified.

View fix
warningBR-DE-10DExrechnungNEEDS INPUT

Skonto payment terms format

Early payment discounts should follow XRechnung Skonto format.

View fix
errorGR-R-004-1GRPEPPOL_BISNEEDS INPUT

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

View fix
errorGR-R-006GRPEPPOL_BISNEEDS INPUT

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

View fix
errorBR-CO-05en16931AUTO-FIX

Allowance reason code and reason text mismatch

Document level allowance reason code (BT-98) and reason (BT-97) must indicate the same type of allowance. The coded reason and textual reason should describe the same discount type.

View fix
errorBR-CO-19en16931AUTO-FIX

Invoice period must have at least one date

If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both.

View fix
errorBR-CO-09en16931AUTO-FIX

VAT identifier missing country prefix

The Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) shall have a prefix in accordance with ISO 3166-1 alpha-2 by which the country of issue may be identified. Greece may use the prefix "EL".

View fix
errorBR-CL-24EN16931AUTO-FIX

For Mime code in attribute use MIMEMediaType.

An attachment MIME type is not valid. MIME types identify file formats like application/pdf, image/png, text/csv.

View fix
errorBR-CL-26EN16931AUTO-FIX

Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD code list

A Delivery Location Identifier scheme is not a valid ISO 6523 ICD code. Location identifiers need proper scheme codes.

View fix
warningBR-CO-23en16931AUTO-FIX

Invoice Line Allowance Reason Required

Each Invoice line allowance (BG-27) shall contain an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140), or both.

View fix
errorBR-CO-24en16931AUTO-FIX

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

View fix
errorBR-DE-17DExrechnungAUTO-FIX

Invalid XRechnung Invoice Type Code

XRechnung only allows specific Invoice Type Codes: 326 (partial), 380 (commercial), 381 (credit note), 384 (corrected), 389 (self-billed), 875-877 (construction invoices).

View fix
errorBR-O-02EN16931NEEDS INPUT

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

View fix
errorBR-DE-18DExrechnungAUTO-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#

View fix
warningBR-DE-21DEXRECHNUNGAUTO-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

View fix
errorBR-DE-22DEXRECHNUNGAUTO-FIX

Duplicate Attachment Filenames

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

View fix
errorBR-DE-27DEXRECHNUNGAUTO-FIX

Seller Contact Telephone Must Contain At Least Three Digits

Contact telephone numbers must follow proper format guidelines. German XRechnung requires telephone numbers to be properly formatted for machine processing, typically with country code and without invalid characters.

View fix
errorBR-DE-CVD-06-bDEXRECHNUNGAUTO-FIX

Missing CVD Classification for Clean Vehicle Attribute

When an invoice line has an AdditionalItemProperty with Name="cva" (clean vehicle attribute), it must also have exactly one CommodityClassification with ItemClassificationCode[@listID="CVD"] containing the vehicle category. This is required for German XRechnung invoices under the Clean Vehicle Directive.

View fix
errorBR-DEC-10EN16931AUTO-FIX

The allowed maximum number of decimals for the Sum of allowanced on document level (BT-107) is 2.

The sum of document level allowances has too many decimal places. This total must have a maximum of 2 decimal places.

View fix
errorBR-DEC-12en16931AUTO-FIX

Invoice total amount without VAT: max 2 decimals

The Invoice total amount without VAT (TaxExclusiveAmount, BT-109) allows a maximum of 2 decimal places.

View fix
errorBR-AF-02EN16931NEEDS INPUT

When invoice lines use the IGIC VAT category, the seller must have a proper tax identifier (VAT ID, tax registration, or

When invoice lines use the IGIC VAT category, the seller must have a proper tax identifier (VAT ID, tax registration, or tax representative VAT ID).

View fix
errorBR-AF-03EN16931NEEDS INPUT

When document level allowances use the IGIC VAT category, the seller must have a proper tax identifier.

When document level allowances use the IGIC VAT category, the seller must have a proper tax identifier.

View fix
errorPEPPOL-EN16931-R010peppol-bis-3NEEDS INPUT

Missing buyer electronic address

Peppol invoices MUST contain buyer electronic address (BT-49) for network routing. The buyer endpoint identifier enables the Peppol network to deliver the invoice to the correct recipient.

View fix
errorBR-DE-01DEUpeppol-bis-3NEEDS 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.

View fix
errorBR-DEC-16en16931AUTO-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.

View fix
errorBR-DEC-17EN16931AUTO-FIX

Rounding amount: max 2 decimals

The rounding adjustment amount has too many decimal places. Rounding amounts must have a maximum of 2 decimal places.

View fix
warningBR-DEC-23en16931AUTO-FIX

Line net amount: max 2 decimals

InvoiceLine/LineExtensionAmount (BT-131) allows maximum 2 decimal places.

View fix
errorPEPPOL-EN16931-R004PEPPOL_BIS

The specification identifier must be exactly "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0

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.

View fix
errorBR-03peppol-bis-3NEEDS INPUT

Invoice must have an issue date

Every invoice must contain an issue date indicating when the invoice was created.

View fix
warningIN-PROFILE-FORMATpeppol-bis-3

ProfileID format recommendation

ProfileID should have the standard Peppol value

View fix
errorBR-17peppol-bis-3NEEDS INPUT

Invoice line item name required

Each invoice line must have an item name describing what is being invoiced.

View fix
errorBR-18peppol-bis-3NEEDS INPUT

Invoice line price required

Each invoice line must have a price amount (item net price).

View fix
warningBR-55peppol-bis-3NEEDS INPUT

Prepayment should reference prepayment invoice

When PrepaidAmount is used, reference the prepayment invoice.

View fix
errorBR-AE-04EN16931NEEDS INPUT

When document level charges use the reverse charge VAT category, both seller and buyer must have proper tax identifiers

When document level charges use the reverse charge VAT category, both seller and buyer must have proper tax identifiers for tax compliance.

View fix
errorBR-AF-04EN16931NEEDS INPUT

When document level charges use the IGIC VAT category, the seller must have a proper tax identifier.

When document level charges use the IGIC VAT category, the seller must have a proper tax identifier.

View fix
errorBR-CL-14en16931NEEDS INPUT

Invalid payment means code

Payment means code must be from UNTDID 4461 code list. Common codes: 30 (credit transfer), 48 (bank card), 58 (SEPA), 59 (SEPA direct debit).

View fix
errorBR-CO-25en16931NEEDS INPUT

Duplicate invoice line identifiers

Each invoice line must have unique ID within document.

View fix
errorBR-CO-26EN16931NEEDS INPUT

The invoice is missing seller identification. At least one of: Seller Identifier (BT-29), Legal Registration ID (BT-30),

The invoice is missing seller identification. At least one of: Seller Identifier (BT-29), Legal Registration ID (BT-30), or VAT Identifier (BT-31) must be present.

View fix
errorBR-DE-1DEXRECHNUNGNEEDS INPUT

Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.

German XRechnung requires Payment Instructions (BG-16). You must specify how the invoice should be paid.

View fix
errorBR-DE-2DEXRECHNUNGNEEDS INPUT

Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.

German XRechnung requires a Seller Contact section (BG-6). Contact details for the seller must be provided.

View fix
errorBR-DE-4DEXRECHNUNGNEEDS 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.

View fix
errorBR-DE-5DEXRECHNUNGNEEDS INPUT

Das Element "Seller contact point" (BT-41) muss übermittelt werden.

German XRechnung requires Seller Contact Point (BT-41). A contact person or department name must be provided.

View fix
errorBR-DE-6DEXRECHNUNGNEEDS INPUT

Das Element "Seller contact telephone number" (BT-42) muss übermittelt werden.

German XRechnung requires Seller Contact Telephone (BT-42). A phone number for the seller must be provided.

View fix
errorBR-DE-7DEXRECHNUNGNEEDS INPUT

Das Element "Seller contact email address" (BT-43) muss übermittelt werden.

German XRechnung requires Seller Contact Email (BT-43). An email address for the seller must be provided.

View fix
errorBR-DE-8DEXRECHNUNGNEEDS INPUT

Das Element "Buyer city" (BT-52) muss übermittelt werden.

German XRechnung requires Buyer City (BT-52). The buyer's city must be specified.

View fix
warningBR-DE-26DEXRECHNUNGNEEDS INPUT

A credit note or corrective invoice must reference the original invoice it is correcting. The preceding invoice referenc

A credit note or corrective invoice must reference the original invoice it is correcting. The preceding invoice reference field is required when the invoice type indicates a correction. This creates the audit trail needed for proper accounting.

View fix
errorBR-DE-TMP-32DEXRECHNUNGNEEDS INPUT

An invoice should specify when goods were delivered or services performed. This can be done via the actual delivery date

An invoice should specify when goods were delivered or services performed. This can be done via the actual delivery date field, an invoicing period at document level, or invoice line periods on each line item. At least one of these date specifications should be present.

View fix
errorBR-E-03EN16931NEEDS INPUT

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

View fix

Found an error? Fix it automatically

Upload your invoice and we'll fix common errors automatically. No XML editing required.

Fix Your Invoice