Skip to main content

Set up transaction rules

Rules categorize repeat transactions for you, like the monthly landscaping payment or the utility bill.

M
Written by Michael Bollinger

Rules categorize repeat transactions for you, like the monthly landscaping payment or the utility bill. You can also have them approved automatically.

Add a rule

  1. On Transactions, click Rules, then Add rule.

  2. Name and scope: enter a Rule name, choose the Direction (Money in or Money out) and a Bank account, or leave All bank accounts.

  3. Match when: choose whether the transaction must match All or Any of your conditions, then add conditions:

    • Description contains, doesn't contain, or is exactly some text.

    • Amount equals, doesn't equal, is greater than or is less than an amount.

    Tip: Make a rule's conditions specific enough that they don't catch other transactions, but not so specific that they miss the ones you want. If the bank description is Garbage Pickup Ref 12306044, use Description contains Garbage Pickup and leave out the reference number, because it changes with each charge.

  4. Then apply: under Transaction type, keep Regular transaction and choose the Category and, if you like, a Vendor. The vendor must already be in your Vendors list; you can't add one from the rule. Leave Vendor blank if these transactions shouldn't have one. For a transfer, choose Transfer to (money out) or Transfer from (money in) instead and pick the other account. A rule can't be saved without one or the other, so a rule can't leave matching transactions with no category.

  5. Turn on Auto-approve matching transactions to skip review for these.

  6. Click Save rule.

Tip: To start from a transaction you already have, open it and click Create rule. The form fills in from that transaction.

How rules work

  • New transactions get the first rule they match. Rules are checked in the order they were created; the # column shows the order. Rules also run in a nightly sweep at 6 pm Eastern, which is why a transaction can be categorized overnight.

  • When you save a rule, it's also applied to transactions waiting on For review that don't have a category yet, or whose category PayHOA only guessed from an earlier transaction with the same description.

  • Rules never change a category that a person or Gable chose, a transaction an earlier rule already handled, or anything already approved. Change those by hand, or in bulk with Actions → Change category on For review; on the other tabs, where approved transactions are, the same action is called Replace category.

  • Rules do replace a guessed category. When PayHOA fills in a category by itself from an earlier transaction with the same description, that's only a guess. A matching rule takes the transaction over: it sets the rule's category (or records the transfer) and approves it if the rule auto-approves. If a rule matches a large backlog of guessed transactions, it takes up to 100 of them each time it runs and picks up the rest on the following nights. Older guessed categories, from before PayHOA began recording where each category came from, are left alone.

  • Rules don't apply to PayHOA financial account transactions.

  • A rule sets the category, the vendor and the approval, and nothing else. A rule adds its vendor only when the transaction doesn't have one yet. A rule can't tick Outside Revenue (a checkbox on income transactions on the older accounting version, for associations on accrual reports). For income such as bank interest that a rule categorizes and approves, open the transaction and tick Outside Revenue yourself if it should count on accrual reports.

  • Rules keep running when Gable's category suggestions are turned off. See Don't want Gable's suggestions?

  • Two rules for the same vendor are fine when each is limited to a different Bank account. But a rule set to All bank accounts matches every account, so if it was created first it wins everywhere. Put the account-specific rule first, or limit both rules to their accounts.

Why a rule did or didn't apply to a transaction

How a rule-handled transaction is marked. On Transactions, a transaction that a rule categorized (or recorded as a transfer) has a small tag icon on its row. Point to it and it reads Transaction is matched via the {rule name} rule. A transaction without the tag wasn't handled by a rule: its category came from a person, from Gable, or from an earlier transaction with the same description.

If some transactions were picked up by a rule and others that look the same weren't, for example some of your monthly transfers but not all, open Transactions → Rules and compare the rule with a transaction it missed. Check these in order:

  1. The description wording. A condition set to is exactly only matches a description that's the same from first character to last (capital letters don't matter). Bank descriptions often change from one month to the next, with a date, a reference number or a different account suffix. Use contains with the part that never changes.

  2. The direction. A Money out rule never matches a deposit, and a Money in rule never matches a payment. The two sides of a transfer need a rule each: one Transfer to rule for the money leaving and one Transfer from rule for the money arriving, or one rule on one side and delete the other side.

  3. The bank account. A rule limited to one Bank account only matches transactions in that account.

  4. All or Any. With All, every condition has to match. An Amount condition set to equals misses a transfer of a different amount.

  5. An earlier rule. A transaction gets the first rule it matches, in # order, and only one.

  6. The transaction was already handled. Rules skip a transaction that's approved, one whose category a person or Gable chose, a split transaction, one that's already a transfer, a journal entry, and PayHOA deposits and other transactions PayHOA records itself.

  7. Timing. A new rule is applied to what's waiting on For review when you save it, and rules run again each evening, so a transaction that arrived before the rule existed and was approved by hand stays as it was.

A rule only looks at transactions that are still waiting on For review. To change ones that are already approved, change them by hand, with Actions → Replace category, or from a file. See Add categories, vendors or memos to transactions from a file.

Manage rules

The Manage rules page lists every rule with its # (the order it's checked in), Rule, Direction, Conditions, Then apply and Auto-approve. Use the ⋯ menu to edit or delete a rule. Deleting asks Delete transaction rule; click Yes, delete.

A warning such as Deleted category or Deleted vendor means something the rule uses was removed. Edit the rule to fix it.

Gable suggests rules

When you've categorized the same kind of transaction the same way by hand three or more times, Gable offers to create a rule for you. Accept it, dismiss it, or snooze it until tomorrow. Rule suggestions are on Other Tools → AI Settings → Autopilot: under Transaction categories (in the Books group), click Review beside Gable suggests N rules. The line only shows when Gable has a rule to suggest.

Did this answer your question?