The notion of a compensation is widely used in advanced transaction models as means of recovery from a failure. Similar concepts are adopted for providing ``transaction-like'' behaviour for long business processes supported by workflows technology. Generally, designing a compensating task in the context of a workflow process is a non-trivial job. In fact, not every task is compensatable since the forcibility of ``reverse'' operations of the task is not always guaranteed by the application semantics. In addition, the isolation requirement on data resources may make a task difficult to compensate. In this paper, we introduce a new concept called confirmation. By using confirmation, we can modify some originally non-compensatable tasks so that they become compensatable. Upon success of a workflow instance, the confirmation tasks of all executed tasks, if defined, are required for execution. An object-oriented framework which incorporates the confirmation concept is presented in this paper as well as its implementation issues.