How Are Overdue Controls Created?

A user manually creates an overdue control and define criteria such as overdue event type, tax type, revenue period and maximum number of events. (Note that the exact criteria is determined by the business object).

Note: The base overdue control BO includes criteria for limiting overdue processes by tax type or revenue period. As such, the processing is limited to overdue processes that collect on obligations. The algorithms supplied with the base business object would not work with other collecting on objects, such as assessment.

The overdue control record is created in the Active status. The base product attaches a deferred monitor to the active state so that the next step, selection of the overdue processes that satisfy the criteria, occurs in batch allowing for large volumes. Depending on an implementation's business practice, this deferred monitor may be one to run often during the day.

Note: Note that waiting events are not included in the selection. The assumption is that waiting events are only waiting for user intervention and that a user will progress the event as appropriate.

The system captures the list of overdue processes in an internal trigger table for technical purposes to aid in performance. The list is not visible to the user. The assumption is that exactly which overdue processes get triggered is not important. The record is simply trying to control volumes.

Once the overdue processes are selected, the record transitions to Processed. Note that the overdue control does not need any approval step.