Weel checks Approval Rules top to bottom and applies only the first one whose conditions are fully met. This puts you in full control of which rule takes priority when more than one could apply. Put specific rules above general ones, since a broad rule higher up can match first and stop a specific rule below it from ever triggering.
How It Works
- Top-to-bottom evaluation: Rules are checked in order, and the system applies only the first one whose conditions are fully met, keeping approval outcomes predictable.
- Rule reordering: Move any rule to the top, up, down, or bottom from its card menu, which tells you "only this rule will apply" or "next rule will be attempted."
- Fallback Rules: Budget Top-ups, Accounts Payable, Reimbursements, and Purchase Orders each get a default Fallback Rule, so nothing goes unapproved.
- Card Expense exception: Card Expense policies can't have a Fallback Rule at all, so unmatched transactions proceed without approval.
- Plan limits: Premium gives up to 3 rules and 2 approval steps each for Budget Top-ups, Accounts Payable, Reimbursements, and Card Expenses; Enterprise removes that limit for the same four types.
- Purchase Orders excluded: Purchase Orders get a default Fallback Rule as above, but the Premium/Enterprise rule-count limit doesn't apply to them.
Good to know
- Card Expense policies don't just default to no Fallback Rule, they block you from adding one entirely.
- If the top rule in a Card Expense policy is broad, transactions that don't match anything else can proceed with no approval at all, so order these rules carefully.
Related Articles