Write-off Event Lifecycle

The following diagram shows the possible lifecycle of a write-off event:

Write-off events are initially created in the pending state. When the application determines that the pending event is with a trigger date on or before the current date, it runs the event's activity and completes the event. The application automatically cancel the pending event when the linked service agreements are all closed.

Write-off events are initially created in the pending state.

When the system sees a pending event with a trigger date on or before the current date, the system executes the event's activity and completes the event.

Fastpath:

For more information about a write-off event's trigger date, see Write-off Event Trigger Date.

A pending event will be cancelled automatically by the system when the service agreements linked to the process are all closed (i.e., they no longer have debt - either because it was paid or transferred to a write-off service agreement). A pending event may be cancelled by an operator at their discretion.