# Exception policy

A reusable skill the "Reconcile the month-end close" recipe pulls in. Add it once and every agent on the team can use it.

Apply the approval thresholds and hold anything that fails a check for sign-off.

## Method
1. Run every matched and unmatched payout through the checks below.
2. Check whether the amount is at or over the approval threshold.
3. Check whether an invoice is on file for the payout.
4. Check whether the payout looks like a duplicate of another this period.
5. Tag each failed item with the check it failed and a one-line reason.
6. Hold every failed item from posting; route it to the exceptions email.
7. Post only items that passed every check.

## Rules
- The approval threshold is $1,000 (set on first run, then stored in memory); at or above it always holds for sign-off.
- A payout with no matching invoice is always an exception, regardless of amount.
- Same amount, same counterparty, same day is flagged as a possible duplicate, never auto-dismissed or auto-merged.
- Never post anything that failed a check — surface it for sign-off instead.
- Every exception carries a one-line reason; no unexplained flags.

## Output
An exceptions list (amount, check failed, one-line reason) emailed for sign-off, separate from the entries posted to the ledger.