AS | Ankit Sarawagi|Founder, CFOmatrix·July 2026·7 min read | Right-sized SOP |
- Set category limits AND require a receipt. Limits make approval objective; the receipt proves the spend is real. A receipt is mandatory for every claim, no exception.
- One approver, not a chain. The manager approves, finance checks against the policy. No one approves their own expenses.
- Reimburse monthly, with payroll. A fixed monthly cycle with a cut-off date is fairer, cheaper to run, and predictable for employees.
- Record everything in one place. Claim, receipts, approval and payment all sit in your accounting tool, so the audit trail is a byproduct.
- Policy = the rules, this SOP = the process. Keep the two linked so employees know the limits before they spend.
| 5 steps Claim → approve → check → pay → record | 1 receipt Mandatory on every single claim | 1x / month Reimburse on the payroll cycle |
| 1. The five-step process 2. Receipts and category limits 3. The category-limits table | 4. Who approves, who checks 5. Petty cash and corporate cards 6. The audit trail and scaling up |
The Expense Reimbursement Process in Five Steps
The whole expense reimbursement process is a short, repeatable loop. An employee spends their own money on something business-related, and the company pays it back, cleanly and on a schedule. Resist the urge to add steps: for a team of five to forty people, five steps with one approver is all you need. This is the pillar SOP, and it sits inside our wider finance SOPs and controls guide.
“My rule for reimbursements is simple: set category limits and always require a receipt, and pay everyone back once a month with payroll. That one cycle removes all the noise. People know exactly when their money comes back, and finance runs it once, not fifty times a month.”
Ankit Sarawagi, from running finance for lean startupsReceipts and Category Limits: the Two Non-Negotiables
Two rules do almost all the work in a reimbursement SOP: every claim needs a receipt, and every category has a limit. Together they turn approval from a judgement call into a simple check. The receipt proves the spend was real and business-related; the limit tells finance and the employee, in advance, what is reasonable.
- Every line has a receipt or valid tax invoice
- Within the category limit
- Genuine business purpose
- Approved by the manager
- Submitted before the monthly cut-off
- No receipt: not paid, no exception
- Over the limit with no prior approval: capped at the limit
- Personal or out-of-policy items
- Duplicate of a card or petty-cash spend
For GST-eligible purchases, insist on a proper tax invoice showing the vendor GST number, not just a card slip. A missing GST number quietly forfeits your input tax credit, which is a pure cash loss on top of the reimbursement.
Remember the division of labour: this SOP is the process, and your expense and reimbursement policy is the rules, the actual limits, the eligible categories, the claim window. Publish the policy so employees read it before they spend, and point the SOP at it rather than duplicating the numbers.
The Category-Limits Table (Editable Example)
Here is a starter set of category limits. Treat the numbers as examples: set your own in the policy to match your city, team and stage. What matters is that the limits exist, are written down, and are the same for everyone at a given level.
| Category | Example limit | Receipt |
| Meals (per day, on travel) | ₹800 per person | Required |
| Local travel (cab / auto) | Actuals, economy | Required |
| Intercity travel (air / rail) | Economy / AC; pre-approve | Required |
| Hotel (per night) | ₹5,000 (metro), ₹3,500 (other) | Required |
| Client meeting / entertainment | ₹1,500 per head; pre-approve | Required |
| Software / subscriptions | Manager pre-approval | Required |
| Office / misc supplies | ₹2,000 per claim | Required |
Grab our ready-to-use expense claim form and reimbursement tracker: one row per line, receipt reference, category, limit check, approval column and a monthly payout summary. Print it or use it as a sheet.
Download the claim form & trackerWho Approves, Who Checks: Segregation Without Bureaucracy
The one control that must never bend is this: no one approves their own expenses. The person who spends is not the person who approves, and the person who pays is not the person who approves either. That is basic segregation of duties, and it holds even when your finance “team” is one person.
- Manager approves the claim
- Finance checks vs policy and pays
- Two people, always
- Never self-approved
- Approved by the founder or another head
- Founder reviews all at month-end
- Needs prior approval to be paid in full
- Otherwise capped at the limit
- Founder sign-off if sensitive
For a tiny team, the founder is the natural second pair of eyes: eyeball claims as they come, and at the month-end financials review approve all reimbursements together before payroll runs. That single monthly review is the compensating control that lets a lean team keep segregation without hiring for it. The same approval logic runs through the payment and maker-checker SOP.
Petty Cash and Corporate Cards, in Brief
Reimbursement is for money employees spend from their own pocket. Two other channels spend company money directly, and they need the same receipt-and-record discipline so they do not become a loophole.
- Petty cash: keep a small float with one custodian, log every disbursement with a receipt, and top it up against the logged spends (an imprest system). Reconcile it monthly. It is for tiny, immediate cash needs, not a way to skip the claim form.
- Corporate / company cards: the cardholder still submits receipts for every transaction and codes them to categories, and someone other than the cardholder reviews the monthly statement against those receipts. A card is not pre-approved spending; it is faster payment with the same proof requirement.
The classic error is an employee paying on the company card AND filing a reimbursement claim for the same spend. Finance’s check must catch duplicates: match every reimbursement claim against card and petty-cash spends before it is paid.
The Audit Trail, and When to Add a Step
Startups rarely get caught for doing the wrong thing; they get caught for doing the right thing and never documenting it. The good news is that if you run the five steps above, the documentation happens on its own. Every claim leaves a trail, and it should all live in one place.
| Record | Where it lives |
| The claim form | Accounting tool (Zoho Books / QuickBooks) or the tracker sheet |
| The receipts / tax invoices | Attached to each claim line in the tool |
| The manager’s approval | In-tool approval log (or saved back if approved on email) |
| The finance check | Marked in the tool / tracker against the limit |
| The payment | Payroll run + expense entry booked to the ledger |
Approving on WhatsApp or Slack for speed is fine, as long as you save that approval back into the record. An approval no one can find later is the same as no approval when the auditor asks.
Lean version vs when to add a step
- The claim form / tracker sheet
- Manager approves on email or chat, saved to the record
- Finance checks and books in the accounting tool
- One monthly payout with payroll
- Volume too high for a sheet: add an expense app that enforces limits and captures receipts by photo
- Multiple teams: route approvals by manager automatically
- Frequent travel: add pre-trip approval and per-diems
“Reimbursements go wrong in exactly two ways: no receipt, and no record of who approved. Fix those two, pay once a month, and the audit trail writes itself.”
Ankit Sarawagi, CFOmatrixFrequently Asked Questions
What is the employee expense reimbursement process?
It is the simple flow a company follows to pay employees back for money they spent on business: the employee submits a claim with receipts, their manager approves it, finance checks it against the expense policy and category limits, the approved amount is paid out in the next monthly payroll run, and the whole thing is recorded in the accounting tool. Keeping the process to those five steps, with one approver and monthly payout, is what keeps it fast and defensible in a lean startup.
Are receipts mandatory for expense reimbursement?
Yes. A receipt or valid invoice should be mandatory for every claim, with no exception. A receipt is what proves the spend was real, business-related and within policy, and it is exactly what an auditor or diligence team asks for. Set category limits and require a receipt for each line: no receipt, no reimbursement. For GST-eligible purchases, a proper tax invoice with the vendor GST number also protects your input tax credit.
Should there be category limits on expense claims?
Yes. Setting per-category limits (for example a daily meal cap, a hotel-per-night cap, class of travel) makes approval objective instead of a judgement call, keeps spend predictable, and means finance is checking a claim against a rule, not negotiating. Publish the limits in your expense policy so employees know them before they spend. Anything above a limit needs explicit prior approval, otherwise the claim is capped at the limit.
Who approves employee expense claims?
The employee’s manager (or department head) approves the claim, and finance then checks it against the policy and limits before paying. That is two sets of eyes with no long chain. No one approves their own expenses, not even the finance team or the founder: finance does the payout, someone else approves it. The founder approves sensitive items and reviews all expenses at the monthly financials review.
How fast should employee reimbursement happen?
Reimburse on a fixed monthly cycle, paid out with payroll. Set a cut-off date each month: claims approved before the cut-off are paid in that month’s payroll, and later claims roll to the next cycle. A predictable monthly payout is fairer and far less work than paying reimbursements ad hoc through the week, and it gives employees a clear expectation of when they get their money back.
How do I keep expense reimbursement audit-ready?
Every claim should leave a record: the claim form, the attached receipts, the manager’s approval, the finance check, and the payment entry in your accounting tool. Keep the approval inside the tool wherever possible so it carries an audit log; if you approve on email or chat for speed, save that approval back to the record. Booked and stored this way, the documentation is produced as a byproduct of the process, which is exactly what an auditor or DD team wants to see.
This is general educational information for founders, current to mid-2026, drawing on the author’s experience running finance for lean startups, and is not legal, tax or audit advice. The category limits shown are illustrative examples, not recommendations; set your own in your expense policy. Tax and compliance rules (GST, input tax credit, MCA audit-trail requirements) change; verify the current position or consult a professional before acting on a specific matter.
The Payroll Processing SOP
Finance SOPs & Controls: The Founder’s Guide
AS | Founder, CFOmatrix | Finance Strategy & Equity Compliance CFOmatrix is a knowledge platform focused on how finance actually works inside growing companies. This SOP draws on hands-on experience building right-sized finance processes for lean startups, from approvals and the tool stack to an audit trail that holds up in diligence. |