E-Invoice Error Reference
1374+ documented errors for Peppol, UBL, CII, and EN16931 validation errors.
347 errors found · Page 6 of 7 in Business Rules
BR-AE-02EN 16931INPUTReverse charge requires both VAT IDs
Reverse charge requires seller and buyer VAT identifiers.
BR-CO-10EN 16931AUTO-FIXSum of Invoice line net amount (BT-106) = Σ Invoice line net amount (BT-131).
Each VAT category taxable amount must be correctly calculated from line amounts.
BR-13EN 16931BLOCKEDInvoice total without VAT required
The invoice must state the amount due for payment (PayableAmount).
BR-CO-02en16931INPUTPayment means code must be valid
Payment means type code must be from UNCL4461.
BR-S-04EN 16931INPUTSeller VAT number missing (required for standard-rated charges)
Your invoice includes a document-level charge (surcharge) with standard VAT rate, but the seller does not have a VAT registration number on the invoice. Standard-rated VAT charges require the seller to be VAT-registered.
BR-S-06EN 16931INPUTStandard rate VAT calculation error
In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Standard rated" the Document level allowance VAT rate (BT-96) shall be greater than zero.. This applies to the `cac:AllowanceCharge` element in the invoice XML.
BR-34peppol-bis-3INPUTInvoice line VAT category required
Each invoice line must specify which VAT category applies to that line.
BR-CO-01en16931INPUTVAT category code must be valid
VAT category code must be from allowed code list (S, Z, E, AE, K, G, O, L, M).
BR-S-05EN 16931INPUTStandard rate taxable amount calculation
VAT category S taxable amount must equal sum of S-rated amounts.
BR-IC-02EN 16931INPUTIntra-community requires both VAT IDs
Intra-community supply requires seller and buyer VAT IDs.
BR-07EN 16931INPUTInvoice must have buyer name
An Invoice shall contain the Buyer name (BT-44). This is the trading name or legal name of the buyer/customer.
BR-54EN 16931INPUTCorrective invoice must reference original
Corrective invoices (type 384) must reference the invoice being corrected.
UBL-SR-07Peppol BIS 3.0INPUTPreceding invoice number missing
Your invoice references a previous invoice (via BillingReference) but the actual invoice number is missing. If this invoice replaces or corrects an earlier one, you need to specify which one.
BR-CO-26EN 16931INPUTThe invoice is missing seller identification. At least one of: Seller...
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.
DE-R-001DEUEN 16931INPUTPayment instructions missing
German invoices must include payment instructions — how the buyer should pay. This typically means a bank account (IBAN) and payment method code (e.g. SEPA Credit Transfer).
DE-R-002DEUEN 16931INPUTSeller contact information missing
German invoices must include contact information for the seller — a contact person name, telephone number, and email address. This is required by German e-invoicing regulations.
BR-28EN 16931AUTO-FIXThe Item gross price (BT-148) shall NOT be negative.
The Item gross price (BT-148) shall NOT be negative.. Review the `cbc:BaseQuantity` element.
DE-R-015DEUEN 16931INPUTBuyer reference required (German)
German invoices must include a Buyer reference (BT-10). For B2G (Business-to-Government) invoices, this is typically the Leitweg-ID routing number.
PEPPOL-EN16931-R003EN 16931INPUTBuyer reference or order reference required
A buyer reference (BT-10) or purchase order reference (BT-13) MUST be provided in Peppol invoices.
PEPPOL-EN16931-R010Peppol BIS 3.0INPUTBuyer electronic address required
Peppol invoices MUST include a buyer electronic address (BT-49) with a valid EndpointID and schemeID for network routing.
DE-R-009DEUEN 16931INPUTThe element "Buyer post code" (BT-53) shall be provided.
Buyer postal code is missing. German invoices must include the buyer's postal code (BT-53).
BR-27EN 16931AUTO-FIXThe Item net price (BT-146) shall NOT be negative.
The Item net price (BT-146) shall NOT be negative.. Review the `cbc:PriceAmount` element.
PEPPOL-COMMON-R040Peppol BIS 3.0INPUTGLN must have a valid format according to GS1 rules
GLN must have a valid format according to GS1 rules. This validation rule ensures Invoice compliance with Peppol BIS 3.0.
BR-63EN 16931INPUTBuyer electronic address is missing its scheme identifier
Your invoice includes a buyer electronic address (EndpointID), but it does not specify what type of identifier it is. The scheme identifier tells the receiving system whether the address is a GLN number, a VAT number, a chamber of commerce number, or another type. Without it, the Peppol network cannot route the invoice to the correct recipient.
BR-35peppol-bis-3INPUTCredit note must reference original invoice
Credit notes should reference the original invoice being credited.
BR-39peppol-bis-3INPUTItem identifier recommended
Line items should have an item identifier for matching and processing.
BR-40peppol-bis-3INPUTNote text should be meaningful
Invoice notes should provide useful information in an appropriate language.
BR-58en16931INPUTDocument charge must have reason
Document level charge must have reason code or text.
BR-59en16931INPUTAllowance base amount required when percentage used
If allowance/charge has percentage, base amount is mandatory.
BR-60en16931INPUTItem classification must have valid scheme
Commodity classification must have valid scheme identifier.
PEPPOL-INV-ITEM-IDPeppol BIS 3.0BLOCKEDItem identification SHOULD be provided for better interoperability
Item identification SHOULD be provided for better interoperability. This applies to the `cbc:ID` element in the invoice XML.
SE-R-003Peppol BIS 3.0AUTO-FIXSwedish organisation numbers should be numeric.
Swedish organization numbers must contain only numeric characters. No letters or special characters allowed.
PEPPOL-EN16931-R043Peppol BIS 3.0AUTO-FIXAllowance/charge ChargeIndicator value MUST equal "true" or "false"
The ChargeIndicator on one of your discounts or surcharges is not in the correct format. It must be exactly "true" (for a surcharge) or "false" (for a discount), in lowercase.
IN-PAYMENT-MEANS-CODESPeppol BIS 3.0BLOCKEDPayment means codes validation
Payment means codes should be from recommended UNCL4461 subset
UBL-SR-47EN 16931AUTO-FIXMultiple different payment methods on one invoice
Your invoice has multiple payment means sections with different payment method codes. The UBL standard requires that all payment means on a single invoice use the same payment method code.
PEPPOL-COMMON-R046Peppol BIS 3.0AUTO-FIXTax Code (Codice Fiscale) must be stated in the correct format
Italian Tax Code (Codice Fiscale) must follow the correct format. This validation applies to a different location in the invoice where tax codes appear.
PEPPOL-COMMON-R044Peppol BIS 3.0AUTO-FIXItalian office code (IPA) has wrong format
The Italian IPA code (Codice Univoco Unità Organizzativa) on your invoice is not in the correct format. It must be exactly 6 uppercase letters and/or digits.
BR-01EN 16931AUTO-FIXInvoice must have specification identifier
Every Peppol BIS invoice must include a specification identifier (CustomizationID) that indicates which profile the invoice conforms to.
BR-23EN 16931AUTO-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.
PEPPOL-EN16931-R008Peppol BIS 3.0AUTO-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.
BR-30EN 16931AUTO-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-51EN 16931AUTO-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.
UBL-SR-12EN 16931AUTO-FIXSeller VAT identifier shall occur maximum once
Your invoice contains multiple Seller VAT identifiers (PartyTaxScheme with VAT scheme). EN16931 allows only one VAT identifier per seller.
BR-05EN 16931AUTO-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.
PEPPOL-COMMON-R049Peppol BIS 3.0AUTO-FIXInvalid Swedish organization number
A Swedish organization number (organisationsnummer) in this invoice is not correctly formatted. Swedish org numbers must be exactly 10 digits and include a valid check digit calculated using the Luhn algorithm. This applies to any identifier using scheme 0007, including seller and buyer endpoint addresses, company registration numbers, and party identifiers.
BR-42EN 16931AUTO-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-AG-05EN 16931AUTO-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.
PEPPOL-EN16931-R101Peppol BIS 3.0AUTO-FIXInvoice line document reference has wrong type code
A document reference on one of your invoice lines uses the wrong type code. Line-level document references in Peppol invoices must use code "130", which means "invoice line object identifier".
BR-CL-13EN 16931AUTO-FIXInvalid product classification scheme
A line item's classification code uses an invalid scheme identifier. The classification listID must be from the UNTDID 7143 code list. Common valid schemes include STI for UNSPSC, EN for eCl@ss, and CPV for EU public procurement.
PEPPOL-COMMON-R041Peppol BIS 3.0AUTO-FIXNorwegian organization number MUST be stated in the correct format.
Norwegian organization numbers must follow the correct format. The organization number is a 9-digit identifier assigned by Brønnøysund Register Centre.
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→