Executive takeaway

An invoice tells you what a vendor says you owe. By itself, it does not show that the work happened as billed. Before payment, compare each important line with the agreement and field records, then record any exception and the final decision.

A clean invoice can still carry a bad charge

Consider a simple, illustrative example. A hauler sends a polished invoice for 120 loads. The vendor is right, the arithmetic works, and the purchase order is listed.

The field records show 116 accepted loads. One ticket was voided. Three billed loads have no receiving record. The invoice cannot settle the difference; someone must compare it with the project record.

That is the central idea: an invoice is a claim for payment, not proof of performance. “Claim” does not imply fraud. It describes the record's proper role.

What an invoice proves, and what it cannot prove alone

An invoice can document who requests payment, what they billed, and how they calculated the total. It does not show by itself that the buyer received and accepted the work.

Federal payment rules make the distinction clear. The Federal Acquisition Regulation bases payment on a proper invoice and satisfactory performance. Most federal invoice payments also need a receiving report or other approval record. That record covers quantity or work, date, acceptance, and the responsible official. Private jobs follow their own contracts, but the control idea is useful: the bill and proof of the work are different records. FAR 32.905

  • Contract or purchase order. What it can establish: Authorized scope, rates, limits, and terms; What it does not establish alone: What actually happened
  • Invoice. What it can establish: What the vendor requests to be paid; What it does not establish alone: That every line was received, accepted, and unbilled before
  • Ticket, delivery record, or daily report. What it can establish: Observed work, delivery, time, quantity, or acceptance; What it does not establish alone: That the rate and invoice math are correct
  • Approval. What it can establish: A named person accepted a decision; What it does not establish alone: That the reviewer saw complete evidence
  • Payment record. What it can establish: What was paid and when; What it does not establish alone: That the underlying charge was valid

The useful question is not, “Does the invoice look valid?” It is, “Which record supports each important line?”

Where invoice verification breaks

In Accounted's discovery work, finance often had to ask project staff to confirm an invoice by searching reports, tickets, photos, email, or files. The answer depended on memory and manual work.

Five failure points appear often:

  1. The agreement is separate from the bill. The reviewer must locate the current order, rate, change, and limit.
  2. Field evidence is late or incomplete. A ticket may be missing, unsigned, illegible, or filed under the wrong project.
  3. Units or scope do not align. The bill uses loads while the field tracks tons, or quantities need several cost codes.
  4. Exceptions disappear inside totals. Rejected, voided, returned, or disputed activity remains billed.
  5. Activity is claimed twice. A repeated ticket, corrected invoice, or copied line reuses the same proof.

These problems begin where work is observed and documented.

The operational issue becomes a margin and cash-flow decision

When evidence is missing, finance can hold the invoice, pay before resolution, or send the question back to the field. Each choice creates exposure.

Use this table in a monthly cost-control review to choose the two failure points worth fixing first.

  • Tickets arrive after the invoice. Business exposure: Approval and payment may be delayed; Metric leadership should review: Days from invoice receipt to supported approval; Executive decision: Set a field-record cutoff and owner
  • Invoice quantity exceeds accepted quantity. Business exposure: Unsupported cost may enter the job; Metric leadership should review: Unsupported amount and quantity by vendor; Executive decision: Require line-level reconciliation above a threshold
  • Rejected or voided work remains billable. Business exposure: Job cost and vendor balance may be overstated; Metric leadership should review: Rejected activity still tied to open claims; Executive decision: Define who can approve an exception
  • One ticket supports more than one charge. Business exposure: Duplicate payment risk; Metric leadership should review: Reused ticket or transaction count; Executive decision: Prevent evidence from being consumed twice
  • Cost code is assigned after the fact. Business exposure: Cost reports may misstate where work occurred; Metric leadership should review: Value awaiting cost-code confirmation; Executive decision: Capture scope at the field event

The goal is to separate supported value from unresolved value quickly, approve the supported portion, and route each exception with a recorded reason.

Use this invoice proof checklist

Apply this checklist to each invoice or material line. Mark every row Green, Yellow, or Red.

  • Green: linked evidence agrees; no exception remains.
  • Yellow: evidence exists, but a mismatch needs review.
  • Red: support is absent, unauthorized, or already used.
  • Vendor and project are correct. Evidence to inspect: Vendor master, contract, project record
  • Work falls within authorized scope. Evidence to inspect: Contract, purchase order, change order
  • Service or delivery date is in the billed period. Evidence to inspect: Ticket, daily report, receiving record
  • Quantity and unit agree. Evidence to inspect: Invoice line and accepted field quantity
  • Rate and markup are allowed. Evidence to inspect: Current rate sheet and contract terms
  • Rejected, returned, or voided activity is removed. Evidence to inspect: Exception or rejection record
  • Supporting identifiers match. Evidence to inspect: Ticket, load, worker, equipment, or delivery ID
  • Evidence has not supported another charge. Evidence to inspect: Prior invoice allocation or paid-item history
  • Required signature or acceptance is present. Evidence to inspect: Receiving report or named approver
  • Taxes, fees, and extensions calculate correctly. Evidence to inspect: Invoice math and applicable terms
  • Yellow and red items have a decision owner. Evidence to inspect: Exception log
  • Approved and held amounts are recorded separately. Evidence to inspect: Approval record

This checklist is an operating aid, not an audit opinion or legal determination. Contract terms control what support is required.

A practical verification playbook

  1. Define what to expect. Record scope, rate, unit, project, vendor, period, and limit before the invoice arrives.
  2. Preserve the claim and source evidence. Keep the original invoice, accepted tickets, daily reports, scale records, signatures, and other relevant records.
  3. Normalize before matching. Align vendors, projects, dates, units, and identifiers. Document any conversion between units.
  4. Match at the lowest useful level. A correct total can hide an unsupported line and an offsetting underbill.
  5. Prevent reuse. Once a ticket or quantity supports a bill, mark it as used unless a recorded correction releases it.
  6. Record the decision. Separate supported and held amounts, assign exceptions, and keep the terms, evidence, checks, and approval together.

Minnesota's Department of Transportation separately publishes field-record, vehicle-load, force-account, and payment-request forms, showing why one invoice is not the whole payment record. MnDOT construction forms

How Accounted is designed to handle the workflow

Accounted is being designed to check records across existing systems, not replace enterprise resource planning, accounts payable, or payments.

For invoice verification, the designed mechanism is specific:

  • Connections and uploads are intended to preserve invoices, tickets, contracts, and delivery records.
  • Mapping would link each record to the right vendor, project, contract, cost code, and period.
  • The design would keep the invoice separate from tickets and observed work.
  • Checks would compare quantity, unit, rate, timing, identity, duplicates, limits, and evidence.
  • Evidence-use tracking would stop one accepted quantity from supporting several invoice lines unless a correction releases it.
  • Exceptions would go to a named owner.
  • A proof packet would show supported and unresolved amounts, evidence, checks, and decisions.

Matching only received documents can create false confidence. When 120 loads are expected but 116 arrive, the missing four must stay visible.

Three takeaways

  1. An invoice is evidence of a payment request, not independent proof that the billed work was received and accepted.
  2. Verification works best when contracts, field activity, claims, and decisions remain separate but linked.
  3. The fastest process approves supported value and isolates exceptions instead of treating the whole invoice as either good or bad.

Public sources