Merchandise Budgets That Do Not Need a Requisition Form
Published 2026-08-05 by Barath A. R.
The default design for a company merchandise store is: everything needs approval. It is the safe-looking choice, and it is usually wrong. Approving a ₹400 T-shirt costs more in attention than the T-shirt costs in money, and a queue full of ₹400 decisions is a queue nobody looks at, which means the ₹40,000 decision sits behind them.
The alternative: give people a bounded amount and let them spend it
An allowance is a balance a person holds and can spend on the store without asking anybody. The control is not in the approval; it is in the size of the balance. Somebody with ₹2,000 cannot spend ₹20,000 no matter what they order, so there is nothing to approve.
This inverts where the attention goes. Instead of reviewing every order, you make one decision — how much this person or this department gets, and why — and then stop thinking about it.
One balance, several reasons
Vendors in this space usually sell two separate products: a "rewards points" scheme and a "spending budget" scheme. They are the same mechanic with different reasons attached, and running both means two ledgers to reconcile, two expiry policies, and two ways for the numbers to disagree.
One balance with a recorded reason per top-up does everything both do:
- **Entitlement** — an annual amount everybody at a grade receives.
- **Recognition** — an award for something specific, which reads very differently on a statement than a routine entitlement.
- **One-off** — a top-up for a particular need, like a team attending a conference.
- **Requested** — somebody asked for more and a checker agreed.
At year end you can still answer "how much of this was recognition versus entitlement", because every top-up carries its reason. You just did not have to run two systems to get there.
Expiry is a feature, and it needs to be honest
Unspent allowance should expire, or the liability accumulates indefinitely and the budget stops meaning anything. But expiry has to be visible: people should be able to see what they hold and when it goes.
The subtle part is what happens when several top-ups overlap. If someone holds a recognition award expiring in March and an annual budget expiring in December, and they spend some of it, which one did they spend? The answer should be the one expiring soonest — it is the arrangement that loses the person the least money, and it is the only one that makes March's expiry calculable.
A rejected order must hand the money back
This sounds obvious and is routinely got wrong. If an order draws on somebody's allowance and is then rejected or cancelled, the balance has to return. Otherwise the person loses both the goods and the budget, which is the fastest way to make people stop trusting the system.
Nobody should be able to lose both the goods and the budget. If the order does not happen, the money comes back.
Where approvals still belong
Allowances do not replace approvals; they remove approvals from the cases where they were never earning their keep. Keep the approval flow for:
- Anything billed to a department rather than to a personal balance.
- Spending above a threshold you set — five hundred brochures is a real decision.
- Requests for more allowance, which should route to a checker and escalate above their limit.
The distinction that makes this coherent: an allowance is money already granted, so spending it is not a request. Company spending is money not yet committed, so it is. Once you draw that line, most of the "should this need approval" arguments answer themselves.
The statement matters as much as the balance
Showing somebody "you have ₹1,200" invites the reply "I thought I had more". Without the movements — what was added, what was spent, on which order, what expired — the only way to answer is to ask somebody with admin access. Every balance should come with the ledger that produced it.
See how allowance works → · WhatsApp us on +91 98866 01717