Expense Documentation Controls for Executive Assistant Agencies
by ExecutiveAssistantAgency Editorial Team · 6 min read
A review of expense documentation controls for executive assistant agencies, covering substantiation, approvals, missing receipts, card reconciliation, and audit trails.
In this article
- Documentation is the control, not the paperwork
- Separate the business purpose from the transaction
- Use an accountable process
- Set approval thresholds before the spend
- Handle missing receipts honestly
- Reconcile cards on a fixed schedule
- Design the expense report for review
- Document client-billable work separately
- Audit a sample every quarter
- Protect sensitive expense data
- Train new assistants on the first trip
Documentation is the control, not the paperwork
An executive assistant agency often pays for travel, client meals, event supplies, and local transport on behalf of clients or its own staff. Each payment creates a record that must explain who spent the money, why, and what business purpose it served. When the explanation is missing, the accounting team has to reconstruct the story months later. Good documentation controls make that story reliable at the moment of spend.
The control is not a large binder of receipts. It is a short set of rules that tells the assistant what to collect, when to submit it, and who approves it. The rules should be simple enough to follow during a busy trip and specific enough to satisfy an auditor. The IRS recordkeeping guidance explains the general principle that records must support the items reported on a return.
Separate the business purpose from the transaction
A receipt shows the amount and the merchant, but it rarely explains the business purpose. The assistant should record the purpose in plain language, such as a client meeting, a recruiting event, or a site visit. Name the people involved and the organization they represent. A note that says only "meeting" is not enough to support the expense.
Record the date and the location as well, because the same merchant may appear many times in a month. Link the expense to the relevant client, project, or internal cost center. If the expense supports a proposal, note the proposal name or number. The link lets finance answer a client question without searching through email.
Use an accountable process
An accountable process requires a business connection, adequate substantiation, and timely return of any excess amount. The IRS publication on travel and entertainment expenses describes the substantiation elements for travel, meals, and gifts. The exact treatment depends on the entity and the arrangement, so the agency should confirm its process with a tax adviser. A written policy that repeats those elements gives the assistant a clear standard to follow.
The process should define what counts as adequate proof for each expense type. A hotel receipt may need the folio rather than the card slip, and a meal may need the attendee list. A mileage record may need the route and the business purpose. Write those examples into the policy so the assistant is not guessing at the counter.
Set approval thresholds before the spend
Define who can approve which expense categories and at what level. The threshold should be high enough to avoid constant escalation and low enough to keep meaningful oversight. Name a backup approver for each level so a trip does not stall when the manager is offline. Record the approval in the expense system rather than in a separate chat.
For client-billable expenses, confirm the client's own documentation rules before the trip. Some clients require pre-approval, a specific cost code, or a receipt within a short window. Add those rules to the trip brief so the assistant collects the right evidence the first time. The travel visa document tracker follows the same principle of recording requirements before departure.
Handle missing receipts honestly
Missing receipts will happen, especially for small local purchases or a machine that does not print. The policy should provide a formal missing-receipt process rather than encouraging a creative reconstruction. Require a written explanation, a bank or card statement, and approval from a manager. Record the substitute evidence and the reason in the file.
Do not let a missing receipt become a routine exception. Track the exceptions by person, category, and vendor. A pattern may point to a merchant that never issues receipts or to a process that is too hard to follow on a phone. Fix the cause rather than repeating the exception form every month.
Reconcile cards on a fixed schedule
Reconcile corporate cards at least monthly and preferably weekly during heavy travel. Match each transaction to a receipt and a business purpose, and flag anything that has no support. Ask the cardholder to resolve an unmatched item before the next statement closes. A card that is reconciled months later loses the context that made the expense explainable.
Separate personal charges from business charges immediately. A personal charge on a corporate card should be repaid through the documented process, not netted against a future expense. Record the repayment so the card balance and the expense report agree. The NIST privacy framework is a useful reference for limiting access to card data to the people who need it.
Design the expense report for review
Put the most important fields first: date, vendor, amount, business purpose, attendees, and approval. Keep the receipt image attached to the line item rather than in a separate folder. Use a consistent category list that matches the accounting system. A report that requires the reviewer to open five tabs will be approved without real review.
Add a short reviewer checklist to the workflow. The reviewer should confirm the business purpose, the attendee list, the approval level, and the receipt match. If a line fails, return it with a specific question rather than a general rejection. A clear question gets a faster correction and creates a better record.
Document client-billable work separately
Client-billable expenses need a clear link to the engagement and the client's approval. Keep the client's cost code, the engagement name, and the approver on the same line as the receipt. Do not combine two clients in one report, even when the expenses were incurred on the same day. A clean separation makes invoicing faster and reduces disputes.
Confirm the client's rules for markups, caps, and excluded items before the expense is incurred. Record any pre-approval in the trip file or the project folder. If the client rejects an item, document the reason and the resolution rather than quietly moving the cost. The vendor management workload review offers a similar method for keeping third-party obligations visible.
Audit a sample every quarter
Select a sample of expense reports each quarter and test them against the policy. Check for missing receipts, vague purposes, split transactions, and approvals from the wrong level. Include cards, reimbursements, and client-billable items in the sample. Record the findings and the corrective action.
Share the themes with the team without naming individuals. A short note about recurring gaps is more useful than a compliance lecture. If a control fails repeatedly, simplify the process or improve the tool. An audit that only produces blame will not improve documentation.
Protect sensitive expense data
Expense records can include personal card numbers, travel itineraries, and client names. Restrict access to finance, the approver, and the assistant who prepared the report. Do not send full card images through ordinary email or chat. Use the expense system's permissions rather than a shared folder with broad access.
Set a retention period for expense records with the accounting lead. Keep the records long enough for tax, audit, and client requirements, then destroy them through the documented process. Confirm that backups and exported files follow the same schedule. A record that survives in a personal download folder is outside the control.
Train new assistants on the first trip
Give every new assistant a short walkthrough before their first business trip. Show them how to capture a receipt on a phone, how to record the purpose, and how to submit an item for approval. Ask them to practice with a sample expense before they travel. The practice run catches confusion while the stakes are low.
Pair the training with a quick reference card that fits in a travel wallet. Include the approval contacts, the client-specific rules, and the missing-receipt steps. Review the card when the policy changes. For agencies that need reliable administrative coverage, contact us to discuss assistant support. The records retention review explains how to keep the supporting documents after the report is approved.
“My EA handles everything from board prep to multi-city travel, and I finally have time to focus on the work that matters.”
Related Research
Research
Decision Memo Traceability and Retention in Executive Offices
An analysis of decision memo traceability and retention, covering identifiers, version links, approval evidence, access control, retention periods, and archive testing.
Research
Executive Correspondence Retention Duties for Support Teams
An analysis of correspondence retention duties for executive support teams, covering classification, ownership, legal holds, mailbox handovers, disposal, and retrieval testing.
Research
Follow-Up Closure Evidence Standards for Executive Support Teams
An analysis of follow-up closure evidence for executive support teams, covering closure states, commitment records, acceptance criteria, owner confirmation, sampling, and retention.