Spending policies for a small team that don't feel like red tape
Published
Small teams often avoid writing a spending policy because they do not want to seem bureaucratic. The result is the opposite: every unusual expense becomes a one-off conversation, and people guess what is acceptable.
A short policy answers those questions in advance.
Three rules are enough to start
- A limit per expense. Anything above this amount needs a word with someone first.
- A receipt from a certain amount. Below it, a note is fine. Above it, the paper is required.
- A monthly limit per person. Not a target, a ceiling that tells you when a pattern is worth a chat.
You can set limits for everything or for particular categories, and per day as well as per month, so that "software" can be generous while "meals" is modest.
Flag, don't block
The policies in Spend never stop anyone from saving an expense. They mark the ones that break a rule, so that people can still record what happened and the owner can look at what stands out. Blocking people at the moment of payment mostly teaches them to forget to record it.
Explain the why
A limit with a reason ("above this we want to compare prices first") is followed. A limit without one is worked around.
Keep it current
Look at the flagged expenses every month. If the same rule fires constantly for good reasons, the limit is too low. If it never fires, it may be too high, or simply doing its quiet job.
Share it, once
Put the policy where the team will see it, in a sentence each, and tell new members on day one. The goal is a team that knows what is normal, not one that checks every receipt.