Key takeaways
- Time the traveler, the reconciler, the approver, and the ledger separately.
- Report missing receipts as a distinct cause of delay.
- Check whether the card statement date is the real cutoff.
- Sample late reports as well as on-time reports.
Question and scope
This audit asks how long a CEO's travel expense report takes to move from trip end to ledger close and where the delay occurs. The unit is one trip report tied to one card statement and one approver. The review follows the receipt, the reconciliation, the approval, and the posting. It does not judge whether the travel itself was necessary.
Set the scope to one executive office and a fixed period of travel. Record the card program, the expense system, and the approval rule. If the policy changed during the period, separate the trips. A new receipt threshold can change the delay without changing the office's behavior.
Include trips with airfare, lodging, ground transport, and meals. Include at least one trip with a changed itinerary and one with a missing receipt. Record the trip type. A sample of only clean reports will hide the exceptions that drive the cycle time.
What the sources establish
IRS Publication 463 sets out substantiation expectations for travel expenses, which supports a record-based audit without prescribing an internal cycle time. GAO data-reliability guidance supports a consistent definition of each timestamp. GAO's Green Book supports separating the control activity from the evidence that it operated. Record the date and the owner so the next review can rebuild the decision.
The sources do not establish a maximum number of days for reconciliation or a required approval chain. They also do not tell the office which expenses should be reimbursed rather than paid directly. The audit therefore measures the office's own policy and the record it produces. The report should keep that local scope visible.
The sources also support separating a timing failure from a documentation failure. A report can be approved quickly and still lack a receipt. The audit should record both the day count and the evidence status. A fast incomplete report is not a strong control.
Definitions and measures
Define trip end as the last business day of travel. Define report ready as the date the traveler submitted a complete report. Define reconciliation complete as the date the card and ledger totals agreed. Define approved as the date the approver signed. Define posted as the date the ledger entry cleared.
Measure the days between each stage and report the stage with the largest median gap. Record the number of reports with a missing receipt and the days added by the request. Keep the denominator as trip reports, not expense lines. One report can contain many lines.
Record whether the report was filed before or after the card statement closed. A report filed early may still wait for the statement. Report the two dates separately. The statement date is often the real constraint and is invisible in a simple cycle-time measure.
Record the approver's role and the number of reports in the queue at approval. A delay may reflect queue depth rather than neglect. Report the queue size beside the approval time. The comparison makes the finding fairer and more useful.
Sampling and collection
Sample reports from the card statement, the expense system, and the ledger. Include reports that were approved late and reports that were approved on time. Record the trip, the traveler, the approver, and the amount. A sample of only late reports cannot show the normal path.
Collect the itinerary, the receipts, the approval note, and the journal reference. Mask card numbers and personal details that are not needed. If a receipt was replaced by a written explanation, record that path. The evidence type is part of the finding.
Include a report that was returned to the traveler for correction. A return adds a loop that a simple stage measure can miss. Record the return date and the reason. The audit should show the rework, not only the final approval.
Verification pathway
Check whether the report total agrees with the card statement and the ledger account. A report that balances to the receipts but not to the card is not reconciled. Record the difference and the clearing entry. The audit should test all three totals.
Confirm that every expense above the receipt threshold has a document. A summary line without a receipt may be acceptable below the threshold and not above it. Record the amount and the evidence. The threshold should be applied consistently.
Review the approval note for the exceptions the approver accepted. A signature without a note does not show what was decided. Record the exception and the approver. The audit should be able to rebuild the judgment.
Analysis and reporting
Report the number of reports, the median days at each stage, and the share with a missing receipt. Break the results down by trip type, approver, and card statement period. Report the returned reports separately. A single cycle-time average can hide a long approval queue.
Inspect the delays for patterns. A cluster of waits at report ready may point to the traveler's receipt habit, while a cluster at approval may point to a queue. Choose one change, such as a receipt checklist or an approval calendar. Do not rank travelers by cycle time when their trip mix differs.
Report the time from trip end to ledger close, not only to approval. An approved report that is not posted still leaves the account open. Show both dates. The ledger close is the point the finance team actually needs.
Limits and next action
The audit cannot prove that every expense was appropriate or that the approver had enough context to judge it. It also cannot capture a receipt that was reconstructed after the fact. The report should state those limits and avoid treating the file as complete evidence. Record the date and the owner so the next review can rebuild the decision.
Set a repeat audit date and keep the stage definitions stable. Assign the correction to the executive office lead and give the traveler a short receipt checklist. The next audit should test whether the same stage or the same exception fails again. A useful result is a report that closes without a chase.
Sources
- Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
- Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
- Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
- Business Formation Statistics, U.S. Census Bureau.
- Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
- Productivity Statistics, OECD Data Explorer.
- World Development Indicators, World Bank DataBank.
- ILOSTAT Labour Statistics, International Labour Organization.
- 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
- The economic potential of generative AI, McKinsey Global Institute.
- Creating helpful, reliable, people first content, Google Search Central.
- Search Engine Optimization Starter Guide, Google Search Central.
- Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
- IRS Publication 463, Travel, Gift, and Car Expenses.
- GAO, Assessing Data Reliability.
- GAO, Green Book.
Related research
Apply the research
Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.
Turn the finding into a support scope.
Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.
Talk through the role