Philippines staffing guide · Published
On this page
Set up a receipt chase queue for missing expense documents
A receipt chase queue that helps an overseas assistant request missing expense documents on a fixed schedule, keep evidence, and hand exceptions to the approver.
Missing receipts delay expense reports and turn a routine reimbursement into a thread of reminders. The assistant often knows which documents are missing but has no shared place to record the request, the date, and the response. A chase queue gives that work a predictable shape so nothing depends on someone remembering to ask again. That record also gives the approver a clear view of which items are genuinely stuck.
The queue should support the approver rather than replace judgment. It records what is missing, who was asked, when the next request is due, and which items need a decision. Keep the categories small and the schedule fixed, because a chase process that changes every week is hard to trust and easy to ignore. The approver should be able to see the open items in a single pass.
Define what counts as a complete receipt
A complete receipt shows the vendor, the date, the amount, and the items purchased. For card expenses, it should also match the statement line closely enough that the approver can reconcile the two. Write these fields into the queue as separate checks rather than a single yes or no. A missing field should be treated as its own gap so the request can name exactly what the vendor must resend. The assistant can then see whether the problem is a missing document or a document with an unreadable amount.
Decide which exceptions are acceptable before the first chase. A handwritten receipt may be fine when the vendor and amount are clear, while a screenshot of a banking app is usually not enough. Record the rule and an example beside the queue. When a new exception appears, add it to the rule set and tell the approver, so the same case is handled consistently next month.
Create the chase states
Use a small set of states such as received, missing, requested, promised, and escalated. Each state should have a clear meaning and a next action, so the queue can be sorted without reading every note. Avoid states that describe feelings, such as waiting or urgent, because they do not tell the next person what to do. The state should change only when the evidence changes.
Add a column for the last contact date and the next contact date. That pair makes the queue usable during a shift handoff, when the next assistant needs to know whether a request is overdue. Keep the original request date even after several reminders. A long history is useful evidence when the approver needs to decide whether to accept an alternative document.
Set the first and second request dates
Send the first request as soon as the report is reviewed, not at the end of the month. Include the specific item, the amount, the date, and a link to the place where the document should be uploaded. Ask for one document rather than a general request for receipts, because a specific ask is easier to answer. Record the send time in the queue.
Set the second request three working days later and copy the approver only when the item is material or the deadline is close. A third request should offer an alternative, such as a vendor copy or a written explanation. Do not keep sending identical reminders without changing the route. The queue should show that the team tried distinct steps before escalating.
Group requests by vendor when several receipts are missing from the same source. One clear message listing the dates, amounts, and reference numbers is easier for a busy vendor to answer than five separate reminders. Keep each item as its own row in the queue so the reply can be matched line by line. If the vendor sends one document for several charges, split the evidence across the rows and note the shared source. This keeps the queue accurate without multiplying the vendor's work.
Handle statements and missing vendor copies
A card statement proves that a charge occurred, but it does not prove what was purchased. Keep the statement as supporting evidence and mark the receipt itself as missing until a vendor document arrives. If the vendor can reissue a receipt, request it through the channel the vendor uses for billing. Record the request and the expected response date in the same row.
When a vendor copy cannot be obtained, write a short missing-document note with the reason, the amount, and the approver's decision. Do not recreate a receipt or edit an image to look complete. The note should make the gap visible to anyone who reviews the expense later. A clear exception with an owner is safer than a tidy folder that hides the problem.
Close the loop with the approver
Before the report is submitted, give the approver a short list of items still open, the action taken, and the decision required. Do not bury exceptions inside the full expense file. The approver should be able to accept, reject, or request a different document without reopening the whole report. Record the decision and the date in the queue.
After the report closes, review why the same vendors or categories keep missing documents. A recurring gap may call for a better upload step, a reminder at the point of purchase, or a different card process. Fix the cause where the team controls it, and note the change in the next month's review. The chase queue is working when fewer items need chasing, not when the reminders get faster.
Questions and operating boundary
Can a card statement replace a missing receipt?
It can support the expense, but it usually does not show what was purchased, so the receipt remains missing until the approver accepts a documented exception.
How many reminders should the assistant send?
Two direct requests and one alternative route are usually enough before escalation; the queue should record each step and its date.
Who decides whether an expense can be approved without a receipt?
The approver or finance owner decides under the written policy, and the assistant records the decision with the reason.
Source
irs.gov provides authoritative background and does not endorse this service.