When an employee pays out of pocket for a business expense — a flight, a client dinner, a software subscription — your company owes them money back. Simple concept. But the process of collecting receipts, verifying expenses, getting approvals, and actually paying people back is surprisingly painful for most companies.
This guide covers everything you need to build a reimbursement process that's fast for employees, auditable for finance, and scalable as your team grows.
The Real Cost of Manual Expense Processing
Before fixing the process, it helps to understand what the broken one is actually costing you.
These numbers add up fast. A 50-person company where each employee submits just two expense reports a year is processing 100 reports — at $58 each, that's $5,800 in hidden administrative cost before anyone touches payroll.
The 5 Components of a Good Reimbursement Process
1. A clear expense policy
Before you can approve or reject expenses, employees need to know what's allowed. A good expense policy covers:
- Which expense categories are reimbursable (travel, meals, software, etc.)
- Per-category limits (e.g., meals capped at $75 per person)
- Receipt requirements (required for expenses over $25)
- Submission deadline (within 30 days of the expense)
- Approval chain (who approves what)
Keep the policy short. A two-page document people actually read is better than a twenty-page document nobody opens.
2. Receipt collection
The most friction in any reimbursement process is receipts. Employees lose them. Finance chases them. Reports get delayed for weeks over a $12 lunch receipt.
Best practice: Ask employees to photograph receipts immediately after the expense — before they leave the restaurant or close the browser. A photo of a receipt taken in the moment is infinitely better than a frantic search three weeks later.
Modern tools like GreenLight let employees upload receipt photos directly to each expense line and use AI to automatically extract the amount, date, and vendor — eliminating most of the manual typing.
3. Expense categorization and GL codes
Every expense should map to a category in your chart of accounts. This matters for two reasons: tax reporting and budget visibility. Common categories include:
| Category | Typical GL code | Examples |
|---|---|---|
| Travel | 6200 | Flights, hotels, rental cars |
| Meals & Entertainment | 6201 | Client dinners, team lunches |
| Office Supplies | 6202 | Stationery, printing, equipment |
| Software & Subscriptions | 6203 | SaaS tools, cloud services |
| Professional Development | 6204 | Courses, conferences, books |
4. A structured approval workflow
One of the most common mistakes small companies make is having no formal approval step — expenses go straight from employee to accounting. This creates two problems:
- Finance catches policy violations too late (after money is already out)
- There's no business justification attached to the expense
A two-step approval process — manager review first, finance sign-off second — catches most errors before they become payments. See our guide to building an approval workflow for details.
5. Fast payment
The most overlooked part of reimbursement is the actual paying back. Employees who wait three weeks to be reimbursed for a $500 flight feel undervalued — and they're right to. Aim for:
- Under 5 business days from final approval to payment
- Include reimbursements in the next regular payroll cycle
- Send a confirmation email when payment is processed
Manual vs. Automated: What's the Difference?
| Manual (email + spreadsheet) | Automated (dedicated tool) | |
|---|---|---|
| Submission | Employee emails receipts to manager | Employee uploads via app, AI reads receipt |
| Review time | 2–5 days (email back-and-forth) | Same day (approval dashboard) |
| Error rate | ~19% of reports | ~3% (validation at submission) |
| Processing cost | ~$58 per report | ~$6–10 per report |
| Reimbursement wait | 14–21 days | 3–5 days |
| Audit trail | Email threads (fragile) | Immutable activity log |
| Accounting export | Manual re-entry | One-click CSV or QuickBooks push |
Common Mistakes to Avoid
No receipt threshold
Requiring receipts for every $3 coffee creates friction without meaningfully reducing fraud. Set a threshold ($25 is common) below which no receipt is required.
Approval chains that are too long
A $50 cab ride shouldn't need sign-off from three people. Match the approval chain to the dollar amount. Small expenses: manager only. Large expenses: manager + finance director.
Late submission deadlines
Allowing employees to submit expenses from six months ago creates accounting headaches. A 30-day submission window is standard — 60 days for travel-heavy roles.
No feedback on rejections
If finance rejects an expense with no explanation, employees don't know what to fix. Always require a reason for rejection. Better yet, build it into your workflow tool so the reason is mandatory.
Getting Started
If you're still processing expenses by email and spreadsheet, the good news is that switching to a structured system is simpler than it sounds. Most teams are up and running in under an hour:
- Set up your expense categories and GL codes
- Add your team members and assign roles (employee, approver, finance)
- Employees start submitting — the system guides them through each step
- Approvers review in a dashboard instead of an inbox
- Finance exports to accounting with one click
Try GreenLight free for 60 days
No credit card required. Set up in minutes. Your team can submit their first expense report today.
Start Free Trial →Statistics sourced from GBTA Foundation, SAP Concur Research, and Aberdeen Group expense management studies. All figures reflect industry averages for SMBs with 10–500 employees.