On this page Jump to section
Define stale by the next action that is missing
A receipt request becomes stale when it has passed the team's agreed follow-up point without a useful response or updated plan. Ask the owner to define that interval, the escalation contact and any exceptions. The rule should reflect the work's deadline and importance; a single arbitrary age limit will not fit every request.
Keep the transaction reference, requested evidence, person responsible, original request date and next follow-up date together. A new reminder should not reset the original age of the request. That history shows how long the evidence has actually been missing.
Make the status describe reality
Distinguish silence from a partial response or a promised delivery date. These cases need different next steps.
- No response
- Keep The original request and latest reminder dates.
- Next action Follow the agreed reminder or escalation route without restarting the request's age.
- Partial document
- Keep The received file and an exact description of what is missing.
- Next action Ask for the missing page, readable copy or required detail.
- Promised delivery
- Keep Who supplied the promise and the stated date.
- Next action Check the approved intake location after that date before sending another reminder.
- Evidence unavailable
- Keep The responsible person's explanation and sources already checked.
- Next action Ask the authorized reviewer how to handle the unresolved evidence.
- Received and reviewed
- Keep The final source link, receipt date and review outcome.
- Next action Close under the agreed acceptance rule while preserving the request history.
Check before chasing
Search the approved receipt inbox or document folder and compare transaction references before sending another reminder. A receipt may have arrived under a different filename or through another authorized person. Link the actual source to the existing request so duplicate reminders do not continue after receipt.
Do not use a similar amount alone to attach a receipt to a transaction. If the merchant, date or purpose is unclear, keep the match as a question. The reviewer should be able to tell which links were confirmed and which still need a decision.
Example: a promise passes without a file
An employee says a receipt will be supplied on Tuesday. On Wednesday, the assistant checks the agreed upload location and finds nothing. Record that check, retain the Tuesday promise and send the next reminder required by the team's rule. If the escalation threshold has been reached, notify the designated owner with the transaction reference and history.
Do not mark the record complete because a reminder was sent. Do not fabricate a replacement receipt or decide expense treatment when the evidence cannot be obtained. Those unresolved questions belong with the authorized reviewer.
Review the queue at a useful cadence
Sort outstanding requests by next action and deadline, with original age still visible. Keep a short summary of overdue promises, partial documents and items awaiting a reviewer. A request with no owner or no next date should be treated as a handoff defect even if it was recently created.
QuickBooks bookkeeping support can help maintain this receipt collection queue and prepare the supporting records for review. Clear ownership and a preserved history make follow-up more useful than repeated generic reminders.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.
