Why receipts alone are not enough for project oversight

What a receipt proves — and what it does not

A receipt is useful evidence. It can show the vendor, date, amount and sometimes the items purchased. But it does not necessarily show that the expense was authorised, that the price was reasonable, that the goods reached the correct site, that the quantity was accepted, that the work was completed or that the transaction was charged to the correct project.

Internal-control guidance consistently treats supporting documentation as one layer rather than the whole control system. U.S. GAO reviews, for example, have highlighted the need for detailed invoice support, pre-approvals and independent receipt or acceptance of goods and services. In one project-control review, contractors were required to link invoiced amounts to tasks completed and explain anomalies, while invoice reviewers checked both mathematical accuracy and supporting evidence.

The principle applies well beyond government accounting: a project owner should not ask only 'Do we have a receipt?' but also 'What did we approve, what did we receive and how does this connect to the project?'

Build a transaction evidence chain

A strong transaction record creates a chain from need to completion. The exact documents depend on the size and nature of the expense, but the logic is consistent.

For a construction-material purchase, the chain might begin with an approved work package or material request, followed by quotation or price confirmation, owner or manager approval, supplier invoice, proof of payment, delivery note, site confirmation of quantity received and photographs where useful. The final record links the purchase to the relevant project stage and updates the remaining budget.

For a service, replace the delivery note with evidence of work performed: inspection report, contractor completion note, technician report, photograph, timesheet or other acceptance record appropriate to the service.

• Request: why the purchase or service is needed.
• Approval: who authorised it and within what spending authority.
• Commercial evidence: quotation, rate, invoice or agreed price basis.
• Payment evidence: how, when and to whom payment was made.
• Receipt/acceptance: proof that the goods or service were actually received.
• Project link: budget line, asset, milestone or work package charged.
• Reconciliation: confirmation that the record appears correctly in the project accounts.

Independent receipt and acceptance is especially valuable

One of the strongest controls is separating the person who spends or orders from the person who confirms delivery, where the scale of the project justifies it. GAO has described independent receipt and acceptance as a way to provide reasonable assurance that an organisation actually received what it purchased and to reduce the risk of fraud, waste and abuse.

For a small project, full segregation of duties may not always be possible. The principle can still be adapted: the site supervisor can confirm physical delivery, the project manager can review the invoice and the owner can approve material payments above an agreed threshold. The important point is that one person should not be able to request, buy, confirm and approve everything without a second check where financial risk is meaningful.

Remote owners benefit particularly from this separation because they cannot physically verify delivery themselves.

Connect expenditure to physical progress

Project accounting becomes more useful when it is read alongside the schedule and work completed. PMI project-control guidance emphasises that cost data and progress data should be analysed together. Money spent does not automatically equal percentage complete; invoices can lag work, materials can be bought in advance and cost overruns can occur without equivalent progress.

A project report should therefore allow an owner to compare planned budget, actual payments, committed costs and the physical state of the work. If roofing has consumed 90% of its budget but inspection evidence shows only half of the defined work complete, the issue becomes visible early enough to investigate.

This is also why a single project percentage can mislead. The owner needs to know which work packages are complete, which are in progress and which have been paid in advance or remain outstanding.

Use approval thresholds and exception reporting

Not every expense deserves the same process. A project can define authority bands: routine expenses within approved budget may be handled by the project manager; higher amounts require owner approval; new scope always requires approval regardless of amount; emergency protective work has a separate procedure with rapid notification.

The control works only if exceptions are visible. If a purchase exceeds the approved rate, is paid to a new supplier, lacks a delivery record or falls outside the budget, the report should flag it rather than allowing the transaction to disappear into a monthly total.

Over time, exception reporting gives the owner a much clearer picture than asking to see every low-value receipt manually.

Reconcile monthly, not at the end of the project

Reconciliation is the process of making different records agree: cash or bank movements, project ledger, invoices, receipts, approved commitments and remaining budget. Waiting until project completion makes missing evidence much harder to recover and gives errors time to compound.

A monthly close can identify duplicate payments, missing receipts, unrecorded advances, supplier balances, budget lines that are overspending and work that has been paid but not verified. It should also document unresolved differences so they remain visible next month.

For a remote owner, the ideal outcome is traceability. Clicking or reading any material expenditure should lead to the underlying approval, invoice, payment proof and delivery or progress evidence. That is what turns financial reporting into project oversight.

A practical evidence standard for material expenditure

For meaningful project spending, aim to be able to answer the following questions without relying on memory.

• What was purchased and why was it needed?
• Was it already in the approved budget or was it a variation?
• Who approved the purchase?
• How was the supplier and price selected?
• Who was paid and what evidence proves the payment?
• Who confirmed the goods or service were received?
• What project stage, asset or work package did the cost support?
• What evidence shows the resulting work or delivery on site?
• Has the transaction been reconciled into the project financial record?