Ask a CFO how much cash is tied up in employee advances right now, and you’ll usually get a pause. Receivables have an aging report. Payables have a schedule. Inventory gets counted. But the money you’ve handed employees for trips, site visits and petty procurement sits in a blind spot — disbursed, spent, and waiting to be reconciled, with no one owning the clock.
It looks small on any single line. A ₹20,000 advance here, a ₹35,000 one there. But across a few hundred employees it compounds into a standing pool of company cash that is out of the account and off the ledger for weeks longer than it should be. That pool is working capital you’ve already earned and can’t use.
This piece does three things: shows you what the pool actually costs, explains why it grows, and lays out four levers — each of which you can operate from a single system — that shrink it.
How the cash gets stuck — and comes back. Read it as a tank. Advances fill it; time heats it; enforcement drains it. The whole game is keeping the level — and the temperature — low. Motion is illustrative.
An advance is an interest-free loan you gave—and forgot to call back
The moment you disburse, company cash converts into an employee IOU. It stays an IOU until the expense is submitted, matched to receipts, and the balance is either reconciled or refunded. Everything between disburse and reconcile is exposure — cash you own but can’t deploy.
The advance lifecycle — and the exposure window. The exposure window is the only part that costs you money. Every day you shorten it is cash back in the account.
Put a rupee figure on the blind spot
Here is a deliberately conservative, mid-size scenario. The point isn’t the exact figures — it’s the method. Swap in your own headcount, advance size and cost of capital and the shape holds.
- ₹40 L — Company cash standing in unsettled advances (at any moment)
- 34 d — Average time from disburse to reconcile (the exposure window)
- ₹14 L — Sitting in advances older than 60 days (35% of the pool)
- 41% — Advances settled within the stated deadline (before enforcement)
Where the ₹40L is stuck — by age. The tail is the problem. The ₹14L older than 60 days is where receipts go missing, employees leave, and balances quietly become write-offs. Figures illustrative.
The model · run it with your numbers
From a 34-day window to a 9-day window
Method: average outstanding scales with cycle length, so cutting the window ~74% releases ~74% of the standing pool as one-time working capital, then saves your cost of capital on it every year after. Replace headcount, ticket size and rate with your own.
You wouldn’t let a customer sit 34 days past terms without a dunning process. An employee advance is the same receivable — it just never had one.
Three failure modes keep the pool full
Unsettled advances aren’t a discipline problem — they’re a system problem. Three gaps do almost all the damage:
- No clock. Most advance policies state a settlement period but nothing enforces it. A deadline nobody is measured against is a suggestion.
- Wrong-sized amounts. Flat advance limits mean over-funding — the excess is pure idle cash, and bigger balances are slower to settle.
- No consequence. When an employee can draw a new advance while an old one is still open, balances stack instead of clearing.
Four levers — and where to pull them
Each maps to something you configure once and the system enforces on every advance, for every employee, in every entity.
Lever 1 — Put a clock on every advance
Attach a settlement deadline at issue and let the system flag, age and escalate anything that crosses it — automatically, without a person watching a spreadsheet.
In MyVyay Per-policy settlement deadlines with automatic overdue detection
Lever 2 — Right-size the amount
Cap advances by role, trip type and advance type so you fund the trip, not a buffer. Suspend advances for anyone carrying an overdue balance.
In MyVyay Advance configuration: per-type limits & user suspension
Lever 3 — Make settling the easy path
Reminders that reach people where they are, receipt capture from a phone camera, and one-tap settlement. Friction is why advances age; remove it and they clear.
In MyVyay SLA reminders, WhatsApp nudges & mobile receipt capture
Lever 4 — Close the loop
Block a new advance until the previous one is settled. The single highest-leverage control — it stops balances from ever stacking.
In MyVyay Advance-request validation gate on open balances
What changes when the levers are on
Average settlement window — before vs after. Same policy, now enforced. The shorter bar is the released working capital in Exhibit 3, made permanent. Illustrative of a typical enforcement outcome.
None of this asks employees to try harder. It asks the system to hold the line — a deadline that flags itself, a limit sized to the trip, a reminder that lands, and a gate that won’t open twice. Configure once; it runs on every advance after.
See it on your own numbers: book a 20-minute demo or start free and run this playbook against your real spend data.