Transaction Rules | Finicom

Automatically categorize, rename, and transform your transactions before they sync to destinations.

Intro

Transaction Rules let you automatically modify transactions before they sync to your destinations. You can rename merchants, assign categories, adjust amounts, change dates, and more — all based on conditions you define.

Rules are applied before destination filters, so your filters will see the modified values. For example, you can categorize transactions first, then filter by category.

How Rules Work

Each rule has three parts:

  1. Condition: A set of criteria that determines which transactions the rule applies to (e.g., "Merchant equals Amazon").
  2. Actions: One or more field modifications to apply when the condition matches (e.g., set Category to "Shopping").
  3. Priority: Rules are evaluated in priority order (lowest first). If multiple rules modify the same field, the last match wins.

Rules are evaluated for every transaction that syncs to a destination. They don't modify your original bank data — they only transform what gets sent to your destinations.

Creating a Rule

  1. Navigate to the Rules page in your dashboard
  2. Click Create Rule
  3. Give your rule a name (e.g., "Categorize Amazon purchases")
  4. Set up a condition using the condition builder — choose a transaction field, an operator, and a value
  5. Add one or more actions — select which field to modify and what value to set
  6. Click Save

Conditions

Conditions determine which transactions a rule applies to. You can match on any transaction field:

  • Merchant — The merchant or payee name
  • Description — The transaction description or memo
  • Amount — The transaction amount
  • Status — Transaction status (Pending, Posted, Void)
  • Creation Date — When the transaction occurred
  • Currency — The 3-letter currency code
  • Institution — The bank or institution name
  • Account Name — The account name
  • Category — The transaction category (for Plaid sources)

Conditions support standard comparison operators: equals, not equals, greater than, less than, contains, and more.

Actions

Actions define what changes to make when a rule's condition matches. Each action sets a transaction field to a new value. Available fields:

  • Merchant — Override the merchant name
  • Description — Override the description
  • Amount — Override the amount
  • Status — Change the transaction status
  • Creation Date — Override the transaction date
  • Currency — Override the currency code
  • Institution — Override the institution name
  • Account Name — Override the account name
  • Category — Assign or override the transaction category

A single rule can have multiple actions. For example, one rule could set both the merchant name and category at once.

Priority and Ordering

Rules are evaluated in priority order from lowest to highest. If multiple rules match the same transaction and modify the same field, the highest priority rule wins (last match).

You can reorder rules by dragging them in the rules list. Rules at the bottom of the list have higher priority and take precedence.

Enabling and Disabling Rules

Each rule can be individually enabled or disabled using the toggle in the rules list. Disabled rules are skipped during evaluation but are preserved so you can re-enable them later.

Per-Destination Opt-Out

Transaction rules are applied organization-wide by default. If you want a specific destination to receive unmodified transactions, you can disable rule application in that destination's settings by toggling off "Apply transaction rules".

Plan Limits

Transaction rules are available on all paid plans:

  • Free: Transaction rules are not available
  • Starter: Up to 3 active rules
  • Personal: Up to 3 active rules
  • Pro: Unlimited active rules
  • Business: Unlimited active rules

You can create additional rules beyond your limit, but only the allowed number can be enabled at once.

Tips

  • Start with simple rules targeting specific merchants, then expand to broader conditions
  • Use the category action to organize transactions that arrive without categories (e.g., from Mercury or Stripe sources)
  • Remember that rules apply before destination filters — you can filter on values set by rules
  • If a rule isn't working as expected, check its priority relative to other rules that might override it