Expense packets come back for predictable reasons. A receipt is missing, a category is wrong, a personal charge is mixed with a business one, or the approver cannot tell what the spend was for. Each correction adds a day and a new message thread. A packet designed around the finance team's actual checks removes most of that churn before the first submission.
Operations
Design an expense packet the assistant can submit without corrections
An expense packet design that matches policy, separates personal spending, and reduces correction cycles for executive support teams.
Table of contents
Why packets come back
Most corrections start with evidence, not arithmetic. The total may be correct while the receipt is unreadable or the business purpose is missing. Finance teams cannot approve a charge they cannot document, so they return the packet and wait. The assistant then has to reconstruct the trip or purchase from memory and email.
The second cause is policy drift. A limit changes, a new category appears, or a vendor starts issuing receipts in a different format. The assistant keeps using the old template and the packet fails a check that did not exist last quarter. A packet that is reviewed against the current policy digest prevents that surprise.
Agree the evidence standard first
Ask the finance team what makes a packet approvable without a follow-up. The answer is usually a readable receipt, a business purpose, the attendee list for a meal, and the correct cost center. Write those requirements down as a short checklist. The assistant can then build every packet against the same standard.
The standard should say what counts as a readable receipt. A photo of a crumpled paper may be unusable, while a digital invoice with the vendor name and tax amount is fine. Clarify whether a bank statement can substitute when a receipt is lost. Getting that rule in writing prevents an argument at submission time.
Build a cover sheet that maps to policy
The cover sheet should mirror the finance system rather than invent a new order. Put the date, vendor, amount, category, cost center, business purpose, and approver in the same sequence the reviewer will see. Add a column for the receipt file name so each line can be matched to its evidence. A reviewer should not need to open a second document to understand the claim.
Keep the purpose specific. "Client dinner" is weaker than "working dinner with the Acme implementation team to close the phase-two scope." The second version tells the approver why the expense existed and who benefited. It also helps during an audit months later, when the original context is no longer fresh.
Separate personal from business spending
A corporate card statement often contains both business and personal charges. The packet should mark personal items clearly and show how they were repaid or removed. Mixing them into one total creates a reconciliation problem for finance and a delay for the assistant. A separate line with a reference to the repayment is enough.
If the executive uses a personal card for business travel, the packet needs a clear reimbursement path. Record the currency, the exchange rate source, and the date of conversion. Finance should not have to guess which rate applied. A consistent method prevents small differences from turning into repeated corrections.
Handle missing receipts before submission
Missing receipts should be resolved before the packet leaves the desk. Use the finance team's missing-receipt form and attach the explanation to the line item. If the policy requires a cap, state the cap and the amount claimed. Do not leave the reviewer to infer what happened from a blank attachment field.
Track missing receipts as a separate count. If the same vendor never provides a usable receipt, the desk can ask for a different delivery method at booking. Over time, that change reduces the number of exceptions. The packet becomes cleaner because the source of the problem was fixed, not because the assistant worked harder at cleanup.
Set a review window and a correction path
Agree how long finance has to review a complete packet and what happens when an item is returned. A two-business-day window is common for routine claims, with a separate path for urgent travel. The assistant should know who to contact when a packet sits past the window. A named reviewer is better than a general finance inbox.
When a correction is needed, ask for the specific fix rather than a general rejection. The reviewer should name the line, the missing evidence, and the policy reference. The assistant can then correct that item and resubmit without rebuilding the whole packet. Record the reason so the next packet avoids the same gap.
Keep a current policy digest
Maintain a one-page digest of the rules the desk uses most: meal limits, mileage rates, approval thresholds, receipt requirements, and submission deadlines. Update it when finance announces a change, and note the effective date. The digest should live next to the packet template so the assistant sees it at the moment of work.
Review the digest quarterly with the finance contact. Ask which rules caused the most returns in the last quarter and whether any are changing. A short conversation prevents a slow drift between what the desk believes and what the system enforces. For the broader operating context, see our guide to setting a document naming standard. For hands-on help with this work, review our executive support services. The IRS recordkeeping guidance explains why supporting documents matter for business expenses.
Key takeaways
- Agree the evidence standard with finance before building the packet, including what counts as a readable receipt.
- Mirror the finance system on the cover sheet and write a specific business purpose for every line.
- Separate personal charges and show the repayment or removal clearly.
- Resolve missing receipts with the approved form and track repeat vendors as a process problem.
- Keep a dated policy digest and review the top return reasons with finance each quarter.
Frequently asked questions
What makes an expense packet easy to approve?
How should an assistant handle a missing receipt?
How often should the expense policy digest be updated?
Keep reading
Related executive support guides.
Build a travel disruption playbook for a multi-city week
A playbook for flight changes, hotel gaps, and meeting overruns that keeps a multi-city executive week recoverable.
Map executive inbox decisions without reading private mail
A routing map that helps an assistant sort decisions, delegations, and sensitive messages while respecting the executive's private correspondence.
Run a monthly vendor renewal watchlist without spreadsheet sprawl
A single renewal watchlist that tracks notice windows, owners, usage, and risk so vendor contracts do not surprise the executive office.