Expense reimbursement policy and approval workflow (with a template)

Every company reimburses expenses, but few have an expense reimbursement policy that people actually read. Employees are unsure what they can claim, managers approve whatever reaches them, and finance spends the end of each month chasing missing bills and arguing over amounts that were never agreed. The result is slow repayments, frustrated staff and costs nobody planned for.

A good policy fixes this with a few clear rules and an approval workflow that matches them. This guide explains what the policy should cover, how to design the approval chain, the controls finance needs, and ends with a short template you can adapt for your company.

Why you need a written expense reimbursement policy

Without a written policy, every claim becomes a negotiation. One manager approves a business-class flight, another refuses a taxi fare. Employees who spend their own money for work feel the inconsistency quickly, and finance has no basis for saying no.

A written policy does three things. It tells employees in advance what they will get back, so they spend accordingly. It gives approvers a standard to apply instead of a judgement to make. And it gives finance and your auditors a reference point for every payment made.

What the policy should cover

Eligible expenses

List the categories you reimburse, such as travel, local conveyance, accommodation, meals while travelling, client entertainment, internet or phone for remote staff, and small purchases made for the company. Equally important, list what is not reimbursed: personal items, fines, alcohol unless approved for client events, upgrades without approval and so on.

Limits

Set a limit per category, per day or per trip. If roles travel very differently, set limits by grade or level. Limits should be realistic for the cities your people travel to; unrealistic limits simply lead to exceptions for everything.

Pre-approval

Decide which expenses need approval before they are incurred. Travel outside the home city, international trips, client entertainment above a set amount and any purchase of equipment are common candidates. Pre-approval prevents the hardest conversation in finance: refusing money someone has already spent.

Documents

Every claim needs proof. Specify the acceptable documents: an itemised bill or invoice, a boarding pass or ticket for travel, and a payment record where the bill does not show one. For expenses where the company may claim GST input credit, such as hotel stays or purchases, ask for a tax invoice showing the company's name and GSTIN.

Deadlines

Set a deadline for submitting claims, for example within 30 days of the expense, and a cut-off each month after which claims move to the next payment cycle. Late claims are harder to verify and distort monthly costs.

Payment

State when approved claims are paid, for example with salary or on a fixed date each fortnight, and how: bank transfer to the salary account is the simplest.

Designing the approval workflow

The policy says what is allowed; the approval workflow decides who checks it. Each approver should be checking something different, otherwise extra steps add delay without adding control.

• First step: business purpose. Was this expense genuinely for work, and was it expected? The reporting manager or HR is best placed to answer.
• Second step: policy and documents. Is it within the limits, is the bill valid, is the amount correct? HR or an HR Director often checks this against the policy.
• Final step: finance. Is the claim correctly coded, is the GST invoice in order, and is it ready to pay? Finance approves and then pays.

Define each step by role, not by person. "The reporting manager, then HR, then Finance" survives a manager's resignation; "Rahul, then Priya" does not. For a deeper look at designing chains like this, see our article on approval hierarchies that scale.

Rules that keep the workflow fair

• Nobody approves their own claim. If the person at a step is the claimant, the claim should go to someone else in that role or skip to the next step.
• Rejections need a reason. The employee should know whether to fix a document or accept the decision.
• A change in the chain does not move claims already submitted. Each claim should follow the chain that applied when it was made, so nobody's claim is caught in a reorganisation.
• Set a turnaround target. For example, two working days per step. Claims waiting longer should be visible to the next level.

Controls finance should insist on

• Duplicate checks. The same bill should not be claimed twice, by the same person or by two people from a shared meal.
• Bill dates within the claim period. Old bills submitted months later deserve a closer look.
• Advances settled against claims. If you give travel advances, each trip's claim should be offset against the advance, and unspent amounts recovered.
• Cost tracking. Code each claim by category and, where relevant, by client or project, so you can see what travel and entertainment really cost.
• A complete trail. Who submitted, who approved at each step, when, and when it was paid. Auditors and employees will both ask.

Expense reimbursement policy template

Adapt the following to your company. Keep it to one or two pages; anything longer will not be read.

1. Purpose and scope. This policy covers reasonable expenses incurred by employees while carrying out company work. It applies to all employees, including those on probation.
2. Eligible expenses. Business travel, local conveyance for work, accommodation and meals while travelling, approved client entertainment, and approved purchases made for the company.
3. Not reimbursable. Personal expenses, traffic and parking fines, travel upgrades without approval, alcohol except at approved client events, and expenses without valid proof.
4. Limits. As set out in the annexure for each category and grade. Amounts above the limit are reimbursed only with prior written approval.
5. Pre-approval. Required for outstation and international travel, client entertainment above ₹[amount] and any equipment purchase.
6. Documents. An itemised bill or invoice for every expense; tickets or boarding passes for travel; a GST invoice in the company's name and GSTIN for hotels and purchases.
7. Submission. Claims are submitted within [30] days of the expense through the company's expense system. Claims received after the [25th] are processed in the next cycle.
8. Approval. Claims are approved in order by the reporting manager or HR, then HR Director, then Finance. No employee approves their own claim. Rejected claims include a reason.
9. Payment. Approved claims are paid by bank transfer [with the monthly salary / on the 1st and 15th of each month].
10. Advances. Travel advances are settled against the trip's claim within [15] days of return; unspent amounts are returned or recovered.
11. Misuse. False or inflated claims are a disciplinary matter and are recovered in full.
12. Review. Finance reviews this policy and its limits every year.

Running it without the paperwork

A policy only works if claiming and approving are easy. If employees have to email scanned bills and chase approvers, they will delay claims or skip the rules. Putting claims, bills and approvals in one system makes the policy the path of least resistance.

Techno IQ handles reimbursements with approval chains you set by role, such as HR, then HR Director, then Finance. Each claim keeps the chain it was submitted under, waits for the right approver at each step, and moves to Finance to pay once approved, with every decision kept on the claim. Business trips and their expenses are recorded and approved in the same product. If you would like to see it with your own policy, book a demo of Techno IQ.