What is an XML invoice and why is it the foundation of e-invoicing standards?
An XML (eXtensible Markup Language) invoice is an invoice encoded in XML format, a structured text format readable by both humans and machines. XML enables machine processing of invoice data without manual data entry, supporting automated matching, validation, and posting. Major e-invoicing standards use XML: UBL, CII (UN/CEFACT Cross-Industry Invoice), FatturaPA (Italy), CFDI (Mexico), NF-e (Brazil), and XRechnung (Germany) are all XML-based formats.
Why are XML invoices preferred over PDF invoices for compliance?
XML invoices vs PDF invoices: (1) Machinability: XML fields are directly processable by software; PDF text must be extracted via OCR with error risk; (2) Validation: XML can be validated against schema and business rules automatically; PDF cannot be automatically validated; (3) Automated matching: XML structured fields enable automatic PO matching without manual keying; (4) Tax authority reporting: XML invoice data submitted directly to CTC platforms; PDF cannot be submitted as structured data; (5) Archiving integrity: XML file integrity verifiable by hash; PDF may be embedded as part of hybrid format (Factur-X).
Frequently Asked Questions
- What is the difference between UBL and CII XML formats?
- UBL (Universal Business Language, OASIS standard) and CII (Cross-Industry Invoice, UN/CEFACT standard) are two different XML structures for representing invoice data. Both satisfy EN 16931 data requirements but use different element names and structures. Peppol BIS Billing 3.0 supports both UBL and CII. Factur-X uses CII as its embedded XML. XRechnung Germany supports both. They are not directly interchangeable but can be converted by a mapping layer. Most European e-invoicing implementations prefer UBL; some industries and applications prefer CII.
- Can businesses submit XML invoices directly to tax authorities without a PDP or access point?
- It depends on the jurisdiction. Italy's SDI accepts direct XML submission via web service or certified email without requiring an intermediary. Brazil's SEFAZ has a web portal for manual NF-e submission. France requires routing through a PDP or the PPF for B2B mandate compliance. ZATCA in Saudi Arabia requires an accredited software (CSID-registered) for submission. For most production volumes, direct integration is impractical without automation; access point providers and compliance platforms provide the technical infrastructure for high-volume submission.