OASIS UBL 2.1 Invoice
A widely used XML syntax for invoices, credit notes and related business documents. National and network profiles constrain the broad UBL schema.
Current version and implementation status
How to recognize the profile
Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.
- urn:oasis:names:specification:ubl:schema:xsd:Invoice-2
- cac:AccountingSupplierParty
- cbc:CustomizationID
Production validation stack
- 1Well-formed XML
Confirm that the document is well formed and structurally compatible with the intended UBL 2.1 syntax.
- 2UBL XSD
Apply semantic and business-rule checks rather than accepting a file merely because it parses.
- 3Profile Schematron
Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.
- 4Country-specific business rules
Apply the national, network or authority restrictions that narrow the base syntax.
Common errors and corrective action
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Countries using or referencing this profile
Questions people ask
What is UBL 2.1?
A widely used XML syntax for invoices, credit notes and related business documents. National and network profiles constrain the broad UBL schema.
How is UBL 2.1 validated?
A production check normally applies Well-formed XML, UBL XSD, Profile Schematron, Country-specific business rules. Local browser preflight cannot replace the official validation artefacts or authority outcome.
Which version should I use?
The current research note is: UBL 2.1 invoice syntax. Confirm release notes at the official source before production deployment.
Inspect and prepare UBL 2.1 files
Invoice format detector
Identify common XML, JSON and national electronic invoice signatures.
Structured invoice viewer
Read supplier, buyer, dates, currency, totals and line items.
Structured invoice draft generator
Create a browser-side UBL XML or JSON draft for testing, mapping and implementation work.
Invoice XML formatter and syntax checker
Format, minify and review well-formed invoice XML locally before deeper profile validation.