How to read a UBL invoice field by field

Most people do not need to read raw XML tags. They need to know where the important business fields are and what to verify first. A useful UBL review is less about XML syntax and more about reading the invoice in the right order.

Reviewed by Ronan for business-field clarity and first-pass invoice review. Last reviewed: July 7, 2026.

1. Start with invoice identity

Check invoice number, issue date, due date, and currency first. These fields tell you whether the file is recognizable and whether it belongs to the business event you think it belongs to.

2. Confirm the supplier and buyer blocks

Next, check who issued the invoice and who is expected to pay it. If supplier and buyer names, registration details, or identifiers already look wrong here, the rest of the review is unlikely to rescue the workflow.

3. Read totals before line items

Look at tax-exclusive total, tax amount, and payable amount before you dive into line-level detail. This gives you a quick sanity check on the scale of the invoice and whether anything looks obviously inconsistent.

4. Check tax and payment references

Tax blocks, VAT IDs, payment references, and account details often matter operationally even when the invoice looks readable. This is the point where finance or accounts-payable teams usually decide whether the file is safe to move further.

5. Review the line items

Only after the header and totals look plausible should you inspect the line items. Line items tell you whether the business description, quantities, and amounts match what the invoice claims as a whole.

When raw XML still matters

If a field looks unusual in the readable summary, go back to the raw XML preview to confirm the source structure. That is why Tooltensor keeps both the readable output and the XML preview available.