Expense Evidence Sufficiency

Abstract

A review protocol for finance-support teams that want to test the evidence behind an executive expense pack without re-auditing every transaction.

Methodology

Define the population as all executive expense claims submitted in a fixed quarter, including corporate card transactions and reimbursements. Record the quarter, the entity, the cost centers, the extract date, and the count. List the required evidence for each claim: date, merchant, amount, currency, payment method, business purpose, attendees where applicable, receipt or missing-receipt note, policy reference, approver, and ledger or card match. Name the authoritative source for each field. A card statement supports the charge; a receipt supports the purchase; an approval record supports the exception. A calendar entry can support context but does not replace the receipt. Sample across categories, amounts, currencies, and approval paths. Include a claim with a missing receipt, a foreign-currency claim, and a claim that was split across cost centers. Classify defects as missing receipt, unclear purpose, missing attendee list, wrong period, duplicate claim, missing approval, currency error, or ledger mismatch. Assign an owner and a correction date. Report the population, sample, defects, and limits. Retain the sample index and the approval record with restricted access. The protocol does not determine whether an expense was prudent or whether a vendor relationship was appropriate.

Claim-level evidence

Each line should stand on its own: date, merchant, amount, currency, purpose, and receipt. A summary total that cannot be traced to the underlying lines is not an expense pack.

For meals and events, the attendee record should be sufficient to show the business relationship without exposing unnecessary personal information. Use the organization's approved level of detail.

Approval and exception

The approval path should be visible beside the claim. A missing receipt, a limit exception, or a late submission needs the named approver and the resolution, not only a comment from the assistant.

The review should compare the approver's authority with the policy threshold. An approval from someone outside the path is a defect even if the amount is small.

Reconciliation

The pack should reconcile to the card statement or the general ledger. Duplicate claims often appear as a card charge and a reimbursement for the same purchase; the review should test for that pattern.

Credits, refunds, and disputed charges should be linked to the original transaction. A refund that appears as a new line without a reference should be flagged.

Archive and limitations

Store the approved pack, the receipt index, and the exception schedule according to the finance retention rule. Keep personal banking details out of shared folders.

The protocol cannot establish whether an expense was appropriate for the business. It can show whether the record supports the approval that was given.

Key findings

  • A card statement proves a charge, not a business purpose.
  • The receipt and the approval answer different questions.
  • Foreign-currency claims need a documented rate and date.
  • A duplicate check should compare the card feed with the reimbursement claim.
  • Exceptions need an approver, not an explanatory note alone.
  • The review tests evidence sufficiency, not the merits of the spend.

Sources

  1. Standards for Internal Control in the Federal Government, U.S. Government Accountability Office
  2. Internal Revenue Service, U.S. Department of the Treasury
  3. Privacy Framework, National Institute of Standards and Technology
  4. Records Management Policy and Guidance, National Archives and Records Administration

Return to the Research Content library