Measuring expense receipt chase response is useful because missing receipts delay review and can affect the deduction. It is also easy to overclaim, because a request is not a receipt and a receipt is not a reviewed expense.
Payables & Expenses
Measuring expense receipt chase response without overclaiming
A research brief on receipt chasing, separating a request that was sent from a receipt that arrived and an expense that was ready to review.
Published · 3 listed sources
Table of contents
Key takeaways
- A chase shows a request, not a receipt.
- Separate the missing receipt, the reminder, the response, and the review readiness.
- Record the age and value of the open items, not only the count.
- Use the pattern to fix the submission habit, not to blame the spender.
An expense report is submitted without a receipt. The bookkeeper sends a request, the employee is traveling, and the report waits. The chase is recorded as "sent" and the item stays open.
What the measure can show
The measure can show the missing document, the request date, the reminders, and the response. It can show the age and value of the open items. It can show the expenses ready for review. Those facts support a review of the submission process. A cluster of missing receipts from one vendor may indicate a receipt format problem. A cluster from one team may indicate a habit.
What the measure cannot show
The measure cannot show whether the expense was valid. It cannot show whether the employee had the receipt and lost it. It also cannot show whether the chase was reasonable. The measure cannot prove that a person is careless. The process and the timing matter. The log shows the steps, not the character.
Methodology
We reviewed public guidance on internal control, recordkeeping, and small-business operations, and mapped it to a private expense process. The sources support documentation and review discipline. They do not prescribe a receipt standard or a chase cadence. We tested the model against four common cases: a receipt provided on the first request, a receipt provided after two reminders, a receipt that never arrived, and an expense with a card statement as the only evidence. The proposed fields are an operating design.
Separate the missing item from the chase
Record the expense, the missing document, and the date the gap was found. Then record the request and each reminder. The gap and the chase are different events. A missing receipt that was found internally is not the same as one that required three emails. The record should show where the document came from.
Set a chase cadence
Use a cadence that matches the business's policy, such as a first request and a reminder after three business days. Record each attempt and the channel. A daily stream of reminders is not a process. If the employee does not respond, escalate to the manager. Record the escalation and the new date. The escalation should name the open item and the impact.
Note the evidence type
A receipt, a card statement, and a vendor invoice are different evidence. Record which one was provided. A card statement may support the amount but not the business purpose. If the policy allows an alternative, record the reason and the approver. The exception should be visible and time-bound.
Track the value and the age
Report the open items by value and age. A small receipt that has waited a month is a different problem from a large one that arrived late. The combination helps prioritize. Keep the currency and the period visible. A multi-currency report in one total hides the exposure in each currency. The review should show the original amount.
Review readiness separately
An expense is ready for review when the required documents are present and the policy check is complete. Record the readiness date and the reviewer. A receipt that arrived but has not been reviewed is not closed. If the expense is blocked by another issue, record it. A receipt is one requirement, not the whole review. The log should show the next action.
Review the pattern monthly
At the end of each month, review the missing receipts by vendor, team, and expense type. Look for the vendor whose receipts are hard to obtain and the team with repeated gaps. The pattern is more useful than a single chase. Change one thing based on the review. A clearer submission prompt or a vendor receipt setting is often enough. Record the change and the date.
Protect the expense data
The log can include employee names, amounts, and vendor detail. Keep it in the approved system and limit access to the people who review expenses. Do not circulate a list that reads like a performance ranking. Set a retention period with the business's records policy. Keep enough to support a tax or audit review and no more. A chase log kept indefinitely creates risk without adding insight.
Keep the sample honest
A review of one month and one entity is a check, not a benchmark. Say so in the summary. Include the expense count and the evidence types so the reader can judge the evidence. A small sample can show a pattern but cannot support a percentage for every team. Repeat the review before a conclusion is treated as stable, and state the limits in the same document.
Agree the acceptable evidence
Write down what counts as acceptable evidence for each expense type. A receipt, a card statement, and a vendor invoice are not interchangeable. The rule should be short and shared with the team. Review it when the card or expense policy changes.
Keep the log light enough to use
The chase log should take a minute per item, not a full email archive. Record the expense, the gap, the request, the response, and the readiness. Leave the documents in the expense system. Review the fields after a month and remove any that nobody used.
Review the submission prompt
A repeated missing receipt may be a prompt problem rather than a person problem. Review the submission screen and the instructions. A clearer prompt at the point of submission is more useful than another reminder. It also reduces the number of chases the team has to send.
Review the vendor receipt format
A vendor that sends a minimal receipt creates repeated gaps. Ask whether the vendor can provide a fuller receipt or a portal copy. Record the request and the response. The fix may be a vendor conversation rather than another reminder. A short note to the vendor is often enough to change the format. It also gives the next reviewer a clear reason for the change. A short note is enough. It should be dated and kept with the expense.
Keep the evidence in one place
Link the expense to the receipt rather than copying it into the log. A reviewer should be able to open the source from the record. Keep the evidence in the expense system and the log as the index. A short link is enough to make the record reviewable.
Bounded pilot
Review one month of missing receipts for one entity. Record the expense, the gap, the requests, the response, and the readiness. Report the open items by value and age. Ask a reviewer who did not chase the receipts to trace three expenses to their evidence. If they cannot, the fields need work.
Limitations
This brief describes an operating review model. It does not establish a tax standard, a legal obligation, or a measure of employee performance. The cited sources support general control, records, and operations principles. Results depend on the completeness of the log and the accuracy of the expense records.
Sources
- Standards for Internal Control in the Federal Government; U.S. Government Accountability Office; checked November 17, 2026.
- Recordkeeping; Internal Revenue Service; checked November 17, 2026.
- Manage your business; U.S. Small Business Administration; checked November 17, 2026.
Conclusion
Expense receipt chase response shows requests and responses, not the validity of the expense. It becomes useful when the gap, the chase, the evidence, and the readiness are recorded together. That discipline improves the process without blaming the spender. For related workflows, see the bank feed reconciliation brief and the bookkeeping services overview.