To audit expense reports, set the coverage rule first, then run every report in scope through the same six checks. Verify each receipt is real and matches the claim. Test amounts against policy and tax rules, screen for duplicates, and confirm business purpose and attendees. Then clear or route the report before reimbursement.
Auditing a report is a fixed sequence, and the sequence matters more than any single check. Set the coverage rule, then test every report the same way. Below are the six steps in order, plus the timing decision underneath them.
An expense audit is the review of submitted employee expense reports against company policy, tax requirements, and supporting receipts, to confirm each claim is legitimate before payment.
Research published in October 2015 by the GBTA Foundation, with HRS, measured the cost of an expense report. Processing one report covering a single night hotel stay averaged $58 and 20 minutes, and 19 percent of reports contained errors or missing information. Treat that 2015 benchmark as a floor.
Run the audit before reimbursement wherever the workflow allows. Once the company has paid, it has to claw the money back through a payroll deduction or an awkward conversation.
The Association of Certified Fraud Examiners studied 2,402 cases for Occupational Fraud 2026. The median scheme lasted 12 months before detection, at a median loss of $104,000 per case. Schemes caught within six months showed a median loss of $40,000. Timing is the variable you control.
Two companion pages go deeper. The expense report audit process covers the stages and the roles that own each of them. Our guide to auditing expense reports covers the desk technique and the red flags an auditor reads first.
Our AI reads every line of every receipt on every report before reimbursement, which takes the coverage decision out of step one. Image provenance, pattern recognition, merchant authentication, mathematical validation, and completeness verification run in 42 languages across 97 countries. Clean reports auto-approve, and the platform routes exceptions to a reviewer with the evidence attached.
Two decisions inside the sequence set the quality of the result. You choose how much of the population to cover, and whether you check before or after payment. Get those right and the individual checks become routine. Start by writing down the current sample rate, then see how AI expense audit covers the rest of the population.
Set the coverage rule, then verify the receipt is authentic and matches the claim. Test each amount against policy and tax rules, screen for duplicates, and confirm business purpose and attendees. Then approve, return, or escalate the report.
Most enterprise finance teams audit 10 to 20 percent of expense reports, usually a random sample plus anything over a dollar threshold. Auditing every report removes the sampling question and gives a defensible answer when an external auditor asks how the population was covered.
Watch for round-number totals, receipts with no merchant detail, and weekend spend with no business purpose. Amounts just under an approval threshold deserve attention, as does a receipt image with editing software in its metadata.
Run the audit before reimbursement. Post-payment audits find problems after the money is gone, and recovery is slow. The ACFE reported in 2026 that the median fraud scheme lasted 12 months before detection. Pre-payment review shortens that window to days.
Finance or shared services owns the audit, managers own the business-purpose approval, and internal audit owns the control testing behind both. A manager approving a direct report's expenses is not an independent control on its own.