What travel-expense evidence can a virtual assistant prepare without deciding tax treatment?

The buyer decision: preparation or judgment

A growing company may have receipts in email, card transactions in an expense platform, trip details in calendars, and reimbursement questions in chat. A Philippines-based virtual assistant can help turn those fragments into a review packet, but the useful boundary is narrower than “handle expenses.” This study asks whether an assistant can collect and reconcile evidence without deciding that a trip was business travel, that an amount is deductible, that an employee has adequately accounted, or that the company should reimburse it. The unit of analysis is one submitted trip or expense report. Preparation includes locating authorized source records, transcribing observable fields, flagging gaps, matching duplicates, and routing questions. Judgment includes interpreting tax rules, setting policy, approving reimbursement, changing payroll treatment, and deciding exceptions. Those decisions remain with the company’s authorized finance, tax, payroll, or management owners. This distinction protects both sides. The reviewer receives an orderly packet rather than a vague folder, while the assistant does not have to infer business purpose from a merchant name or invent a missing explanation. A packet is complete when it shows what was submitted, what source supports each field, what remains uncertain, and who must decide. Completeness does not mean approval. A perfectly indexed hotel bill can still relate to a personal trip, and a legitimate business expense can still lack enough contemporaneous evidence for the reviewer’s policy.

What the sources establish, and what they do not

IRS Publication 463 describes recordkeeping for travel, gift, and car expenses, including timely records and documentary evidence. It explains that records and receipts should work together and that a canceled check alone does not establish business purpose. Publication 583 discusses business records more broadly and emphasizes a recordkeeping system that clearly shows income and expenses. GSA publishes federal per diem rates, but those rates are not a universal reimbursement command for every private company. The FTC’s data-security guidance supports collecting only necessary personal information, controlling access, and disposing of information appropriately. These sources support a source-linked packet, not an assistant’s tax conclusion. Publication 463 applies within a particular US federal tax context and contains definitions, exceptions, and taxpayer-specific consequences. A company may have a stricter receipt threshold, a different reimbursement arrangement, contractual limits, local-law duties, or non-US operations. A rate lookup can be correct for the wrong location, season, travel date, or policy. The assistant should therefore record the exact rate table and date consulted rather than label an expense “within IRS limits.” The evidence can show the merchant, date, amount, currency, traveler, trip, submitted purpose, payment method, and attached receipt. It cannot by itself establish ordinary and necessary business character, tax home, accountable-plan compliance, or deductibility. Those are determinations for authorized professionals using the full circumstances.

Build a packet that preserves provenance

Start with a stable report identifier and the traveler’s submitted statement, not an assistant-written reconstruction. For each line, record transaction date, posting date where relevant, merchant as shown, amount, currency, conversion source if used, expense category proposed by the submitter, and the business purpose in the submitter’s own approved field. Link to the receipt or invoice in the controlled system. If calendar entries, booking confirmations, attendee lists, mileage logs, or approval emails are authorized evidence, reference them without copying more personal data than the reviewer needs. Record who supplied each item and when. Separating evidence from transformation matters. “Receipt shows USD 214.00” is an observation. “Allowable lodging” is a decision. “Card feed and receipt differ by USD 18.00” is a reconciliation finding. “Tip is excessive” is a policy judgment. The packet should retain both original currency and any converted amount, the rate source, effective date, and rounding rule. It should not silently overwrite a card amount with a receipt amount. For split expenses, preserve the original total and show the proposed allocation as a separate field. For missing receipts, use the company’s approved exception form; never manufacture a receipt, fill in a purpose from context, or mark an item compliant because the value is small. A reviewer should be able to reproduce every copied field from the named source.

A representative shadow test

Before live processing, construct synthetic cases that resemble the company’s real mix without exposing employee or customer data. Include an ordinary airfare receipt, hotel folio with personal incidentals, meal with several attendees, rideshare with a tip, foreign-currency charge, mileage claim, conference fee later refunded, duplicate receipt, card transaction with no receipt, receipt with no matching transaction, and a trip spanning two rate periods. Add ambiguous cases: a booking for a traveler whose trip was canceled, a merchant located outside the destination, a combined personal and business stay, and an expense submitted long after travel. Freeze the company policy version, rate source, categories, receipt rules, and owner map for the exercise. The assistant prepares packets while an authorized reviewer independently establishes the expected evidence status. Compare field-level results: correct match, duplicate detection, preserved original, missing-business-purpose flag, unsupported category, wrong date basis, incorrect currency conversion, excess data copied, or question routed to the wrong owner. Do not reduce serious errors to one average. Losing a receipt link, exposing a passport image, or converting with an unexplained rate deserves separate review. The test evaluates whether the preparation instructions are usable. It does not prove legal compliance, tax accuracy, employee honesty, or savings. Expand the lane only after ambiguous cases reliably stay unresolved until an owner decides them.

Exception paths matter more than the happy path

Expense work becomes risky when deadlines encourage someone to turn missing evidence into assumed facts. Define stop conditions in advance. A suspected altered receipt, unfamiliar payee-bank change, duplicate reimbursement, credential request, unusually sensitive attachment, executive expense outside normal review, or allegation of misconduct should leave the routine lane. The assistant should preserve the item, restrict discussion to approved channels, and notify the named owner. They should not accuse the submitter, contact a merchant using details from a questionable message, edit an accounting entry to “fix” the mismatch, or broaden access to investigate. Other exceptions are operational rather than suspicious. A traveler may be unavailable, a receipt may be in a system the assistant cannot access, or the card feed may arrive after the report deadline. The correct state is pending with a reason, owner, and next review date. Approval latency should not be disguised as assistant processing time. If policy permits a missing-receipt declaration, the authorized submitter should make it and the reviewer should decide it. If policy changes mid-trip, the packet should name the applicable version instead of blending old and new rules. When a reviewer corrects a category or amount, preserve the proposed value, corrected value, actor, timestamp, and reason. That history supports learning and prevents a later viewer from mistaking an edited record for the original submission.

Measures that support an operating decision

Useful measures focus on reconstructability rather than the dollar amount “processed.” Count reports received, eligible lines, source links present, fields copied correctly, duplicates surfaced, currency conversions reproducible, questions resolved by the proper owner, and packets accepted without evidence correction. Track exceptions by reason and time spent waiting for submitter or reviewer input. Sample approved and rejected packets, because reviewing only rejected items overstates defects while reviewing only clean reports hides the difficult cases. Keep security events and material payment errors separate from ordinary completion rates. Avoid misleading interpretations. A high missing-receipt rate can reflect travel conditions or a newly enforced rule; it does not prove poor assistant work. Rapid turnaround can mean efficient preparation or superficial review. A low correction rate can mean accuracy or weak sampling. Dollar value is not a quality score, and a GSA rate match is not a tax conclusion. The buyer should ask whether each line has traceable evidence, uncertainty is visible, and a named owner makes the consequential decision. If those conditions are met in shadow work, the company can delegate collection and reconciliation with narrow access. It should retain policy design, business-purpose validation, reimbursement approval, accounting treatment, payroll treatment, and tax conclusions. That is a useful support role: faster review through better evidence, not outsourced judgment.

Implementation sequence for a small team

Choose one expense type and one reviewer rather than opening every travel and purchasing system at once. Document the accepted source records, minimum fields, prohibited data, storage location, policy version, and escalation route. Give the assistant only the access needed to prepare the packet. Run a small historical or synthetic sample, correct the instructions, then use shadow mode on current reports before allowing routine preparation. Review every early packet and keep an explicit reject-and-return reason list. When performance stabilizes, sample routine cases while continuing full review of defined exceptions. Revisit access whenever the source set changes. A new corporate card, booking tool, international office, or reimbursement policy changes the evidence model and may invalidate the old checklist. Establish retention and deletion instructions so duplicated receipts and identity documents do not accumulate in chat or personal folders. Finally, tell travelers what the assistant can ask for and who decides disputes. Clear communication prevents a request for missing documentation from sounding like a tax ruling or accusation. The outcome is deliberately modest: an orderly, privacy-conscious evidence packet that reduces reviewer search time. The study does not claim that the packet makes an expense deductible, reimbursable, or compliant. It makes the decision easier to inspect.

Does this study report service performance?

No. It proposes a bounded workflow and reports no observed company, assistant, or customer outcomes.

Who keeps consequential decisions?

The business and its authorized legal, finance, HR, safety, privacy, security, tax, or executive owners retain decisions within their fields.

When should the support lane expand?

Only after representative cases remain reconstructable and exceptions reach the named owner.