|
BUSINESS
PRACTICE |
Revised: 08/07/02
1100-3 ADDING A NON-ACCRUING OBLIGATION
This procedure describes how to activate a non-accruing obligation (i.e. a judgment) on the system. All legal information about the obligation and person/program history must be built prior to activating an obligation. All payment history must be entered prior to activating a non-accruing obligation (i.e. a judgment), if applicable. Once a non-accruing obligation is activated, payments can be credited to the obligation.
NOTE: All payment history information must be migrated or entered on REIP (See Business Practice 1100-15 Recording Individual Payment History and Business Practice 1100-15b Migrating Payment History) if applicable.
Next to the appropriate screen:
1. See Business Practice 900-3 Adding/Recording a Pre-Existing Legal Action (Not KS CSE), Business Practice 900-4 Adding/Generating a Subsequent Legal Action Under an Existing Court Case Number (KS CSE), or Business Practice 900-5 Adding/Recording a Private or Out of State Financial Journal Entry for setting up the following legal screens--
LACT (legal action)
LROL (legal roles)
LDET (legal detail)
LOPS (legal obligation person)
Proceed to LDET screen
2. On LDET:
--Enter an
AS@ in the Sel field opposite the legal detail selected to add to the system-The system will automatically select the appropriate screen based on Obligation Type in the legal detail. (Non-accruing obligations:718B, SAJ, MJ, IJ, CRCH, AJ.)
--Press PF18 (Oblig) to go to the Maintain Non-Accruing Obligation (ONAC) Screen-
3. On ONAC:
--Enter--
-Covered Period for the obligation.
-Note/Contingency Reason-Provide explanation for the covered time period, or -for the amount of the obligation or any other unusual information regarding the obligation. (Example: farm crops harvested once per year.)
--Interstate obligations will require input of the interstate indicator
AI@, referring state or country code, and interstate case number from the referral----Foreign country obligations will require input of the interstate indicator
AI@ and the country code----For all obligation types (except 718b), the supported person(s) can be selected and the program code
AAF, FC, NF, NC, NA, AFI, FCI or NAI@ entered when the obligation is first added. The appropriate program code will display on DEBT.NOTE: Upon an Add, a comparison will be made with PEPR to check for a blank time frame for the covered period start date, if there is no active program for the covered period start date, the obligation can not be added. The user will need to change the covered period start date or add the correct program to PEPR.
Once an entry is made in the program type field and the obligation is added, the program type can be changed by using the PF6 (Update) function. A change in program will become a trigger for retro-processing.
If a mistake is made, the entire obligation can be deleted on the same day it is entered but not on any later day--
--Press PF5 to Add--
--Press PF21 to REIP if applicable--
--Press PF17 to release payments on REIP for distribution if applicable--
NOTE: When adding a new non-accruing obligation to a court order than has had previous AF, FC, NC or NF payments applied, the user should receive a message that states:
>State retained collections exist, do you want to protect prior payments?=If the user enters
AY@, all appropriate collections will be automatically protected from retro processing. The protected time frame can be viewed on COLP.If the user enters
AN@, collections will not be protected from retro processing.See Business Practice 1100-34 Adding a Manual Protected Time Frame to create a manual collection protection time frame, Business Practice 1100-35 to Deactivate a Protected Time Frame.