Teams and small businesses often have simple spending rules: purchases above a certain amount need a receipt, some categories are off limits, and large single payments need a look. Spendix supports this through policies that flag transactions which break a rule. The word flag matters, because policies in the app flag; they do not block.
What policies can check
A policy is a rule with a scope and an action. The kinds of rule it can describe include a limit on any single transaction, a limit over a period, a receipt requirement above a certain amount, a category that should not be used, and spending outside normal hours. When a transaction trips one, it is marked and appears in the policy violations list.
Creating and editing policies is an administrative job that is done on the web, where the settings have room. On the phone you can read policies and review what they have flagged.
The review list
The policy violations screen collects flagged transactions that need a decision. Each shows that policy flagged the transaction, with the reason. When everything has been reviewed, the screen says so, and new flags will appear there as they arise. Access is limited by role, so someone without permission sees a no-access message.
Reviewing with fairness
A flag is a question, not a verdict. Many flagged transactions have good explanations: a one-time bulk purchase, a receipt not yet scanned, a legitimate exception. Approach each by checking the facts.
- Open the transaction and read the note.
- Check whether a receipt is attached or sitting in the inbox.
- Compare the amount with the limit and the context.
- Decide: accept, ask for more information, or follow up.
Treat the person who made the payment as a colleague, not a suspect. The tone of review determines whether people record spending honestly.
Use flags to improve the process
If the same policy flags many harmless transactions, the policy may be badly set. A receipt rule that flags small amounts will bury you in noise. Adjust the threshold so that flags are rare enough to be worth reading. Conversely, if nothing is ever flagged, check that the policy is enabled and its scope is right.
Pair with receipts and rules
Receipt requirements work best when receipts are easy to submit. Encourage scanning at the point of purchase so that the receipts inbox and matching handle the evidence. Combined with auto-categorisation rules, the flags highlight the exceptions while routine spending passes quietly.
| Policy type | Typical review question |
|---|---|
| Single transaction limit | Was the large payment expected? |
| Period limit | Did the team exceed its allowance? |
| Receipt required above amount | Is the receipt attached? |
| Blocked category | Why was this category used? |
| Out of hours | Was this a legitimate late payment? |
Privacy and tone
Flagged transactions often involve individuals, so handle the list with discretion. Discuss questions privately, not in group channels, and focus on the transaction rather than the person. Clear communication about what the rules are, and why, makes flags feel like a shared safety net instead of surveillance, and it makes people more willing to explain exceptions.
Document your policies
Even a small team benefits from writing its rules on a single page: what needs a receipt, what limit applies to a single purchase, which categories are off limits. A flag then points to a written agreement rather than someone's memory, and new members can understand the expectations without trial and error.
Remember the limits
Policies cannot stop a payment; they only highlight it afterwards. They are an aid to attention, not a control system. For real control, combine them with clear agreements about who may spend what, and treat the flags as the prompt for a conversation.
Useful ideas start with a clearer picture of your own spending.
Explore your reports