Completing an expense claim takes just a few minutes, yet it can take days to reach payment. A receipt is missing, the business purpose is unclear, the cost center is incorrect, or the need for additional approval only emerges during the finance review. The claim is returned to the submitter, then passes through the checkpoints again. Meanwhile, everyone involved has to pick up where they left off.
The reduction of rework therefore involves more than simply tightening controls. When fine-tuning existing business processes, we need to examine where errors originate, when they become detectable, and why they are only identified later. The aim of workflow optimization is to ensure that, wherever possible, the next person receives a case they can process, rather than another task requiring clarification.
1. A returned claim is a symptom: identify the root cause
A request for missing information arises when data, documents or explanations needed to move forward must be obtained after submission. Rework occurs when this requires a previously completed activity to be repeated in part or in full. A missing attachment can therefore create more than just the extra work of uploading it: it may trigger another finance review and even a further management decision.
Use the process assessment to compile a specific list of errors. Do not stop at saying that “many expense claims are incorrect.” Review completed and returned cases, then group the problems:
- Missing data: the cost center, date or business purpose has not been provided.
- Document errors: the receipt is missing, illegible or belongs to a different item.
- Content discrepancies: the amount, currency and details in the attached document do not match.
- Process errors: the case is routed to the wrong approver, or an additional requirement is identified too late.
For each error, record where it originates and where it is detected. If submitters regularly misunderstand the same thing, the underlying cause is likely a shortcoming in the form, guidance or policy rather than individual carelessness. This calls for a different intervention than a one-off mistake.
2. Mandatory fields only help when supported by clear rules
Mandatory fields are an obvious way to prevent omissions, but a completed field does not necessarily contain usable data. Entering “meeting” in the business purpose field, for example, may be technically acceptable while providing little information for the approver. Field labels therefore need to be accompanied by brief guidance and specific expectations.
Plan checks at three levels. Format validation checks data types and permitted values. Consistency checks assess whether the data agrees across fields. Business validation supports assessment against organizational rules. These checks do not replace one another: a correctly entered amount may still represent an expense that breaches policy.
Not every field should be mandatory in every situation
Tailor requirements to the expense type. A travel expense claim may require different information from an office supplies purchase. Unnecessary fields can encourage placeholder entries and workarounds. Every mandatory requirement should have an identifiable business reason and an owner.
For attachments, do not merely check whether a file has been uploaded. Make it clear which documents are required for each item and what quality standards apply. For claims with multiple items, receipts should be linked to individual items; otherwise, the reconciliation work falls to finance. The presence of a file does not prove that its content meets the requirements.
3. Place checks where compliance can already be determined
Checks performed too late are costly, while checks performed too early can obstruct work. When saving a draft, for example, a missing attachment may be perfectly reasonable. At submission, the same omission is a valid reason to stop progress. The placement of checks should therefore be determined by the purpose of the work stage, not by technical convenience.
In an expense claim workflow, the following allocation may be appropriate:
- During completion: immediate feedback on incorrect formats, invalid selections or conflicting data.
- At submission: checks on mandatory data, required attachments and basic consistency.
- Before management approval: ensuring that the information needed to assess the business justification is available.
- Before financial processing: checks against the financial and supporting-document requirements defined by the organization.
A handover criterion clearly defines when a case is ready for the next person to process. It is more than a “next” button: it is a shared agreement between the person handing over the case and the person receiving it.
When designing an xFLOWer-based process, link these criteria to tasks, status transitions and responsibilities. The specific rules must be tailored to business operations and the available system integrations. Checks that the system performs reliably should not be repeated unchanged by every person involved.
4. Make corrections targeted, rather than restarting the entire process
Not every error can be prevented. Reducing rework therefore also means designing the return path. Instead of a comment saying “incorrect, please fix,” give the submitter itemized, actionable feedback: which data or document is problematic, what correction is expected, and what happens next.
The amount on the receipt attached to the second item is illegible. Please upload a legible copy for this item. You do not need to re-enter the other details of the expense claim.
After a correction, repeat only the checks affected by the change. If the amount, cost center or business purpose changes, a new approval may be needed. Uploading a more legible copy of a document with unchanged content may warrant different treatment. The rule for this must be established in advance, rather than left to the case handler’s decision at the time.
Change traceability is also important: who corrected what and when, and which data informed each decision. Exceptional cases should have a separate route, with a designated owner and a documented justification. Otherwise, rigid checks may encourage people to handle cases by email, outside the system.
5. Measure errors, correction effort and waiting time separately
A reduction in the number of returned submissions does not, on its own, prove improvement. Submitters may be spending longer struggling with the form, or problems may be resolved outside the process. It is therefore worth tracking several complementary metrics.
- First-time-right rate: the proportion of cases closed without requests for missing information among all cases closed during the period.
- Number of correction rounds: how many times an expense claim was returned for correction.
- Correction effort: how much active work was required to supply missing information and repeat the review.
- Waiting time due to missing information: how much time elapsed between returning the claim and its resubmission.
- Breakdown of error causes: which omissions cause the most repeated work.
Use consistent definitions and similar case types for comparisons. For example, examine simple and complex expense claims separately, as changes in the case mix can produce misleading results. Status-change timestamps alone are not sufficient to determine active working time.
The purpose of measurement should not be to rank people by their mistakes. Instead, identify which rule, field or handover point could be changed to prevent the most unnecessary rounds.
6. Refine the existing process in small steps
There is no need to overhaul the entire expense management system at once. Select a common error, clarify its root cause, then modify one clearly defined element. This could be a conditionally required attachment, clearer field guidance or a pre-submission consistency check.
Test the change on a limited scale first. Involve submitters, approvers and finance staff who process the claims. Check both standard and exceptional cases, then compare the results with the baseline. If the check blocks too many valid cases, it needs refinement.
In summary: lasting improvement rests on clear input requirements, well-placed checks and a targeted correction path. This enables the workflow not merely to route tasks, but also to help prevent recurring errors.
Would you like to identify where avoidable rework occurs in your company? Speak with xFLOWer experts about reviewing an existing process. Start with the most common reasons for missing-information requests and identify intervention points whose impact can be measured and tracked.
This article is part of our comprehensive guide: Business process optimization: a complete guide to improving existing workflows
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
