Expense Report Submission

ContextPer-meal limits, nightly hotel caps, and approved transportation categories change more often than most employees realize. A $75 dinner limit in effect last year may now be $55 — or may now require manager pre-approval for anything over $40. Spending three minutes reviewing the current policy before you start prevents building a report you'll need to rebuild. Pay particular attention to: alcohol reimbursement eligibility (often excluded entirely or capped separately from meals), receipt thresholds by dollar amount (many policies require receipts for anything above $25), and the process for handling personal charges that appeared on a corporate card.

ContextA hotel stay typically generates several expense categories from one payment: room rate (Lodging), parking (Ground Transportation), laundry (Personal — generally not reimbursable), room service or minibar (Meals, subject to policy), and incidentals. Accounting requires these split into separate line items; a single $480 'hotel' entry will be returned for itemization. Ask for the itemized folio at checkout — specify 'itemized' explicitly, since some front desks hand you a summary by default. If you've already checked out, call the hotel and ask them to email it; virtually every major hotel property will do this. Many chain hotels also send the folio automatically to the email on file — check your inbox before calling.

ContextPersonal expenses on a corporate card — a personal dinner, an in-flight entertainment purchase, a souvenir — are a policy violation if submitted as business expenses, even unintentionally. Before opening your expense tool, review every card transaction from your departure date through your return date and flag any personal ones. Most companies have a formal repayment process: a direct bank transfer to the company account, or a payroll deduction from your next paycheck. Handle this proactively before submission — accounting cross-checks card statements against submitted reports, and unexplained personal charges that surfaced weeks later look significantly worse than ones you flagged yourself.

ContextThe rate that applies is the rate on the day you spent the money, not the day you're submitting the report. Retrieve it from your credit card statement (which shows the exact converted amount charged, the most authoritative source), from XE.com's historical rate tool, or from OANDA's currency converter for that specific date. If your expense system handles conversion automatically, verify in the settings that it's using transaction-date rates — some default to the current rate unless configured otherwise. For significant amounts, even a 3–5% rate difference creates a discrepancy that accounting will notice and flag.

ContextThe receipts are completely legible the day you land. The categorizations are obvious. You remember which dinner was the client pitch and which was a solo meal between flights. One week later, a merchant name is unrecognizable. Two weeks later, the meal attendees are a blur. Three weeks later, you're submitting estimates and hoping accounting doesn't ask questions. Beyond accuracy: most companies have submission deadlines — often 30 or 60 days from the transaction date — and the deadline applies per transaction, not per trip. A three-week delay on a two-week trip can push the oldest expenses outside the eligible window entirely.

ContextA single entry for '$312 — meals and travel' will be rejected by any properly run accounting department. Every charge needs its own row with a specific category, the exact amount, the precise date, the vendor name, and a business purpose note. Hotel stays are the most common bundling mistake: the room rate, parking charge, and room service must each appear as separate lines, even if they appeared as a single total on your card statement. When in doubt whether to separate: separate. A report with too many lines is never rejected. A report with bundled lines always is.

ContextStandard corporate categories include: Airfare, Lodging, Ground Transportation (rideshare, taxi, train, rental car), Meals and Entertainment, Parking and Tolls, Mileage, Conference or Event Registration, Office Supplies, Client Gifts (subject to IRS limits — $25/person/year for U.S. tax purposes), and Other. When something genuinely doesn't fit: use Other, write a specific explanation in the Notes field (not 'miscellaneous' — something like 'Translation services for Seoul contract review'), and flag it for manager approval before submitting if it's above a significant threshold. A categorization question asked before submission takes two minutes. A rejection and resubmission cycle takes two days.

ContextBefore attaching a receipt photo, verify it shows: the vendor name, the date, the itemized charges (not just the total), and the final amount. A photo taken at an angle in dim restaurant lighting, or a merchant copy showing only the charged total without itemization, will come back for resubmission — the auditor needs to see what was ordered, not just what was paid. For digital receipts (emailed confirmations, in-app receipts from ride services): forward directly from your inbox to your expense tool or take a clean screenshot. For any receipt with information that's partially obscured, call the vendor and request a replacement — this is always faster than a rejection cycle.

ContextFor group meals: list every attendee with their full name, title, and company — not a headcount, not 'team,' actual names. The purpose must be specific: not 'client meeting' but 'strategy session with [Names] from Harwell Partners to review pilot scope ahead of April contract renewal.' For a solo meal during business travel: note the city, the trip dates, and the nature of the travel — 'Solo dinner in Singapore during 4-day regional onboarding visit, March 10–13.' These notes are what make an expense auditable at the line-item level. They protect you and your employer whether the review happens next month or in an audit two years from now.

ContextCheck four things: the report total matches the sum of all line items (data entry transpositions are common — '$158' entered instead of '$185' changes the total and triggers a mismatch with your card statement); all line item dates fall within the expected trip dates (an out-of-range date usually signals a wrong category assignment); every line above your company's receipt threshold has an attachment; and any expense that required pre-approval has documentation of that approval. If your expense tool offers a pre-submission validation check, run it and resolve every flagged item before submitting. A five-minute review eliminates the most common rejection reasons.

ContextReimbursement timelines are measured from manager approval, not from your submission date — and the chain typically runs: your submission triggers manager review, manager approval triggers accounting processing, and accounting processing triggers payment. Most companies have a defined window (typically 5–15 business days from accounting receipt). Know which step of the chain your report is currently on — most expense tools show this in a status view. The submission date you record is your reference point for when to follow up, not when to expect payment.

ContextCheck the status view in your expense tool first — it often shows exactly where the delay is. If the report has been sitting with your manager for more than five business days without approval: a brief message is appropriate and normal ('Hi [Name], just checking on expense report #[ID] submitted [Date] — anything I can help clarify?'). If it cleared manager approval but hasn't been processed by accounting: email accounting with your report number, submission date, and the manager approval date. Keep the message factual and brief. Most delays resolve within 24 hours of a polite follow-up.

ContextCopies stored only in your company's expense tool become inaccessible the moment your employment ends — and you may need them afterward. Your own records serve several purposes: unreimbursed business expenses may be deductible for self-employed individuals or in jurisdictions that permit employee expense deductions; records help resolve discrepancies between what you submitted and what was reimbursed; and a multi-year history of your travel and project spending is useful context in performance reviews, salary conversations, or role transition discussions. Store by year in a cloud folder you control.