As you add more rules, two rules may sometimes fit the same payment. For example, a rule for one customer and a catch-all rule for bank fees. Priority decides which rule gets the first go. Rules with a lower number go first.
The golden rule: put specific rules above general ones. A rule for one customer, or with narrow conditions, should have a lower number than a rule that covers everyone.
How Kolleno picks the rule
Kolleno tries your active rules in order, starting with priority 1.
If a rule's conditions fit the payment, it looks for invoices.
The first rule that finds invoices handles the payment. If it finds nothing, Kolleno moves on to the next rule.
If that rule finds invoices but the amounts don't add up, it suggests them to you. Rules further down the list don't get a turn on that payment.
If no rule finds anything, you'll see Kolleno's usual suggested matches. See How suggested matches are determined.
Change the order
Drag and drop rules in the list. Kolleno renumbers them 1, 2, 3… to match.
You can also type a number in the Priority field when editing a rule. Each active rule needs its own number.
The "higher-priority rule" warning
When you save a rule, you might see a warning like this:
Rule 'All customers — bank fees' (priority 1) also applies to these customers and may take precedence with a looser adjustment band.
In plain terms: another rule, higher up the list, covers some of the same customers and accepts bigger differences. Because it goes first, it might handle payments you meant for your new rule.
To fix it, either narrow the other rule so it doesn't cover these customers, or drag your new rule above it.
Good to know
Kolleno has a built-in safety net. Even if a general rule finds a match, Kolleno asks you to check it if a rule set up for specific customers, lower down the list, would match the payment to a different customer. This stops a catch-all rule from quietly taking a payment meant for someone else.