Format Rules Errors
Data format validation errors for fields like dates, amounts, identifiers, and codes that must follow specific patterns.
100 errors documented
UBL-CR-077UBL 2.1AUTO-FIXA UBL invoice should not include the StatementDocumentReference
Your invoice contains StatementDocumentReference which is not allowed in EN16931 invoices. Statement references are not supported.
UBL-CR-470UBL 2.1AUTO-FIXA UBL invoice should not include the PrepaidPayment
Your invoice contains a PrepaidPayment element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-491UBL 2.1AUTO-FIXA UBL invoice should not include the PricingExchangeRate
Your invoice contains a PricingExchangeRate element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-079UBL 2.1AUTO-FIXA UBL invoice should not include the OriginatorDocumentReference UUID
Your invoice contains OriginatorDocumentReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-017UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference UUID
Your invoice contains OrderReference/UUID which is not allowed in EN16931 invoices.
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.
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.
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.
IN-ALLOWANCE-AMOUNT-REQUIREDpeppol-bis-3INPUTAllowance/Charge amount required
AllowanceCharge elements must have an Amount element specified.
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.
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.
FORMAT-002factur-xBLOCKEDPDF must be PDF/A format
Factur-X requires PDF/A-3 base document.
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.
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.
UBL-SR-24EN16931CONFIRMDeliver to information shall occur maximum once
Your invoice contains multiple Delivery location elements. EN16931 allows only one Delivery element per invoice.
UBL-SR-26EN16931CONFIRMPayment reference shall occur maximum once
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
UBL-SR-27EN16931AUTO-FIXPayment means text shall occur maximum once
Your invoice contains multiple Payment means text elements (PaymentMeans/InstructionNote). EN16931 allows only one instruction note.
UBL-SR-28EN16931AUTO-FIXMandate reference identifier shall occur maximum once
Your invoice contains multiple Mandate reference identifiers (PaymentMandate/ID). EN16931 allows only one direct debit mandate reference.
UBL-SR-29EN16931CONFIRMBank creditor reference shall occur maximum once
Your invoice contains multiple Bank creditor reference elements (PaymentMeans/PayeeFinancialAccount/ID with creditor reference). EN16931 allows only one.
UBL-SR-31EN16931CONFIRMDocument level charge reason shall occur maximum once
Your invoice contains multiple Document level charge reason texts (AllowanceCharge/AllowanceChargeReason). EN16931 allows only one reason per charge.
UBL-CR-353UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation CountrySubentity
Your invoice contains a DeliveryLocation CountrySubentity element which is not allowed in EN16931 invoices. This element must be removed.
UBL-SR-32EN16931CONFIRMVAT exemption reason text shall occur maximum once
Your invoice contains multiple VAT exemption reason texts (TaxCategory/TaxExemptionReason). EN16931 allows only one exemption reason per VAT category.
UBL-CR-016UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference CopyIndicator
Your invoice contains OrderReference/CopyIndicator which is not allowed in EN16931 invoices.
IN-PAYABLE-POSITIVEpeppol-bis-3BLOCKEDPayable amount should be positive
The amount due for payment (PayableAmount) should typically be a positive value.
UBL-CR-356UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation InformationURI
Your invoice contains a DeliveryLocation InformationURI element which is not allowed in EN16931 invoices. This element must be removed.
UBL-SR-33EN16931CONFIRMSupporting document description shall occur maximum once
Your invoice contains multiple Supporting document description elements (AdditionalDocumentReference/DocumentDescription). EN16931 allows only one description per document.
IN-TAX-TOTAL-AMOUNTpeppol-bis-3INPUTTax total amount required
Invoice must have a total VAT amount in the TaxTotal element.
IN-PRICE-POSITIVEpeppol-bis-3BLOCKEDItem price should be positive
Item price (PriceAmount) should typically be a positive value.
IN-QUANTITY-POSITIVEpeppol-bis-3BLOCKEDLine quantity should be positive
Invoice line quantity (InvoicedQuantity) should typically be a positive value.
UBL-SR-34EN16931CONFIRMInvoice line note shall occur maximum once
Your invoice line contains multiple Note elements (InvoiceLine/Note). EN16931 allows only one note per invoice line.
UBL-SR-35EN16931CONFIRMReferenced purchase order line identifier shall occur maximum once
Your invoice line contains multiple Referenced purchase order line identifiers (OrderLineReference/LineID). EN16931 allows only one per line.
UBL-CR-020UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference CustomerReference
Your invoice contains OrderReference/CustomerReference which is not allowed in EN16931 invoices.
UBL-SR-36EN16931CONFIRMInvoice line period shall occur maximum once
Your invoice line contains multiple Invoice line period elements (InvoiceLine/InvoicePeriod). EN16931 allows only one period per line.
UBL-SR-39EN16931CONFIRMProject reference shall occur maximum once.
Your invoice contains multiple Project reference elements (ProjectReference/ID). EN16931 allows only one project reference per invoice.
UBL-CR-357UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation Name
Your invoice contains a DeliveryLocation Name element which is not allowed in EN16931 invoices. This element must be removed.
UBL-SR-40EN16931CONFIRMBuyer trade name shall occur maximum once
Your invoice contains multiple Buyer trade name elements (AccountingCustomerParty/Party/PartyName). EN16931 allows only one buyer trading name.
UBL-SR-42EN16931CONFIRMParty tax scheme shall occur maximum twice in accounting supplier party
Your seller party (AccountingSupplierParty) contains more than two PartyTaxScheme elements. EN16931 allows maximum two (one VAT scheme and optionally one other tax scheme).
UBL-SR-43EN16931CONFIRMScheme identifier shall only be used for invoiced object (document type code with value 130 or 50)
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). Scheme identifiers are only valid for these document types.
UBL-CR-028UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference Xpath
Your invoice contains BillingReference/Xpath which is not allowed in EN16931 invoices.
UBL-SR-45EN16931CONFIRMDue Date shall occur maximum once
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
UBL-CR-111UBL 2.1AUTO-FIXA UBL invoice should not include the AdditionalDocumentReference UUID
Your invoice contains AdditionalDocumentReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-034UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference Attachment
Your invoice contains BillingReference/Attachment which is not allowed. Attachments belong in AdditionalDocumentReference, not BillingReference.
UBL-CR-358UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation ValidityPeriod
Your invoice contains a DeliveryLocation ValidityPeriod element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-036UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference IssuerParty
Your invoice contains BillingReference/IssuerParty which is not allowed in EN16931 invoices.
PEPPOL-EN16931-CL006PEPPOL_BISBLOCKEDInvoice period description code must be according to UNCL 2005 D.16B.
The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).
UBL-CR-037UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference ResultOfVerification
Your invoice contains BillingReference/ResultOfVerification which is not allowed in EN16931 invoices.
UBL-CR-038UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference...
Your invoice contains BillingReference/SelfBilledInvoiceDocumentReference which is not allowed in EN16931 invoices.
UBL-SR-15EN16931CONFIRMBuyer name shall occur maximum once
Your invoice contains multiple Buyer name elements (AccountingCustomerParty/Party/PartyName/Name). EN16931 allows only one buyer name.
UBL-CR-040UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference...
Your invoice contains BillingReference/SelfBilledCreditNoteDocumentReference which is not allowed in EN16931 invoices.
UBL-CR-041UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference DebitNoteDocumentReference
Your invoice contains BillingReference/DebitNoteDocumentReference which is not allowed in EN16931 invoices.
UBL-DT-12EN16931BLOCKEDFormat attribute should not be present
Your invoice contains the format attribute on an element. This attribute is not allowed in EN16931 and must be removed.
UBL-SR-49EN16931CONFIRMValue tax point date shall occur maximum once
Your invoice contains multiple Value tax point date elements (TaxPointDate). EN16931 allows only one tax point date per invoice.
UBL-DT-19EN16931BLOCKEDLanguage identifier attribute should not be present
Your invoice contains the languageID attribute on a text element. This attribute is not allowed in EN16931 and must be removed.
UBL-CR-046UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference UUID
Your invoice contains DespatchDocumentReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-622UBL 2.1AUTO-FIXA UBL invoice should not include the InvoiceLine Item ItemInstance
UBL 2.1 Invoice schema does not include `cac:Item/cac:ItemInstance`. This element must be removed for EN 16931 compliance.
UBL-SR-50EN16931CONFIRMItem description shall occur maximum once
Your invoice line Item contains multiple Description elements. EN16931 allows only one item description per line.
UBL-SR-51EN16931CONFIRMAn address can only have one third line.
Duplicate address line 3. An address can have at most one additional address line (third line).
UBL-CR-006UBL 2.1AUTO-FIXDisallowed element: cbc:IssueTime
UBL 2.1 Invoice schema does not include `cbc:IssueTime`. This element must be removed for EN 16931 compliance.
UBL-SR-52EN16931CONFIRMDocument reference shall occur maximum once
Duplicate document reference. Document reference can only appear once in the specified context.
UBL-CR-019UBL 2.1AUTO-FIXA UBL invoice should not include the OrderReference IssueTime
Your invoice contains OrderReference/IssueTime which is not allowed in EN16931 invoices.
UBL-CR-048UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference IssueTime
Your invoice contains DespatchDocumentReference/IssueTime which is not allowed in EN16931 invoices.
FORMAT-001internalBLOCKEDUnrecognized invoice format
Your file was read successfully as XML, but it does not contain a recognized e-invoice structure. Supported formats are UBL 2.1 Invoice, UBL 2.1 CreditNote, and UN/CEFACT Cross-Industry Invoice (CII D16B). The file may have been exported in the wrong format, or it may be a different type of XML document (such as an order or dispatch advice).
UBL-CR-411UBL 2.1AUTO-FIXA UBL invoice should not include the PaymentMeans ID
Your invoice contains a PaymentMeans ID element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-023UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference CopyIndicator
Your invoice contains BillingReference/CopyIndicator which is not allowed in EN16931 invoices.
UBL-CR-053UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference LocaleCode
Your invoice contains DespatchDocumentReference/LocaleCode which is not allowed in EN16931 invoices.
UBL-CR-054UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference VersionID
Your invoice contains DespatchDocumentReference/VersionID which is not allowed in EN16931 invoices.
UBL-CR-055UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference...
Your invoice contains DespatchDocumentReference/DocumentStatusCode which is not allowed in EN16931 invoices.
UBL-CR-057UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference Attachment
Your invoice contains DespatchDocumentReference/Attachment which is not allowed. Attachments belong in AdditionalDocumentReference.
UBL-CR-024UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference UUID
Your invoice contains BillingReference/UUID which is not allowed in EN16931 invoices.
UBL-CR-009UBL 2.1AUTO-FIXDisallowed element: cbc:PaymentAlternativeCurrencyCode
UBL 2.1 Invoice schema does not include `cbc:PaymentAlternativeCurrencyCode`. This element must be removed for EN 16931 compliance.
UBL-CR-058UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference ValidityPeriod
Your invoice contains DespatchDocumentReference/ValidityPeriod which is not allowed in EN16931 invoices.
UBL-CR-060UBL 2.1AUTO-FIXA UBL invoice should not include the DespatchDocumentReference...
Your invoice contains DespatchDocumentReference/ResultOfVerification which is not allowed in EN16931 invoices.
PEPPOL-EN16931-CL007PEPPOL_BISBLOCKEDCurrency code must be according to ISO 4217:2005
Currency codes must be valid ISO 4217:2005 codes. Only standard 3-letter currency codes like EUR, USD, GBP are accepted.
UBL-CR-011UBL 2.1AUTO-FIXA UBL invoice should not include the LineCountNumeric
Your invoice contains LineCountNumeric which is not allowed in EN16931 invoices.
UBL-CR-359UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery DeliveryLocation Address ID
Your invoice contains a DeliveryLocation Address ID element which is not allowed in EN16931 invoices. This element must be removed.
UBL-CR-385UBL 2.1AUTO-FIXA UBL invoice should not include the Delivery CarrierParty
Your invoice contains a CarrierParty element which is not allowed in EN16931 invoices. This element must be removed.
PEPPOL-EN16931-CL002PEPPOL_BISAUTO-FIXReason code MUST be according to subset of UNCL 5189 D.16B.
The allowance reason code must be from the UNCL 5189 D.16B subset. This code explains why a discount or allowance is being applied.
PEPPOL-EN16931-CL003PEPPOL_BISAUTO-FIXReason code MUST be according to UNCL 7161 D.16B.
The charge reason code must be from the UNCL 7161 D.16B list. This code explains why a surcharge or additional charge is being applied.
UBL-DT-01EN16931AUTO-FIXAmounts shall be decimal up to two fraction digits
Your invoice contains amount values with more than 2 decimal places. EN16931 requires all monetary amounts to have maximum 2 decimal digits (e.g., 100.00 not 100.001).
UBL-SR-18EN16931CONFIRMBuyer VAT identifier shall occur maximum once
Your invoice contains multiple Buyer VAT identifiers (PartyTaxScheme with VAT scheme). EN16931 allows only one VAT identifier per buyer.
UBL-CR-025UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference IssueTime
Your invoice contains BillingReference/IssueTime which is not allowed in EN16931 invoices.
UBL-CR-412EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans PaymentDueDate
Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.
UBL-CR-027UBL 2.1AUTO-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-029UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference LanguageID
Your invoice contains BillingReference/LanguageID which is not allowed in EN16931 invoices.
UBL-CR-031UBL 2.1AUTO-FIXA UBL invoice should not include the BillingReference VersionID
Your invoice contains BillingReference/VersionID which is not allowed in EN16931 invoices.
UBL-CR-665EN16931AUTO-FIXA UBL invoice should not include the AdditionalDocumentReference ID schemeID unless the DocumentTypeCode equals '130'
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-CR-680EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans/PayerFinancialAccount
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-CR-681EN16931AUTO-FIXA UBL invoice should not include the PaymentMeans InstructionNote
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-CR-682EN16931AUTO-FIXA UBL invoice should not include the Delivery DeliveryAddress
This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.
UBL-DT-08EN16931BLOCKEDScheme name attribute should not be present
Your invoice contains the schemeName attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-09EN16931BLOCKEDScheme agency name attribute should not be present
Your invoice contains the schemeAgencyName attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-10EN16931BLOCKEDScheme data uri attribute should not be present
Your invoice contains the schemeDataURI attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-11EN16931BLOCKEDScheme uri attribute should not be present
Your invoice contains the schemeURI attribute on an identifier element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-13EN16931BLOCKEDUnit code list identifier attribute should not be present
Your invoice contains the unitCodeListID attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-14EN16931BLOCKEDUnit code list agency identifier attribute should not be present
Your invoice contains the unitCodeListAgencyID attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-15EN16931BLOCKEDUnit code list agency name attribute should not be present
Your invoice contains the unitCodeListAgencyName attribute on a quantity element. This attribute is not allowed in EN16931 and must be removed.
UBL-DT-16EN16931BLOCKEDList agency name attribute should not be present
Your invoice contains the listAgencyName attribute on a code element. This attribute is not allowed in EN16931 and must be removed.
Handle Format Rules Errors in Your Pipeline
The compliance engine auto-remediates format rules errors with controlled safety policies.
Get API Access