What happens when a delegate approves a request above the cap on their delegation?

At Aster Financial, a relationship manager submits fee waiver request `WAIVER-0931` for $7,500 on a business loan account. The authority matrix says a credit officer can waive up to $5,000 and the head of credit must approve anything above that. The credit officer is on leave, so delegation record `DELEG-0114` passes their authority to a senior analyst, capped at $2,000 and valid for two weeks.

The senior analyst opens the request and approves it. The workflow checks the delegation, finds that $7,500 exceeds the $2,000 cap, and moves the request to the state `rejected_over_limit`. A new task, `TASK-2240`, routes it to the head of credit. The head of credit approves $5,000, declines the remaining $2,500, and the decision record cites the matrix row used.

The consequence: had the waiver been processed on the analyst's approval, the loan account would carry a fee reversal made without authority, and an audit finding would follow. Because the state change and the routing are recorded, the error is caught before money moves.

**What it teaches:** a capable agent checks the delegation cap and not only the role title, handles partial approvals, and leaves a decision record that names the policy row it relied on. For a reseller, a scenario like this has a single expected final state, so customers can score results without subjective review.