What share of expense claims arrive without usable receipts?

Question and scope

This review asks what share of expense claims arrive without a usable receipt and what a team can do about it. The unit is a claim submitted for reimbursement or client billing that lacks the documentation the reviewer needs. The scope covers routine business expenses handled by an assistant or a small operations team. The review does not estimate a universal rate, because the mix of card, cash, and mileage claims varies by organization and country.

The question matters because a missing receipt creates work that is invisible in the original claim. The reviewer has to ask for it, the traveler has to find it, and the payment waits. A small number of incomplete claims can consume a disproportionate share of the weekly reconciliation time. The useful measure is not only the count but the delay each one causes.

The review separates a missing receipt from an unusable one. A receipt can exist and still lack the merchant, the date, the amount, or the business purpose. A photo can be too blurry to read, or a card statement can show the charge without the detail. The claim is incomplete until the reviewer has enough to support the business purpose and the amount.

What counts as a usable receipt

A usable receipt shows the merchant, the date, the amount, the currency, and the items or service purchased. It should be legible and complete enough to match the payment record. For a client-billable expense, it should also connect to the client or project. A receipt that shows only a total may be enough for a small claim and insufficient for a larger or disputed one.

The IRS recordkeeping guidance for business expenses emphasizes supporting records that show the amount, the time, the place, and the business purpose. IRS Publication 463 applies the same idea to travel, meals, and gifts, with additional limits. These sources define a tax recordkeeping standard, not a universal company policy. A business may require more detail, but it should not require less than the law demands.

The business purpose is often the weakest field. A receipt proves that a purchase happened, not why it was necessary. Ask the claimant to write one sentence that connects the expense to the work. A purpose such as client lunch to review the renewal is more useful than a label such as meals. The reviewer can then judge the claim against policy.

Why claims arrive incomplete

The most common cause is timing. A receipt captured weeks later is harder to find, and the purpose is harder to recall. A traveler who is moving between meetings may photograph the receipt but never attach it to the claim. The gap is a process problem rather than a character flaw. A capture step at the point of purchase removes most of it.

A second cause is a mismatch between the claim tool and the payment method. The card statement may show a merchant name that differs from the receipt, or a foreign transaction may post in a different currency. The claimant may not know which document the reviewer needs. Clear instructions and a worked example reduce the ambiguity.

A third cause is the exception. A taxi driver who does not provide a receipt, a small vendor who writes a handwritten slip, or a cancelled flight with a credit rather than a refund all create a gap. The process needs a legitimate path for these cases. Without one, the claimant either gives up or invents a document, and both outcomes are worse than an exception.

The cost of rework and delayed reimbursement

An incomplete claim triggers a message, a search, a reply, and a second review. The direct time may be small, but the delay can push the claim past a card due date or a client billing cycle. The reviewer also carries the claim in memory, which adds to the invisible workload. A weekly count of rework makes that cost visible.

The claimant bears part of the cost through a delayed reimbursement or a personal cash flow gap. That experience shapes future behavior, and not always for the better. A traveler who waits a month for a legitimate claim may start avoiding small expenses or hoarding paper receipts. Neither response improves the record.

Client billing adds another layer. An expense that cannot be supported may be disallowed or written off, which turns a documentation gap into a margin loss. The team may also spend time reconstructing the charge from emails and calendars. A first-pass completeness measure should include the client-billable claims separately, because the cost of a miss is higher.

Controls that improve first-pass completeness

Move the capture step to the moment of purchase. Ask the traveler to photograph the receipt and add the business purpose before leaving the counter or the meeting. A mobile form with three fields is usually enough. The goal is to capture the two things that fade fastest, which are the paper and the reason.

Match the claim to the card feed before the claimant submits it. A pre-filled claim with the merchant, date, and amount removes typing and catches a missing charge early. The claimant only adds the purpose and the client reference. This design reduces both the effort and the number of fields that can be left blank.

Publish a short list of acceptable substitutes for a missing receipt, such as a bank record plus a written explanation, and name who approves them. Train the reviewer to apply the same standard every time. A substitute that is accepted for one claimant and rejected for another creates distrust and more exceptions. Keep the list short so it is easy to apply under pressure.

The legitimate missing receipt

Some expenses genuinely lack a receipt. A small cash purchase, a tip, or a foreign vendor without a receipt printer may qualify. The process should require a written explanation and a secondary record, such as a card or bank line. The approver should see the substitute and the reason in one place. The exception should be rare and visible.

Set a limit for receiptless claims and a separate approval for anything above it. Review the pattern monthly to see whether one traveler or one category produces most of the exceptions. A repeated exception is a sign that the process, not the person, needs a change. Adjust the intake or the payment method before adding more rules.

Record the exception in the same system as the claim so the history is visible to the next reviewer. Do not keep a separate side list that only one person can find. Name the approver and the expiry of the exception. A substitute that is documented is easier to defend than one that is merely remembered.

Review the approved exceptions at the end of the quarter and look for a category that has become common. A type of expense that repeatedly lacks a receipt may need a different payment method rather than a stricter rule. Change the method and measure the exception count again. The best control is the one that removes the need for the exception.

Method and limitations

This review describes a measurement and control method rather than a study of claim completeness at a specific organization. The sources define recordkeeping expectations, not a benchmark rate. The actual share of incomplete claims depends on the payment mix, the tool, the culture, and the type of expense. A team should measure its own claims before setting a target.

A completeness measure can also encourage behavior that looks good but hides risk. A claimant may attach a blurry photo to close the field, or a reviewer may accept a substitute to clear the queue. Sample the accepted claims, not only the rejected ones. The measure should reward a supportable claim rather than a complete-looking one.

Decision checklist

Define a usable receipt and a legitimate substitute in writing. Name the fields a complete claim needs, including the business purpose and the client reference. Put capture at the point of purchase and pre-fill from the card feed where possible. Set a limit and an approver for receiptless claims.

Measure first-pass completeness and the delay caused by rework. Sample the accepted claims as well as the exceptions. Review the pattern by traveler, merchant, and category. Change one part of the process and compare the count next month.