Most people meet rules as a way to file transactions into categories automatically. A less obvious feature is that a rule can look at whether a transaction has a receipt. In the rule editor, the conditions include options such as has a receipt and no receipt. That small switch opens some useful ways to keep your records tidy.
What the condition does
A rule is a set of conditions plus actions. When a transaction meets the conditions, the actions apply: set a category, flag it as business or personal, rename the merchant, mark it reimbursable or exclude it from reports. Adding a receipt condition means the rule fires only for transactions that do, or do not, have a receipt attached.
Because you can choose to match all conditions or any of them, the receipt test can be combined with others such as an amount threshold, a merchant or a direction of money. For example, money out above a certain amount with no receipt.
Putting it to work
Here are a few practical uses, each of which depends on your own situation.
- **Spot undocumented large spending.** A rule for payments above a chosen amount that have no receipt can tag them so you can find them quickly and go looking for the paper.
- **Separate documented business costs.** A rule that marks purchases with a receipt as business, while leaving undocumented ones for manual review.
- **Treat reimbursable items carefully.** Flag expenses you intend to claim, and use the no-receipt condition to catch those still missing proof.
The best uses involve a decision that you would otherwise make by eye each week. If you find yourself scanning the list for big payments without paper, a rule can do the scanning.
A worked scenario
Imagine a person who occasionally buys work supplies on a card and wants each one to have a receipt. They create a rule: money out, above 2,000 units, no receipt. The action sets a distinct label or category used only for review. Each week, anything under that label is a to-do: find the receipt, attach it, and the rule no longer applies on the next run.
The rule does not stop anything from happening. It simply makes missing evidence visible.
Things to keep in mind
A rule that depends on receipts changes its mind over time, because receipts are attached after transactions arrive. A payment can match a no-receipt rule on Monday and stop matching on Thursday once the slip is attached. That is helpful if the rule only tags, but it can be confusing if the rule also changes a category.
For that reason, keep receipt-based rules light. Use them for flags and review labels rather than for decisions that should stay fixed. Remember too that rules can be applied to existing transactions as well as new ones, so test before you apply broadly, and read the preview of what a rule would match.
Who can write rules
In shared workspaces, writing rules is limited to certain roles. The editor notes that only owners, admins and accountants can write auto-categorisation rules. If you cannot find the option, the role you hold is probably the reason, and an administrator can help.
A useful pairing with reports
When a receipt rule tags undocumented spending, a report filtered by that tag gives a monthly list of what still needs proof. Reviewing it takes a minute and gives a clear to-do list before the month closes, which is when finding a missing slip is still realistic.
Keeping it simple
Start with one rule and run it for a month. If the flagged list is useful, keep it; if it is noisy, adjust the amount threshold. A single well-tuned receipt condition is worth more than a handful of clever ones nobody reviews.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

