A professional invoice is one the buyer can identify, check and process. A polished logo will not rescue a wrong customer name or a total that ignores an advance payment. Use two passes: check the transaction first, then inspect the exported document.
This checklist is for the moment before sending. The invoice template supplies the layout; the checks below help you catch mistakes in a completed bill.
Pass one: compare the bill with the agreement
- Supplier: Does the name match the legal/trading identity and the buyer’s supplier record?
- Customer: Is this the entity that ordered the work, at the correct billing address?
- Scope: Does each line map to agreed work, a billing period or an approved variation?
- References: Are project and purchase-order details present where required?
- Dates: Are issue date, relevant supply date and agreed due date correct?
- Number: Is the invoice reference unused and consistent with your register?
If a requirement is unknown, resolve it before treating the invoice as final. A blank purchase-order box can be harmless for one customer and a reason for rejection by another.
Recalculate one line and the total
For a fictional check, take two units at £50. Subtotal is £100. A 10% discount gives £90. An illustrative 20% tax on that discounted amount is £18, producing £108. If your document shows £110, inspect whether tax or discount was applied to a different base.
This example does not decide the applicable tax rate or treatment of a discount. Check those decisions separately. For UK VAT, use the VAT field and calculation guide and official guidance.
Look for the less obvious mistakes too: decimal separators, accidental negative quantities, a currency symbol copied from an old template, or a previous payment entered as a price discount. Earlier payments need a traceable allocation rather than an improvised arithmetic shortcut.
Check the payment handover
Compare bank or payment instructions with verified records, especially after a change. Include a usable reference and an explicit agreed due date. A finance contact should be able to tell what to pay, where to pay and how to identify that payment.
Do not accept changed bank details solely because they appear inside an existing email conversation. Verify through a previously known channel. The invoice can be correct while the surrounding message is fraudulent.
Pass two: open the actual exported file
- Are every address, registration detail and line description visible?
- Are totals together and easy to read?
- Did a long note push payment instructions onto a nearly empty second page?
- Does the file contain the intended invoice, rather than the previous customer’s bill?
- Can text be selected where expected, and does it remain readable when enlarged?
- Does the filename identify the invoice without exposing unnecessary personal data?
Review the file you are about to attach, not just the editable document behind it. A browser’s PDF output can differ with page size, margins and print settings.
A compact sign-off record
Invoice: [reference] Agreement/order checked: [reference] Arithmetic checked: [date / person or process] Payment details verified against: [record] Final file opened and checked: [filename] Delivery route: [accounts email / portal] Issued record saved: [location]
Use this privately as a process note. It is not a certification to place on the customer’s invoice. Do not invent another person’s review or initials.
After sending
Record the issue and due dates, retain the final file and match later receipts. If delivery fails or the portal rejects the document, record the reason and correct that specific problem. Avoid issuing a second bill with another number just because the first email was missed.
For legal fields, consult the requirements that apply to the transaction. GOV.UK provides the UK checklist. This review improves clarity and catches operational errors; it does not establish every legal or tax requirement.
Published by Talentra Solutions. Revised 19 October 2026 with a practical workflow and clearer limits. Examples are fictional. Report a correction.