← Back to Business File Tools

UBL Viewer for Peppol and UBL 2.1 invoices

Use this UBL viewer to turn a Peppol or UBL 2.1 invoice XML file into a readable summary with the fields people normally need first.

Reviewed by Ronan. Built for first-pass invoice reading before accounting, ERP, or validator handoff.

Drop a UBL or Peppol XML invoice here, or choose a file.

The viewer extracts a compact summary, then lists the line items and shows a raw XML preview for verification.

No file selected

Waiting for an XML file.

Upload a UBL or Peppol XML invoice to see the key invoice fields.
Line items will appear here after parsing.

Raw XML preview

Raw XML preview will appear here.

How to use this page

Use the viewer after you already know the file is structured XML or after the detector tells you the file looks like UBL or another invoice XML family. The goal is to make the invoice readable fast, not to replace ERP or accounting software.

What the summary is for

The summary is built for first-pass review. It helps answer questions such as who sent the invoice, who should pay it, what dates matter, what the payable total is, and how many line items exist before you hand the file off to another system.

What this page is good for

Use it when a supplier sends XML and you want to confirm the invoice number, dates, supplier, buyer, totals, and line items without digging through raw tags. If users search for a UBL viewer or a UBL 2.1 viewer, this is the exact first-pass reading tool.

If the XML structure is unusual, the raw preview still gives you the full file for manual checking.

What to verify first

Start with supplier identity, buyer identity, invoice number, issue date, payable total, and currency. Those fields usually tell you fastest whether the file matches the expected business document.

Then check line items and tax values before moving the file into payment or ERP workflows.

Typical review workflow

A practical sequence is: detect the file family, open it here for readable review, compare the summary against the raw XML if anything looks unusual, and only then hand it off to accounting or another system.

Limitations

This viewer is designed for readable inspection, not for full semantic validation. If a supplier file uses a rare extension or non-standard field naming, the raw XML preview remains the authoritative source on the page.

Quick answers

Can this replace invoice validation? No. It is a reading and review tool, not a validator for network, tax, or legal rules.

What if line items do not appear? The XML may use a structure the current parser does not map yet. The raw XML preview is there so the user can still inspect the original source.

Why keep both summary and raw XML? Because readable output speeds up review, while raw XML remains the fallback when fields need manual confirmation.

Does this work as a UBL 2.1 viewer? Yes. The page is designed to read common Peppol and UBL 2.1 invoice XML structures in a business-readable way.

Related pages

Run the format detector · Read the Peppol guide · Compare invoice formats · How to read a UBL invoice