ApeX
The Business OS
Explore ApeX
UAE E-Invoicing Fundamentals/UAE E-Invoicing Requirements
9 min

Structured E-Invoice Requirements

Learn about the structured electronic formats required for UAE e-invoices and the Peppol BIS standard.

Structured E-Invoice Requirements

The UAE e-invoicing framework requires invoices to be in a structured electronic format — not PDFs, scans, or free-form documents. Understanding these format requirements is essential for compliance.

What is a structured e-invoice?

A structured e-invoice is an electronic document in a standardised, machine-readable format that:

  • Contains invoice data in defined fields (not free text)
  • Follows a published data model and schema
  • Can be automatically validated, processed, and stored by software
  • Is transmitted through a secure, authenticated network

Common structured formats

UBL (Universal Business Language)

  • International standard for electronic business documents
  • XML-based format defined by OASIS
  • Widely used in Peppol and government e-invoicing systems
  • Version 2.1 is the current standard in Peppol BIS

Peppol BIS (Business Interoperability Specifications)

  • The specific profile of UBL used in the Peppol network
  • Defines which fields are mandatory, optional, and conditional
  • Includes business rules and validation constraints
  • Peppol BIS Billing 3.0 is the current standard

EDIFACT

  • Older standard used in some industries (retail, logistics)
  • Less common in modern e-invoicing frameworks
  • May be supported for legacy system compatibility

The Peppol BIS structure

A Peppol BIS invoice (based on UBL 2.1) contains three main sections:

1. Header (Invoice level data)

  • Invoice number and issue date
  • Seller (supplier) details — name, address, TRN, contact
  • Buyer (customer) details — name, address, TRN, contact
  • Payment terms and due date
  • Currency
  • Tax details (total tax, taxable amount per rate)

2. Lines (Item level data)

  • Line number
  • Item description and identifier
  • Quantity and unit of measure
  • Unit price
  • Line total
  • Tax rate and tax amount per line
  • Discount/charge information per line

3. Summary (Totals)

  • Total line amount
  • Total allowances (discounts)
  • Total charges
  • Total taxable amount per tax rate
  • Total tax amount
  • Total amount due

Data validation

Structured e-invoices are validated against:

  • Schema validation — The XML must conform to the UBL schema
  • Business rules — Peppol BIS defines specific rules (e.g., tax rate must be valid, dates must be logical)
  • UAE-specific rules — The UAE may add additional validation rules (e.g., TRN format, specific fields for UAE VAT)

If an invoice fails validation, it is rejected and must be corrected before transmission.

Digital signatures and integrity

E-invoices may require:

  • Digital signatures — To ensure authenticity and non-repudiation
  • Timestamps — To prove the invoice was issued at a specific date/time
  • Hash values — To detect any alteration after issuance
  • Certificates — Issued by accredited certificate authorities

Format requirements summary

| Requirement | Description | |---|---| | Format | UBL 2.1 (Peppol BIS Billing 3.0) | | Transmission | Peppol network via certified Access Point | | Validation | Schema + business rules + UAE-specific rules | | Integrity | Digital signature, timestamp, hash | | Archiving | Electronic, tamper-evident, for 5+ years |

Draft note: Specific format requirements, validation rules, and signature requirements for the UAE will be confirmed by FTA technical guidance. The information above is based on Peppol BIS standards and international e-invoicing best practices. Always verify against current official UAE specifications.

Practical UAE example

**Scenario: What a structured e-invoice looks like** A Dubai company sells consulting services to an Abu Dhabi client for AED 10,000 + 5% VAT. **In PDF format (current, non-structured):** The company creates a PDF with the invoice details and emails it. The buyer's accountant reads the PDF and manually enters the data into their accounting system. **In Peppol BIS format (structured e-invoice):** The company's ERP system generates an XML file containing: ```xml <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"> <cbc:ID>INV-2026-001</cbc:ID> <cbc:IssueDate>2026-10-06</cbc:IssueDate> <cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode> <cac:AccountingSupplierParty> <cac:Party> <cac:PartyName><cbc:Name>Consulting Co LLC</cbc:Name></cac:PartyName> <cac:PartyTaxScheme> <cbc:CompanyID>100123456700003</cbc:CompanyID> <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme> </cac:PartyTaxScheme> </cac:Party> </cac:AccountingSupplierParty> <cac:AccountingCustomerParty>...</cac:AccountingCustomerParty> <cac:InvoiceLine> <cbc:ID>1</cbc:ID> <cbc:InvoicedQuantity>1</cbc:InvoicedQuantity> <cbc:LineExtensionAmount>10000.00</cbc:LineExtensionAmount> <cac:Item> <cbc:Description>Management consulting services</cbc:Description> </cac:Item> <cac:TaxTotal> <cbc:TaxAmount>500.00</cbc:TaxAmount> <cbc:TaxAmount currencyID="AED">500.00</cbc:TaxAmount> </cac:TaxTotal> </cac:InvoiceLine> <cac:TaxTotal> <cbc:TaxAmount>500.00</cbc:TaxAmount> <cbc:TaxableAmount>10000.00</cbc:TaxableAmount> <cac:TaxSubtotal> <cbc:TaxableAmount>10000.00</cbc:TaxableAmount> <cbc:TaxAmount>500.00</cbc:TaxAmount> <cac:TaxCategory><cbc:Percent>5</cbc:Percent></cac:TaxCategory> </cac:TaxSubtotal> </cac:TaxTotal> <cac:LegalMonetaryTotal> <cbc:TaxInclusiveAmount>10500.00</cbc:TaxInclusiveAmount> <cbc:PayableAmount>10500.00</cbc:PayableAmount> </cac:LegalMonetaryTotal> </Invoice> ``` This XML is transmitted through the Peppol network. The buyer's system receives it, automatically validates it, and processes it without any manual data entry.

Key takeaways

  • Structured e-invoices use machine-readable formats like UBL, not PDFs or scans.
  • Peppol BIS Billing 3.0 (based on UBL 2.1) is the expected standard for UAE e-invoicing.
  • Structured invoices contain header, line, and summary sections with defined fields.
  • Invoices are validated against schema, business rules, and UAE-specific requirements.
  • Digital signatures and timestamps ensure authenticity and integrity.

Authoritative sources

UAE National E-Invoicing Framework (Peppol Network Adoption)

UAE Federal Tax Authority (FTA) / Ministry of Finance · E-Invoicing Implementation Guidance

Effective: 1 Jan 2025Verified: 6 Oct 2026View source

Federal Decree-Law No. 8 of 2017 on Value Added Tax

UAE Federal Tax Authority (FTA) · Article 66 — Tax Invoices and Tax Credit Notes

Effective: 1 Jan 2018Verified: 6 Oct 2026View source
Knowledge check

1. Which format is expected to be the standard for UAE e-invoicing?

2. What are the three main sections of a Peppol BIS invoice?

Sign in to save your progress.

PreviousNext lesson

This lesson is general educational content, not individualized tax or legal advice. Always consult a qualified professional for your specific situation.