Employee Expense Reimbursement Policy: India Guide 2026

Every growing Indian company eventually hits the same wall: a founder is forwarding UPI screenshots on WhatsApp, a sales manager is chasing a six-month-old hotel bill, and the finance lead is trying to close payroll while three people argue about whether an airport taxi counts as "local conveyance". The fix is not a stricter finance team. The fix is a written employee expense reimbursement policy that says exactly what the company pays for, how much, who approves it, by when it must be claimed, and what proof is required.

This guide is written for HR managers, founders and payroll/finance teams at Indian SMBs. It walks through designing a policy from a blank page: scope and categories, spending limits by grade, the tax difference between reimbursements against bills and taxable allowances, travel and per diem rules, approval matrices, submission cut-offs tied to your payroll calendar, GST input credit basics, documentation and audit trails, fraud red flags, and how to automate the whole thing in an HRMS with employee self-service.

One important caveat up front: tax rules in India change with each Finance Act, and the treatment of several allowances differs between the old and new personal tax regimes. Everything in this guide is directional and structural. Confirm current rates, limits and conditions with your CA or tax advisor before you publish your policy.

Why a Written Expense Reimbursement Policy Matters More Than You Think

A lot of SMBs run for years on an unwritten understanding: "spend sensibly, we'll pay you back." That works at eight people. It breaks somewhere between thirty and eighty, and the breakage is expensive in ways that do not show up on a single line of the P&L.

Here is what an undocumented process actually costs you:

• Cash leakage. Without limits, spend drifts upward. Nobody is cheating; everyone is simply anchoring to the most generous precedent they have seen.
• Payroll delays. Claims arriving on the 29th for a payroll that locks on the 25th force either an off-cycle payout or a month's delay. Both annoy employees.
• Tax exposure. Reimbursements paid without supporting bills can be reclassified as taxable salary during an assessment. If you did not deduct TDS on them, the liability plus interest lands on the employer.
• Lost GST credit. Invoices in the employee's name, or without your GSTIN, mean input tax credit you were entitled to simply evaporates.
• Manager inconsistency. One manager approves business-class-equivalent spending, another rejects a ₹300 auto fare. Employees notice, and it reads as favouritism.
• Audit friction. At statutory audit, due diligence or a funding round, "we have the WhatsApp messages" is not an answer.
• Fraud. Duplicate submissions, inflated bills and personal spends dressed up as business spend thrive precisely where there is no policy to violate.

A good policy is not a control mechanism aimed at employees. It is a decision-removal device. It answers the ninety percent of questions in advance so that managers approve rather than adjudicate, and employees spend confidently rather than defensively.

Reimbursement vs Allowance: The Distinction Your Policy Must Get Right

If you take one structural idea from this guide, take this one. In Indian payroll there are two fundamentally different ways to put money in an employee's hands for work-related spending, and confusing them is the single most common cause of tax trouble.

Reimbursement (against actual bills)

The employee spends their own money, submits proof of the actual expenditure, and the company pays back exactly what was spent, up to a policy cap. The defining features:

• Payment is against a bill or invoice documenting a real expense.
• The amount reimbursed is linked to actual spend, not to a fixed monthly figure.
• It is typically not treated as income in the employee's hands, because the employee is not enriched; they are made whole for money spent on the employer's behalf.
• Unspent amounts stay with the company. There is no "use it or lose it" cash payout.
• It usually sits outside the CTC salary structure as a separate payment, or inside CTC as a bill-linked component.

Allowance (fixed monthly payment)

The company pays a fixed amount every month regardless of what the employee actually spends. No bills, no proof, no reconciliation.

• Paid as a fixed sum in the salary structure.
• Generally taxable as salary income, subject to specific exemptions that the Income Tax Act may provide for particular allowance types and conditions.
• Requires TDS deduction by the employer on the taxable portion.
• Simple to administer, but tax-inefficient for the employee and, if mislabelled, risky for the employer.

Why the difference bites

Consider two companies paying an employee ₹2,000 a month towards mobile expenses.

Company A pays a flat ₹2,000 "mobile allowance" every month. No bills collected. In most cases this is fully taxable salary. At a 30% marginal rate plus cess, the employee nets roughly ₹1,376 of the ₹2,000. The employer must run TDS on it.

Company B reimburses actual mobile bills up to ₹2,000 a month, requiring the employee to upload the operator invoice. The employee submits a bill for ₹1,850 and gets ₹1,850. Because it is a reimbursement of a business expense against proof, it is generally not treated as taxable perquisite income where the connection to official duties is established and the policy is genuine.

Same headline number, materially different outcome for the employee — and Company B also has documentation if a tax officer asks.

The trap: a "reimbursement" with no bills is just an allowance wearing a costume. If your policy says "mobile reimbursement ₹2,000" and you pay it every month without collecting a single invoice, a tax officer will treat it as an allowance, and rightly so. The label in your payslip does not decide the treatment; the substance does.

The taxability quick-reference

The table below is a structural guide to how common categories are generally treated. It is not a statement of current rates or limits, and treatment varies between old and new tax regimes and with the specific conditions attached to each provision. Verify with your tax advisor.

Two design principles follow from this table:

1. Prefer bill-linked reimbursements over fixed allowances wherever the expense is genuinely incurred and provable. It is better for the employee and cleaner for you.
2. Do not manufacture reimbursements to reduce tax. Structuring ₹8,000 a month of "books and periodicals" for a warehouse supervisor who buys no books is not tax planning; it is a finding waiting to happen.

Step 1: Define Scope — Who and What the Policy Covers

Start the policy document by drawing boundaries. Most disputes come from ambiguity at the edges, not the middle.

People in scope

Spell out coverage explicitly:

• Full-time employees on the company's rolls — covered.
• Employees on probation — usually covered, sometimes with lower limits or restricted categories.
• Interns and trainees — decide explicitly; typically conveyance and meals only.
• Fixed-term contract staff — covered, generally at the grade equivalent stated in their contract.
• Consultants and freelancers on professional fees — usually not covered by the employee policy. Their expenses should be billed through their invoice, with the tax and TDS consequences that follow. Say so plainly, or you will be reimbursing consultants through payroll and creating classification confusion.
• Third-party contract labour and agency staff — covered by the agency's own arrangement; not by you.
• Candidates attending interviews — often reimbursed for travel under a separate clause. Include it if you do it.

Expenses in scope

Define categories affirmatively, then define exclusions. The exclusion list matters more than people expect, because it is what a manager points to when saying no.

Typically reimbursable:

• Domestic and international business travel: air, rail, bus, taxi, mileage for own vehicle
• Accommodation on tour
• Meals on tour, either actuals or per diem
• Local conveyance for client meetings, vendor visits, bank and statutory work
• Client entertainment within limits
• Team meals and small team events within limits and with prior approval
• Mobile, data and home internet within grade caps
• Fuel and vehicle maintenance where the role requires field travel
• Office supplies and consumables purchased locally in a pinch
• Courier, postage, printing, notarisation, stamp paper
• Professional subscriptions, memberships, certifications, conference fees with prior approval
• Visa fees, travel insurance, forex conversion charges for business trips
• Relocation costs on transfer or at joining, where offered in the offer letter
• Work-from-home connectivity and ergonomics within a defined scheme
• Statutory and vendor payments made personally by an employee in an emergency

Typically excluded (state these explicitly):

• Personal travel, personal meals, family expenses on a business trip
• Alcohol, unless a named senior grade is permitted it for client entertainment and it is separately called out
• Traffic fines, parking violations, speeding penalties
• Personal grooming, laundry beyond a policy limit on long tours
• In-room entertainment, minibar, spa, gym
• Hotel upgrades beyond the entitled grade
• Loss of personal belongings, cash or devices
• Insurance premiums that are personal in nature
• Gifts to government officials, or anything that touches anti-bribery boundaries — this deserves its own sentence in the policy
• Any expense incurred more than the stated number of days before submission (see cut-offs below)
• Expenses already covered by a company card, corporate booking tool or advance

Add one catch-all sentence: "Any expense not expressly listed as reimbursable requires prior written approval from the Finance Head before it is incurred." This turns "the policy doesn't say I can't" into "the policy says ask first."

Step 2: Set Spending Limits by Grade

Limits are where policies either become useful or become theatre. Three rules for getting them right:

1. Tie limits to grade, not designation. Designations proliferate; grades do not. Map every role to a band (say G1 to G6) and set entitlements per band.
2. Tie travel limits to city tier. A ₹4,500 hotel cap is generous in Indore and unusable in Mumbai. Define city tiers in the policy and publish which cities are in which tier.
3. Set limits at the 80th percentile of reasonable spend, not the median. If your cap forces half your team to seek exceptions, the exception process becomes the real policy and your control is gone.

Illustrative category limits matrix

The figures below are illustrative only, meant to show structure. Calibrate to your own cost base, industry and cities before adopting anything.

Some design notes on this matrix:

• Mileage rates should be reviewed annually. Fuel prices move. Publish the rate as an annexure so you can update it without reissuing the whole policy.
• Hotel caps should be "up to" figures, not entitlements. Add a line: "Caps are maximums. Employees are expected to book the most economical suitable option."
• Where the company books centrally, say so. If flights and hotels above a threshold must go through the admin desk or a corporate booking tool, self-booking becomes an exception requiring justification.
• Two-person sharing rules for accommodation on team travel should be explicit, and should never be applied across genders or to grades where privacy is reasonably expected.

Defining city tiers

Keep this simple and publish it as an annexure:

• Tier A: Mumbai, Delhi NCR, Bengaluru, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad
• Tier B: State capitals and large commercial centres — Jaipur, Lucknow, Chandigarh, Kochi, Coimbatore, Indore, Bhubaneswar, Nagpur, Surat, Vadodara, Visakhapatnam, Guwahati and similar
• Tier C: All other locations in India
• International: Separate schedule by country or region, in local currency, with a stated forex conversion basis

Step 3: Design the Travel Expense Policy

Travel is where most of the money and most of the disputes live. Treat it as its own chapter.

Before the trip

• Travel request and approval. No trip should begin without an approved travel request that records purpose, destination, dates, expected mode and estimated cost. This is your first control, and it is far more effective than arguing about a bill after the fact.
• Advance booking window. Require domestic flights to be booked at least 7 days out and international at least 14–21 days out, except for genuine emergencies with a documented reason. This single rule saves more money than any per diem cap.
• Lowest logical fare. Define it: the cheapest fare on a reasonable routing, allowing a premium for a flight that avoids an overnight halt or an unreasonable layover. Without a definition, "cheapest" invites arguments about 5 a.m. departures.
• Travel advance. Decide who gets one, how much, and the settlement deadline. A reasonable default: advances up to 80% of estimated out-of-pocket spend, requested at least 3 working days before travel, settled within 7 days of return.

During the trip

• Accommodation. Book within grade caps for the city tier. Require a GST invoice in the company's name with the company GSTIN where the hotel is registered.
• Meals. Choose one of two models and stick to it:
• Actuals model: employee submits food bills, reimbursed up to a daily cap. More paperwork, more accurate, better documentation.
• Per diem model: a fixed daily amount is paid without individual meal bills. Less paperwork, more predictable, more popular with travelling employees.
• Local transport. App-based cabs preferred because they generate an invoice with route and time. Autos and local transport up to a small daily limit on self-declaration.
• Communication. International roaming packs or local SIM costs on foreign trips should be pre-approved and reimbursed at actuals.
• Laundry. Typically permitted for trips beyond 4 consecutive nights, within a modest daily cap.

Per diem policy: how to run it properly

Per diem is popular because it removes receipt-chasing for small amounts. But it must be designed carefully, because a per diem that exceeds reasonable expenditure starts looking like a taxable allowance rather than a reimbursement of tour expenses.

Design rules:

1. Per diem covers meals and incidentals only. Hotel, flights and intercity travel are reimbursed separately at actuals. Say this explicitly, otherwise you will get claims for both.
2. Define what counts as a day. A common approach: full per diem for each full day away, 50% for the departure and return day if travel is more than 6 hours on that day. Publish the rule; do not leave it to interpretation.
3. Do not pay per diem where meals are provided. If the conference includes lunch and dinner, or the client is hosting, reduce the per diem proportionally. Build the deduction table into the policy: breakfast 20%, lunch 35%, dinner 45%, for example.
4. No double-dipping. If per diem is paid, individual meal bills are not separately reimbursable.
5. Keep rates reasonable and defensible. Per diem set at a level that a reasonable person would consider actual tour expenditure, and supported by an approved tour record, sits on much safer ground than a generous flat rate paid to everyone regardless of travel.
6. Record the tour. Dates, destination, purpose, and approval must exist in the system for every per diem payment. This record is the difference between a reimbursement and an allowance in the eyes of an assessing officer.

Worked example: a three-day domestic trip

A G4 manager travels Bengaluru to Delhi, departing Monday 7 a.m. and returning Wednesday 9 p.m. Company runs a per diem model.

Points worth noticing in this example:

• The hotel GST of ₹1,836 is potentially available as input tax credit only if the invoice carries the company's name and GSTIN and the supplier reports it correctly. If the employee booked in their own name, that credit is lost.
• The Tuesday per diem was reduced because the client hosted dinner. The employee still needs to declare that, which is why your claim form should ask.
• The advance settlement is netted in the same claim, not tracked in a separate spreadsheet.

Step 4: Non-Travel Categories — Mobile, Internet, Fuel, WFH and Relocation

Mobile and internet

The cleanest structure is a bill-linked reimbursement with a grade cap:

• Employee pays their own operator/ISP bill.
• Uploads the invoice monthly or quarterly.
• Company reimburses the lower of actual bill and grade cap.
• The connection must be in the employee's own name; family members' bills are not reimbursable.
• Where the plan is a bundled family plan, reimburse a reasonable apportioned amount defined in the policy rather than the full family bill.

Two practical variations: allow quarterly submission for small amounts to reduce transaction load, and allow prepaid recharge receipts where postpaid invoices do not exist — but require the operator's official receipt, not a screenshot of a payment app.

Fuel and vehicle

This is the category most likely to attract tax scrutiny, because the line between official and personal use is genuinely blurry. Structural options:

1. Company-owned vehicle with driver, used for official and personal purposes. Specific perquisite valuation rules apply and a monthly perquisite value is added to the employee's income. Your payroll system needs to handle this.
2. Employee-owned vehicle, official use reimbursed. Reimburse on a per-kilometre basis against a trip log, or on fuel bills against a declaration of official usage percentage. The trip log matters — date, from, to, purpose, kilometres.
3. Fixed monthly fuel allowance with no logs. Simple, and generally taxable as salary.

If you want the tax-efficient version, you need the documentation version. Pick one and be honest about the trade-off. A fuel reimbursement with no logbook and no odometer readings is an allowance.

Work-from-home and hybrid claims

Post-2020, most Indian SMBs run some form of hybrid. Two clean approaches:

• Company-owned asset model. Company buys the laptop, chair, monitor or router; it is capitalised, entered in the asset register, tagged to the employee, and returned at exit. No perquisite issue for a business asset used for business.
• Reimbursement model. Employee buys within a capped scheme, submits the invoice, and the item is recorded in the asset register as company property with an agreed treatment at exit. Decide up front: does the employee keep it, return it, or buy it out at written-down value? Put it in the policy, because the conversation at resignation is much harder.

Avoid the third approach — a flat "WFH allowance" of ₹2,000 a month with no bills. It is administratively easy and taxable.

Internet at home for hybrid employees should sit under the internet reimbursement clause, not under a separate WFH bucket, to avoid double claims.

Relocation

Relocation reimbursement is usually offered at joining or on transfer, and it needs its own mini-schedule:

• Eligible heads: packers and movers for household goods, travel for employee and immediate family, temporary accommodation for a defined number of days, brokerage for rental housing up to a cap, school admission assistance if offered.
• Caps by grade, usually expressed as an overall ceiling plus sub-caps.
• Quotation requirement: at least two or three quotations for packers above a threshold, with the company reserving the right to choose the vendor.
• Service commitment: many companies require repayment on a pro-rata basis if the employee resigns within 12 months. If you do this, put it in the offer letter as well as the policy, and be reasonable about it.
• Documentation: transfer or appointment letter, invoices in employee or company name, rent agreement for brokerage claims.

Note that transfer-related reimbursements have specific tax treatment and some elements can become perquisites. Get your CA to review your relocation schedule once; it rarely needs revisiting after that.

Petty cash: keep it small and controlled

Even in a UPI-first economy, some offices still need physical cash for autos, courier boys, tea, stamp paper and municipal errands. Petty cash is fine — uncontrolled petty cash is not.

Run it as an imprest system:

1. A fixed float (say ₹10,000) is issued to a named custodian, usually the office admin.
2. Every disbursement is recorded in a petty cash register with date, payee, purpose, amount, and the recipient's signature.
3. Vouchers are attached for every payment. For payments where no bill exists (an auto fare, a coolie), a self-prepared voucher signed by both the payer and the approver is used.
4. When the float is depleted to a trigger level, the custodian submits the register and vouchers, finance verifies, and reimburses exactly the amount spent — restoring the float to ₹10,000.
5. Single transaction cap. Nothing above a stated limit (₹2,000 is a common choice) goes through petty cash. Larger payments go through the bank.
6. Surprise counts. Someone other than the custodian counts the cash and reconciles it to the register at least monthly, unannounced. Document the count.
7. Segregation. The person who holds the cash should not be the person who approves the vouchers or the person who does the accounting entry. In a small team you may not achieve perfect segregation; achieve two out of three and document who does what.

Be aware that Indian income tax law restricts deductibility of cash payments above specified thresholds and there are separate restrictions on receiving cash above certain limits. Keeping your single-transaction petty cash cap well below any statutory threshold protects your deduction and keeps you out of trouble. Confirm the applicable thresholds with your advisor.

Step 5: Build the Expense Approval Workflow

An approval matrix answers one question: for a claim of this type and this size, whose sign-off is required? Get it wrong in one direction and the CFO is approving ₹200 auto fares. Get it wrong in the other and a ₹3 lakh conference sponsorship slips through on a team lead's nod.

Design principles

• Two-level rule for anything material. Manager approves the business justification; finance approves the policy compliance and the numbers. Managers should not be checking GSTINs, and finance should not be judging whether a client dinner was worthwhile.
• Self-approval is never permitted. If a manager's own claim would route to themselves, it escalates one level up automatically. This includes founders — especially founders, if you have external investors or are heading toward a diligence.
• Approval thresholds by amount, exceptions by category. Some categories should always require a higher approval regardless of amount: client entertainment, gifts, anything involving government interaction, anything outside the policy.
• Set an auto-escalation SLA. If an approver does not act within a defined number of days, the claim escalates to their manager. Without this, claims die in inboxes and employees blame finance.
• Approvers must be able to reject with a reason, and partially approve. Partial approval — approving ₹4,200 of a ₹5,000 claim with a note on the disallowed line — avoids the all-or-nothing rejection loop.

Illustrative approval matrix

Thresholds are illustrative; scale them to your revenue and spend patterns. A ₹15 crore revenue company and a ₹150 crore revenue company should not use the same numbers.

The end-to-end claim process, step by step

Here is the workflow to write into your policy, in order:

1. Incur the expense within policy limits, with prior approval where the category requires it.
2. Collect the proof at the moment of spending — photograph the bill immediately, before it fades or gets lost. Thermal-print receipts fade in weeks.
3. Create the claim in the HRMS or expense tool, selecting the correct category, entering the date of expenditure (not the date of claim), the amount, the vendor, the GSTIN where applicable, and the business purpose in one plain sentence.
4. Attach the document — an image or PDF of the bill. One bill per line item; do not merge ten receipts into one PDF and claim a lump sum.
5. Link the claim to a travel request, project, cost centre or client code where your accounting needs it. Doing this at entry saves finance hours at month end.
6. Submit before the cut-off for the current payroll cycle.
7. Manager reviews for business justification: was this trip necessary, was this dinner appropriate, is this spend attributable to their budget. Approve, reject with reason, or send back for more information.
8. Finance reviews for policy compliance: within grade cap, correct category, valid bill, GSTIN captured, no duplicate, advance adjusted, within submission window.
9. Approved claims are batched into the payment run — either with payroll as a separate non-taxable reimbursement line, or as a separate bank transfer.
10. Payment is made and the payment reference is written back to the claim record.
11. Accounting entry posts to the correct expense head and cost centre; GST input credit is recorded where eligible.
12. The claim is archived with its full audit trail and retained for the statutory record retention period.

Submission cut-offs tied to the payroll calendar

This is the operational detail that determines whether your process feels fast or feels broken. Publish an actual calendar.

A few rules that make the calendar work:

• Never accept "the system was down" as a permanent excuse. Give employees a reminder on day 20 after the expense, day 25, and a final warning on day 28.
• The 60-day hard stop needs teeth and a safety valve. Claims beyond 60 days require a written exception approved by the Finance Head, with the reason recorded. Employees on long medical leave or extended field deployments are the real cases; publish that they will be accommodated.
• The financial year cut-off is absolute. Expenses incurred in one financial year must be claimed within that year, because otherwise your books and your tax position are wrong. Communicate this in early March, not on 30 March.
• Off-cycle payouts should exist but be rare. A claim above a stated amount (say ₹25,000) that would create genuine hardship can be paid off-cycle within a defined number of working days, with Finance Head approval.

Step 6: GST Input Credit Basics for Expense Claims

Most SMBs quietly lose meaningful GST input tax credit through expense claims. Not because the law denies it, but because the paperwork was wrong.

The core principle: to claim input tax credit, you generally need a tax invoice issued to you, the registered person, showing your name, address and GSTIN, and the supplier must have reported that invoice in their returns so it flows into your auto-populated statement. A receipt made out to "Rohit Sharma" for a hotel stay in Delhi gives you nothing, even though your company paid for it.

Practical implications for your expense policy:

• Instruct employees to always ask for a GST invoice in the company's name. Give them a wallet card, a phone note or a line in the app: Company legal name, registered address, GSTIN. Hotels and restaurants will do it if asked at check-in, and will usually refuse to reissue after check-out.
• Capture the supplier GSTIN as a field in the claim form. Make it mandatory for categories where credit is typically available, optional elsewhere.
• Understand place-of-supply for hotels. Accommodation is generally taxed where the hotel is located, and if your company is not registered in that state, the credit position differs from a same-state stay. This is the single most common source of confusion; ask your consultant to explain it once for your registration footprint.
• Know which categories are blocked. GST law specifically restricts credit on certain items, and food and beverage, outdoor catering, club memberships and some motor vehicle related expenses have historically been in that category subject to conditions and exceptions. Do not assume credit on client dinners.
• Reconcile. Credits claimed through expense reimbursements should be reconciled against the auto-populated statement, same as vendor invoices. If your expense tool does not export GSTIN-wise data, you will not do this reconciliation, which means you will over-claim or under-claim.
• Do not let the tax tail wag the dog. If chasing a ₹90 credit costs your finance executive twenty minutes, stop chasing it. Set a materiality threshold and apply GST discipline above it.

Take this to your CA once a year with a sample of claims and ask a blunt question: what credit are we losing, and what is the cheapest process change that recovers it?

Step 7: Documentation, Audit Trail and Record Retention

Your policy should specify not just what employees submit, but what the system must retain.

What counts as acceptable proof

• Preferred: GST tax invoice with supplier name, GSTIN, invoice number, date, description, taxable value and tax breakup.
• Acceptable: a bill of supply, cash memo or receipt from an unregistered supplier with vendor name and date.
• Acceptable for app-based services: the invoice PDF generated by the app, not the ride-completion screenshot.
• Acceptable with limits: a self-declaration voucher for genuinely bill-less spends — auto fares, parking at unmanned lots, tips to porters — capped at a small daily amount, countersigned by the approver.
• Not acceptable: UPI payment screenshots as the sole proof, credit card statements as the sole proof, handwritten chits without a vendor name, photos too blurred to read, or a bill dated outside the claimed period.

A UPI or card statement proves payment. It does not prove what was bought. You need both the payment trail and the nature of the expense for a defensible file.

What the audit trail must capture

For every claim, the record should hold:

• Claim ID, employee ID, cost centre, project or client code
• Date of expenditure and date of submission (kept separately — this is how you monitor discipline)
• Category, sub-category, amount, currency and conversion rate where applicable
• Vendor name and GSTIN
• The attached document, stored immutably with a hash or version lock
• Every approval action with approver identity, timestamp, decision and comment
• Any modification to the claim after submission, with before-and-after values
• Payment reference, date and mode
• Accounting posting reference

The two fields people forget are date of expenditure vs date of submission and the edit history. The first lets you measure and enforce submission discipline. The second is what stops a "small correction" from being invisible.

Retention

Keep claim records and supporting documents for the period required under income tax, GST and company law — in practice, most Indian companies retain financial records for eight years, and some retain longer where litigation or assessments are open. Storage is cheap; reconstruct-from-memory is not. Retain digitally, with a backup, and make sure the records survive a change of expense tool. Before you migrate systems, export everything.

Step 8: Fraud Controls and Red Flags

Expense fraud in Indian SMBs is rarely dramatic. It is almost never a fake ₹5 lakh invoice. It is a hundred small things: the same restaurant bill submitted twice three months apart, a personal weekend stay folded into a business trip, a fuel bill from a city the employee did not visit, an inflated auto fare on a self-declaration.

The most common patterns

• Duplicate submission. The same bill claimed twice, sometimes accidentally, sometimes not. Often split across two months to avoid detection.
• Round-number claims. Repeated ₹500, ₹1,000, ₹2,000 self-declared conveyance claims. Real expenses are rarely round.
• Just-under-threshold clustering. A steady stream of claims at ₹1,950 when the receipt requirement kicks in at ₹2,000, or at ₹9,900 when second-level approval starts at ₹10,000. This is the single strongest statistical signal of gaming.
• Weekend and holiday spending on a business trip that has no business reason to extend.
• Mismatched dates. A hotel bill for Tuesday to Thursday and a flight arriving Wednesday.
• Personal items in an itemised bill — the alcohol line in a restaurant bill, the minibar line in a hotel folio, a second guest's meal.
• Doctored bills. Amount altered on the image, or a bill generated from an online template. Look for inconsistent fonts, misaligned totals, or a serial number that does not fit the vendor's pattern.
• Vendor collusion. A vendor issues inflated invoices and refunds cash. Hard to detect from documents alone; shows up as one employee consistently using one small vendor.
• Advance never settled. An advance taken, partly claimed, and the balance quietly forgotten. This is the most common form of leakage in companies without a settlement tracker.

Controls that actually work

1. Automated duplicate detection on amount + date + vendor + employee, and separately across the whole company for the same invoice number.
2. Receipt requirement above a low threshold. Set it low — ₹500 is defensible in most SMBs — and require a self-declaration below it.
3. Statistical exception reports run monthly: top 10 claimants by value, top 10 by claim count, claims within 5% of any approval threshold, claims submitted more than 45 days after expenditure, and repeat use of the same vendor by the same employee.
4. Random sampling audit. Pick 5% of claims each quarter, at random, and verify the original document against the vendor where possible. Publish that you do this. The deterrent effect exceeds the detection effect.
5. Hard controls on advances. No new advance while a previous one is unsettled beyond the deadline. Automatic recovery from salary after a stated period, with prior written notice to the employee — and check that your standing authorisation to recover is documented and lawful in your context.
6. Manager accountability. Approvers own the claims they approve. If a manager approves twenty claims in three seconds, that shows in the timestamp data and should be part of their own review conversation.
7. Anonymous reporting channel for employees who see something. Most fraud is discovered by a colleague, not by a control.
8. A stated consequence. The policy should say plainly that falsified claims are treated as misconduct, may lead to recovery and disciplinary action up to termination, and in serious cases to legal action. Then apply it consistently — inconsistent enforcement is worse than none.

One cultural note: build these controls without treating everyone as a suspect. Frame the policy around clarity and speed of payout, mention controls factually, and reserve the harsh language for the misconduct clause. Teams that feel trusted submit cleaner claims.

Ready-to-Adapt Expense Reimbursement Policy Template

Copy the structure below into your own document, replace the bracketed placeholders, delete what does not apply, and have it reviewed by your CA and, if you have one, your employment counsel before you circulate it.

---

[COMPANY NAME] — EMPLOYEE EXPENSE REIMBURSEMENT POLICY Policy owner: [Head of Finance] | Effective from: [DD-MM-YYYY] | Version: [1.0] | Next review: [DD-MM-YYYY]

1. Purpose This policy defines the expenses [Company] will reimburse to employees who incur costs on the Company's behalf, the limits applicable to each category, the approvals required, and the process and timelines for claiming. It exists to ensure employees are never out of pocket for legitimate business spending, and that Company funds are used responsibly and are properly documented for tax, GST and audit purposes.

2. Scope Applies to all [full-time employees / employees on probation / fixed-term employees] on the rolls of [Company] in India. Does not apply to consultants, contractors on professional fee arrangements, or agency-supplied staff, whose expenses are governed by their contracts.

3. Guiding principles - Spend Company money as you would your own. - Incur only expenses that are necessary, reasonable and directly connected to Company business. - Obtain prior approval where this policy requires it. - Keep proof of every expense. - When in doubt, ask before you spend.

4. Reimbursable categories and limits Refer to Annexure A — Category Limits Matrix, and Annexure B — City Tier Classification. Limits are maximums, not entitlements.

5. Non-reimbursable expenses [Insert the exclusion list — personal expenses, fines, alcohol except as permitted, in-room entertainment, upgrades beyond entitlement, losses of personal property, gifts to public officials, and any expense not listed as reimbursable and not pre-approved by the Finance Head.]

6. Business travel 6.1 All travel requires an approved Travel Request raised in [HRMS/tool] before booking. 6.2 Domestic flights must be booked at least [7] days in advance; international at least [14] days. 6.3 Employees must select the lowest logical fare and accommodation within their grade cap for the applicable city tier. 6.4 Bookings above ₹[amount] must be made through [central travel desk / corporate booking tool]. 6.5 Travel advances up to [80]% of estimated out-of-pocket cost may be requested at least [3] working days before travel and must be settled within [7] days of return.

7. Per diem 7.1 Per diem covers meals and incidental expenses only. Accommodation and transport are reimbursed separately at actuals. 7.2 Rates are set out in Annexure A by grade and city tier. 7.3 Full per diem applies to each full day away; [50]% applies to the day of departure and the day of return where travel on that day exceeds [6] hours. 7.4 Where meals are provided by the Company, the client, a conference or the hotel tariff, per diem is reduced by [breakfast 20% / lunch 35% / dinner 45%]. 7.5 Individual meal bills are not separately reimbursable when per diem is claimed.

8. Mobile, internet and fuel 8.1 Mobile and internet are reimbursed against bills in the employee's own name, up to the monthly grade cap. 8.2 Fuel is reimbursed [at ₹[rate]/km against a trip log / against fuel bills with an official-use declaration] for roles designated as field roles. 8.3 Claims without supporting bills or logs will not be processed.

9. Approvals Refer to Annexure C — Approval Matrix. No employee may approve their own claim or a claim from which they benefit; such claims escalate one level. Approvers must act within [3] working days, failing which the claim escalates automatically.

10. Submission timelines 10.1 Claims must be submitted within [30] days of the date of expenditure. 10.2 Claims submitted more than [60] days after expenditure will be rejected unless a written exception is approved by the Finance Head. 10.3 The cut-off for inclusion in the current month's payout is the [15th] of the month. Claims after this date move to the following cycle. 10.4 All expenses relating to a financial year must be claimed on or before [31 March] of that year.

11. Documentation 11.1 Every claim line must be supported by an original bill or invoice uploaded as an image or PDF. 11.2 Where GST credit is available, the invoice must carry [Company]'s name, address and GSTIN: [insert details]. 11.3 Payment screenshots and card statements alone are not acceptable proof. 11.4 Self-declared expenses without bills are permitted only for [conveyance and incidental spends] up to ₹[amount] per day.

12. Payment Approved claims are paid [with the monthly salary as a separate reimbursement line / by separate bank transfer] on [the last working day of the month]. Reimbursements against valid bills are not treated as taxable salary; any payment that does not meet the documentation requirements of this policy may be processed as a taxable allowance with applicable TDS.

13. Misuse Submission of false, altered, inflated or duplicate claims constitutes serious misconduct and may result in recovery of amounts paid, disciplinary action up to and including termination, and legal action where warranted.

14. Exceptions Any deviation requires prior written approval from the [Finance Head]. Approved exceptions are recorded with the claim.

15. Review This policy is reviewed annually by [Finance and HR]. Rates in the annexures may be revised without amending the main policy.

Annexure A — Category Limits Matrix | Annexure B — City Tier Classification | Annexure C — Approval Matrix | Annexure D — Mileage Rates | Annexure E — Claim Form Fields

---

Automating Expense Reimbursement in an HRMS

Every step above can be run on paper and email. Most SMBs start there. The reason to move it into an HRMS with employee self-service is not elegance; it is that manual expense processing consumes finance time that scales linearly with headcount, and it produces exactly the gaps that cost you money.

What automation should actually do

On the employee side: - Capture the bill from a phone camera at the moment of spending, so nothing depends on a paper receipt surviving a week in a wallet - Pre-fill category, date and amount from the image where possible, with the employee confirming - Show the applicable grade limit before submission, so out-of-policy claims are caught at entry, not at rejection - Show claim status in real time — submitted, with manager, with finance, approved, paid — which eliminates most of the follow-up email traffic - Handle advances and settlements in the same place, with the balance visible - Work on mobile, because the people with the most claims are the people least often at a desk

On the manager side: - Approve or reject from a phone, in bulk where appropriate, with visible policy flags on each claim - See the employee's claim history and the team's spend against budget - Receive escalation reminders rather than silence

On the finance and payroll side: - Automatic policy validation: grade cap, category eligibility, submission window, duplicate check, advance adjustment - Batch approval and a single export to the payment file - Direct posting into the payroll run as a distinct non-taxable reimbursement line, so it does not get mixed into taxable earnings - GSTIN-wise reporting for input credit reconciliation - Cost centre, project and client tagging that flows into accounting - Exception and analytics reports without anyone building a pivot table

On the compliance side: - An immutable audit trail with approver identity and timestamps - Documents stored against the claim for the retention period - A clean answer for the auditor: filter, export, done

Where automation pays back fastest

If you are prioritising, the highest-return automations for an Indian SMB are, in order:

1. Mobile receipt capture with policy validation at entry. Kills the two biggest problems — lost bills and out-of-policy claims — at once.
2. Automatic routing and escalation. Removes the "waiting for approval" black hole.
3. Direct payroll integration. Removes the manual re-keying that causes payment errors and, worse, taxable/non-taxable misclassification.
4. Advance tracking. Recovers real money that is otherwise quietly lost.
5. Duplicate detection and exception reports. Pays for itself the first time it catches something.

A realistic rollout plan

Do not launch a new policy and a new tool on the same day to the whole company.

1. Weeks 1–2: Draft the policy with Finance and HR. Get CA review on tax and GST clauses.
2. Week 3: Socialise the draft with 5–8 heavy claimants — sales, field service, senior leadership. They will find the practical problems you missed.
3. Week 4: Finalise limits, approval matrix and calendar. Get management sign-off.
4. Weeks 5–6: Configure the HRMS — categories, grade limits, approval routing, cut-off dates, cost centres.
5. Week 7: Pilot with one department for a full cycle, including an actual payout.
6. Week 8: Fix what broke. Publish the policy with a one-page summary, a two-minute video, and an FAQ.
7. Week 9: Go live for everyone, with a 30-day amnesty for old claims submitted the old way.
8. Month 4: Review adoption, cycle time from submission to payment, rejection reasons and exception volume. Adjust limits where rejections cluster — repeated rejections in one category usually mean the cap is wrong, not that employees are.

Measure four numbers after go-live: average days from expenditure to submission, average days from submission to approval, average days from approval to payment, and percentage of claims rejected or sent back. If all four are trending down, the policy is working.

Frequently Asked Questions

1. Is an expense reimbursement taxable in the hands of the employee? Generally, a reimbursement of an actual business expense incurred on the employer's behalf and supported by bills is not treated as taxable salary income, because the employee is being made whole rather than enriched. A fixed monthly payment made without any requirement to spend or prove spending is generally taxable as an allowance, subject to any specific exemption available under the Income Tax Act. The label you use on the payslip does not determine the treatment — the substance and the documentation do. Confirm your specific structure with your tax advisor, especially given the differences between the old and new tax regimes.

2. How long should employees get to submit a claim? Thirty days from the date of expenditure is a common and workable standard, with a hard stop at sixty days and a documented exception route beyond that. Anything longer and you get claims arriving after the financial year closes, which creates accounting problems. Anything much shorter and you will be granting exceptions constantly for employees on extended travel or leave.

3. Can we reimburse expenses without bills? For small, genuinely bill-less spends — auto fares, parking at unmanned lots, tips — yes, on a self-declaration voucher within a low daily cap. For anything else, no. Reimbursements without supporting documents are the fastest route to having your reimbursements reclassified as taxable allowances, and they make GST credit impossible.

4. Should we pay per diem or reimburse meals at actuals? Per diem is simpler, faster and more popular with employees, and works well when your travel volume is high and your rates are set at genuinely reasonable levels tied to documented tours. Actuals give you better documentation and are easier to defend if your rates would otherwise look generous. Many companies run per diem for domestic travel and actuals for international. Whichever you choose, be consistent and never allow both for the same trip.

5. What is the difference between a travel advance and a reimbursement? An advance is money paid before the trip against an estimate; it is a receivable from the employee until settled. A reimbursement is money paid after the fact against actual bills. Advances need their own tracker, a settlement deadline, a rule blocking new advances while old ones are open, and a recovery mechanism. In practice, unsettled advances are one of the biggest quiet leakages in SMB finance.

6. Can we claim GST input credit on employee expense claims? Sometimes, and only with the right invoice. The tax invoice must be in the company's name with the company's GSTIN, the supplier must report it correctly, and the expense category must not be one on which credit is blocked under GST law. Hotel accommodation raises place-of-supply questions depending on where you are registered. Food and beverage and certain other categories are restricted. Get your consultant to map your specific categories once, then build the rules into your claim form.

7. Should reimbursements be paid with salary or separately? Either works. Paying with salary is operationally simpler and needs only one payment run, provided your payslip and payroll system show reimbursements as a distinct non-taxable line and do not fold them into taxable earnings. Paying separately makes the distinction obvious and lets you run faster cycles for large claims. Many SMBs do both: routine claims with payroll, large or urgent claims off-cycle.

8. How do we handle a claim from the founder or CEO? Exactly like any other claim, except the approval routes to the Finance Head and then to a board designee or, in a smaller company, to a co-founder or the audit committee where one exists. Self-approval at the top is the single most damaging exception you can make — it undermines the policy for everyone below and it is one of the first things a diligence team looks at.

9. What should we do about employees who consistently submit late? Treat it as a process problem first and a performance problem second. Send automated reminders at 20, 25 and 28 days. If a specific team is consistently late, ask why — often the cause is a manager who does not approve, or a category that is hard to claim. If it persists after the process is fixed, it becomes a line manager conversation, and repeated late submission can reasonably be reflected in a performance discussion.

10. Do we need a separate policy for international travel? Not a separate policy, but a separate annexure. You need per diem rates by country or region, a defined forex conversion basis (card statement rate, RBI reference rate on the date of expense, or the rate on the forex card statement — pick one and publish it), rules for visa fees and travel insurance, and guidance on international roaming. Keep the approval matrix and submission timelines identical to domestic so employees have only one process to learn.

Bringing It Together

A good employee expense reimbursement policy is not a long document. It is a clear one. If your policy answers what can I spend, how much, who approves, by when do I claim, and what proof do I need in language a new joiner understands on first reading, you have solved most of the problem.

The rest is operational discipline: a published calendar tied to payroll, an approval matrix that routes by amount and category, documentation standards that protect both the employee's tax position and your GST credit, and a few quiet controls that catch the small leakages before they become habits. Review the limits once a year, review the exception log once a quarter, and fix the caps that generate the most rejections rather than blaming the people who hit them.

Most importantly, remember what the policy is for. Employees who spend their own money on the company's behalf should get it back quickly, predictably and without chasing anyone. Every day you shave off the expenditure-to-payment cycle buys goodwill that costs you nothing.

If you are running this on spreadsheets and email today, that is a reasonable place to have started — and a poor place to stay past fifty people. CozyHR brings expense claims, approval workflows, travel advances, policy limits and payroll together in one system, with mobile receipt capture and full employee self-service, built for how Indian SMBs actually work. Set up your categories and grade limits once, and let the claims route, validate and settle themselves. Try CozyHR free and see your next payroll cycle close without a single WhatsApp receipt.

This article is general guidance for HR and finance teams and is not tax or legal advice. Indian tax and GST rules change and depend on your specific facts. Please confirm current provisions, rates and limits with your chartered accountant or tax advisor before finalising your policy.