An expense policy that prevents fights

Most expense disputes are not about dishonesty. They are about a policy nobody wrote down, applied by an approver who is guessing, to a claim filed three weeks late. You can remove almost all of that friction with one page of clear rules and a system that enforces them the same way for everyone.

Categories: few, and defined by example

Start with six to eight categories, no more: travel, local conveyance, lodging, meals, client entertainment, office supplies, software and subscriptions, other. Define each with two examples of what belongs and one of what does not. "Meals" should say whether it covers a solo lunch on a normal office day (usually no) versus a meal while travelling (usually yes). The examples do more work than the definitions.

Every category should map to an accounting head. If finance has to reclassify claims after the fact, your categories are wrong.

Limits: per instance, not per month

Monthly caps invite gaming and punish uneven travel. Set per-instance limits instead: hotel per night by city tier, meals per day while travelling, local conveyance per trip. Publish the numbers. An employee booking a hotel at 11 pm should not need to message anyone to know the ceiling.

Allow exceptions through approval, not through forgiveness. "Get it approved before you spend" is a fair rule; "we will decide after you spend" is a fight scheduled for later.

Receipts: required above a floor, digital, at filing time

Pick a floor, say ₹200, below which no receipt is needed; auto-rickshaws do not print invoices. Above it, a photo of the receipt attached at the time of filing, not collected in an envelope for month-end. Claims older than 30 days need a reason; claims older than 90 days are rejected by policy, not by an approver's courage.

Approval chains by amount

Route by amount, mechanically:

1. Up to ₹2,000: reporting manager only.
2. ₹2,000 to ₹25,000: manager, then finance.
3. Above ₹25,000, or any policy exception: manager, finance, and a director or founder.

The exact thresholds matter less than the fact that they exist and the system routes automatically. When routing is manual, approvals stall in inboxes and employees pay the float. ZekoHR's expense module routes by these rules and shows each claimant exactly where their claim is sitting; the platform overview covers how approval chains are configured.

Advances and reconciliation

For planned travel, give advances rather than forcing employees to fund the company from personal cards. Then close the loop: every advance must be reconciled against claims within a set window after the trip, with the unspent balance recovered, ideally through payroll so nothing depends on remembering. An advance without a reconciliation deadline is a small interest-free loan that slowly becomes a write-off.

Keep the payroll linkage tight in the other direction too: approved reimbursements should flow into the payroll cycle or a defined weekly payout run, so employees know when money arrives. Reimbursements that appear "whenever finance gets to it" generate more resentment than the amounts justify. If reimbursements ride along with salary, they belong in your payroll run inputs before the cutoff, like everything else.

Capture GST on business expenses

This is the part most small companies leave on the table. When an employee pays for a hotel, software subscription or client meal, the invoice often carries GST that the company can claim as input tax credit, but only if the invoice is in the company's name with its GSTIN, and only if someone actually records the GST details.

So the policy should say: for business expenses above a threshold, ask the vendor to bill the company with GSTIN, and capture the GST number and tax amount when filing the claim. ZekoHR's expense capture includes GST fields for exactly this reason; a claim filed with the invoice photo and GST details is usable by finance without a second round trip. Over a year of travel and subscriptions, the recovered credit is real money, and it costs nothing but a field in the form.

Publish it, then let the system be the enforcer

Put the policy where everyone can find it, link it from the expense screen, and let limits, routing and deadlines be enforced by software rather than by awkward conversations. The goal is not control for its own sake; it is that two employees filing the same expense get the same answer, every time. That consistency is what actually prevents the fights.

This article is general information, not tax advice. GST input credit eligibility depends on the nature of the expense and current law; confirm treatment with your tax advisor.