Approving expense claims in a small team does not need an ERP. It needs a single intake point, a short list of who can approve which amounts, and a payout rhythm that people can set their watch by. The rest is discipline: claims decided within a few days, receipts attached, and a record of who said yes.
This version suits a twelve-person physiotherapy and wellness clinic with a practice manager doing the admin, and the examples are in Australian dollars. It does not cover tax or workplace law; ask your accountant about that.
What does the practice manager actually need to know?
Four things for each claim: who spent it, what it was for, how much and whether there is proof. Everything else is decoration. Staff in a clinic spend in small, scattered ways, such as consumables bought on the way in, a parking fee at a home visit, a course booking or a gift for a retiring colleague, so the form has to be quick enough to fill on a phone between patients.
Build the intake: a form, a sheet and a folder
- Make a shared form with fields for name, date paid, supplier, purpose, amount and a file upload for the receipt
- Send the form responses to one sheet so every claim becomes a row automatically
- Add columns the form does not fill: Approver, Decision date, Paid date, Note
- Create a folder where receipts are stored with the claim date in the file name
- Tell staff that claims not on the form do not get paid
The last point feels harsh and saves hours. A rule everyone knows is kinder than a manager chasing stray messages.
Which spending tiers work for a small team?
Tiers let small amounts move fast without making the owner a bottleneck. These numbers are hypothetical; set yours to match how much risk you are comfortable with.
| Amount (A$) | Who approves | Turnaround target |
|---|---|---|
| 0 to 75 | Practice manager | 2 working days |
| 75.01 to 300 | Practice manager, then owner confirms | 3 working days |
| Over 300 | Owner, before purchase | Before spending |
Remember that the practice manager's own claims go to the owner, even when they are small.
What about cash advances?
Staff sometimes need cash up front, for a conference or a supplies run. Treat the advance as its own line and reconcile it with a claim. Say the clinic gives A$300 for a workshop trip. The traveller returns with receipts of A$212.35 for accommodation and A$41.90 for meals, which total A$254.25. The balance is A$300.00 minus A$254.25, so A$45.75 comes back. Record the advance, the receipts and the refund as three rows tied to one reference so the books show a clean zero.
How often should claims be paid?
Pay on a fixed cycle. A fortnightly run lined up with the usual payday works for many small teams, because people stop messaging to ask where their money is. Cut-off is the day before the run; claims approved after cut-off roll to the next one. Combine all approved claims for one person into a single transfer and note the claim references in the payment description, so the person can match it to their own record.
Is it time to upgrade from the sheet?
If you need approvals by role, a trail of edits, or receipts that stay attached to each entry without a folder system, then a dedicated claims tool earns its fee. Make sure it supports Australian dollars and your payment routine. SpendixAI is an India-focused tracker for personal records and does not offer team approval workflows, so it would not replace this setup.
Monthly review
- How many claims were approved, queried and rejected
- Days from submission to payment, worked out from your own dates
- Any category that is growing quickly
- Receipts still missing
Useful ideas start with a clearer picture of your own spending.
Explore your reports


