Small Business

How to avoid rejected reimbursement claims with better receipts

Claims get rejected for six predictable reasons, and five of them are fixed at the moment of capture rather than at the moment of submission.

Written for whoever ends up chasing the team for missing receipts.

A rejected claim costs far more than the delay suggests. The claimant resubmits, the approver reviews it a second time, finance reopens a closed period, and somebody spends twenty minutes on a £14 taxi. Do that forty times a quarter and the administrative cost exceeds the value of the claims.

Rejections cluster into six causes. The useful thing about that list is how early each one becomes unfixable.

1. The card receipt instead of the itemised receipt

The most common rejection by a wide margin. A restaurant hands over two pieces of paper: the itemised bill listing what was ordered, and the card slip showing only the total and the last four digits. People photograph the card slip because it is the one the server hands back with the card.

The card slip proves a payment occurred. It does not prove what was bought, which is the thing an approver needs when meals, alcohol, and entertainment are treated differently.

Fixed at capture. If the piece of paper does not list line items, it is not the receipt. Photograph both if you are unsure.

2. No business purpose recorded

A claim for "Lunch — £38.50" is not a claim, it is a transaction. The approver has no basis to approve or reject it and will ask, which is a rejection with extra steps.

Compare:

Lunch — £38.50

Lunch — £38.50 — Nakamura account kickoff, 3 attendees (J. Rhys, client x2)

The second takes eight seconds to write and never comes back. It also answers the question that gets asked eighteen months later during an audit, when nobody remembers the meeting.

Fixed at capture. The attendee list in particular is unreconstructable after about a week.

3. Submitted after the policy window

Most expense policies carry a submission deadline — thirty, sixty, ninety days. Claims submitted after it are rejected on process grounds regardless of merit, and these are the ones that generate genuine resentment, because the spending was legitimate.

This is a capture problem disguised as a discipline problem. Nobody consciously decides to sit on a receipt for sixty-one days. The receipt goes in a wallet, the wallet gets emptied, and the claim surfaces during a desk clearout.

Fixed at capture, by making same-day submission less effort than putting the paper in a wallet.

4. Duplicate submission

Two ways this happens, and only one is carelessness. The careless version: the same receipt is photographed twice and submitted in consecutive months.

The subtle version is worse. A team books a hotel on a company card, the traveller also photographs the hotel receipt, and the cost enters the books twice — once through the card feed and once through expenses. Nobody has done anything wrong, and the duplicate is invisible unless something is checking.

Fixed by tooling. Humans do not reliably spot a duplicate across a hundred-row month. Duplicate detection at the point of capture — flagging an image or merchant-date-amount combination already seen — is one of the few parts of this problem that genuinely needs software. Scan2Sheet flags repeat captures before the row reaches the sheet, which catches the first variety; the card-feed variety needs a reconciliation step where the card statement is matched against the claims for the same period.

5. Illegible or degraded image

Thermal paper fades. A receipt photographed in a dim restaurant, at an angle, with a thumb across the total, is a rejection waiting to happen — but it will not be rejected today. It gets rejected in six weeks, by which time the original has faded to a grey rectangle and no better evidence exists.

Three habits remove almost all of these:

  • Photograph flat, in the best light available, before leaving the premises
  • Check that merchant, date, and total are readable on the image, not on the paper
  • Capture the same day, because thermal degradation is measured in weeks for a receipt left in a car

6. Amount does not match the supporting document

Usually a transcription error — 41.50 typed as 14.50 — or a currency problem, where a traveller claims the amount printed on a foreign receipt rather than the amount their card was actually charged after conversion and fees.

The currency case is the one worth a policy decision. Claim the printed foreign amount and the converted figure will not match the statement; claim the card-charged amount and it reconciles but no longer matches the receipt. Pick one, write it in the policy, and record both numbers on the row so whichever an approver wants is present.

What this means for how you capture

Five of the six are decided at capture, not at submission. That is the actionable conclusion: approval workflows, however well designed, cannot recover information that was never recorded.

A capture step that meets all six looks like this, and takes under thirty seconds:

  1. Photograph the itemised receipt, flat and in good light, before leaving
  2. Confirm merchant, date, and total are legible in the image
  3. Add the business purpose and attendees while you still remember them
  4. Record the card-charged amount if the receipt is in another currency
  5. Submit now rather than later

Scan2Sheet handles steps two and four's mechanics — extraction, duplicate flagging, and the receipt image stored and linked from the row — but the business purpose in step three is yours. No tool can infer why a meal was a business cost.

For whoever administers the policy

Two changes do more than tightening the rules.

Publish the rejection reasons. Most people have never been told what a complete claim looks like. A six-line policy that says "itemised receipt, business purpose, attendees for meals, submit within 30 days" prevents more rejections than a two-page policy nobody reads.

Look at what actually gets rejected. If one reason accounts for most of your rejections, the fix is in the process, not the people. A spike in late submissions usually means capture is too hard. A spike in missing purposes usually means the field is buried in a form.

Pull your last quarter's rejections and sort them by reason. The distribution tends to be lopsided, and the biggest bar is usually something you can design out in an afternoon.