Invoice review checklist before payment

Many invoice problems are not discovered during payment execution. They are discovered too late, after the team already trusted the file. A practical invoice review checklist helps earlier: at intake, during approval, or before the payment file is released. This page is designed as a real working checklist, not as a theory page.

Reviewed by Ronan for payment-control workflow logic. Last reviewed: July 7, 2026.

1. Confirm what kind of file you received

Do not assume every attachment is just a PDF. Confirm whether the invoice is plain PDF, hybrid PDF, UBL XML, CII, XRechnung, or another structured file family. If the type is unclear, use the detector first.

2. Confirm supplier and buyer identity

Check that the supplier name, buyer name, registration details, and any party identifiers match the expected business relationship. If the file already looks wrong at the identity level, do not let the workflow continue just because the totals seem plausible.

3. Check invoice number, issue date, due date, and currency

These are basic control points that anchor the file in a real transaction. Missing or inconsistent values here often indicate a source problem, duplication risk, or a workflow mismatch.

4. Review totals before line items

Look at tax-exclusive total, tax amount, and payable amount first. If those numbers already look wrong, there is no value in pretending the rest of the workflow is safe. Totals are the fastest sanity check.

5. Review the line items

Only after the header and totals pass a quick sense check should you inspect the line items. Make sure quantities, descriptions, unit prices, and line totals fit the business reality.

6. Check VAT and tax identity where relevant

If the process depends on supplier VAT details, run a structural VAT check. A format pass does not prove live registration status, but it does catch obvious mistakes before the file moves further.

7. Check the IBAN before payment handling

Validate the IBAN structure and checksum before the payment process continues. A valid result does not prove the beneficiary is correct, but it does reduce avoidable typing and formatting errors.

8. Check participant data if the workflow uses Peppol routing

If the invoice workflow depends on Peppol routing, confirm participant details separately. A readable invoice and a valid routing setup are different questions.

9. Separate readable inspection from formal validation

If the workflow needs formal invoice validation, do that after the readable review. Do not use a validator as a substitute for understanding the file first. That only hides where the real problem started.

10. Keep the source file authoritative

Do not rely only on forwarded screenshots, copied values, or converted exports when the original source file is available. The original invoice file remains the best reference point if something has to be checked again later.