GUIDE · GUIDES

How to read an invoice: the 9 checks before you approve payment

A practical, field-by-field check for vendor invoices: what each section means, the errors that cost money, and how to handle a bill that does not add up.

invoice verificationapprovalsaccounts payable
How to read an invoice: the 9 checks before you approve payment

You do not need accounting training to read a vendor invoice well. You need a consistent order of checks, so the same mistakes get caught every time — duplicate bills, wrong totals, and payments sent on changed bank details.

Work through these nine checks before you approve anything.

1. Who sent it — and is it the vendor you expect?

Confirm the legal vendor name, address, and contact details against your vendor record, not just the logo on the page. A familiar logo with a new remit-to address or new bank details is the classic payment-diversion pattern. Bank-detail changes deserve their own out-of-band confirmation (call a number you already have, not one printed on the invoice).

2. Invoice number

Every invoice should carry a unique number from that vendor. It does three jobs: it is your filing reference, your duplicate check, and the reference your vendor will quote when they ask where payment is. Same vendor and same invoice number again? Pause — it is a duplicate, a resend, or a corrected bill, and each needs different handling.

3. Dates and payment terms

The invoice date starts the clock; the terms (Net 30, 2/10 Net 30, due on receipt) set the due date. Check both:

  • Has the due date been calculated from the right start date?
  • Is there an early-payment discount worth taking — or a late fee about to apply?
  • Does the date fall in the period you expected? A bill dated months ago may signal a lost original now arriving twice.

4. Line items: what, how many, at what price

Each line should describe the goods or services, a quantity, and a unit price. Compare against what you ordered and received:

  • Descriptions you recognize, in the quantities delivered
  • Unit prices that match your agreement or purchase order
  • No lines you cannot explain — freight, fuel surcharges, and “miscellaneous” fees hide here

If you use purchase orders, match the PO number on the invoice to the order and the receipt. Variances should be explicit exceptions, not silent edits to make the totals fit.

5. The arithmetic

Do not trust the printed total. Verify:

Sum of line items        = Subtotal
Subtotal + tax + shipping = Total due

Then confirm the tax treatment: which lines are taxable, at what rate, and whether tax should apply at all for this vendor and jurisdiction. Arithmetic that does not reconcile is the single cheapest fraud and error signal you have.

6. Currency and total due

Confirm the currency before the amount. A correct number in the wrong currency is an expensive mistake, and totals written in words vs. figures occasionally disagree — ask which governs before paying.

7. Purchase order and contract references

A PO number, contract, or job/project reference connects the bill to a budget and an owner. No reference on a bill that should have one usually means it bypassed your buying process; route it to the person who can confirm the work happened.

8. Payment instructions

Where exactly will the money go, and by what method? Check the account or payment link against the vendor record (see check 1). If instructions on this invoice differ from the last one you paid, stop and verify — do not let an agent or an auto-pay rule absorb that change silently.

9. What is missing

Sometimes the problem is absence: no tax ID where you need one for reporting, no itemization behind a lump sum, no credit applied for a returned item. A bill you cannot code to your books is not ready to approve, however correct the total looks.

When the invoice does not add up

  1. Do not pay a corrected amount of your own invention. Short-paying without agreement creates reconciliation chaos.
  2. Contact the vendor with specifics — line, amount, and what you expected — and ask for a corrected invoice or a credit memo.
  3. Document the correction on the bill’s record: what changed, who agreed it, and where the corrected document lives.
  4. Update your records so the corrected bill, not the original, is what gets approved, paid, and filed.

Making the checks stick

Reading well once is a skill; reading well at volume is a system. Keep the original document attached to every bill, make the nine checks an explicit approval step, and record who verified what. That record is your audit trail and your defense when a payment is questioned months later.

Payvy is being built around this workflow: an agent prepares the draft and flags exceptions such as a delivery charge that is not on the purchase order, and a person reviews the evidence and authorizes payment through your own bank. See agent controls for the authority boundaries, try the sample workflow, or inspect the source. Payvy is in development — the checklist above works with whatever you use today.

Updated November 10, 2026.

See it in the product.

Try the sample approval workflow, inspect the Rust source, or tell us what your AP process needs.

← Back to all articles