Staff Expense Claims: Why a Receipt, Approval and Reimbursement Need Separate States

2026-10-24

A receipt upload should create evidence for an expense claim, not tell an employee that repayment is complete. Before commissioning an expenses tool, define who paid, what is being claimed, who can approve it and how the eventual reimbursement is recorded. Those decisions matter more than making a photograph appear instantly in a list.

This is workflow planning guidance. Your accountant or payroll adviser should review eligibility, tax treatment, record retention and payment arrangements. An app cannot establish those rules merely by offering an expense category.

Begin with who actually paid

An employee paying personally and an employee uploading a company-card receipt are different cases. Both may need a record, but only the first normally represents money the employee is asking to receive back. A shared upload screen must not turn every business purchase into a personal reimbursement claim.

Odoo's official expense-entry documentation illustrates this distinction with a Paid By choice between Employee (to reimburse) and Company. Its form also records the employee, expense date, category and amount. These are product-specific examples, not a compulsory form for every business.

For your brief, ask for the original amount and currency, purchase date, business purpose, payer and supporting receipt. If repayment uses another currency, have the conversion basis and rounding policy reviewed and show the resulting reimbursable amount separately. Do not silently replace the original receipt amount with a converted figure.

Keep capture separate from submission

Let employees correct a draft before submitting it. A readable receipt and an amount are not necessarily a complete explanation of the business purpose. Conversely, an image that is difficult to read should produce a request for clarification, not an unexplained disappearance from the list.

If the proposed tool reads receipt details automatically, require a review screen. Extracted merchant, date, amount and currency should remain editable before submission, with the original image available for comparison. This is an acceptance requirement, not a claim that automated extraction is always inaccurate or that a particular provider includes this review.

Also decide how to handle one receipt uploaded twice, several receipts supporting one claim, and a receipt containing both personal and business items. Odoo documents that multiple receipts can be attached to an individual expense. That does not mean every attachment should create another reimbursable amount.

Approval must identify what was accepted

The reviewer should see the submitted details and evidence together. Decide who can approve, who substitutes during absence, and how an employee's own claim avoids unreviewed self-approval. Keep access to receipts limited to the people who need them.

Distinguish a question from a refusal. “Please attach the missing page” should not look like a final decision that the expense is ineligible. Give the employee a visible next action and preserve the review conversation.

Odoo's processing guide describes restricted processing permissions, requests for missing information and a required reason when refusing an expense. Those examples support having an explicit review process; they do not define your organisation's employment policy.

If an approved amount, payer or receipt changes, specify whether a fresh approval is required. Do not let an approval of one version silently authorise a materially different claim.

Approved is not paid

Show approval and settlement separately. An approved claim may still await accounting review, inclusion in payroll or a separate transfer. Employees need to know which step is outstanding without being shown a misleading paid label.

Odoo's reimbursement documentation describes reimbursement through payslips or other payment methods. It also explains removing an expense from a future payslip if it has been repaid another way before that payslip is processed. The practical lesson is to coordinate settlement routes, not to assume a payroll flag proves a bank transfer has arrived.

For a custom workflow, record the intended payment route, the claim it settles, the amount and the confirmed outcome. A payment instruction, a manually recorded settlement and confirmation from an integrated payment system are different kinds of evidence. Agree which one justifies each status.

If an external payment request times out, preserve the uncertain operation and reconcile it before attempting another payment. Do not create a second reimbursement solely because the first response was missing. A receipt-approval tool need not initiate payments at all; an export and a controlled settlement-recording process may be sufficient.

Ask for a demonstration with awkward cases

Use fictional employees and receipts for the project acceptance tests:

A company-paid receipt does not create money owed to the employee.
A draft can be corrected without being presented as submitted.
A duplicate upload is flagged for review rather than paid twice.
Multiple attachments do not multiply the claim amount.
A missing-information request has an understandable next step.
A material change after approval follows the agreed reapproval rule.
Payroll and separate reimbursement cannot unknowingly settle the same claim twice.
An uncertain payment remains unresolved until its actual outcome is checked.
Employees can distinguish submitted, approved, awaiting settlement and settled claims.

Bring the reviewed expense policy to a discussion about internal workflow tools. Start with the path from evidence to settlement. Add scanning, exports or payment integrations only where they support that path.

Source boundary

The cited Odoo 19 documentation supports the payer distinction, receipt attachments, review/refusal examples and alternative reimbursement routes. Draft controls, conversion transparency, versioned approval, duplicate detection and payment reconciliation above are requirements to specify and test, not guarantees about every expenses product or statements of legal entitlement.