Can a generated release include exceptions, holds and returned files, not just clean bookings?

**Can a release include files that should not be booked?** Yes. A buyer can ask for a mix of clean bookings, held files and returned files, each with a recorded reason and the correct next action.

**What kinds of exceptions could be generated?** Typical families include open conditions precedent, an expired approval, a missing guarantor, a mismatch between approved and requested limit, a pricing exception without a named approver, and a settlement account that fails validation.

**How is the right answer defined?** Each exception file can carry an expected disposition (`book`, `hold` or `return`), the blocking item, and the role the file should go to. Graders compare the agent's action and stated reason against these.

**Can exceptions be combined?** A task can layer two issues, such as an open condition and a settlement mismatch, to test whether the agent finds both or stops at the first.

**What about ambiguous cases?** Some tasks can be designed so that reasonable reviewers might differ. Mark these in the pack so they are scored with partial credit or excluded from pass/fail.

**What should a buyer check?** That the exception patterns are plausible for the product and that the labelled dispositions are consistent with the generated policies. Scope the exact mix in a pilot.