Who knows what in expense reimbursement, and where the gaps cause trouble

The claimant knows why money was spent. The approver knows whether the trip or purchase made business sense. The expense auditor knows the policy wording. Tax staff know what evidence a deduction needs. Payroll knows what is owed back. Trouble starts where each assumes another has checked.

The claimant holds the context

Only the person who spent the money knows what actually happened. They know who attended the dinner and why the hotel was more expensive than usual. They also know the taxi was really two journeys on one receipt.

Very little of this reaches the claim. Expense tools ask for a category and an amount. They rarely ask the question that would settle a dispute later. So the claimant picks the nearest category, attaches whatever receipt they kept, and moves on. Months afterwards, nobody can reconstruct the story, including the claimant.

Approvers see the person, not the policy

A line manager approving a claim knows the employee, the project and whether the trip was needed. That is real knowledge, and finance cannot replace it.

What approvers usually lack is a working grasp of the rules. Most have never read the expense policy past the first page. They approve on trust, often in batches, often from a phone. When a claim breaks a limit, they assume finance will catch it. Finance, meanwhile, assumes the manager looked. Each side treats the other as the control.

Approval limits make this worse when they are set by grade and never revisited. A senior approver may sign off spending they have no visibility of, simply because the system routes it to them.

The auditor sees the receipt, not the reason

The expense auditor or accounts payable clerk knows the policy in detail. They spot missing receipts, duplicate submissions and meals claimed on days the person was not travelling.

But they cannot judge business purpose. A conference fee looks fine on paper even if the employee went for personal reasons. When the auditor queries something, the answer often comes back from the claimant with the manager's blessing, and the auditor has no grounds to push further. Many auditors quietly stop querying the things they know they will lose.

Tax data depends on what was captured at the point of sale

Recoverable sales tax and VAT need a valid tax invoice, the supplier's registration details and a correct split between goods and service charges. Tax specialists know this. Claimants and approvers generally do not.

The gap shows up long after payment. A card slip gets accepted as a receipt. Recoverable tax is lost, or claimed without support and later disallowed. Some expenses also carry personal tax consequences for the employee, such as certain meals, mileage above approved rates, or gifts. Those need reporting through payroll. If the category chosen at submission was wrong, the reporting never happens.

Personal accounts and the money nobody is chasing

Advances, personal charges on corporate cards and overpayments all create balances an employee owes back. Payroll or a cards team usually holds these. The claimant may have forgotten them entirely. The manager almost never knows they exist.

Trouble surfaces when someone leaves. An outstanding advance or an unreconciled card sits on a personal account, and the leaver's final pay has already been processed. Recovering it after that point is awkward and frequently abandoned. HR knows about the departure first, but the people holding the open balance tend to learn of it late.

Policy owners write for cases that rarely arrive

Whoever owns the policy, often a finance controller working with HR, knows the intent behind each rule. They know why the hotel cap exists and what the mileage rate was meant to cover.

They seldom see the daily exceptions. Frontline staff build workarounds for situations the policy never imagined, such as travel to high cost cities or client entertainment abroad. These workarounds become the real policy. When the written version changes, the informal one carries on unchanged, because no one told the auditors which exceptions are now allowed and which are not.

Questions to ask the people who run it

The documented flow and the lived one tend to diverge. These questions help find where.

• When a claim breaks a limit, what actually happens to it, and who decides?
• Which policy rules are routinely waived, and who agreed to that?
• How does an approver know what they are approving beyond the total?
• What does the auditor do when the business reason seems weak but the paperwork is complete?
• Who checks that a receipt supports tax recovery, and at what point?
• How do expenses with personal tax consequences reach payroll?
• When an advance is paid, what triggers its settlement, and who follows up if nothing comes back?
• Who hears first when an employee with an open card or advance is leaving?
• Which claims get paid outside the normal system, and why?
• What do claimants most often get wrong, and has anyone told them?

The answers usually reveal that one role is carrying a check that everyone else believes sits somewhere else. That is where redesign effort pays off, more than in the approval workflow itself.

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.