Employee reimbursement software manages money the employee has already advanced. It should make evidence, approval, repayment, rejection, and excess-return status clear without treating the claim like a company-card charge. Each made the list for a different reason: Expensify's published scope starts from receipts, reports, and reimbursement; Zoho Expense handles expense reporting and reimbursement inside the Zoho suite; Airbase treats reimbursement as one payment rail in a request-to-pay process alongside cards and payables.
Buyer scenario: repayment waits behind a missing detail
Consider an employee paying personally for an urgent purchase, submitting a partial receipt, and changing managers before approval. The business purpose is valid, but project coding is disputed and repayment timing matters to the employee.
Where each one helps the claimant, and where it breaks
Expensify. Trigger: dozens of claimants, many filing only a few times a year, and most complaints are about not knowing what is missing. Check: have a new hire submit from a phone with a partial receipt and confirm they can see exactly what blocks approval and when payment is scheduled. Wrong pick: an employer that wants every reimbursable purchase approved in advance; its published scope starts from reports filed after the money is spent, so confirm any pre-approval step in a trial before relying on it.
Zoho Expense. Trigger: customers and projects are already kept in Zoho, and some claims are re-billed to clients. Check: code a claim to an existing Zoho customer and project and confirm the value comes from that record rather than a typed copy. Wrong pick: a company with no other Zoho app; the suite context it was shortlisted for is then absent.
Airbase. Trigger: policy requires a request before the spend, as with conference trips, equipment, or training, and the claim should be checked against what was approved. Check: link a claim to its approved request, submit a higher amount, and confirm the difference is flagged for review. Wrong pick: a handful of ad hoc claims a month; the request step adds work for employees without changing what they are owed.
IRS Publication 463 discusses federal travel and accountable-plan concepts. California Labor Code section 2802 may be relevant for California expense obligations. Software cannot decide qualification, reasonableness, or legal compliance for the employer.
Map employee communication as a sequence. The claimant should see whether finance needs evidence, the manager has not acted, the claim was partly rejected, payment was scheduled, or repayment failed. Avoid one generic status that forces an employee to contact finance while personal cash remains outstanding. Record who owns every transition and what evidence closes it.
Compare repayment rails separately from report approval. An approved expense is not necessarily paid, and a failed bank or payroll event should return to a visible finance queue without reopening the business-purpose decision. This boundary matters especially after employee departure.
Test partial approval and partial repayment. A report can contain a supported business expense, a disputed line, and a personal portion. The employee should know which amount is approved, which remains under review, and which will not be repaid. Finance should post and pay only the appropriate states without cloning the report. If the policy permits continued review, the unresolved line should retain its evidence and owner rather than disappear into the completed payment.
Track repayment aging separately from submission aging. A complete approved claim that remains unpaid is a finance exception, not an employee documentation problem, and should escalate to a different owner.
Decision criteria from personal payment to repayment
Inspect mobile submission, business purpose, receipts, duplicates, mileage or other evidence where relevant, split coding, policy exceptions, approval delegation, employee status, rejection reasons, payment states, excess repayment, currency evidence, and close queues.
Define whether payroll, bank, or another rail pays the employee, who owns failure, and how accounting reconciles. Keep employee reimbursement separate from company card settlement.
Reproducible reimbursement evaluation
Create a personal purchase, mixed receipt, duplicate-looking claim, foreign-currency item, and company-card transaction for contrast. Omit evidence, add it later, split coding, delegate approval, reject one line, correct it, reimburse only the approved amount, and record an excess payment due back.
Deactivate the employee before payment and trigger an invalid accounting code. Repair, retry, and reconcile claim, approval, repayment, return, and posting. Spend Management Guide has not executed this configured comparison.
Edge case: expense is valid but policy was unclear
Submit an urgent business expense outside the normal category because no company card was available. Test whether reviewers can approve an attributable exception without rewriting policy or leaving the employee uninformed.
Then process a repayment failure after employee departure. The obligation and communication path should remain visible without reopening financial access.
Verdict, and the reimbursements none of them settles
Pick by when the decision about a claim is really made. If it is made after the fact by a reviewer looking at receipts, Expensify. If it hinges on which client or project the cost belongs to and that data lives in Zoho, Zoho Expense. If it was made before the purchase, through a request someone approved, Airbase. In each case the employee should see exactly what is missing and finance should see what has been approved, paid, returned, and posted.
None of the three settles reimbursements that run through payroll, such as recurring stipends or allowances: their accuracy depends on the payroll system and its handoff, so test that first. None of them settles what an employer must repay under state law either. Workflow support does not make an accountable plan qualify or prove compliance with reimbursement laws; that remains a question for counsel.
For car use, the 2026 federal mileage rates are in mileage reimbursement and the IRS rate.
Traceable evidence
Sources for this decision
- vendorExpensify official product siteExpensify · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Teams evaluating receipt, expense report, reimbursement, and card workflows. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- vendorZoho Expense official product siteZoho Expense · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: SMBs evaluating expense reporting and reimbursement within the Zoho business suite. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- vendorAirbase official product siteAirbase · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Finance teams evaluating request-to-pay, cards, reimbursements, and accounts payable controls. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.Open source ↗
- regulatorPublication 463, Travel, Gift, and Car ExpensesInternal Revenue Service · checked Aug 5, 2026 · supports: Federal substantiation, accountable-plan, travel, gift and vehicle-expense rules within Publication 463; it does not determine deductibility or reimbursement treatment for specific facts.Open source ↗
- officialCalifornia Labor Code Section 2802California Legislative Information · checked Aug 5, 2026 · supports: California statutory text requiring employer indemnification for necessary expenditures or losses in the scope stated by section 2802; it does not decide applicability to particular facts.Open source ↗