Setting Up Overdue Process Templates
An overdue process template encapsulates the business rules that govern a given type of overdue process. Open Admin > Credit & Collection > Overdue Process Template > Add to set up overdue process templates.
Note: 
Recommendation. Before using this transaction, we strongly recommend that you review The Big Picture Of Overdue Processes.
Description of Page
Enter a unique Overdue Process Template and Description for the overdue process template.
Collecting On Object defines the type of object managed by this overdue process. This field actually references a foreign key characteristic type that references the managed object. For example, if this overdue process template manages overdue bills, you'd reference a foreign key characteristic that references the bill object.
The Algorithms grid contains algorithms that control important functions. You must define the following for each algorithm:
• Specify the algorithm's System Event (see the following table for a description of all possible events).
• Specify the Algorithm to be executed when the System Event executes. Set the Sequence to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.
The following table describes each System Event (note, all system event's are optional and you can define an unlimited number of algorithms for each event).
System Event
Optional / Required
Description
Calculate Unpaid & Original Amount
Required
This algorithm is executed to calculate the unpaid and original amounts of the objects associated with the overdue process. These amounts are shown on the overdue process page and in the base-package overdue info string.
Cancel Criteria
Required
This algorithm is executed to determine if an overdue process can be cancelled. Refer to How Are Overdue Processes Cancelled for the details.
Cancel Logic
Required
This algorithm is executed to cancel an overdue process. Refer to How Are Overdue Processes Cancelled for the details.
Hold Event Activation Criteria
Optional - only used if overdue processes of this type can be suspended while some condition is true
This algorithm is executed to determine if the activation of overdue and cut events should be suspended. Refer to Holding Events for the details.
Overdue Process Information
Optional - only used if you want to override an overdue process's info string
This algorithm is executed to construct an overdue process's override info string. Refer to Overdue Process Information Is Overridable for the details.
The Event Types control the number and type of overdue events linked to an overdue process when it is first created. The information in the scroll defines these events and the date on which they will be triggered. The following fields are required for each event type:
• Event Sequence. Sequence controls the order in which the overdue event types appear in the scroll.
• Overdue Event Type. Specify the type of overdue event to be created.
• Days After. If Dependent on Other Events is on, events will be triggered this many days after the completion of the dependent events (specified in the grid). Set this value to 0 (zero) if you want the event triggered immediately after the completion of the dependent events. If Dependent on Other Events is off, events will be triggered this many days after the creation of the overdue process. Refer to How and When Events Are Activated for the details.
• If Dependent on Other Events is on, define the events that must be completed or cancelled before the event will be triggered.
◦ Sequence is system-assigned and cannot be specified or changed.
◦ Dependent on Sequence is the sequence of the dependent event.