The simplest approval process for a small team is a monthly batch: everyone submits by a cut-off day, one person checks each claim against a short list, and a single payment run follows. It avoids a daily trickle of emails and makes it easy to see what the month cost. The example uses pounds and made-up amounts.
Why batch claims instead of approving them one by one?
Daily approvals mean daily interruptions and daily payments to reconcile. A batch asks claimants to be organised once a month and gives the approver one sitting. The trade-off is delay: someone who spent money early in the month waits. For a studio or small shop that is usually acceptable. If it is not, run a second batch mid-month.
What does the approver check on each claim?
- Is there a receipt or a clear proof of payment?
- Does the amount on the receipt match the amount claimed?
- Is the category right?
- Was it for the business, and does it match what the team agreed?
- Is it a duplicate of an earlier claim?
Five yes answers means approve. Any no means query it with a one-line note.
A worked example
Say a seven-person studio has a cut-off of the 25th. One team member's claim has three lines:
| Line | Receipt shows | Claimed | Outcome |
|---|---|---|---|
| Train fare | £64.20 | £64.20 | Approved |
| Hotel for client visit | £118.00 | £118.00 | Approved |
| Working lunch | £37.50 | £37.50 | Approved |
| Claim total | £219.70 | £219.70 | Paid in the run |
Check: 64.20 + 118.00 + 37.50 = £219.70. If the lunch had been claimed as £47.50 against a £37.50 receipt, the approver would query that one line and approve the rest.
How do I keep a record of who approved what?
- A column for Approved by and Date approved.
- A column for Paid on.
- A rejected claim kept in the sheet with its reason, not deleted.
- A monthly tab that is locked once paid.
When might a tool be better?
If you find yourself chasing receipts every month or losing track of who approved a claim, consider a tool with a built-in queue. Ask whether it handles approvals, limits and receipts attached to each claim. SpendixAI is built around India and INR, so it is not offered here as a UK product, and as a Pro personal workspace it is not a team approvals tool.
How do I deal with cash and missing receipts?
Agree one form of proof for small cash spends, such as a photo of the item and a short note, and a limit below which that is enough. Above the limit a receipt is required.
For a lost receipt, ask the claimant to sign a one-line statement saying what was bought and why, and mark the line Approved without receipt so it is visible later. Keep the limit low and review those lines at each batch.
If the same person has several such lines, have a quiet conversation, because it usually means a habit problem, such as photographing receipts too late, and not dishonesty.
What if the approver is also a claimant?
Someone has to approve the approver. In a seven-person studio, that can be a partner or the owner, and for the owner's own claims a second person who simply confirms the receipt. Write this into the rule, in one line, so nobody feels singled out. The point is not distrust; it is that anyone who signs off money should not sign off their own.
Your first month
- Pick the cut-off date.
- Share the five-point check with the team.
- Create the sheet with approver and paid columns.
- Put the payment run in the diary.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


