Expense Reimbursement Process: From Claim to Payment

An expense reimbursement process turns an employee's claim and supporting evidence into an approved amount, a recorded payment and a reconciled claim. It normally covers submission, evidence and policy checks, approval, payment and record retention.

The process answers one practical question: what does the organisation owe this employee, and can it show how it reached that figure? The answer is not always the total printed on the receipt. Four amounts must remain distinct:

• Receipt total: the full amount shown by the source document.
• Amount claimed: the portion the employee asks the organisation to repay.
• Amount approved: the portion authorised after evidence, payment-source and policy checks.
• Amount reimbursed: the amount actually paid to the employee.

Suppose a receipt totals £126, including a £16 personal item. The employee claims £110. A £100 policy cap then reduces the approved amount to £100, which is paid in full. The claim record should retain all four figures, not replace the receipt or claimed amount with the final £100 payment. That history explains both reductions without forcing a later reviewer to reconstruct them from messages or bank entries.

Even where every figure is identical, each represents a different event. A receipt is evidence of a transaction. A claim is the employee's request. Approval creates an authorised payable. Reimbursement records settlement. Reconciliation confirms that the payment and the approved claim agree, or documents why they do not.

Document capture can supply facts such as merchant, date, currency and total, but it does not establish that the cost had a business purpose, complied with policy or should be reimbursed. Tax treatment and VAT recovery are separate judgements again. Keeping those decisions separate prevents a clean-looking receipt from becoming an automatic payment instruction.

Build one reviewable record from the claim and its evidence

A useful claim-review work file is organised around the decisions finance must be able to reconstruct. It needs to connect the claimant, business purpose, payment source and supporting documents to the amounts under review. The exact columns can follow the organisation's process, but the relationships should not depend on filenames, inbox threads or a reviewer's memory.

Give the claim a stable reference when it enters the process. Use that reference on its claim lines, evidence, approval and eventual payment record. If the employee submits three receipts, all three can sit under one claim while retaining their own merchant, transaction date, currency and receipt total. If one hotel receipt covers accommodation, meals and a personal charge, its separate claim lines should all point back to that same source rather than becoming detached figures.

At claim level, keep the employee, submission date and overall status. At line level, preserve the facts needed to decide the amount owed:

• the business purpose and relevant project, client or cost centre;
• the source document and the page on which the transaction appears;
• the payment source, such as the employee's own card, cash or a company-funded method;
• the original currency, receipt total and amount claimed; and
• any relationship between the line and another line, receipt or prior payment.

This structure also handles less tidy cases. A single claim can contain purchases in several currencies without replacing original values with converted ones. One receipt can support several claim lines, and several receipts can support one line, provided the link between the evidence and the figure remains explicit. The exchange rate, converted amount and rate date then become review facts rather than silent changes to the receipt.

For a small batch, a reviewer may enter these facts directly. For a recurring or larger batch, it can be useful to turn receipts into an Excel spreadsheet or otherwise prepare receipt data for expense review before applying policy checks. Invoice Data Extraction converts receipts and expense claims into structured Excel, CSV or JSON data and includes source file and page references for checking. The resulting file prepares document facts for review; it does not determine business purpose, establish eligibility, approve the claim or make a payment.

Keep the source document with the record even after its facts have been entered. An extracted total without its receipt is difficult to challenge, while a receipt without a claim reference is difficult to place. Both need to remain connected to the employee's request and to the decision made from it.

Identify who paid before deciding who is owed

A receipt proves that a transaction occurred, but it may not show that the employee funded it. Payment source determines whether the transaction can create an employee payable.

Payment source	Finance treatment
Employee's personal card or cash	Review as a possible out-of-pocket reimbursement
Company card	Record and reconcile company-card transactions separately
Company bank account or centrally booked travel	Record the company-paid cost, with no employee reimbursement
Cash advance	Compare eligible spending with the advance and settle only the balance

Capture the payment source on the claim line and retain whatever supports it. That might be the receipt's card suffix, a company-card statement, an advance record or confirmation from the claimant. A document should not default to employee-funded merely because it arrived with an expense claim.

This is where a common duplicate begins. An employee attaches a restaurant receipt to a claim, while the same transaction is already waiting in the company-card feed. If the claim is approved from the receipt alone, the organisation both pays the card issuer and reimburses the employee. Matching the receipt's date, merchant and amount against company-funded transactions before approval stops the second payment without treating the receipt itself as suspect.

Already-reimbursed costs need the same treatment. A resubmitted receipt, a copied claim line or an expense previously paid outside the normal run should retain its earlier claim or payment reference. Marking it as previously settled is more informative than deleting it, because the retained relationship explains why no new amount is owed.

Where the payment source cannot be established, keep the line open for clarification. Do not turn uncertainty into a payable by assumption. The claim can continue through review on its other facts, but the amount owed remains unresolved until finance knows whether the employee, the organisation or a third party supplied the funds.

Record policy checks and adjustments without rewriting the claim

Policy review compares what the employee claimed with what the employer has agreed to reimburse. The reviewer needs the business purpose, permitted cost type, spending limit, required evidence and any approval condition that applies to the line. A mathematically correct receipt can still produce a lower approved amount, but the review should never erase the employee's original request.

Record adjustments as movements from the claimed amount to the proposed approved amount. Each movement needs a value, a reason and the reviewer responsible. For example, a £74 meal claim subject to a £60 policy limit should retain £74 as the amount claimed, record a £14 policy adjustment and show £60 as the amount proposed for approval. Replacing £74 with £60 loses the explanation and makes it appear that the employee never claimed the difference.

Mixed personal and business spending follows the same principle. Keep the full receipt total as a source fact, identify the portion the employee claimed for business, then record any further review adjustment separately. If a £120 receipt includes £30 of personal spending, the receipt total remains £120 even when the employee correctly claims only £90. The personal portion is part of the reconciliation between evidence and claim, not an error to remove from the record.

Missing or incomplete evidence is a decision point, not a reason to invent a document. Note what is absent, what alternative evidence was supplied, which policy exception applies and who accepted or rejected it. A card or bank statement may help show that a payment occurred, but it does not automatically prove the business purpose or satisfy every tax or VAT evidence requirement. If finance holds the line pending more information, preserve the amount claimed and record the reason for the hold.

One claim may therefore contain different outcomes:

• a line approved in full because the evidence and policy checks agree;
• a line reduced to a policy limit;
• a mixed-cost line approved only for its business portion;
• a line returned for missing business purpose or evidence; and
• a line rejected because the organisation did not owe the cost.

These decisions establish the employer's reimbursement position. Whether a reimbursement is exempt from tax, reportable to HMRC or supported for VAT recovery requires its own accounting and tax assessment. Those treatments should refer to the same claim evidence, but none should be inferred solely from an approval to repay the employee.

Approval establishes the amount payable

Approval is the point at which a reviewed figure becomes an authorised amount payable. It is not proof that the employee has been paid. Record the approver, approval date and amount approved, together with any condition that must be met before payment.

An expense claim approval workflow works best when each person answers a different question. The claimant confirms that the spending and business purpose are theirs. A line manager or budget owner confirms that the spending was necessary and belongs to the relevant budget. Finance checks the evidence, payment source, policy treatment, arithmetic and accounting information. A small organisation may combine roles, but the record should still show which checks were performed and who authorised the payable.

To process employee expenses without losing control of the claim:

1. Register the claim under a stable reference and retain the original amount claimed.
2. Check its supporting evidence, business purpose and payment source.
3. Record policy decisions and adjustments at line level.
4. Submit the resulting amount for approval by the appropriate authority.
5. Lock or version the approved figure before it enters the payment run.

Status labels should describe real operational differences. Submitted can mean the employee has finished the claim, while under review means finance owns the next action. Returned for information identifies a claimant action, and partially approved distinguishes a claim with some approved lines from one still awaiting a full decision. After authorisation, approved, scheduled for payment, paid and reconciled refer to different events. An organisation needs only the statuses that affect ownership, control or reporting; a long taxonomy adds nothing if every label triggers the same action.

Partial approval should remain visible at line level. If four lines are accepted and one needs more evidence, finance can approve the four only if its policy permits separate settlement. The claim record then shows which amount is payable now and which amount remains unresolved. It should not present the whole claim as fully approved or overwrite the held line with zero.

If the amount changes materially after approval, record an amendment and obtain reapproval at the appropriate authority level. Editing the approved figure in place severs the connection between the decision the approver made and the payment finance later releases.

---

Pay the approved amount and reconcile it to the same claim

When an approved claim enters a payment run, add the payment method, date, reference and amount reimbursed to the existing claim record. An entry on a separate bank-payment list is not enough unless it can be traced back to the claim reference and approved amount.

Reconciliation compares the amount reimbursed with the amount approved. If both are £100, and the bank confirms the payment under the recorded reference, the monetary part of the claim can close. If they differ, the difference needs its own explanation rather than a status change that hides it.

Common reconciling items include:

• Partial settlement: £100 was approved but only £60 was paid, leaving £40 outstanding.
• Combined payment: one £240 bank transfer settles several approved claims, so the payment record must allocate the £240 across their claim references.
• Payment in instalments: several transfers settle one claim, requiring each payment to remain linked until their total reaches the approved amount.
• Returned or rejected payment: the payment instruction was issued but the employee did not receive the money, so the claim remains unpaid.
• Correction: the wrong amount was paid and a supplementary payment or recovery is recorded separately.

This relationship is the basis for how to reconcile employee expense reimbursements. Do not assume one claim equals one bank transaction. Use the claim-to-payment allocation to prove that every approved pound was settled once, whether the payment pattern is one-to-one, one-to-many or many-to-one.

Already-paid amounts should remain visible during later payment runs. A claim imported twice, an employee's resubmission or a manually paid urgent expense can otherwise appear outstanding. The earlier payment reference lets finance exclude it for a reason that another reviewer can verify.

Once the reimbursement decision is established, finance can assign the nominal code, tax treatment and cost centre needed for the ledger. Teams that prepare this work in spreadsheets may categorise receipt and invoice expenses in Excel, but category assignment does not determine eligibility or change what the employee is owed. If the category or accounting treatment changes later, the approved and reimbursed amounts should remain intact.

Retain the route from evidence to payment

Expense reimbursement records should let a reviewer reconstruct the claim without access to the original claimant's inbox or the first reviewer's memory. The closed record is not just a receipt beside a bank line. It is the connected route from the employee's request through the decision and into settlement.

For each claim, retain the original evidence and the information that gives it meaning: the employee, business purpose, payment source, receipt total and amount claimed. Keep every adjustment with its reason, the amount approved, the approver and approval date. Complete the route with the payment date, amount reimbursed, payment reference and reconciliation outcome. An unresolved evidence or approval exception should remain visible with its owner and outcome.

Under HMRC's expenses and benefits record-keeping guidance, UK employers must keep records of employee expenses and benefits for three years from the end of the tax year they relate to. That requirement does not set the retention period for every accounting record or obligation connected with the claim. The employer's policy should account for any longer period required by other applicable rules, as well as any longer period it chooses for contractual, insurance or internal-control reasons.

A paid status alone does not make the record complete. Before closing a claim, check that:

• the original claimed figures and evidence are still available;
• payment source and business purpose have been resolved;
• adjustments and exceptions have recorded reasons and decisions;
• the approved amount has an accountable approver;
• the reimbursed amount is allocated to a confirmed payment; and
• the approved amount has been fully settled, or any remaining balance stays recorded as payable until it is formally resolved.

Where evidence remains missing but an exception was authorised, retain the exception rather than presenting the file as if the evidence had existed. Where payment failed, keep the claim payable until replacement payment is confirmed. A claim is closed only when its monetary balance has been settled or formally resolved and its decision history can be traced.