# Classification rules Rules recognize repeated transaction patterns and propose a Use, Category and relevant business information. ## Create a rule Open the rule editor from a transaction. Review its prefilled values, give the rule a name, and choose a scope: this account, this statement only, or all accounts. Add conditions as needed. All conditions must match. Text conditions support contains, equals, starts with and ends with. Amount conditions support equals, greater than and less than. Choose Use and Category independently. For business information, use the statement default or a specific business. Personal + business requires a valid business percentage. **Preview matches** shows the match count and up to 100 example rows. Review before saving. New rules start in **Suggest** mode. **Apply this rule now to matching unclassified items** explicitly applies the new rule to eligible existing rows. It preserves completed classifications and manually assigned fields, and saves only valid, complete matches. This is separate from changing the rule to Commit mode. ## Suggest and Commit Suggest supplies choices for your review. Commit permits eligible complete classifications to be saved automatically during import or statement loading. A statement requiring manual review prevents automatic commitment. Previously saved rows are not automatically overwritten when loaded. If several rules match, priority and rule order determine the first available suggestion for each field. Review overlapping rules carefully. ## Maintain rules The Rules list supports search, inactive entries, activation and mode changes, and history inspection. Conditions and targets are read-only after creation: deactivate the old rule and create a replacement when these need changing. Deleting a custom category resets affected rule category targets to Unspecified. Those rules can no longer produce a complete classification with that target until replaced appropriately. Return to [Classify statements](statement-classification.md).