Understanding Exception and Collection Processing Options

PeopleSoft Receivables enables you to monitor a customer's account and take action when a condition occurs, such as reaching a credit limit or exceeding a user-defined balance due. It also enables you to create deductions, put an item in dispute or collection, calculate a risk score and track and manage these items.

If a customer violates a condition, the Condition Monitor Application Engine process (AR_CNDMON) determines the appropriate action plan. The Condition Monitor process creates the actions and assigns them to an owner on a user-defined date. If field values on items, item activity, item distribution lines, and the customer match a user-defined criteria, the Condition Monitor also creates actions and assigns them to an action owner on a user-defined date.

You specify the type of owner, such as collector, credit analyst, receivables (AR) specialist, or sales person, for each type of condition. You also define the rules that the Condition Monitor process uses to determine whether a customer has violated a condition or whether an item meets specified criteria, and to determine if it should create an action plan for the customer or item.

Note: You must complete the tasks discussed in this topic to implement exception and collection processing.