Choose invoice XML
Select a self-contained UTF-8 UBL 2.1 Invoice file up to 2 MB.
Open UBL invoice XML locally. Review seller, buyer, line items, tax fields and totals, then export Excel, CSV or JSON without uploading your invoice.
UBL 2.1 Invoice XML. PDF containers, Factur-X/ZUGFeRD, CII and credit notes are not supported in this milestone.
Select a self-contained UTF-8 UBL 2.1 Invoice file up to 2 MB.
Review parties, dates, payment information, line items, taxes and stated totals.
Download all tables as Excel, invoice lines as CSV or the normalized model as JSON.
Read the business fields without navigating XML tags.
Check quantities, unit prices, allowances and tax categories against the source.
Export source values for your own review and reconciliation.
The details that matter before you use E-Invoice Viewer.
This milestone reads UBL 2.1 Invoice XML only. It does not claim verified Peppol or XRechnung profile support or compliance. CII invoices, credit notes, PDF containers and unsupported versions are rejected.
No. Those hybrid formats need PDF attachment extraction and CII parsing, which are outside this milestone. Renaming a PDF to XML does not make it supported.
It checks XML safety, supported structure and required business fields. It does not run XSD or Schematron, verify signatures, validate tax treatment or check payment accounts.
No. Source decimal strings are retained exactly. Missing and invalid fields remain distinct in JSON; missing table values are blank. No line tax, gross amount or exchange rate is invented.
Excel includes invoice lines, document totals, taxes, allowances and charges, and payment details. CSV includes line items only. JSON includes normalized parties, addresses and field states. XLSX cells are text; CSV formula prefixes are neutralized.
No. XML parsing and export run in your browser. Files, names, invoice text, amounts and payment information do not enter analytics or the control database.
Use UTF-8 XML up to 2 MB, with at most 2,000 invoice lines, 30,000 XML elements and 64 levels of nesting. DTD, entity definitions and external inclusions are rejected.