Exception routing

Where each kind of ambiguity goes, how urgent it is, and how long it may sit there.

Settings → Exception Routing.

When automation cannot decide, something has to happen to the item other than nothing. This is where you say what.

For each kind of exception — an unmatched payment, a transaction below confidence, a vendor bank change, a failed rule — you set who it goes to, how urgent it is, and how long it may sit before it escalates.

The ageing limit is the part that matters. A review queue with no time limit is where work goes to be forgotten, and the month-end discovery that forty items have been waiting since the 3rd is the normal outcome of not setting one.

Items past their limit are escalated and surfaced on the close-readiness view, so an exception cannot quietly become a reason the books are late.

Related: Anomaly detection decides what becomes an exception; this decides where it then goes.