You can run a sound expense claim approval process for a small team with three things: one standard claim form, one place where claims arrive, and a written rule for who approves what. Email threads and a shared spreadsheet are enough if every claim passes through the same four states and nobody pays out from memory.
The examples below use Canadian dollars and a studio of seven people. Nothing here is about tax or employment rules, which differ by province and by business; this is about records and habits, and your accountant can tell you what applies to you.
Why does email-and-spreadsheet approval break down?
The failure is rarely the spreadsheet. It is that claims arrive in four different ways: a forwarded receipt, a photo in a chat, a line typed into the sheet, a verbal remark at the Monday meeting. The lead then has to remember which of them were approved, which were queried and which were paid. By the third month, a claim from February is still sitting in someone's inbox and the employee is too polite to ask.
The fix is to shrink the number of doors. Every claim goes through one inbox address or one shared form, and the spreadsheet is filled from that door only, never from chat messages.
What should a claim form capture?
- Claimant name and the date they paid
- Merchant and a one-line purpose, such as client meeting or conference booth supplies
- Amount in the currency actually paid, plus the currency code if it is not Canadian dollars
- Who it should be charged to: a client job, an internal budget, or general overhead
- A photo or PDF of the receipt, attached, not promised for later
- Claim date, so you can see how long approval takes
Add nothing else at the start. Every extra mandatory field becomes a reason for a claim to bounce back.
Who approves what? Write the thresholds down
Pick limits that suit your team and put them in one short note that everybody can read. A common shape is a tier for small items the lead approves alone, a tier that needs a second person, and a category of items that must be approved before the money is spent. The numbers below are made up for illustration; choose your own.
| Claim size (C$) | Approver | Receipt needed | Pre-approval |
|---|---|---|---|
| Up to 100 | Team lead | Yes | No |
| 100.01 to 500 | Team lead and a second signer | Yes | Preferred |
| Above 500 | Owner | Yes, plus quote | Yes, before buying |
| Travel booked for the team | Owner | Yes | Yes |
The second signer matters most for a lead's own claims. Nobody should approve their own expenses, so decide in advance who signs when the lead is the claimant.
A worked month: four claims, one payout
Say four claims land in March: a taxi at C$38.50, a client lunch at C$64.20, a design plug-in at C$129.00 and parking at C$22.75. Each is logged with its status. The lead approves the first two, queries the lunch because the guest name is missing, and approves the plug-in with a note that it belongs to the Harbour Co job.
Once the lunch is fixed, the four claims add up to C$254.45 (38.50 plus 64.20 is 102.70, plus 129.00 is 231.70, plus 22.75 is 254.45). Instead of four small transfers on four days, the studio pays one batch on the 5th of the next month. That gives one bank entry to match against the sheet, and one date when everybody knows to expect their money.
How do you track a claim's status?
Use four statuses and nothing fancier: Submitted, Query sent, Approved, Paid. Add two date columns, one for approval and one for payment. A simple filter on the status column then shows everything stuck. Review the Submitted and Query rows at a fixed weekly time. If anything has been waiting longer than seven days, the lead sends a reminder, and that discipline matters more than any software.
When is a spreadsheet no longer enough?
Signs that you have outgrown the sheet: claims regularly sit unseen for weeks, two people edit the same row, you need to know who changed an amount, or you are chasing receipts at year end. At that point look for a tool that has a proper submit-and-approve queue and a change history. Check that it fits your country and currency, because many tools, including SpendixAI, are built around India and INR and do not run approvals for teams.
Starter checklist
- Pick one door for claims and tell the team in writing
- Publish the approval thresholds and the self-approval rule
- Create the form with only the fields above
- Set a weekly review time and a monthly payout date
- Keep receipts and the sheet for as long as your accountant advises
Useful ideas start with a clearer picture of your own spending.
Explore your reports

