What Is XML Invoicing? A Plain-Language Guide with Examples

An XML invoice is an electronic invoice where every data field is stored in structured, machine-readable tags. Unlike a PDF that is designed for human eyes, an XML invoice is designed for software. It can be read, validated, and processed automatically by any accounting system, ERP, or tax authority. If you have heard the terms "e-invoicing," "UBL," or "Peppol" and wondered what ties them all together, the answer is XML.

1. What is XML?

XML stands for Extensible Markup Language. It is a text-based format that stores data inside descriptive tags. Each tag tells you what the data means. For example, <InvoiceDate>2026-03-01</InvoiceDate> is immediately clear: this is the invoice date, and its value is March 1, 2026.

XML was designed to be both human-readable and machine-readable. You can open an XML file in any text editor and understand its contents. But the real power is that software can parse and process XML automatically. No OCR, no data entry, no copy-pasting between systems.

XML is platform-independent. It works on Windows, Mac, Linux, in web applications, desktop software, and mobile apps. This universality is exactly why it was chosen as the foundation for European e-invoicing standards.

2. XML vs. PDF vs. EDI

Not all electronic invoices are created equal. There are three main categories of invoice transmission, and understanding the differences matters for compliance and efficiency.

The key distinction is structured vs. unstructured. A PDF looks like an invoice, but to a computer it is just a picture of text. It has no idea which number is the total, which is the VAT, or which is the invoice number. An XML file labels every piece of data explicitly. That is why regulators across Europe require structured formats for B2B e-invoicing.

3. Why businesses use XML invoicing

XML invoicing is not just a regulatory checkbox. It delivers real operational benefits that compound as your invoice volume grows.

4. What an XML invoice looks like (real example)

Here is a simplified e-invoicing sample in UBL XML format. This is the actual structure that gets transmitted over the Peppol network when a Belgian company sends an invoice.

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">

  <!-- Header: who, what, when -->
  <cbc:ID>INV-2026-0042</cbc:ID>
  <cbc:IssueDate>2026-03-01</cbc:IssueDate>
  <cbc:DueDate>2026-03-31</cbc:DueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>

  <!-- Seller -->
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0208">0123456789</cbc:EndpointID>
      <cac:PartyName>
        <cbc:Name>Webbureau Leuven BVBA</cbc:Name>
      </cac:PartyName>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>BE0123456789</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
    </cac:Party>
  </cac:AccountingSupplierParty>

  <!-- Buyer -->
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0208">0987654321</cbc:EndpointID>
      <cac:PartyName>
        <cbc:Name>Bakkerij Peeters NV</cbc:Name>
      </cac:PartyName>
    </cac:Party>
  </cac:AccountingCustomerParty>

  <!-- Line item -->
  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:InvoicedQuantity unitCode="HUR">40</cbc:InvoicedQuantity>
    <cbc:LineExtensionAmount currencyID="EUR">3200.00</cbc:LineExtensionAmount>
    <cac:Item>
      <cbc:Name>Website redesign</cbc:Name>
      <cac:ClassifiedTaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>21</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:ClassifiedTaxCategory>
    </cac:Item>
    <cac:Price>
      <cbc:PriceAmount currencyID="EUR">80.00</cbc:PriceAmount>
    </cac:Price>
  </cac:InvoiceLine>

  <!-- Totals -->
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="EUR">672.00</cbc:TaxAmount>
  </cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:TaxExclusiveAmount currencyID="EUR">3200.00</cbc:TaxExclusiveAmount>
    <cbc:TaxInclusiveAmount currencyID="EUR">3872.00</cbc:TaxInclusiveAmount>
    <cbc:PayableAmount currencyID="EUR">3872.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>

</Invoice>

Let's break down what makes this efficient XML:

• Every field is labeled. The tag <cbc:Name> tells software "this is a name." No guessing, no pattern matching.
• Data types are explicit. Amounts include a currencyID attribute. Quantities include a unitCode. No ambiguity.
• Structure is hierarchical. The invoice contains parties, which contain names and tax schemes. Line items contain items, which contain tax categories. This nesting makes relationships clear.
• It is self-describing. You can open this file in a text editor and understand what it says, even without knowing UBL.

For a deeper look at every section of a UBL invoice, read our complete UBL format guide.

5. Common XML invoice formats

Not all XML invoices use the same schema. Several standards exist, each designed for different networks and regions.

6. How XML invoicing works in practice

You do not need to create XML files manually. Here is how the process works for most businesses.

The entire process takes seconds. The recipient gets a machine-readable invoice that can be booked automatically. No scanning, no OCR, no manual data entry on either side.

7. Hybrid invoicing: XML inside PDF

Some formats combine the best of both worlds. ZUGFeRD (Germany) and Factur-X (France) are hybrid formats that embed a CII XML file inside a PDF/A-3 document. When you open the file, you see a normal-looking PDF invoice. But inside the PDF, there is a hidden XML attachment with all the structured data. Use our ZUGFeRD XML Extractor to extract and view the embedded XML from any ZUGFeRD or Factur-X PDF.

This approach works well for the transition period: recipients who have modern software can extract and process the XML data automatically. Recipients who don't can still open the PDF and read it like a traditional invoice.

However, hybrid formats are not universally accepted. Belgium and most countries adopting Peppol require pure UBL XML delivered via the Peppol network. A ZUGFeRD PDF sent by email does not meet the Belgian e-invoicing mandate.

8. How to get started

You have two paths depending on your setup.

Either way, you never have to write XML yourself. Read our API integration guide for code examples, or check the Peppol registration guide to get started in 10 minutes.

9. Frequently asked questions