Peppol / UBL Invoice Viewer

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 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.

Related pages

Run the format detector · Read the Peppol guide · Compare invoice formats