Owdyn's auto-categorisation currently supports only one rule type..."contains", which limits how precisely users can match transactions to the right category. Adding more rule types would make categorisation both more accurate and more flexible.

Suggested Additional Rule Types:

Starts with / ends with - useful when a merchant string is prefixed or suffixed with variable reference numbers, so matching the fixed portion at the start or end avoids false positives from "contains" matching an unrelated substring elsewhere in the description.

Exact match - for cases where the entire description string is stable and predictable, giving the tightest possible match with zero ambiguity.

Does not contain - to exclude specific transactions from a rule that would otherwise be too broad (e.g. matching "Costco" for groceries, but excluding "Costco gas").

Regex - regular expressions for power users.

Amount equals / greater than / less than / between - letting users categorise based on transaction value, useful for splitting recurring bills of a known amount from other spend at the same merchant, or catching unusually large/small transactions for review.

Specific account - restricting a rule to only apply to transactions from a particular linked account, so the same merchant string can be categorised differently depending on which account it hits.

Credit vs debit - letting a rule apply only to incoming or outgoing transactions.

The rule engine should support multiple conditions per rule (AND/OR logic) and rule prioritisation. Rather than one condition per rule, allowing users to combine conditions - e.g. "description contains 'Netflix' AND amount equals $22.99", would let a single rule handle more nuanced cases without needing several overlapping rules that could conflict with each other. Rule prioritisation ensures the correct rule wins when multiple conditions are met.