Onboarding

Set a receipt submission routine for a virtual assistant's expenses

A receipt routine that covers naming, context, missing documents, and the weekly cut-off so reimbursements do not become a month-end chase.

By OnboardingEmployees editorial team | | 5 min read

Set a receipt submission routine for a virtual assistant's expenses
On this page
  1. Define what counts as a receipt
  2. Set the naming and folder
  3. Record the expense context
  4. Handle missing receipts
  5. Set the weekly cut-off
  6. Review the routine with the approver
  7. Related reading

A receipt submission routine tells a virtual assistant what to keep, how to name it, and when to send it after spending money for the role. It covers purchases, travel, and small supplies that are easy to forget until the end of the month. The routine should be short enough to follow at the counter and clear enough for an approver to review without a meeting. It also protects the assistant when a receipt is missing.

Define what counts as a receipt

Record the documents that are acceptable as proof of an expense, such as an itemized receipt, an invoice, or a confirmation with a payment amount. A card statement alone may show the amount but not what was bought. The routine should say which combination is acceptable. A clear definition prevents a submission from being rejected after the work is done.

Include the small purchases that seem too minor to record, because a group of small purchases can still need an explanation. A coffee for a candidate visit and a parking charge for an interview are both part of the cost of the work. The routine should set a threshold below which a simplified note is allowed. The threshold should come from the finance owner, not from the assistant.

Record what to do when a vendor offers only a digital receipt. The assistant should save the original file rather than a screenshot of a screenshot. The file should show the vendor, date, amount, and items. A forwarded email may hide the original attachment, so the routine should say where the original lives.

Set the naming and folder

Use a naming pattern that starts with the date, then the vendor, then the amount. A name such as 2026-11-10-office-supply-42-18 makes the file sortable and searchable without opening it. The pattern should avoid spaces and special characters that break on some systems. The assistant should use the same pattern for every currency and vendor.

Record the folder where receipts are stored and the folder where the submission copy goes. A receipt saved only in an email thread is hard to find when the thread is archived. The routine should name one working folder and one final folder. The final folder should be read-only for the assistant after submission.

Keep the receipt with the task record that explains the purchase. A receipt without a purpose is a number, while a task without a receipt is an unproven claim. The routine should link the two in both directions. A reviewer should be able to move from the expense to the reason in one click.

Record the expense context

Write the business purpose in one sentence, such as a supply run for the interview room or a taxi to a client meeting. The sentence should name the role activity, not a general category such as work. A purpose that could describe any purchase will be questioned. A specific purpose speeds the approval.

Record who approved the spend before it happened, or why the spend was urgent if approval came later. A routine that ignores pre-approval will create disputes about authority. The record should name the approver and the date. If the approval was verbal, the assistant should confirm it in writing the same day.

Note the cost center or project the expense belongs to when the team uses one. A correct amount sent to the wrong cost center creates work for someone else. The routine should show the current list rather than relying on memory. A short list is easier to keep accurate than a long chart of accounts.

Handle missing receipts

Write a short process for a missing receipt before it happens. The assistant should record the date, vendor, amount, and reason, then ask the vendor for a copy. If no copy is available, the assistant should submit a missing-receipt note with the approval. The note should not be treated as a routine substitute for a receipt.

Set a deadline for resolving a missing receipt, such as five business days after the purchase. A missing receipt that waits until month-end is harder to reconstruct. The routine should name the person who decides whether to accept the note. The decision should be recorded with the expense.

Record what happens when a receipt is rejected. The assistant should receive a specific reason and a date to resubmit. A rejection without a reason creates a loop. The routine should also say whether the expense can be corrected or must be withdrawn.

Set the weekly cut-off

Choose one day and time each week when receipts are submitted, and treat the cut-off as part of the role. A weekly rhythm is easier to remember than a monthly one and gives the approver time to ask questions. The cut-off should be after the busiest purchase day, not in the middle of it. The assistant should know the next date if a receipt arrives late.

Record what the assistant should do with a receipt that arrives after the cut-off. It should go into the next submission with a note, not into a separate exception thread. The routine should say whether a late receipt changes the approval route. A small late item should not require a meeting.

Send a short submission summary with the total, the number of items, and any missing documents. The summary gives the approver a quick way to check completeness. It also creates a record of what was sent and when. The assistant should keep a copy of the summary with the submission.

Review the routine with the approver

At the end of the first month, review the rejected items and the missing receipts with the approver. Look for a pattern in the vendor, the category, or the timing. A single missing document is an accident, while a recurring gap is a process problem. The review should change one part of the routine.

Ask the assistant which step took the most time and which rule was unclear. The answer may show that the naming pattern is too long or that the purpose field is ambiguous. Simplify the step rather than adding another reminder. A routine that is easy to follow is more likely to be followed.

Keep the routine beside the expense form and link it from the role-scope card. A document that lives only in a finance folder will be opened after the first rejection. The next reviewer should be able to see the current version and the date. The routine should be reviewed when the finance process changes, not only when a problem appears.

Continue building the workflow

Related support: onboarding operations support, contact us. The Internal Revenue Service - Recordkeeping for individuals general guidance on keeping supporting records for expenses.