Invocie

Tech

UBL 2.1 sade bir dille: modern e-faturalamanın arkasındaki XML standardı

Dünyadaki neredeyse her büyük e-fatura zorunluluğu arka planda UBL 2.1 üretir. Gerçekten anlamanız gereken parçaların jargon içermeyen bir gezintisi.

Invocie Team · 21 Ocak 2026 · 5 dk okuma


UBL — Universal Business Language — is the OASIS standard underpinning Peppol BIS, EN 16931, ZATCA Phase-2, the UAE's PINT profile, India's IRP/e-invoice schema (with extensions), and several LATAM regimes. If your e-invoicing strategy doesn't make peace with UBL 2.1, you're going to be re-implementing the same XML over and over.

The shape of an UBL invoice

An UBL invoice is an XML document with three main namespaces: cbc (Common Basic Components — primitive types like ID and Amount), cac (Common Aggregate Components — complex types like Party and TaxTotal), and the document namespace itself. Every UBL document follows the same pattern:

<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">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
  <cbc:ID>INV-2026-0001</cbc:ID>
  <cbc:IssueDate>2026-01-15</cbc:IssueDate>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
  <cac:AccountingSupplierParty>...</cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>...</cac:AccountingCustomerParty>
  <cac:TaxTotal>...</cac:TaxTotal>
  <cac:LegalMonetaryTotal>...</cac:LegalMonetaryTotal>
  <cac:InvoiceLine>...</cac:InvoiceLine>
</Invoice>

Five concepts that are almost always wrong

  1. TaxTotal vs. LegalMonetaryTotal. The former breaks tax down by rate. The latter is the consolidated payable amount. Don't confuse them.
  2. AllowanceCharge can be either a discount or a surcharge — controlled by ChargeIndicator (false = allowance, true = charge). Wrong indicator → wrong total.
  3. Endpoint IDs need a scheme attribute (schemeID="0088" etc.). Without it, validators give cryptic errors about missing identifiers.
  4. Quantities use a unit code from UN/CEFACT (EA = each, KGM = kilogram, HUR = hour). "piece" is not a valid value.
  5. TaxCategory codes are UNCL5305: S = standard rate, Z = zero rate, E = exempt, AE = reverse charge. Don't invent new codes.

Invocie's EUStrategy emits UBL 2.1 conforming to BIS Billing 3.0 — same XML works for Peppol APs, the UAE PINT profile, and any system that consumes EN 16931.


İlgili okumalar

Kurcalamaya dayanıklı denetim izleri için hash zincirleri

ZATCA bunları zorunlu kılar, AB denetçileri bunlara bayılır ve uygulaması ucuzdur. Zincirlenmiş SHA-256'nın bir fatura defterini, bütünlüğünü kanıtlayabileceğiniz bir şeye nasıl dönüştürdüğüne bakalım.

Çok-bölgeli bir e-fatura API'si tasarlamak: cepheden dersler

Hem clearance hem post-audit ülkelerine hizmet eden bir altyapı kuruyorsanız, soyutlamaları doğru kurmak için tek şansınız var. İşte zor yoldan öğrendiklerimiz.

Integrating UAE E-Invoicing With Your ERP: A Technical Guide

A technical walkthrough for the Head of IT and ERP transformation lead: how UAE PINT maps onto SAP, Oracle, Microsoft Dynamics, and custom ERPs, the data you must clean first, and the integration patterns that survive production.

Her pazarda uyumlu fatura gönderin

ZATCA, FTA, Peppol ve küresel post-audit — tek bir API.

Ekibimizle konuşun