Forecasted- and transaction categorization rules

Create custom categorization rules to organize your transactions and automatically sort, classify, or group new transactions into specific categories. Categorization rules are predefined conditions that automatically categorize transactions based on specific parameters. The following are examples of two categorization rules:

• A categorization rule for salaries where any transaction containing the word 'salary' in its description will automatically be assigned to the 'Salary' category.
• A categorization rule for interest where any transaction equals the word 'interest' in its description will automatically be assigned to the 'Interest' category.

Atlar offers the ability to automatically categorize either transactions or forecasted transactions:

• Transactions: a transaction is an entry on a bank statement that impacts the balance of the account.
• Forecasted transactions: Forecasted transactions relates to the Cash Flow Forecasting feature and are projected cash inflows and outflows. The Forecasted transactions are are either uploaded manually or can be automatically sourced from other systems, for example your ERP system.

Configure a categorization rule

1. Navigate to the Atlar dashboard → Settings → Cash flow Setup
2. Go to the tab Transaction Categorization rules or Forecaster transaction rules
3. Click on Create rule in the top right corner
4. Configure the categorization rule
   1. Give it a name
   2. Select one or more conditions for which the rule should apply
   3. Select the category that the transaction should be categorized to if it meets the conditions

Best practice for conditions

• Use Equal when you want to specify that a value must match exactly. Use Does not equal when you want to exclude certain values or specify that the value should be anything other than a certain one.
• When selecting description the transaction description will be compared to this value by transforming both to lowercase text string.
• Add condition block if you want either condition 1 or condition 2 to apply.
• Add condition if both condition 1 and condition 2 must apply.

Good to know

• New rules only apply to future transactions. Past transactions can be adjusted using categorization tasks.
• Rules can be created using multiple transaction fields (like amount, merchant, or account).
• You can prioritize rules, placing more specific ones at the top and fallback rules at the bottom.

Testing

The Test mode button in the top-right corner allows you to test your rule set against the last 10 000 transactions we have received for your accounts. The point is to be able to test your newly written rules without actually writing any category to any transaction. Once you are happy with the categories and how they apply, you can opt to run the Categorization task to adjust historic transactions.