dispose_exception
End an exception in a financial journal by applying book, carry_forward, chase, or write_off, moving money and clearing the worklist while enforcing policy limits.
Instructions
End an exception in a journal entry: book, carry_forward, chase, write_off.
This moves money, and it is meant to. The item leaves the worklist, double entry is written, and the record carries your name and the fact that an agent put it there.
What it will still refuse, all of it from the loop's signed policy and
none of it from you: a write-off above the per-item ceiling, one that would
exhaust the close's write-off budget, a book on a code the taxonomy has
not promoted, and any second disposition of an item already ended. There is
no ceiling parameter and no chart parameter, so there is nothing to widen.
due_on is YYYY-MM-DD and applies to chase only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"run_id": "<run_id>",
"exception_id": "<exception_id>",
"disposition": "<disposition>",
"rationale": "<rationale>"
},
"name": "dispose_exception"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No | ||
| due_on | No | ||
| run_id | Yes | ||
| rationale | Yes | ||
| disposition | Yes | ||
| exception_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||