← Back to work

Fintech · Corporate Travel

The wallet that doesn't pretend every expense is the same.

Field employees pay for business trips out of pocket, then wait weeks to get it back. TravelWallet fixes this with three mechanisms, not one, each matched to how predictable an expense actually is.

Ops Ran Blind Dashboard
Role Product Designer
Team Cross-functional, Finance & Ops
Timeline v1.0, 2025
Scope PRD, flows, security model
90%
of trips with zero personal spend, 6-month target
<24h
from emergency claim approval to bank transfer
3
purpose-built mechanisms, one for each predictability tier
60%
target reduction in month-end reconciliation time

— The Thesis

You can't pre-load what you can't predict

Existing tools pick one mechanism for every expense. A hotel booking, a daily meal allowance, and a vehicle breakdown have nothing in common, except that one app tries to handle all three the same way.

I benchmarked logistics and pharma, industries that solved field-expense problems for the field years before software tried to. None of them use one wallet. They split by predictability.

That became the thesis.

— The Model

Three mechanisms, one axis

Every expense category sits somewhere on a predictability line. The mechanism it gets is a direct function of where it sits, not a default applied to everything.

High predictability

Per Diem

Auto-credited to the employee's wallet the moment a trip starts. No request, no approval loop. Receipts required only above ₹500. Unused balance returns automatically at trip end. Non-transferable.

In plain terms: like a daily allowance that just shows up.

Medium predictability

Advance Request

Known before the trip, variable in amount. Employee requests a category, amount, and context. Finance approves the exact figure. The wallet is category-locked, so it cannot be spent anywhere else.

In plain terms: ask for money before you spend it.

Low predictability

Emergency Claim

Camera opens first. The amount field stays locked until a bill photo is uploaded, non-negotiable. On approval, funds move to the employee's bank account within 24 hours.

In plain terms: snap the bill, then enter the amount.

— The Guardrail

A disabled field, not a policy line

"Receipts must be uploaded within 24 hours" is a sentence in an onboarding PDF nobody reads. A greyed-out amount field is a sentence nobody can ignore.

The policy approach

Most expense tools enforce receipt rules as written policy, a clause employees agree to once and forget. Compliance depends on memory and goodwill.

What TravelWallet does

For Emergency Claims, the camera is the first screen. The amount input is physically disabled until a bill photo exists, so the employee cannot submit a number before proof.

— Designed Against

Idle money sitting in a wallet

Unused balances, per diem or advance, auto-return to the company wallet 24 hours after trip end. Per diem can't be cashed out or transferred to another account.

This wasn't about distrust. It was about making the wallet behave like a tool, not a slush fund. Every rupee that goes out has a category, an expiry, and a return path.

— The Outcome

One decision, splitting the wallet by predictability instead of by role, solved both sides at once.

Finance gets an inline approve/reject queue with no email digging. Emergency claims surface in red, flagged Urgent, with the bill thumbnail visible before the click.

For the employee: per diem lands automatically, advances load the moment they're approved, and emergency reimbursements move to their bank account in under 24 hours, a window that used to be measured in weeks.

Next project
Driver App: When the Customer Goes Missing