An expense reimbursement process employees won't hate

Your best engineer fronted $1,400 for a conference flight and hotel in March. It's now May, and she's quietly asked the office manager twice where her money is. That delay isn't a paperwork problem—it's a trust problem. When people spend their own cash to do their job, every day you make them wait sends a message about how much you value them.

Slow, vague reimbursements cost you in two places at once. The first is morale: nobody should have to float a loan to their employer, and the people who do remember it. The second is your books. When expense submissions arrive as a pile of mismatched receipts with no clear coding, your bookkeeper guesses, and guesses turn into a messy general ledger—the master record of every dollar your company spends—that nobody fully trusts at tax time.

The good news: a process that fixes both problems takes an afternoon to set up. You need four things to be boringly predictable—how people submit, what they must attach, who approves, and when they get paid.

Make the process predictable, not perfect

Pick one submission method and ban the rest. Whether it's a tool like Expensify or Ramp, a shared form, or a single email inbox, the rule is that requests go to one place. The moment expenses can arrive three different ways, half of them get lost and your team learns that the system is unreliable.

Then lock down the other three pieces so nobody has to wonder how it works:

• A required receipt or invoice for every line—no receipt, no reimbursement, no exceptions that quietly become the norm.
• One clear approver per request, usually the person's manager, so it never sits in limbo because three people each assumed someone else owned it.
• A predictable pay cadence—reimbursements go out with the next regular payroll run, so people can plan around a date instead of chasing a check.

That last point matters more than it sounds. "You'll be paid with the next payroll" turns an open-ended wait into a known one, and known waits don't breed resentment.

Use an accountable plan so the money stays tax-free

Here's a detail most founders miss. The IRS treats employee reimbursements as taxable wages unless you run them under what's called an accountable plan—a simple set of rules that keeps the money non-taxable to your employee and fully deductible to you.

An accountable plan has three plain-English requirements. The expense must have a real business purpose. The employee must substantiate it—meaning prove it with a receipt, the date, the amount, and what it was for. And any excess advance must be returned. Miss those, and that $1,400 flight could land on your employee's W-2 as income they owe tax on, which is a miserable surprise to hand someone. The "required receipt" rule above isn't bureaucracy; it's what makes the whole thing tax-free.

Cut the reimbursements you don't need

The cleanest reimbursement is the one that never happens. Company cards—physical or virtual—move the spending onto the business directly, so the money never leaves your employee's pocket in the first place. Give a corporate card to anyone who travels or buys software regularly, and you eliminate most reimbursement requests outright.

Cards also fix the float problem at its root. Your salesperson on the road isn't lending the company $3,000 a month and waiting to get it back—the company pays from the start. Pair the card with the same receipt rule and you keep clean records without the back-and-forth.

Code costs to what they actually are

On the bookkeeping side, there's one rule that saves you every quarter: code each reimbursed cost to the real expense account it belongs to. A reimbursed flight is travel. A reimbursed client lunch is meals. A reimbursed app subscription is software. Never dump everything into a vague "reimbursements" bucket.

Why it matters: that catch-all bucket hides where your money actually goes. When you want to know what you spent on travel last quarter, or your accountant needs to separate meals (often only partly deductible—check current rules with your advisor) from fully deductible costs, a "reimbursements" line tells you nothing. Coding to the real account means your P&L—the profit-and-loss statement that shows what you earned and spent—reflects reality.

Finally, write a one-page spending policy so approvals aren't guesswork: what's reimbursable, any per-category limits, and what needs pre-approval. The whole system works because everyone—spender, approver, and bookkeeper—already knows the answer before the question comes up.