E-Invoice Error Reference
1350+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
1350 errors found · Page 2 of 27
RO-R-002ROUubl-2.1BLOCKEDe-Factura submission required
Romanian B2B/B2G invoices must go through e-Factura (SPV).
BR-29EN 16931AUTO-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-32EN 16931AUTO-FIXEach Document level allowance (BG-20) shall have a Document level allowance...
Each Document level allowance (BG-20) shall have a Document level allowance VAT category code (BT-95). Check the `cac:AllowanceCharge` element in your invoice XML.
BR-33EN 16931AUTO-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.
RO-R-003ROUcius-roBLOCKEDCIUS-RO format required
Romanian e-invoices must use CIUS-RO profile.
BR-38EN 16931AUTO-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.
UBL-SR-09ubl-2.1CONFIRMInvalid boolean value
Boolean elements must be true or false.
BR-44EN 16931AUTO-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.
RO-R-004ROUubl-2.1BLOCKEDRON conversion may be required
Romanian tax reporting requires RON amounts.
BR-CO-15EN 16931AUTO-FIXTax exclusive amount calculation error
Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).. This applies to the `cbc:TaxInclusiveAmount` element in the invoice XML.
HU-R-001HUNnavINPUTHungarian tax number required
Hungarian invoices must include adószám (tax number).
HU-R-002HUNnavBLOCKEDNAV Online Invoice reporting required
Hungarian invoices over HUF 100k must be reported to NAV.
UBL-SR-11EN16931CONFIRMSeller legal registration identifier shall occur maximum once
Your invoice contains multiple Seller legal registration identifiers (PartyLegalEntity/CompanyID). EN16931 allows only one legal registration ID per seller.
UBL-CR-493UBL 2.1AUTO-FIXA UBL invoice should not include the PaymentAlternativeExchangeRate
Your invoice contains a PaymentAlternativeExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
BR-45EN 16931BLOCKEDEach VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).
Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).. Check the `cac:TaxSubtotal` element in your invoice XML.
BR-47EN 16931AUTO-FIXLine allowance amount required
Line-level AllowanceCharge must include the Amount element.
BR-48EN 16931BLOCKEDDocument allowance tax category required
Document-level allowances/charges must specify the VAT category.
HU-R-003HUNnavBLOCKEDNAV technical user required
NAV reporting requires registered technical user.
HU-R-004HUNnavINPUTHungarian VAT code required
NAV requires Hungarian-specific VAT category codes.
BR-49EN 16931INPUTA Payment instruction (BG-16) shall specify the Payment means type code (BT-81)
A Payment instruction (BG-16) shall specify the Payment means type code (BT-81). This applies to the `cac:PaymentMeans` element in the invoice XML.
BR-52EN 16931INPUTEach Additional supporting document (BG-24) shall contain a Supporting...
InvoiceTypeCode must be a valid UNTDID 1001 document type code.
BR-57EN 16931INPUTEach Deliver to address (BG-15) shall contain a Deliver to country code (BT-80)
Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80). This applies to the `cac:Address` element in the invoice XML.
BR-55EN 16931INPUTPrepayment should reference prepayment invoice
When PrepaidAmount is used, reference the prepayment invoice.
UBL-SR-13EN16931CONFIRMSeller tax registration shall occur maximum once
Your invoice contains multiple Seller tax registration elements (PartyTaxScheme). EN16931 allows maximum one tax registration per seller.
UBL-SR-14EN16931CONFIRMSeller additional legal information shall occur maximum once
Your invoice contains multiple Seller additional legal information elements (PartyLegalEntity/CompanyLegalForm). EN16931 allows only one.
BR-62EN 16931AUTO-FIXThe Seller electronic address (BT-34) shall have a Scheme identifier.
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?
BR-64EN 16931AUTO-FIXItem standard identifier needs scheme
If item has standard identifier, scheme must be specified.
BR-65EN 16931AUTO-FIXBuyer item identifier should be unique
The Item classification identifier (BT-158) shall have a Scheme identifier.
BR-DEC-03en16931BLOCKEDDocument charge: max 2 decimals
Document level charge amount allows max 2 decimal places.
BR-66EN 16931AUTO-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.
UBL-SR-17EN16931CONFIRMBuyer legal registration identifier shall occur maximum once
Your invoice contains multiple Buyer legal registration identifiers (PartyLegalEntity/CompanyID). EN16931 allows only one legal registration ID per buyer.
DE-R-022DEUPEPPOL_BISCONFIRMDuplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) i
Duplicate attachment filename. All attached documents in German invoices must have unique filenames (case-insensitive) in element BT-125.
BR-DEC-08en16931BLOCKEDAllowance total: max 2 decimals
AllowanceTotalAmount allows max 2 decimal places.
IN-ALLOWANCE-AMOUNT-REQUIREDpeppol-bis-3INPUTAllowance/Charge amount required
AllowanceCharge elements must have an Amount element specified.
BR-67EN 16931AUTO-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.
XML-003ubl-2.1BLOCKEDXML encoding declaration recommended
XML should declare character encoding.
DE-R-023-2DEUPEPPOL_BISCONFIRMConflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct d
Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct debit (BG-19) groups must not be provided.
XML-005ubl-2.1BLOCKEDXML schema validation failed
Document does not conform to XSD schema.
XML-006en16931BLOCKEDSchematron validation failed
Document failed business rule validation.
UBL-SR-19EN16931CONFIRMPayee name shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee name elements (PayeeParty/PartyName/Name). EN16931 allows only one payee name.
DE-R-024-2DEUPEPPOL_BISCONFIRMConflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and dir
Conflicting payment information. When payment code 48, 54, or 55 (payment card) is used, credit transfer (BG-17) and direct debit (BG-19) groups must not be provided.
UBL-SR-20EN16931CONFIRMPayee identifier shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee identifier elements (PayeeParty/PartyIdentification/ID). EN16931 allows only one payee identifier.
BR-02EN 16931INPUTInvoice must have an invoice number
Every invoice must contain a unique invoice number (ID) to identify the document.
FORMAT-002factur-xBLOCKEDPDF must be PDF/A format
Factur-X requires PDF/A-3 base document.
BR-AE-02EN 16931INPUTReverse charge requires both VAT IDs
Reverse charge requires seller and buyer VAT identifiers.
UBL-SR-21EN16931CONFIRMPayee legal registration identifier shall occur maximum once, if the Payee is different from the Seller
Your invoice contains multiple Payee legal registration identifiers (PayeeParty/PartyLegalEntity/CompanyID). EN16931 allows only one.
UBL-CR-015UBL 2.1AUTO-FIXA UBL invoice should not include the InvoicePeriod Description
Your invoice contains InvoicePeriod/Description which is not allowed. Use DescriptionCode instead.
BR-AE-03EN 16931INPUTWhen document level allowances use the reverse charge VAT category, both...
When document level allowances use the reverse charge VAT category, both seller and buyer must have proper tax identifiers for tax compliance.
DE-R-025-1DEUPEPPOL_BISCONFIRMIf "Payment means type code" (BT-81) contains a code for direct debit (59), "DIRECT DEBIT" (BG-19) shall be provided.
Direct debit details missing. When payment code 59 (direct debit) is used, the Direct Debit group (BG-19) with mandate information must be provided.
UBL-SR-22EN16931CONFIRMSeller tax representative name shall occur maximum once, if the Seller has a tax representative
Your invoice contains multiple Tax representative name elements (TaxRepresentativeParty/PartyName/Name). EN16931 allows only one.
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→