Why Expense Reports Get Rejected: The Hidden Cost of Rework

An employee submits a £68 expense for a client dinner. Finance notices that the business purpose is missing and sends a clarification request. The employee replies two days later.

Rejection and correction are different outcomes

An expense returned for correction may be entirely legitimate. It needs additional information before it can proceed.

A claim awaiting clarification may require a decision from a manager or another responsible person. A rejected claim, by contrast, has been found ineligible for reimbursement, either in full or in part.

These are outcomes of the process. To understand why work is being repeated, the company needs to identify the underlying errors.

Five types of expense errors

The first three categories often involve information employees can provide themselves. Better submission questions and validation can prevent some of these problems from reaching finance.

Approval exceptions are different. A system can identify a policy breach, but the authorized person must decide whether an exception is justified.

Likewise, a system can flag a possible duplicate without establishing that two submissions represent the same transaction. Finance must still examine the evidence before withholding or correcting a payment.

Mistakes are not evidence of dishonesty

An employee may submit a receipt twice, choose the wrong payment method or transpose digits.

Those errors should be corrected and recorded.

Suspected deliberate misrepresentation requires an appropriate investigation, not an automatic conclusion based on a software flag.

Where the additional work happens

Consider an expense with a missing business purpose.

A typical correction cycle

1. Finance reviews the submitted claim and identifies the missing information.
2. Finance contacts the employee.
3. The employee retrieves the information and responds.
4. Finance checks the answer and updates the claim.
5. The manager reviews the corrected information if a new decision is required.

If the missing information is collected before the employee confirms the claim, the later clarification cycle may be avoided.

The same applies to unreadable receipt images, missing project identifiers and information that does not match the supporting document.

Calculate the cost of rework, then identify what can be prevented

A company can estimate the cost using its own claim volume, additional handling time and staff costs.

Step 1: Calculate total rework

Suppose a 25-person company processes 40 employee expenses each month.

Twelve claims require correction. Finance spends an average of nine additional minutes on each, while employees spend seven minutes providing missing information.

Four of those claims also require five additional minutes from a manager.

Assume the following illustrative hourly employment costs:

Under these assumptions, correcting claims consumes three hours and 32 minutes each month, equivalent to £143 of allocated staff time.

Over 12 months, that would be £1,716 if the same pattern continued.

Step 2: Separate preventable corrections from judgment

Suppose nine of the 12 corrected claims involved missing information, unreadable documents or incomplete submission details.

The other three involved policy exceptions or questions requiring a decision from someone with authority.

The nine information-related cases account for:

The calculation applies the assumed average handling times to the nine information-related claims. One of these also required renewed approval after a correction. The other three manager reviews concerned cases requiring judgment.

That gives a theoretical upper bound of approximately £97 per month, or £1,167 per year, for potentially preventable rework.

It is an upper bound, not an expected saving. Employees still need to supply information, finance must still review claims, and some corrections will remain.

Step 3: Compare the opportunity with the cost of fixing it

For this company, the first response should be inexpensive:

1. Improve the submission instructions and ask employees for the information most frequently omitted.
2. Check whether the existing accounting or payroll software can collect those details in a structured way.
3. Consider a separate expense tool only if the remaining problem justifies its subscription, setup, administration and integration costs.

In this example, rework alone may not justify purchasing software.

The broader purchasing decision is covered in Employee Expense Management for Small Businesses: When Is Software Worth It?.

Keep payment errors separate

Incorrect reimbursements are a different category of risk.

A duplicate payment or reimbursement of a company-card purchase creates an actual cash outflow, not merely staff time spent correcting a claim.

One material payment error could outweigh several months of administrative rework. It may also create recovery work and employee disputes.

Track the number and value of incorrect payments separately from the cost-of-rework calculation. Do not add the full amount of a recoverable payment to staff-time costs as though both represented the same kind of loss.

Two ways to process the same hotel expense

Consider a fictional 30-person engineering consultancy.

An employee submits a £124.50 hotel expense after visiting a customer site. The receipt is readable, but the project is not identified and the employee incorrectly records the payment as personal.

The hotel was actually paid using the company card.

Process A: Errors discovered after approval

Finance receives the claim and asks the employee which project it relates to.

The employee responds the next day. Finance updates the claim, and the manager approves it.

Later, while preparing reimbursement payments, finance matches the hotel charge to the company-card statement. The claim was incorrectly submitted as privately paid.

The planned reimbursement is cancelled.

Because the payment method and reimbursement entitlement are decision-relevant, the employee confirms the corrected claim and the manager approves the changed version.

Outcome: The expense remains a valid company expense, but the employee receives no reimbursement. The process required two clarification exchanges, two approval decisions and cancellation of a planned payment.

Process B: The payment consequence is made explicit

The employee sends a photo of the receipt, and the amount is read from it.

Before submission, the process requests the project and asks:

How was this expense paid?

• Company card: The company has already paid. No employee reimbursement is due.
• Personally: The employee paid and may be entitled to reimbursement.

The employee selects the company card and confirms the completed claim.

The manager approves it. Finance matches the transaction to the company-card statement before closing the record.

Outcome: One confirmed submission and one approval. There is no employee reimbursement to cancel.

Making the payment consequence explicit reduces the likelihood of the employee selecting the wrong option. It does not guarantee correctness. The card-statement reconciliation remains necessary in both processes.

Measure rework without rewarding weak controls

A submission completed in ten seconds is not efficient if finance must spend ten minutes repairing it.

Three measures provide a useful starting point:

Record the error categories alongside these measures. A rework rate of 20% is difficult to act on if the company cannot distinguish missing receipts from legitimate policy exceptions.

Rejection is not the same as rework

A falling rejection rate does not necessarily indicate improvement.

If managers stop challenging questionable claims, fewer expenses may be rejected while the quality of financial controls deteriorates.

A company with strict spending policies may also reject more claims than one with permissive rules.

Measure unnecessary corrections separately from legitimate approval decisions.

Improve the part of the process that creates the work

Once the most frequent errors have been identified, change the relevant submission questions, responsibilities or payment controls.

Some improvements require only clearer instructions or deterministic validation. They do not need artificial intelligence.

If the remaining problems justify evaluating software, use the four-question diagnostic and six vendor tests in Employee Expense Management for Small Businesses: When Is Software Worth It?.

Bea and expense-report corrections

Bea works on the first three error types. In Telegram, it asks for missing information before a claim can be submitted, including how the expense was paid: personally or with a company card. The employee confirms the claim, and the approver sees a possible duplicate flagged before deciding. Policy exceptions still go to a person with the authority to decide them.