Where expense reimbursement breaks: handoffs, exceptions and workarounds

Expense reimbursement usually breaks at the points where a claim changes hands: when an approver reads policy loosely, when receipts and tax details arrive incomplete, when advances go unsettled, and when personal spending lands on company cards. Each leaves a trace in returned claims, aged balances or side spreadsheets.

Policy that nobody reads the same way

Most trouble starts upstream of any claim. The written policy says what is allowed, but approval limits and category rules get interpreted locally. One manager treats client dinners as routine. Another wants a business reason attached to every coffee. Employees learn which approver is lenient and route claims accordingly.

The giveaway is inconsistency. Look at rejected and returned claims side by side. If the same type of expense is waved through in one department and challenged in another, the policy is not doing its job. Frequent questions to the finance inbox about whether something is claimable point the same way.

Approvals that sit in a queue

Approval is the handoff most likely to stall. Claims wait on a manager who is travelling, on leave or simply ignoring notifications. Delegation rules exist on paper but are rarely set up in the system. When a reporting line changes, claims can end up routed to someone who no longer manages the claimant.

Watch for claims approved in large batches by the same person, which suggests approval happens in bursts with little scrutiny. Escalations from employees chasing payment are another signal. So is finance staff approving on a manager's behalf because nobody else will.

Receipts and tax data captured too late

Tax treatment depends on details the claimant often does not think about: whether a receipt is a valid tax invoice, which jurisdiction the cost falls under, whether part of a meal or trip is personal. If these are not captured at submission, someone in finance has to reconstruct them afterwards, usually by emailing the employee.

This shows up as claims bounced back for missing or illegible receipts, and as manual adjustments to tax coding after approval. If reclaimable tax is routinely left unclaimed because the paperwork is too weak to support it, capture is failing at the source.

Advances that never quite close

Cash advances for travel or projects create a balance that should be settled against later claims. In practice, the settlement step is easy to skip. The employee submits a claim that ignores the advance, or returns unspent cash without anyone recording it, or leaves the company with money still outstanding.

An ageing list of open advances tells the story quickly. Advances that carry over period after period, or employees holding a fresh advance while an old one is unreconciled, mean the control has slipped.

Personal charges on company cards

Where corporate cards are issued, personal spending inevitably lands on them, sometimes by mistake and sometimes not. Managing these personal accounts means identifying the charge, getting the employee to acknowledge it, and recovering the amount through payroll deduction or direct repayment. Each of those steps depends on a different team, which is where it falls apart.

Unreconciled card transactions that sit unexplained are the clearest sign. Recoveries agreed by email but never actioned in payroll are another. If card statements are cleared by booking unexplained items to a suspense account, the problem is being hidden.

The spreadsheet beside the system

When the expense system cannot handle an exception, people build their own tool. A tracker of claims paid outside the normal run, a list of approvers who should be bypassed, a file of manual tax corrections. These workarounds keep payments moving but make the official record unreliable.

Ask to see any file the team keeps open while processing claims. Its contents usually reveal which exceptions the designed process never anticipated. Off-cycle payments made by bank transfer outside the scheduled run are a related warning.

Questions to ask the people who run it

The documented procedure and the daily routine often diverge. Conversations with processors, approvers and frequent claimants surface the gap faster than any process map.

• Which claims get sent back most often, and what is usually missing?
• When an approver is unavailable, what actually happens to the claim?
• Is there a list, formal or informal, of people whose claims are always checked more closely?
• How are tax details confirmed when the receipt does not show them?
• Who chases an advance that has not been settled, and what triggers the chase?
• When a personal charge appears on a card, who tells the employee, and who makes sure the money comes back?
• Are any payments made outside the normal run? Why?
• What spreadsheets or notes are kept alongside the system, and what would break if they disappeared?
• Which policy rules cause the most arguments?
• If one part of this could be removed tomorrow, which would it be?

The last answer is often the most revealing. People who process claims every day know exactly which step adds effort without adding control, and they rarely get asked.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.