A bank rule proposes coding for an unrecorded statement movement that meets its conditions. Saving the rule doesn't post the transaction. Review the proposed contact, account and tax treatment, then explicitly accept the supported proposal.
Order specific rules before broader rules that could also match the line. Otherwise, a general payee condition can select an expense that looks plausible but misses the source's purpose. The conditions must describe the actual evidence, not just force a preferred result. Rules create bank transactions; they aren't the route for allocating a receipt to an invoice already in the books. For an existing document or payment, use matching. These tasks use local rule definitions and proposals only. They don't enable unattended reconciliation or connect to a live feed, and every accepted proposal remains visible in the accounting trail.