rules.md

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Rules

Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic. Once a rule is created, it runs automatically every time a matching transaction syncs.


When to use rules

Rules are useful any time you find yourself making the same correction repeatedly. Instead of updating a transaction manually each month, create a rule once and let Kick handle it going forward.

Examples:


Rule Types

Kick has four standard Rule Types that run at different times and for different purposes:

  1. Transactions, Transfer, and Split Rules run when transactions are first synced or a new Rule is created
  2. Accounting Rules run every time a transaction is updated or recategorized

Transactions Rules

Transactions Rules run when new transactions sync into Kick or when a new Transactions Rule is created. They’re ideal for setting simple, proactive Rules to categorize transactions or move them to a different entity - including your Personal entity.

Transactions Rules currently support the following actions:

Examples:

Rules are especially helpful if you’re using Custom Categories, since these categories are not automatically assigned by Kick’s categorization model.

Creating a Rule ensures that your Custom Categories are automatically applied to the right transactions going forward.


Accounting Rules

Accounting Rules run every time a transaction is updated or recategorized.

These Rules are ideal for ensuring your transactions are consistently mapped to the correct account in your Chart of Accounts (CoA).

Examples:

Kick Rules

Kick Rules apply to transactions that aren’t affected by any custom Accounting Rules. They serve as the default mapping between your transaction categories and the Chart of Accounts. If no Accounting Rule is triggered, Kick will use these built-in Rules to assign transactions to the appropriate accounts.

These Rules cannot be edited or deleted, but they’re easy to override by creating a custom Accounting Rule. Accounting Rules always take priority - Kick Rules will never override them.


Transfer Rules

Transfer Rules run automatically when new transactions sync into Kick or when you create a new rule. They let you set custom conditions to match transfers between accounts, ensuring both sides of the transaction are properly linked.

Example:


Split Rules

Split Rules run automatically when new transactions sync into Kick or when you create a new rule. They let you set custom conditions to split transactions across categories or entities based on percentage or amount.

Examples:


Rule Groups

Most accounting rule engines rely on a long, disorganized list of Rules that are hard to manage at scale. Kick breaks this pattern with Rule Groups—a system that makes it simple to organize and prioritize your Rules with full transparency.

To create a Rule Group, click Add rule group in the top right corner of the Rules tab. To rename an existing group, including the default General Rule Group, click the three dots next to the group name and select Edit.

To change priority, just drag and drop your Rule Groups into the order you want—so you always know exactly how Rules will be applied.


Editing Rules

Editing a Rule

To edit a Rule, hover over it and click the three dots () at the far right of the row. From the dropdown menu, select Edit. This opens the Rule details so you can update the Conditions or Actions.

Disabling a Rule

To temporarily stop a Rule from running, click the three dots () and select Disable. Disabled Rules remain in your list but won’t apply to future transactions until re-enabled.

Deleting a Rule

To permanently remove a Rule, use the same menu and choose Delete. This action cannot be undone, so make sure you no longer need the Rule before deleting it.

Rule Prioritization

Rules are applied in order from top to bottom. You can drag and drop Rules to change their priority.

Conflicting Rules

If two or more Rules could apply to the same transaction, only the first matching Rule (based on priority) will run. Reorder or edit your Rules if one is unintentionally blocking another from applying.