Expense Reimbursement Policy: Template and Workflow Guide

Every growing company in India reaches the same awkward moment. A salesperson returns from a three-day client trip with a crumpled bag of receipts, a WhatsApp screenshot of a cab fare, and a hopeful message to HR: "Please clear my claim before month-end." Finance asks which budget it belongs to. The manager says he never approved the hotel upgrade. Payroll wants to know whether to add it to salary or pay it separately. Two weeks later, everyone is irritated and the employee is still out of pocket.

A clear expense reimbursement policy prevents this. It tells employees what they can spend, how to claim it, who approves it, and when they will be paid. It tells managers what they are accountable for. It gives finance and auditors a trail they can follow without chasing people. And it protects the company from the slow leak of small, unchecked claims that quietly turn into a real cost line.

This guide is written for HR managers, founders and finance leads at Indian small and mid-sized businesses. You will find a full claim workflow, approval limits, per-diem design, travel and client entertainment rules, receipt requirements, the general difference between reimbursement and taxable allowance, payroll integration, fraud controls, audit trail practices, and a ready-to-adapt policy template. Worked examples use fictional companies and numbers, chosen only to illustrate the mechanics.

A note before we start: this article is general guidance, not tax or legal advice. Tax treatment of reimbursements and allowances depends on current Income Tax rules, the employee's tax regime and the exact facts. Always verify with the latest rules and with your chartered accountant before finalising your policy.

Why an expense reimbursement policy matters more than you think

Many small companies run expenses on goodwill. The founder approves things over chat, and everyone assumes the rules are obvious. That works at ten people. It breaks somewhere between thirty and a hundred, for predictable reasons.

• Inconsistency feels unfair. If one manager approves a Rs 6,000 hotel and another rejects Rs 3,500, employees notice. Trust erodes quickly when rules live in people's heads.
• Cash flow suffers on both sides. Employees fronting company costs for weeks resent it. The company, meanwhile, cannot forecast spend it only learns about late.
• Finance cannot close the books cleanly. Claims that arrive months after the expense date land in the wrong period, distort budgets and complicate GST input credit reviews.
• Fraud and padding hide in the gaps. Most employees are honest. But without limits, receipts and checks, even honest people drift into generous interpretations, and the occasional dishonest one finds easy room.
• Tax and compliance risk accumulates. Paying personal expenses as "reimbursements" without proper basis can create questions at assessment time. A written policy with documentary proof is your first defence.

A good policy is not about suspicion. It is about making the right behaviour the easy behaviour, and making the exceptions visible.

What a policy should accomplish

Before drafting, agree on five outcomes. Everything else in the document should serve them.

1. Clarity: An employee can read the rules once and know what is claimable.
2. Speed: Valid claims are paid within a predictable window.
3. Control: Spend stays within budget, and unusual claims get a human look.
4. Evidence: Every rupee paid has proof attached and an approver named.
5. Fairness: Similar roles and situations are treated the same way.

Reimbursement, allowance and advance: get the vocabulary right

Teams often use these words interchangeably, and that causes confusion in payroll and in tax treatment. Define them in your policy.

The practical difference: a reimbursement follows the spend, an allowance follows the salary structure. That distinction matters for payroll, and we return to it in the tax section below.

Designing the claim workflow step by step

A workflow is simply the path a claim travels from the moment money is spent to the moment it is paid and recorded. Keep it short, because every extra step is another place for a claim to stall.

Step 1: Pre-approval for anything that is not routine

Routine, low-value spend, such as a local cab to a client meeting, should not need permission each time. But some categories should be approved before the money is spent:

• Outstation travel and hotel stays
• Client entertainment above a set amount
• Purchases of equipment or software for work
• Any single expense above a threshold you define, for example Rs 10,000

Pre-approval can be a short request: purpose, dates, estimated cost, approver. The point is that the manager knows about the spend before it happens. Surprises at claim time are the main source of disputes.

Step 2: Spend and collect proof at the time

Tell employees to capture proof when the expense occurs, not at month-end. A photo of the bill taken at the table beats a hunt through a laptop bag three weeks later. Make this a habit through your tooling: mobile upload from the phone works far better than emailed scans.

Step 3: Submit the claim within a fixed window

Set a submission deadline. Many companies choose 30 days from the expense date, with a hard cut-off at the financial year end so that costs land in the correct period. Late claims are not automatically void, but they need a senior approval and a reason.

A good claim form captures:

• Date of expense and date of submission
• Category (travel, lodging, meals, client entertainment, communication and so on)
• Amount, currency and tax details if shown on the bill
• Business purpose, in a sentence
• Project, client or cost centre code
• Attachment of proof
• For client entertainment: names and companies of attendees

Step 4: Manager review

The reporting manager confirms three things: the expense was real, it was business-related, and it fits the policy. Give managers a service-level target, for example approval or rejection within three working days. Escalate automatically if they miss it. A claim sitting in a manager's inbox is the most common reason employees complain.

Step 5: Finance verification

Finance checks what the manager is not expected to check: whether the bill is valid and legible, whether the amount matches, whether the category is correct, whether limits were respected, and whether the same bill has been submitted before. For higher-value claims, a second approver or department head signs off.

Step 6: Payment

Decide the payment mode and cycle and publish it. Two common patterns:

• With payroll: Approved claims are added to the monthly payroll run and paid with salary, shown as a separate line on the payslip.
• Off-cycle batch: Approved claims are paid weekly or fortnightly through bank transfer, independent of salary.

Off-cycle batches are friendlier to employees who travel a lot. Payroll-attached payments are simpler to administer. Many companies combine them: small claims in the weekly batch, larger ones with payroll.

Step 7: Record and reconcile

Once paid, the claim is posted to the right expense ledger and cost centre, with proof retained. Monthly, finance reconciles total approved claims against payments and budgets. Anything open or rejected is closed out with a reason.

The workflow at a glance

Treat these targets as starting points. A ten-person company can compress them. A multi-location business may need more time.

Setting approval limits that actually work

Approval limits balance speed against control. If every Rs 200 snack needs three signatures, nobody follows the process. If anything under Rs 50,000 sails through, controls are decorative.

A tiered approach

Use value bands and let each band require a progressively senior approver. Here is an illustrative structure. Your figures should reflect your cost base and risk appetite.

These numbers are examples, not recommendations. Choose bands that match how your business actually spends.

Principles for good limits

• Never let anyone approve their own claim. This applies to founders too. If the founder claims, another director or the finance head approves.
• Look at cumulative spend, not just single claims. Splitting a Rs 12,000 expense into three Rs 4,000 claims to dodge a limit is a classic pattern. Flag repeated near-limit claims.
• Define monthly caps per role where useful. A field sales executive's local conveyance cap will differ from an engineer's.
• Set grade-wise limits for hotels and flights. More on this below.
• Document the delegation. When a manager is on leave, who approves? Name an alternate, so claims do not stall.

Worked example: a sensible limit in practice

Imagine Brightloom Textiles, a fictional 80-person garment exporter in Tiruppur. Their merchandisers travel often. Before the policy, each merchandiser's manager approved whatever came in. Monthly claims varied wildly for people doing the same job, from Rs 4,000 to Rs 31,000, with no clear reason.

HR introduced three changes: a monthly local-conveyance cap per grade, hotel ceilings by city category, and a rule that any claim over Rs 15,000 needed the department head's approval. Within two months the spread narrowed, and the conversations with managers changed from "why was this paid?" to "why do you need an exception?" The numbers are invented for illustration, but the pattern is real: consistency comes from caps and bands, not from policing each bill.

Per-diem: simplify food and incidentals on the road

Asking employees to collect every tea and sandwich bill during travel is tedious for them and for finance. A per-diem replaces this with a fixed daily amount tied to the city and the duration of the trip.

How to build a per-diem

1. Classify cities. Group locations into tiers, for example metro, large city and other. Costs differ, and your policy should reflect that.
2. Set a daily rate per tier and grade. Base it on real local costs, checked against what your travellers actually spend. Review annually.
3. Define what the per-diem covers. Typically meals, local tea and snacks, laundry and small incidentals. Lodging and transport are usually separate.
4. Decide part-day rules. For example, travel under six hours earns no per-diem, between six and twelve hours earns half, beyond twelve hours earns the full amount.
5. Reduce for provided meals. If the client hosts lunch or the hotel includes breakfast, deduct a portion. State the percentages clearly.
6. Decide the proof. Normally travel proof such as tickets, hotel invoice or an approved trip request is enough. No meal bills are required.

Illustrative per-diem table

These are fictional figures to show structure. Set your own after looking at real costs and your budget.

Worked example: calculating a per-diem claim

Meera, a fictional account manager at a Pune software services firm, travels to Bengaluru for a client workshop. She leaves home at 6:30 am on Monday, spends two nights in a hotel, and returns Wednesday at 9:00 pm. Her company's policy gives Tier 1 executives Rs 1,200 per day, with the following rules: full day for 12 hours or more away, half day for 6 to 12 hours, and a 25 percent deduction per provided meal.

• Monday: away more than 12 hours, full day: Rs 1,200
• Tuesday: full day, but the client provided lunch, so deduct 25 percent: Rs 900
• Wednesday: away about 15 hours, full day: Rs 1,200

Total per-diem: Rs 3,300. Meera submits her flight tickets, the hotel invoice and her approved trip request. She does not submit any meal bills. Her hotel and flights are reimbursed at actuals, subject to her grade's ceilings.

The advantage is plain: less paperwork, no incentive to inflate meal bills, and a number she can predict before leaving.

When not to use a per-diem

Per-diem is awkward for client-hosted events, one-off high-cost situations such as international travel with special requirements, and trips where employees have documented dietary or safety needs. Keep an exception route so that these are handled as actuals with approval.

Travel rules: transport, lodging and everything in between

Travel is typically the largest reimbursable category and the one with the most grey zones. Write specific rules.

Choosing travel mode and class

• Air: Economy class by default, with a booking window (for example, at least seven days ahead where possible) to control fares. Allow higher classes only with named approval or for senior grades on long routes.
• Rail: Specify the class by grade. Many companies allow AC classes for managers and above, and allow sleeper or chair car for junior grades, but this is a business choice.
• Road: Prefer company-arranged cabs or pre-approved rentals for outstation journeys. For personal vehicle use, pay a fixed rate per kilometre with a trip log.
• Local transport: Cabs, autos and metro on actuals with app receipts, or a capped monthly conveyance for field roles.

Lodging ceilings

Set a maximum nightly rate by city tier and grade. Include rules on:

• Booking through a preferred portal or corporate rate if you have one
• Exceptions during conferences or peak seasons, with advance approval
• Sharing rooms on team trips
• Extra nights only with business justification

Personal vehicle and kilometre claims

If employees use their own cars or two-wheelers, define a per-kilometre rate, require an opening and closing odometer reading or a map-based distance record, and exclude commuting between home and the regular office. Payment of fuel or vehicle running cost to an employee may be taxed differently depending on structure and usage, so confirm treatment with your tax adviser.

Things to exclude clearly

State what is never reimbursable. Employees should not have to guess. Typical exclusions:

• Fines, challans and penalties
• Personal entertainment, minibar and spa charges
• Upgrades chosen for comfort without approval
• Travel insurance extras not required by policy
• Family members' travel and stay
• Alcohol, unless explicitly allowed for client events within limits

Worked example: a three-city sales trip

Consider Arjun, a fictional regional sales head at a Delhi-based packaging firm. He plans a five-day trip to Ahmedabad, Mumbai and Pune. Before leaving, he submits a trip request with estimated cost of Rs 62,000 across flights, hotels and cabs. Because the estimate exceeds Rs 50,000, his department head and the founder both approve it.

During the trip he books flights within the policy's economy limit, chooses a hotel in Mumbai Rs 800 above the ceiling because of a trade fair, and has prior written approval for that exception. On return he submits the claim with all tickets, hotel invoices and cab receipts, plus per-diem for five days. Finance matches the claim against the approved estimate. Total actual: Rs 58,400. It is within the approved range, the exception is documented and the claim is cleared in the next batch.

If Arjun had booked the pricier hotel without approval, the extra Rs 800 per night would have been disallowed or required retrospective sign-off. The system works because the exception was visible beforehand.

Client entertainment and business meals

Client entertainment is the category most likely to be questioned by auditors and most likely to be abused. It is also a normal part of doing business. The aim is to allow reasonable hospitality while keeping a record of who, what and why.

Policy elements

• Pre-approval above a threshold, for instance any event over Rs 5,000 or any gifting beyond a defined value.
• Per-head ceilings. A simple cap per attendee, varying by city tier, avoids arguments about restaurant choice.
• Attendee list. The claim must list the names and organisations of external guests and the internal staff present.
• Business purpose. One clear sentence, for example: "Contract renewal discussion with ABC Logistics."
• Itemised bill. A card slip alone is not enough. The restaurant invoice should show items and tax.
• Gifts policy. Define value limits and ban gifts to government officials or to anyone where a gift could be construed as influencing a decision. Also consider your anti-bribery and client-side policies, since many large clients restrict what vendors may offer their staff.
• Alcohol rule. Prohibit it, or allow it only with senior approval and a stated cap. Whatever you choose, state it.

Entertainment versus employee welfare

Do not mix client entertainment with internal team meals and celebrations. Internal events belong under a separate category, with separate approval and budgets. Mixing them hides real spend and creates audit confusion. Also, the tax treatment of internal staff welfare spend can differ from client hospitality, so keeping the categories apart helps your accountant.

Worked example: client dinner

A fictional design studio, Kaveri Creative Labs in Chennai, hosts a prospective client dinner. The studio's policy caps client meals at Rs 2,500 per head in Tier 1 cities. Their creative director invites three client representatives and brings one colleague, a total of five people.

The ceiling for the dinner is therefore Rs 12,500. The bill comes to Rs 11,200 including taxes. The claim lists all five attendees and their organisations, gives the purpose as "Proposal discussion for brand refresh project", attaches the itemised invoice and links to the sales opportunity code. The manager approves, finance verifies and the amount is reimbursed. A similar dinner claimed at Rs 21,000 with no attendee names would have been returned for details and probably referred upward for exception approval.

Receipts and proof: what to ask for and how long to keep it

Proof is the backbone of reimbursements. Without it, a claim is simply an assertion.

What counts as acceptable proof

• Original tax invoices or bills with the vendor's name, date and amount
• Digital invoices and e-tickets, including emailed ones
• App-generated trip receipts for cabs and similar services
• Payment confirmation alongside the bill (supporting, not replacing it)
• For toll, parking or small items without bills, a signed declaration within a low limit

Setting a no-receipt allowance

For tiny expenses where a bill is not practical, such as tolls, auto-rickshaws or parking attendants, allow a self-declaration up to a modest monthly cap. Document the limit, the format of the declaration and the consequences of misuse. Keep this cap low so it does not become a loophole.

GST invoices and vendor details

Where the company wants to use input tax credit, the invoice should carry the company's GSTIN and the vendor's tax details, and the bill should be in the company's name where possible. Employees should be told this at booking time, for hotel stays and business services. Eligibility for credit depends on the nature of the expense and current GST rules, so check with your tax adviser and do not assume everything qualifies.

Handling lost receipts

Receipts get lost. Create a short route: the employee signs a lost-receipt declaration, gets the manager's countersignature and, if the amount is above a small threshold, obtains a duplicate from the vendor. Limit how often an employee can use this route within a year, so it remains an exception.

Digitise and retain

• Require clear photographs or scans uploaded to the claim at submission.
• Store them in a system where they are linked to the claim and cannot be quietly replaced.
• Retain records for the period your accountant and applicable laws advise. Retention requirements differ by record type, so confirm the right duration rather than guessing.
• Do not insist on collecting paper originals unless there is a reason. Where you do, define who receives them and how they are filed.

Reimbursement versus taxable allowance: the general picture

This is the area where many small businesses become nervous, and rightly so. The tax treatment of what you pay employees depends on how it is structured and documented. What follows is a general orientation only, not advice. Rules change, thresholds differ, and your employees' regime choice can affect outcomes. Verify current Income Tax rules and consult your chartered accountant before designing any pay structure.

The core idea

Broadly, a payment to an employee is either part of their remuneration or a repayment of expenses the employee incurred on behalf of the employer.

• A genuine reimbursement of business expenses is the company paying back a cost that belongs to the company. It is generally not treated as the employee's income, provided it is truly for official purposes and is supported by evidence.
• An allowance is typically a fixed sum paid as part of compensation. Unless a specific exemption applies under the prevailing rules and conditions, it is generally treated as part of taxable salary.
• A payment that looks like a reimbursement but covers personal costs can be treated as salary income, with consequences for tax deducted at source.

Why the label alone is not enough

Calling something "reimbursement" does not make it so. Documentary proof that the cost was incurred, was business-related, and was paid by the employee for the company's purposes is what supports the treatment. Conversely, calling something an "allowance" does not automatically make it taxable or exempt. The conditions and current rules decide that.

Practical implications for HR

Some policy habits that keep you on safer ground

• Keep the reimbursement category separate from the salary structure on payroll and payslips.
• Never convert "unused" reimbursement limits into cash or salary at year end unless your adviser confirms the treatment.
• Do not allow employees to submit claims to "use up" an entitlement. Reimbursement is for actual spend.
• Document the business purpose for each claim.
• Review the structure annually with your accountant, especially after Budget announcements or notified rule changes.

Tax regime and employee choices

Employees may be under different tax regimes, which can affect how certain pay components are treated for them. This is a payroll configuration issue as much as a policy one. Your payroll process should know which components are taxable for which employees and compute TDS accordingly. If you are unsure, ask your tax adviser to review your component list and set up the rules once, rather than fixing mismatches each quarter.

Integrating reimbursements with payroll

Approved claims have to reach the employee's bank account and the books accurately. The way you connect expenses to payroll shapes the workload for HR and finance.

Options for payout

1. Pay through the payroll run. Approved claims are included as a separate earnings line, marked non-taxable or taxable as classified. This reduces separate transfers, but delays payment until the next run.
2. Pay in a separate reimbursement batch. Faster, but needs separate bank files and reconciliation.
3. Hybrid. Small claims go in the weekly batch. Large travel settlements are paid with the next payroll.

Whichever route you choose, publish the cut-off dates. For example: "Claims approved by the 20th will be paid with that month's salary."

Payslip presentation

Show reimbursements as a clearly labelled line, distinct from salary components. This helps employees understand their pay, and it helps you demonstrate that these amounts are repayments, not part of compensation. Include the claim reference where possible.

Handling taxable reimbursements

Some payments, such as certain relocation benefits or non-business items you decide to cover, may be taxable. Configure these as taxable components so that TDS is calculated correctly. The most reliable approach is to maintain a short mapping of expense categories to payroll component type, approved once by your accountant and applied automatically.

This mapping is illustrative. The correct classification belongs to your tax adviser and the current rules.

Advances and recoveries

When an employee takes an advance, tie it to a trip or event, set a settlement date and track the open balance. If the employee leaves the company before settlement, recover the balance through full and final settlement as per your policy and applicable law. Make sure the offer letter or policy acknowledgment mentions this, so recoveries are not a surprise. Check applicable rules on deductions from wages before recovering amounts.

Month-end and year-end hygiene

• Freeze claim submission for the closing month a few days after month-end, so accruals are accurate.
• Accrue approved but unpaid claims at period end.
• Sweep up any open advances before the financial year closes.
• Share category-wise totals with finance for tax filings and budget reviews.

Worked example: the monthly cycle

Take Northwind Foods, a fictional 120-person packaged food business in Indore. Claims approved by the 22nd are included in that month's payroll. Finance exports an approved-claims file with employee ID, category, amount and cost centre. Payroll maps each category to a component: business travel and client meals to non-taxable reimbursement, and the occasional personal-use approval to a taxable component. The payslip shows "Expense reimbursement" as its own line.

After the payroll run, finance reconciles total claim payments against the ledgers by cost centre. One mismatch of Rs 1,450 turns out to be a claim approved after the cut-off but paid in error. It is documented, adjusted in the following cycle, and the cut-off rule is added to the approver checklist. A small incident, but exactly the type that regular reconciliation catches early.

Fraud controls that respect your people

Most expense issues are not dramatic crimes. They are rounding up, double claiming, claiming for personal use, or recycling old receipts. Your goal is to make these difficult and visible without turning the workplace into a place of suspicion.

Common patterns to watch for

• Duplicate claims: the same bill submitted twice, or once by the employee and once by a colleague who shared the meal.
• Inflated or altered receipts: changed amounts, edited dates, or invoices created from templates.
• Personal expenses presented as business: weekend trips, family meals, personal shopping.
• Split claims: breaking a large expense into pieces to stay under approval limits.
• Round-number claims: a pattern of claims at suspiciously neat amounts, particularly for categories where receipts are not required.
• Fictitious attendees: inflating client entertainment with names that do not exist.
• Collusion: manager and employee agreeing to approve each other's questionable claims.
• Mileage padding: inflated kilometre claims for personal vehicle use.

Preventive controls

1. Segregation of duties. The person who incurs, the person who approves and the person who pays should not be the same. At a minimum, no one approves their own claim.
2. System-enforced rules. Category limits, date limits and required fields should be enforced by the tool, not by memory.
3. Duplicate detection. Check vendor, date, amount and invoice number against earlier claims.
4. Mandatory attachments. No proof, no submission, apart from the declared small-value exceptions.
5. Clear consequences. The policy states that false claims are a disciplinary matter, up to and including termination and recovery of amounts. Employees sign an acknowledgment.
6. Manager accountability. Approvers are responsible for what they approve. Track approval patterns, such as managers who approve everything within minutes.

Detective controls

• Periodic sampling. Finance reviews a random sample of approved claims each month, verifying proof against a vendor or booking record.
• Analytics. Look for outliers by employee, category and vendor. Compare spend against peers in the same role.
• Vendor checks. Spot-check unfamiliar vendors, or those that appear repeatedly with round-number bills.
• Exception reports. Weekend and holiday expenses, claims just under limits, late submissions and frequent lost-receipt declarations.
• Whistleblower route. Employees should know how to raise concerns confidentially.

Responding to a suspicious claim

Respond with process, not accusation.

1. Pause the claim and record the reason.
2. Ask the employee for clarification or additional proof, in writing, in neutral language.
3. Verify with the vendor or booking source where needed.
4. If the explanation is reasonable, release the claim and note the outcome.
5. If not, escalate to HR and a senior leader. Follow your disciplinary process, apply principles of natural justice, and take legal advice before taking serious action.

Treat first-time honest errors differently from deliberate falsification. A policy that distinguishes them is both fairer and easier to defend.

Worked example: a catch by simple pattern checks

At a fictional logistics startup in Hyderabad, finance runs a monthly exception report. It shows one executive who submitted 14 cab claims of exactly Rs 480 each, all on weekends, with screenshots that look identical in layout. Finance does not accuse anyone. It requests the original app receipts with trip details. The employee cannot produce them. After a conversation and the company's review process, the claims are rejected and the matter is handled under the policy. The company also adds a rule: cab claims need the app-generated receipt with trip route, not a screenshot of a payment. The loophole is closed for everyone.

Building an audit trail you can defend

An audit trail answers a simple question: for any rupee paid, can you show who spent it, why, who approved it, who paid it and what proof exists? If you can answer in minutes, you are in good shape.

What the trail should contain

• Claim ID and unique reference
• Employee identity and cost centre
• Date of expense, date of submission and date of each approval step
• Amount claimed, approved and paid, including any adjustments
• Category, business purpose and linked project or client
• Attached proof, stored unchanged
• The name and role of each approver, with timestamps
• Comments, queries and rejections, including who raised them
• Payment details: date, mode and bank reference
• Policy version in force at the time

Principles of a reliable trail

• Immutability: Once a claim is approved, edits should create a new version rather than overwrite the old one.
• Timestamps and identity: Every action should be tied to a named user.
• Searchability: Finance should be able to filter by employee, category, vendor, date and approver.
• Access control: Only the right roles see sensitive data, and only they can change settings.
• Policy versioning: When the policy changes, keep the previous version and the date of change.
• Retention: Keep records for the period your adviser confirms, and make sure they can be retrieved at the end of that period.

Using the trail proactively

An audit trail is not just a shield for the day an auditor visits. Use it as a management tool:

• Review average approval times to find bottlenecks.
• Review rejection reasons to improve policy clarity.
• Review top spenders by category to rebalance budgets.
• Review exception volumes to see whether limits are realistic.

If 40 percent of hotel claims need exceptions, the problem is probably the ceiling, not the employees.

Policy template: a draft to adapt

Below is a starting template. Replace bracketed items with your values, remove clauses that do not apply, and have your legal and tax advisers review it before issuing. Figures are placeholders.

---

[Company Name] Employee Expense Reimbursement Policy

Version: [1.0] Effective date: [DD/MM/YYYY] Owner: [HR / Finance] Review cycle: [Annually]

#### 1. Purpose

This policy sets out how [Company Name] reimburses employees for reasonable, necessary and documented expenses incurred while performing official duties. It aims to ensure consistent treatment, timely payment and proper control of company funds.

#### 2. Scope

This policy applies to all permanent, contract and probationary employees of [Company Name]. [Consultants and interns are covered only where their agreement says so.]

#### 3. General principles

• Expenses must be incurred for genuine business purposes.
• Expenses must be reasonable, and economical choices are expected.
• Claims must be supported by valid proof, unless covered by a stated exception.
• Employees must not claim for expenses already paid or reimbursed by the company, a client or any third party.
• Personal expenses are not reimbursable.
• No employee may approve their own claim or one in which they have a personal interest.

#### 4. Eligible expense categories

• Travel: air, rail, road, local conveyance
• Lodging
• Meals and per-diem during official travel
• Client entertainment and business meals
• Communication and internet for official use (where not covered by an allowance)
• Courier, printing and minor office supplies
• Training and conference fees (with prior approval)
• Other expenses approved in writing in advance

#### 5. Non-reimbursable expenses

Fines and penalties; personal entertainment; alcohol (except as approved under clause 9); family travel; luxury upgrades without approval; personal grooming or clothing; expenses lacking proof; any expense contrary to law or company policy.

#### 6. Pre-approval

The following need prior written approval from the reporting manager: outstation travel; lodging; client entertainment above Rs [5,000]; any single expense above Rs [10,000]; purchase of equipment or software.

#### 7. Approval limits

In the manager's absence, the nominated alternate approves. Claims in the name of a manager or department head are approved by the next senior authority.

#### 8. Travel

• Air: economy class, booked at least [7] days in advance where possible.
• Rail: [class] by grade, as set out in Annexure A.
• Lodging: within city-tier ceilings in Annexure A.
• Personal vehicle: Rs [rate] per kilometre with trip log; no reimbursement for home-to-office commute.
• Exceptions require written approval before the expense is incurred.

#### 9. Client entertainment and gifts

• Maximum Rs [amount] per head in Tier 1 cities and Rs [amount] elsewhere.
• Claims must state names and organisations of all attendees and the business purpose.
• Alcohol is [not reimbursable / reimbursable only with approval of [role] and up to Rs [amount]].
• Gifts to clients are limited to Rs [amount] per person per year and must not be given to government officials or in circumstances that could create a conflict of interest or breach anti-bribery rules.

#### 10. Per-diem

Employees on overnight official travel receive the per-diem in Annexure A in place of meal receipts. Part-day and provided-meal rules apply as set out there. Per-diem requires an approved trip request and travel proof.

#### 11. Proof of expense

• Claims must include original or digital invoices, tickets or receipts.
• Self-declaration is accepted for expenses below Rs [200] each, up to Rs [1,000] per month, for tolls, parking and similar items without receipts.
• Lost receipts require a signed declaration countersigned by the manager and are permitted no more than [twice] in a financial year.
• Where possible, invoices should carry the company's GST details.

#### 12. Submission deadlines

Claims must be submitted within [30] days of the expense date through [the HR system]. Claims submitted later need approval of the department head and a written reason. Claims for expenses in a financial year must be submitted before [date] following the year-end.

#### 13. Review and payment

• Managers will approve, query or reject within [3] working days.
• Finance will verify within [3] working days.
• Approved claims are paid [with the monthly payroll / in the weekly batch]. Cut-off dates are published by Finance.
• Reimbursements appear as a separate line on the payslip.

#### 14. Advances

Advances may be issued for planned travel or events with the approval of the manager and Finance. The employee must settle within [7] days of completing the trip with proof of spending. Unsettled advances may be recovered from salary or full-and-final settlement in accordance with applicable law and the employee's acknowledgment.

#### 15. Tax treatment

Reimbursements are processed in line with current Income Tax provisions as advised by the Company's tax adviser. Amounts that do not qualify as business reimbursement may be treated as taxable and subjected to TDS.

#### 16. Misuse and consequences

Submitting false, altered, duplicate or personal claims is misconduct. The Company may reject the claim, recover amounts paid and initiate disciplinary action under the Company's code of conduct and applicable law.

#### 17. Records and audit

All claims and supporting documents are retained in the Company's system for [retention period as advised]. Finance may sample or audit claims at any time. Employees must cooperate with queries.

#### 18. Exceptions and review

Exceptions require written approval from [Department Head and Finance Head]. This policy is reviewed [annually] and the latest version is available on [location].

#### 19. Acknowledgment

I have read and understood this policy and agree to comply with it.

Name: ____ Employee ID: __ Signature: __ Date: ____

---

Annexure A (to be completed)

Rolling out the policy without a revolt

A beautiful policy that nobody reads is a wasted document. A rollout plan matters as much as the wording.

A practical rollout plan

1. Draft with input. Ask a few frequent travellers, a couple of managers and someone from finance to review the draft. They will spot unrealistic limits quickly.
2. Pilot the numbers. Check the proposed limits against the last six months of real claims. See how many would have been rejected or flagged. If the answer is half of them, the limits need adjusting.
3. Get leadership sign-off. Founders and senior leaders must follow the policy visibly, or no one else will.
4. Announce with examples. A one-page summary with three or four examples works better than a twenty-page document.
5. Train approvers. Managers need a short briefing on what to check and how fast to respond.
6. Set a start date and grace period. Allow a month during which claims under the old rules are still processed, with gentle reminders.
7. Collect feedback after 60 to 90 days. Adjust the limits and clarify wording.

Common mistakes to avoid

• Copying a large corporate policy. Rules designed for a company with a travel desk and a procurement team will smother a 50-person firm.
• Setting limits without data. Check actual costs in the cities where your people travel.
• Ignoring junior staff. A policy that expects employees to float large sums for weeks excludes those who cannot afford it. Use advances or company cards where possible.
• Making exceptions informal. If exceptions happen by chat message, you have no policy. Route them through a visible approval.
• Treating the policy as static. Prices rise and business models change. Review at least annually.
• Slow reimbursement. Fast, predictable payment is the best compliance tool, because people stop looking for workarounds.

Measuring whether your policy works

Policies drift unless someone measures them. Choose a handful of simple indicators and look at them monthly.

Review these with finance and HR together, then fix the root cause. If many claims lack proof, improve the upload experience before blaming employees. If a single manager's team always sits at the top of the spend table, have a conversation.

How software helps, and what to look for

You can run a reimbursement process on spreadsheets and email, and many small companies do it for years. The cracks usually show up as lost attachments, duplicate payments, manual rekeying into payroll and a scramble at audit time.

A good HRMS with expense management typically gives you:

• Policy rules built in: category limits, grade-wise ceilings, per-diem calculation and required fields enforced at submission.
• Mobile capture: employees upload receipts from their phone at the point of spend.
• Configurable approval chains: by amount, department or category, with delegation when approvers are away.
• Duplicate detection: flags repeated invoice numbers and similar claims.
• Payroll integration: approved claims flow into the payroll run with the right component type, with no retyping.
• Audit trail: time-stamped history of every action, searchable and exportable.
• Reports: category-wise spend, approval times and exception lists.

When you evaluate any tool, test it with your own policy. Can it handle your per-diem rules? Can it separate taxable from non-taxable components? Can it show the history of one claim in one screen? Pick the tool that fits the policy you have, not the one that forces you to rewrite it.

Frequently asked questions

1. What should an expense reimbursement policy include at minimum?

At minimum: purpose and scope, eligible and non-eligible expenses, pre-approval rules, approval limits, submission deadlines, proof requirements, payment timelines, advance handling, consequences for misuse and the review cycle. Add travel, per-diem and client entertainment rules if your people travel or meet clients regularly. The template above covers all of these.

2. How long should employees have to submit a claim?

Many companies use 30 days from the expense date, with a hard cut-off tied to the financial year end. The right window depends on your travel patterns. Shorter windows improve accounting accuracy; longer windows reduce rejected claims from forgotten submissions. Whatever you choose, apply it consistently and allow exceptions only with senior approval.

3. Is a per-diem the same as a reimbursement?

Not exactly. A reimbursement repays an actual cost shown on a bill. A per-diem is a fixed daily amount paid for being away on official travel, without individual meal bills. The tax treatment of each can differ and depends on current rules and facts, so confirm with your tax adviser how your per-diem should be classified and paid.

4. Can we reimburse expenses without receipts?

You can allow it in narrow cases, such as small tolls, parking or auto fares, using a signed declaration with a low per-claim and monthly cap. For anything larger, require a receipt. Without documentary proof, it is harder to show that the expense was incurred for business, and the amount may be treated differently for tax purposes. Keep exceptions rare and visible.

5. Is reimbursement taxable for the employee?

In general terms, repayment of genuine, documented business expenses is not treated as the employee's income, while fixed allowances or payments that are really personal benefits may be taxable unless a specific exemption applies. The details depend on current Income Tax rules, the nature of the expense and the employee's regime. Verify the latest rules with your chartered accountant before finalising your structure.

6. How do we stop employees from inflating claims?

Combine prevention and detection. Use clear limits and required proof, prevent self-approval, check for duplicates, require attendee names for entertainment, use per-diem to remove the incentive to inflate meal bills, and review exception reports and random samples every month. Pair these controls with a policy that states consequences, and make sure managers understand they are accountable for what they approve.

7. Who should approve the founder's expenses?

Someone other than the founder. In a company with co-founders or directors, a fellow director can approve. If there is no one, a finance head or external accountant can review the claims and report to the board or an advisory member. The point is that no individual approves their own spend, regardless of seniority.

8. How often should we update the policy?

Review at least once a year, and sooner if travel costs change sharply, you enter new cities, your tax adviser flags a rule change or you notice recurring exceptions. Version every change, communicate it with an effective date and keep old versions on file so past claims can be assessed under the rules in force at the time.

Conclusion

A strong expense reimbursement policy is a quiet kind of infrastructure. When it works, nobody talks about it. Employees get paid back promptly, managers know where they stand, finance closes the month without detective work, and auditors find a clean trail. When it is missing, you feel it in disputes, delays, uneven treatment and the slow erosion of trust.

The essentials are not complicated. Define the vocabulary. Make the workflow short and the approvers accountable. Set limits and per-diems based on real costs. Write explicit rules for travel and client entertainment. Ask for proof and make it easy to provide. Understand, in general terms, the line between reimbursement and taxable allowance, and confirm the specifics with your tax adviser against current rules. Connect approved claims to payroll without rekeying. Build fraud controls that are fair, visible and consistent. And keep an audit trail you could hand to anyone tomorrow.

Start small if you need to. Take the template above, adjust the numbers, test it against your last six months of claims and roll it out with a short briefing. Then improve it every quarter based on what the data shows.

If you would rather not manage this on spreadsheets, CozyHR is built for Indian SMBs that want HR, payroll and expense workflows in one place, with approvals, proof capture and payroll integration working together. You are welcome to try CozyHR and see how your own policy would look in practice. Whatever tool you choose, the most important step is to write the policy down and apply it fairly, and you can begin that this week.