CEO Executive Assistant
What an Executive Expense Exception Packet Should Contain solves a narrow but important executive-office problem: whether an expense exception has enough verified evidence and the correct owner for review without asking the assistant to approve it.
For this workflow, capture transaction, date, amount, currency, merchant, business purpose, attendees, receipt status, policy issue, evidence, requester, reviewer, decision, correction, and reconciliation date.
The assistant may gather records, identify the applicable process, route the exception, and reconcile an approved outcome. Finance or another authorized owner interprets policy and decides reimbursement, accounting treatment, tax handling, and exceptions.
Consider this case: A card charge from an executive trip has no itemized receipt, the converted amount differs from the statement, a guest list is incomplete, and the month-end close begins tomorrow.
Useful indicators include exceptions complete on first review, missing evidence by type, approval time, duplicate charges found, corrections posted, repeat exception causes, and items reconciled by close.
Separate the transaction from the exception
Start with what can be proven: merchant, amount, currency, date, business purpose, traveler or purchaser, payment method, and available evidence. Then state the rule or expected process that was not met. A missing receipt, unapproved cabin change, personal charge on a company card, and purchase above a delegated limit are different exceptions even when they appear on the same report.
Avoid writing a defense before the facts are stable. The packet should let an approver see the transaction and policy question without searching email. Link the card record, itinerary, invoice, agenda, or attendee list in the approved expense system. Do not copy card numbers, passport details, or unrelated calendar content into the explanation.
Work a disrupted-trip exception
An executive’s flight is canceled after the final customer meeting. The approved travel tool shows no same-day options, and the traveler buys a higher-priced ticket directly from the airline to attend a board session the next morning. The original ticket later receives a partial credit. The expense report contains the replacement ticket but not the cancellation notice or credit status.
The assistant obtains the carrier cancellation record, original itinerary, replacement receipt, business reason for the timing, and evidence of the credit request. The packet distinguishes the fare increase caused by disruption from any voluntary upgrade. It identifies who may approve the policy exception and who must track the unused-ticket credit. The assistant does not label the entire amount “emergency travel” and leave accounting to infer the details.
If the direct purchase exposed personal data or bypassed a preferred vendor, note the operational issue without turning the expense review into a security investigation. Route any separate incident to its owner. The expense decision can proceed on verified financial facts while related remediation remains visible elsewhere.
Present a decision, not a narrative dump
The front page should state the requested treatment: reimburse, charge back, allocate to a project, use a documented exception code, or return for more evidence. Show the amount affected, policy reference, reason the normal process failed, prior similar exceptions when relevant, and the consequence of delay. Keep attachments in an order that supports the decision.
An approver may accept part of a claim and reject another part. Record each outcome at the transaction level. A short statement such as “approved because the carrier cancellation left no policy-compliant route to the fixed board session” is more useful than a generic approval. It explains the boundary without creating an unlimited travel exception.
When evidence cannot be recovered, follow policy rather than manufacturing certainty. The purchaser may provide an attestation, manager confirmation, or other approved substitute. The packet should say what is missing and why. An assistant should never recreate a receipt or edit an invoice to make the file look complete.
Keep roles distinct
The person assembling evidence need not be the person approving the exception. Finance owns accounting treatment and system controls. The budget owner confirms business purpose. A designated approver decides the policy exception within authority. The cardholder or traveler supplies facts. Separating these roles protects the assistant from becoming the de facto approver simply because they know the itinerary.
Executive status should not bypass review. It may change who holds approval authority, but it does not remove the need for evidence and a recorded decision. Apply the same factual standard while respecting confidential business context. A sensitive trip can use restricted access without disappearing from financial control.
Close the financial loop
After approval, verify that reimbursement, card coding, tax treatment, project allocation, and vendor credits agree with the decision. An approved exception can still produce a duplicate reimbursement or leave a credit unused. Assign those follow-ups before closing the packet.
Analyze patterns by cause. Frequent direct bookings may show that the approved tool lacks inventory. Repeated missing itemization may trace to one vendor. Late submissions may reflect an unclear handoff during travel. Fixing the process is more valuable than repeatedly documenting the same exception, and it avoids using the packet as a record of individual blame.
Set a closure deadline for credits, reimbursements, and corrected postings that outlive the original approval. These items can disappear once the executive’s report is marked complete. Finance should retain ownership until the ledger reflects the expected result, while the assistant keeps only the operational reminder needed to follow up. If the value cannot be recovered, record the final treatment and authority rather than leaving an indefinite open note.
Compare the exception with the nearest compliant choice
An approver needs to know what the employee could reasonably have done instead. For a last-minute hotel above policy, compare the booked rate with available compliant rooms at the time of booking, including distance and cancellation terms. A cheaper room that would have stranded the traveler after a late meeting is not a meaningful alternative. Preserve the contemporaneous search or booking record rather than recreating prices weeks later.
Patterns matter, but they should be attributed carefully. Repeated late bookings may reflect poor traveler planning, a manager who confirms trips too late, or a policy ceiling that no longer matches the market. Code the cause only after reviewing the surrounding events. Then choose the right correction: coaching, earlier approval, a revised market cap, or a negotiated supplier rate. The packet should close with the accounting treatment and any repayment or tax question routed to the proper owner. Approval of the business reason does not automatically settle how finance must record the expense.