Policies & Approvals

Expense Approval Evidence Checklist for Internal Controls

Build a reviewable evidence packet for one employee expense approval, from policy criteria and transaction support to the recorded decision and follow-up.

By Remizen Editorial · · 3 min read

An approval is only reviewable when another person can reconstruct what was examined, which rule applied, and why the decision was made. This procedure is for a finance or operations reviewer assembling evidence for an individual employee expense, not a substitute for your written policy or any legal, tax, or audit advice. The 2025 GAO Green Book is a framework for U.S. federal agencies; its Section 2 says nonfederal entities may use it as a framework, so private organizations may adapt these practices but it is not a mandate for all employers.

Define the evidence before reviewing

Start with the control objective: establish that the expense is business-related, supported, coded appropriately, within applicable approval authority, and decided before payment or posting where your process requires that sequence. Principle 12 of the Green Book says policies should describe expectations and procedures should identify actions implementing them; adapt that idea into a short evidence standard your reviewers can follow. For each report, identify the employee, transaction date, merchant, amount and currency, business purpose, cost center or project, and applicable policy clause. Request only records relevant to those tests.

Gather the itemized receipt or other support required by your policy, the submitted report detail, and any business-purpose explanation. Preserve the applicable policy version or section reference rather than relying on a reviewer to guess which rule was in force. Add approval evidence showing the approver, decision date, status, rationale when an exception or judgment was involved, and conditions or follow-up. A screenshot can help explain a system state, but keep the underlying record or report when available and label its capture date.

Test the packet and document the decision

Compare amounts and dates across the report and supporting record; note discrepancies instead of choosing one silently. Confirm that the approver had delegated authority for the amount and category under your own approval matrix. A manager's confirmation of business purpose does not automatically resolve a missing receipt, unsupported coding, or a policy limit. For each failed test, record whether the report is pending, returned, escalated, or declined and who owns the next action. Principle 13 of the Green Book emphasizes relevant, quality information for internal control; a compact, clearly indexed packet is more useful than a folder of unlabelled attachments.

Worked example: a split dinner charge

A submitted dinner charge is $186, while its receipt shows $168 plus a separate $18 tip. The employee's note identifies the client meeting and attendees, but the expense report records only “team dinner.” The reviewer keeps the transaction pending, asks the submitter to correct the business-purpose detail, and checks the receipt and policy's meal documentation rules. Once corrected, the reviewer records the reviewed amount, policy section, approval identity and date. If the itemized receipt is unavailable, the reviewer follows the organization's missing-document procedure rather than treating an approval click as evidence that the underlying requirement was met.

Handle gaps and close the record

Do not backfill evidence with assumptions or convert an unresolved question into an approval. If records conflict, request clarification and preserve both the initial and corrected submissions. If the approver is unavailable or has a conflict, follow the documented alternate route; do not ask the submitter to approve their own transaction. Record correction owner, due date, outcome, and any escalation. The Green Book's Principle 12.04 discusses procedures that include timing and corrective follow-up; this is useful design guidance, not a prescribed private-company timeline.

  • Identify the transaction and relevant policy version or section.
  • Retain receipt/support, business purpose, report fields, and any clarification.
  • Record reviewer authority, decision, date, rationale, and conditions.
  • Assign and close any correction or escalation with an outcome.

Apply this guidance: Automate Approval Routing with Human Decision Points

Sources and further reading

  • Expense Approval Best Practices

    Improve expense reviews with clear authority, complete context, consistent decisions, and practical exception handling. These practices help teams balance oversight with a process employees can navigate.

  • Expense Report Approval Process

    A reliable approval process routes each expense report to the right reviewer, checks evidence and business context, and records decisions for finance. Learn how to define responsibilities and handle returns without bottlenecks.

  • How to Create an Expense Policy

    Build an expense policy employees can follow and finance can administer. This step-by-step guide covers scope, spending rules, approvals, exceptions, and how to keep the document useful as the business changes.

  • Missing Receipt Policy Guide

    A missing receipt policy gives employees and reviewers a consistent way to document expenses when the original evidence cannot be obtained. Define reasonable steps, required explanations, approval ownership, and safeguards against routine workarounds.