How-to: Submit a Clean Expense Report the First Time
Finance does not reject expense reports to annoy you. They reject incomplete receipts, wrong cost centers, out-of-policy items, and mystery merchants. A clean first-try report is a courtesy to approvers and a gift to your future self when audit questions arrive months later.
Time box: 20 minutes end-to-end once receipts are gathered (longer if you are catching up a whole trip). Do it within your company’s deadline, ideally within a week of the spend.
Ground yourself with finance for non-finance managers and how invoices and AP/AR work so you understand why coding and dates matter. New hires: check the New hire hub for card and policy links from onboarding.
When to use / when not
Use when:
– You have out-of-pocket or corporate-card expenses to file
– Policy allows the category (travel, client meal, software, etc.)
– You can attach proof that meets company rules
Do not use when:
– You are trying to expense personal spend “because everyone does”
– Alcohol, gifts, or client entertainment need pre-approval you never got
– You lack receipts and plan to invent amounts (do not)
– The spend needs a PO or vendor onboarding instead of an expense report
If unsure whether something is reimbursable, ask Finance or your manager before you buy when possible.
Prep
- Policy PDF or intranet page (per diem, mileage rate, meal limits, tip rules)
- Receipts: itemized when required (especially meals)
- Business purpose: who / what / why in one line
- Correct cost center, project code, or customer code
- Attendees list for meals (names and companies)
- Card statement if you need to match dates and amounts
Create a phone album or email folder named “Receipts – [Month]” so you are not hunting at month-end.
Steps
- Sort receipts (5 min). One expense per logical item. Split personal vs. business if the bill mixed them, per policy.
- Check policy hot spots (3 min). Meals over limit, hotel incidentals, rideshares to non-work locations, software subscriptions that need IT approval.
- Enter lines with purpose and code (7–8 min). Merchant, date, amount, category, cost center, business purpose. Attach the matching receipt to each line.
- Self-audit (3 min). Totals match receipts. Dates inside the trip. Attendees listed. No duplicate filings against corporate card and out-of-pocket for the same charge.
- Submit and note the report ID (1 min). Screenshot or save the confirmation.
- If rejected: fix the exact reason the same day. Do not argue in the rejection thread without reading the policy cite.
Managers approving reports should skim for purpose and policy, not rubber-stamp; see the New Manager hub.
Script (what to say / send)
Pre-approval ask (when required):
Can I get written OK to expense [item] for [business purpose] on [date], estimated [amount], cost center [code]? I’ll attach this approval to the report.
To Finance after a rejection:
Thanks – I’ll resubmit. Confirming you need [itemized receipt / attendee list / different GL code]. I’ll upload today and reply with the new report ID.
To a teammate who asks you to “just expense this for me”:
I can’t file spend I didn’t incur. Please use your own report or ask Finance about the right path (card / PO / reimbursement).
Output artifact
Clean Pass Checklist (run before Submit):
[ ] Every line has a receipt or allowed exception documented
[ ] Itemized meal receipts where policy requires
[ ] Business purpose on every line
[ ] Attendees listed for meals / entertainment
[ ] Correct cost center / project / customer code
[ ] Dates match travel or event
[ ] Amounts match receipts (tax/tip handled per policy)
[ ] No personal items
[ ] Pre-approvals attached if required
[ ] Report ID saved after submit
Optional: a monthly “expenses closed” note in your work log helps during reviews and promo packets.
Watch-outs
- Missing itemization. Credit card totals without line items fail many meal audits.
- Vague purposes. “Team dinner” is weaker than “Dinner with [Client] to review Q3 renewal.”
- Wrong codes. Mis-coded spend corrupts project margins. Ask rather than guess; P&L explained simply shows why managers care.
- Late filings. Old receipts get lost and may fall outside reimbursement windows.
- Sharing logins or filing for others. Creates compliance risk.
- Arguing policy on the report. Policy questions belong in a separate thread with Finance, not as a novel in the memo field.
Cross-functional travel (sales + solutions + CS) should agree who files what before the trip; how sales works and how departments work together reduce duplicate filings for the same client dinner.
If you travel often, batch receipts every Friday for twenty minutes instead of once a month. Small cadence prevents the “shoebox” problem and keeps business purpose fresh in your mind. For client meals split across sales and solutions, agree before dinner who files and which cost center pays so Finance does not receive two partial stories.
Approvers should reject politely with the policy cite, not with sarcasm. A clean reject teaches the filer; a vague reject creates repeat mistakes. Keep the tone boring and precise. That is how expense culture stays adult without becoming a gotcha game.
Done looks like: checklist all marked, report submitted once, approval without a bounce for missing docs.