An assistant that can issue refunds

What the day looks like

             this one   day so far
refund #1    $40           $0      -> approved
refund #2    $120          $40     -> approved
   ...
refund #38   $150          $4,910  -> approved
refund #39   $60           $5,060  -> REVIEW
                                      queue: finance
                                      no answer in 24h -> reject

Every one of those is a good decision. A refund is small, it makes a customer happy, and a human approving each one adds cost and delay to something that should take seconds.

The thirty-ninth refund is not wrong either — the day's total is. So the rule cannot judge one refund at a time: it has to keep a running total.

The timeout matters as much as the threshold

A queue nobody watches is worse than no queue: it silently holds money back, or silently lets it through. So the rule declares what happens if nobody decides the case within a day: here, the refund is rejected.

The same shape, larger

Replace the refund with a transfer, a claim payment or a credit line and the mechanism does not change: a running total for one account, a threshold, and an answer declared in advance for when nobody responds. Business rules covers the running total, and human review covers the queue.