errorformatinternal

FORMAT-001:Unrecognized invoice format

Fix: Re-export the file from your invoicing software as a UBL 2.1 or CII D16B e-invoice.

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

Severity
Fatal
Rule set
internal
Country
All EU
Fix type
BLOCKED
Category
format

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Cannot be auto-fixed. The file does not contain a recognized e-invoice structure (UBL Invoice, UBL CreditNote, or CII CrossIndustryInvoice). Re-export the document from your invoicing software in a supported format.

What is FORMAT-001?

FORMAT-001 is a fatal validation rule defined in the internal specification. It validates the The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules. element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

FORMAT-001 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

The file cannot be validated or submitted as an e-invoice. Peppol Access Points, government portals (like those requiring XRechnung or Factur-X), and automated invoice processing systems will reject it because they cannot identify it as an invoice.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: FORMAT-001
  • ·Specification: internal

How to Fix It

1.

Check the file type

Open the XML file in a text editor. Look at the very first element after the XML declaration. It should be <Invoice>, <CreditNote>, or <CrossIndustryInvoice> with the correct namespace.

2.

Re-export from your software

Go back to your invoicing or ERP software and export the document specifically as an e-invoice. Look for options like 'UBL 2.1', 'Peppol BIS 3.0', 'XRechnung', 'Factur-X', or 'ZUGFeRD'. Avoid generic XML exports.

3.

Validate again

Upload the re-exported file to verify it is now recognized as a valid e-invoice format.

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Triggers validation error -->
<The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.></The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.>
After
<!-- Corrected -->
<The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.>VALID_VALUE</The XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.>

Technical Reference

XPathThe XML root element does not match any known e-invoice namespace. Expected one of: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 (UBL Invoice), urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2 (UBL CreditNote), or urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100 (CII). The validator checks the root element and its namespace to determine the invoice format before applying business rules.
Specinternal
StrategyCannot be auto-fixed — the entire file structure is unrecognized. The invoice must be re-exported from the source system in a supported e-invoice format (UBL 2.1 or CII D16B).

Common Causes

  • ·The file is a different XML document type (e.g., purchase order, dispatch advice, catalogue)
  • ·The invoicing software exported a generic XML format instead of an e-invoice format
  • ·The file was exported as a PDF/A with embedded XML (Factur-X/ZUGFeRD) but only the PDF was uploaded
  • ·A custom or proprietary invoice format was used instead of UBL or CII
  • ·The file is a valid e-invoice but uses an unsupported older version of UBL or CII

Seeing this in production? The API handles FORMAT-001 automatically. See the fix response →

Commonly Seen In

Software that exports proprietary XML formats instead of standard e-invoice formatsOlder ERP systems without UBL 2.1 or CII D16B export capability

Frequently Asked Questions

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

Re-export the file from your invoicing software as a UBL 2.1 or CII D16B e-invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, FORMAT-001 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of FORMAT-001 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

FORMAT-001 is commonly seen in exports from Software that exports proprietary XML formats instead of standard e-invoice formats, Older ERP systems without UBL 2.1 or CII D16B export capability. These packages sometimes generate invoices that need adjustment.

Related Errors

FORMAT-002PDF must be PDF/A formatXML-001Invoice file is not well-formed XML

Related Content

Learn
Format Finder
Errors
Format Rules ErrorsDanish Chamber of Commerce P-Number Format Invalid

Last updated: 21 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for FORMAT-001

Detect FORMAT-001 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API