Stop sorting through transactions yourself and enjoy a tidy transaction history.
Transaction Rules puts your spending on autopilot by applying custom “if-this-then-that” logic to every new entry. Let’s see how it works.
What are Transaction Rules? (Mobile)
Think of them as automated filters for your transactions. Define what to watch for, like “Starbucks,” any charge over $100, or transactions on a specific account, and choose what happens next: rename, re-categorize, tag, or even exclude from calculations. From that moment on, matching entries flow into your account exactly the way you want.
How to create your first rule
-
Go to the Transactions tab
Tap the ⏩ icon (top right) → Create rule - Name your rule. This means you can easily find it later.
-
Set the trigger. What should the rule look for?
- Merchant name or Original statement (contains / exactly matches)
- Amount (equals, greater than, less than, between)
- Category
- Account
-
Choose the action. What should happen next?
- Rename merchant (e.g., “Starbucks” → “Coffee Shop”)
- Change category (e.g., “Dining Out”)
- Add hashtag(s) (e.g., #work, #reimbursable)
- Mark as Don’t count (exclude from your calculations)
-
Apply & save
- (Optional) Toggle “Apply for [X] existing transactions” if you want the rule to update your past transactions
- Tap Save and you're done! 🎉
Your rule will now automatically organize future transactions that match your trigger. You can edit or delete it anytime.
How to edit or delete a rule
- Go to the Transactions tab and tap the ⏩ icon in the top right corner.
- Find the rule you want to change. Tap on it to open the rule details.
-
To edit the rule:
- Make the necessary changes (name, category, merchant, etc.).
- Tap Save to apply the updates.
-
To delete the rule:
- Tap the trash icon in the top right corner of the screen.
-
Confirm the deletion.
If you have any other questions about Transaction Rules or need help setting them up, feel free to reach out to us at support@pocketguard.com. We're happy to help!
Scan to install



Comments
0 comments
Article is closed for comments.