Approving, rejecting and undoing a task

The plan is what you read before; the steps are what happened after.

Opening a task shows what it proposes to do — the plan — alongside every control that ran and what each found.

Plan and steps are kept apart on purpose. The plan is written before anything happens and is what an approver reads. The steps are recorded as it runs. Merging them would make an approval a formality.

Approving applies it. Where your delegation rules require more than one approval — payroll and large payments typically do — the task waits until it has them.

Rejecting records who and why, and the task ends.

Undoing is offered where it is honest. A posted entry is reversed with a reversing entry dated in the current open period, never deleted, so the original and its reversal both survive. Where something genuinely cannot be undone, no undo is offered. See Work that cannot be undone.

The rule that was applied is stored on the task, so a year later you can prove which policy allowed it.