Advanced System Processes

This lesson will cover:

• Result Code Strategy on Demand
• State Compliance Strategy on Demand
• WORD Letter
• Letter Generation
• Credit Reporting
• Morning Daily Processes
• Afternoon Daily Processes

Result Code Strategy on Demand

The figure below illustrates navigation to the Strategy on Demand:

The Result Code (“RESSOD”) activity type allows users to define an SOD Workflow Manager that can be hinged to a Result Code. When the Result Code is used via the work card, the set of evaluations and updates as defined in the associated RESSOD are executed. If any of the evaluations defined in the RESSOD fail, the agent receives a verbose notification indicating which conditions were not met for the account to which the Result Code was executed.

To create a RESSOD workflow, click on the  icon to add a new project. Enter the six character alphanumeric code and up to a 30-charatcer alphanumeric description. Using the Activity Type drop-down, select the RESSOD option and enter an optional title. Save the new SOD by clicking on the  icon.

Please note that checking either the “Display Everything if Failed” or “Display Failure Items Only” radio buttons in the Alert Display options will suppress any notifications to the agent when all evaluations pass and automatically execute the updates defined in the RESSOD.

To access this, click on the “Start” object at the top of the SOD WFM Canvas to expose these options on the lower left-hand area of the screen.

Like any other SOD, use the Evaluation Object to define the criteria for your project from the work canvas. The evaluation levels available here are as follows:

Account, Client, Demographic, Legal, DemLegal, Bankruptcy

Use the  icon to perform updates just like with any other SOD.

Once all evaluations and updates have been defined to satisfaction, proceed to test the SOD as with any other Activity Types in order to save your changes. The RESSOD requires a Dem Identity Number (“dem_idty_no”) to be tested.

As with any other SOD WFM, the system will open the three tabs of the test harness showing:

• Eval: all evaluations performed for the selected dem_idty_no
• Update: all updates that will be executed for the selected dem_idty_no
• SQL: the SQL statement associated with the evaluations performed for the selected dem_idty_no

The RESSOD is designed to be hinged to a Result Code. To do this, create a Result Code (Tables – Collection Tables Result Code Table) of type “RS” (“Result SOD”).

Selecting the “RS” Result Code Activity Type will disable the “Change” tab and, in its place, display the “Result SOD” tab.

The “Result SOD” allows users to select properly tested RESSODs using the “Result SOD” drop-down selector. Also, this tab displays an expandable tree with the “Branch – Department – Desk” selections to define at what level the RESSOD will be available. Use the checkboxes to the left of each selection to define.

Note that, outside of the following, all other selections have been disabled from the “Coding” tab. 

Company Security, Advance Work Date, History Note, Security, Cost:

Once the appropriate Activity-Result combination has been selected, click on “Save” or “Save & Next”. At this point the evaluations defined in the RESSOD associated with the Result Code selected are executed. The system returns a verbose message to the agent indicating whether the account meets all the conditions defined in the SOD. If so, the message contains a “Continue” button so the agent can proceed with the execution of the Result Code SOD. If any of the evaluations fail, the agent will receive a notification to that effect outlining the conditions that failed.

Once the agent clicks on the “Continue” button, any updates associated with the SOD will be performed.

The account is automatically annotated with “before and after” field updates (i.e.: “dbt_fwd_amt_fwd: 0 to 167.20”):

State Compliance Strategy on Demand

The State Compliance Strategy on Demand (“STCMPL”) is a type of Strategy on Demand that is hinged at the System Parameters level that allows for the definition of a multilevel set of system-wide evaluations that automatically execute upon an account being accessed manually via the workcard function. If a particular nested object in the SOD meets all the conditions (“is TRUE”), this makes that subset of rules invalid (“FAILS”). The STCMPL features a comprehensive set of verbose notifications that are displayed in an alert window presented to the user when an account is either pulled-up, reloaded or a demographic is updated.

Security 

 State Compliance SOD’s are created in the SOD Workflow Manager. To enable user security, under the “Impact Menu Selections” in the Security Group table (Impact – Company Tables – Security Code Table – Menu tab), define access to a Security Group for SOD Workflow Manager.

Check the corresponding checkbox to enable access to the corresponding Security Group for the SOD Workflow Manager, found under IMPACT! – Collection Tables – SOD Workflow Manager.

Creating a State Compliance SOD

To create a new State Compliance SOD, open the SOD Workflow Manager from Impact – Collection Tables – SOD Workflow Manager from the drop-down menu.

The figure below illustrates navigation to the Strategy on Demand:

Once the SOD Workflow Manager has been opened, click on the  button to create a new Workflow and choose Activity Type STCMPL for State Compliance Workflow:

Give the STCMPL SOD an SOD Code, SOD Name and Title. Then click the  button to save the new SOD.

Evaluations

Evaluations are available at the following levels:

• Account Level
  • User Defined Windows (“UDWs”)
  • Views
• Client Level
• Demographic Level
• Legal Level (“Legal Case”)
• Dem Legal Level (“Legal Party”)
• Bankruptcy Level

Using Views with the STCMPL Activity Type

The use of views allows a user ample flexibility to perform evaluations at the State Compliance Table level (Tables – Company Tables – State Compliance Table) where the most prevalent Federal and State requirements can be stored. In addition, specific Client covenants and requirements can be adhered to by defining evaluations using the Client Table and/or Client-Level User Defined Windows (“UDWs”) to store such information.

IMPACT! will display the results of the evaluations defined in the State Compliance SOD as a pop-up alert that is displayed when an account is accessed via the workcard function and then, upon display of the demographics and corresponding POE phone numbers, masks any non-qualifying phone numbers that have failed the evaluations defined.

Phone numbers are evaluated for the following levels:

• Demographic Level: Phone1 and Phone1,
• POE Level: Phone1 and Phone2 for each of the nine (9) available POEs (18 total phone numbers),
• Auxiliary Phone Tabl (“APT”): all telephone numbers in this table.

Hinging a STCMPL SOD to System Parameters

 This option can be located under:

Tables – Company Tables – System Parameters – SODs tab – STCMPL SOD Drop-Down Menu

The “Save” function on the workcard has been enhanced to require the designation of which phone number was just worked by an agent (DEM PH1, DEM PH2, POE 1-9 PH1 or Ph2) when an “OC” (“Outgoing Call”) Activity Code is selected. Call activity is saved not only to the History Table (“HST”) but into a new table “DEMPHA” that allows for evaluation through a view of how many calls to what type of number have been attempted (or resulted in contact) in how many days (from State Compliance Table.)

If the STCMPL SOD has been enabled under System Parameters, upon pulling up an account, the system will perform the evaluations defined in the SOD for demographics A0-D0 and V0-ZZ and invoke a Notifications pop-up window displaying the details of each evaluation that passes and fails. Furthermore, if an evaluation that includes a telephone number is true, each out of compliance phone will be masked entirely with asterisks in order to prevent potential compliance violations.

STCMPL (Workflow Type) Logic

For a STCMPL SOD:

• An evaluation that meets all criteria (“TRUE”) is an evaluation that will FAIL
• An evaluation that does not meet all criteria (“FALSE”), is an evaluation that will PASS

This can be determined by using the test harness built-in the SOD.

Testing the STCMPL SOD 

To perform a test, click on the  button

In the example below, the A0 Phone1 phone meets all criteria and therefore the evaluation = TRUE. The alert message in the workcard will display that evaluation = FAILED and, since this is a phone number, it will be masked in the workcard. Note the first six digits of the failed phone are masked as well on the alert message.

 

Building Custom Alert Messages

By clicking on the Nested object to expose theoption for Custom Alert Messages.

Once these options are exposed, click on the  gear icon to view each of the fields being evaluated for the selected Nested object. Use these elements to build a custom message. The system will display the corresponding data element for each defined field in the Alert Message. See example below.

In the example below, the Evaluation Objects for the selected Nested Object are the following

• DBT_NO: This will be displayed in every Nested Object whether it is part of the evaluation or not.
• DEM_ID:
• DEM_PHONE1
• DEM_PHONE_STATUS

The sample custom message is as follows:

DEM_ID = {DEM.DEM_ID} WITH PHONE {DEM.DEM_PHONE1} HAS A PHONE STATUS OF {DEM.DEM_PHONE_STS}

This will yield the following message in the Alert Window:

“DEM_ID = A0 WITH PHONE [phone] HAS A PHONE STATUS OF 3 -à FAILED”

The text within the curly brackets “{}” is the field name that will display the corresponding data. Any text outside is custom text. The source of à FAILED is from the Custom Message for “Failed” status option below.

Microsoft Word^® Letter

Impact Word® Letters offer the simplicity of creating letters in Microsoft Word® without the hassle of using mail merge. Instead field replacement takes place all within IMPACT!

Introduction

Impact Word® Letters offer the simplicity of creating letters in Microsoft Word® without the hassle of using mail merge. Instead field replacement takes place all within IMPACT!

Notes

• Letter code must exist in IMPACT
• Letter layout/fields done in Microsoft Word
• Letter template uploaded to IMPACT
• Requesting a letter that has been set up using Microsoft Word will create a .pdf of the letter in the QUEUE.

Create or Edit a Letter

The figure below illustrates navigation to the Letter table:

Once the letter table is opened the following window is displayed:

The following buttons are available for the user:

Exit - Navigates back to the main IMPACT window without any changes

Add - Creates a new Letter record.

Edit - Modify an existing record.

Delete - Removes an existing record.

Print - Prints the Letter to the print queue

Once a letter is added or edited the following window is available

Letter Info Tab

The following options are available for the letter setup:

Letter Code - 3 digit unique identifier, it can be entered from 1-3 alphanumeric combinations.  Possible values are, in order of lowest to highest, 0-9 and A-Z

Letter Type - Select what Type of Letter you are creating. (Debtor = Letter to Debtor, Client = Letter to Client and Forward = Letter to Forward Company)

Letter Security - 1 digit unique identifier, it can be alphanumeric.  Possible values are, in order of lowest to highest, 0-9 and A-Z.

Letter Description – Serves identify the letter by providing a more detailed description

Stationary Type – Used to categorize the letters when displayed in the print queue

Form Type - Options are from a Standard letter, Mail merge, Inhouse Form type of letter. Standard letter is the most commonly used form type. Mail merge will send a file to the print queue to be used with your document editor of your choosing. In-house Form is still able to be restricted by a Letter SOD; however, the restrictions set up on the letter table will be ignored and the letter will always be requested and generated.

Page Length - Page length of the letter. This is only an option required for letters to be printed in-house. Outsourced letters are not affected by this setting. Standard and In-house letters can have up to 66 lines in page length.

Page Margin - Margin size of the letter. The page margin is measured in characters and it only applies to the left side margin. The right side margin is controlled by the user entering carriage returns for the legacy letter creation.

Outsource - Options are Yes or No.  If Yes is selected, a third party company will be used for processing the letter.

Outsource ID - A unique ID code that identifies the letter for the outsource letter. This is normally not required and it is an optional field.

Letter Head - Options are Yes or No.  If Yes is selected, letters printed in house will have an additional space on the top of the letter to accommodate paper with an existing letter head printed on it.

Bar Code - Options are Yes or No. This serves as a flag for outsourced letters to let the letter vendor use a barcode on the letter. This field is optional.

NCOA - Options are Yes or No to select if NCOA (national change of address) is to be used. This serves as a flag for outsourced letters to let the letter vendor an NCOA service for the letter. This field is optional.

Prompt Fields - Options are Yes or No.  If Yes is selected, the Prompts tab will need to be filled. The prompts defined will be available for the collector to populate during the letter request process. These fields can be used in the letter by adding the corresponding letter dictionary code.

Prompt Text- Choice of 0-2, this option is for the number of freeform paragraphs that can be used in the letter. Similar to prompt fields, these fields can be used in the letter by adding the corresponding letter dictionary code.

Number of Pages - The number of pages the letter will take. If the letter length is more than one page then this field should reflect the number of pages.

Send Regardless MR – Options are Yes or No. When this field is set to Yes the letter will be requested and sent regardless of the Mail Return flag being set to Yes on the corresponding demographic.

Not a WF Letter - Options are Yes or No. When this field is set to Yes then the letter is not part of a legacy workflow and it is not counted in the number of letters sent, which is evaluated.

Link First Notice - If letter is the first letter in Link Letter Series

States IE - The option to select to Include or Exclude any specific state(s) or to leave out a specific state(s) to be used for a specific letter. Option is meant to be used in conjunction with the states fields.

States - The ability to select any individual state from each drop down selection. (see States IE)

Min Amount - Minimum dollar amount required to send letter based on the TOTAL DUE on the account.

PmtArr/LS Type - If used in a Payment Arrangement or Loan Service Arrangement.

Initial Demand – This field is mandatory. If the letter being created or edited is an initial demand letter, this option should be set to Yes.

Letter SOD – Select the SOD which will be used for evaluation to determine if a letter can be sent or requested.

Save Letter Values – When this option is set to Yes then the values of the letter are recorded in the letter history.

HTML – This option is for the advanced letter feature. This option will allow the letter to be defined using HTML which allows for the letter to be formatted with different font styles, graphics, and tables. HTML knowledge is required to use this feature.

Prompts Tab

There are 28 letter prompts available. Each fields is available in the letter dictionary. The following are available for setup in each prompt field:

Label: This is how the user will be able to identify the fields being prompted

Type: It is possible to restrict the type of data for each field. Options are Alpha, Date, Money.

Length: This allows each fields to be different lengths. Options are 0 – 50

Views Tab

Fields and any type of calculated or formatted fields currently not available in the letter dictionary are available via the letter views.

Field Examples: Proper case fields, date calculations, amount calculations, database fields not in the letter dictionary, concatenated database fields etc.

A “Views” tab has been added to the IMPACT! (Add New Letter) and IMPACT! (Edit Letter) Forms (see following).

Views can be at 5 different levels. Demographic, Bankruptcy, Legal, Post Judgement Legal, or Legal Wizard History.

There is no limit to the number of views available for letters; however, each letter can only have a maximum of one view per level. Each view is also currently limited to 100 fields per view.

Additionally, the use of the 5 types of views is limited by the type of the letter as selected on the Letter Info tab:

DEBTOR – Dem Level only
CLIENT – Dem Level only
FORWARD – Dem Level only
LEGAL – Dem and Lgl level views
POST JUDGMENT LEGAL – Dem, Lgl, and Lglpj level views
BANKRUPTCY – Dem and Bkr level views
EMAIL – Dem level only

Formatting of data such as dates and money must be handled in the views themselves.
Example: Date fields in the view need to be formatted as MM/DD/YY or MM/DD/YYYY and include the slashes "/". Money fields must contain the decimal followed by the 2 digit cents, 14.50.

Please note that the aliasing of database view fields is required for ALL fields.

Dem View Name (Demographics)

In order to create a view that would populate the Dem View Name drop down such view must be named ltr_dem_NAME.

Fields available for the ltr_dem_NAME views are dunning letter field numbers 21001 thru 21100.

The first field in a ltr_dem_NAME view must be the dem_idty_no.   (See sample at end of document).

BKR View Name (Bankruptcy)

In order to create a view that would populate the Bkr View Name drop down such view must be named ltr_bkr_NAME.

Fields available for the ltr_bkr_NAME views are dunning letter field numbers 22001 thru 22100

The first field in a ltr_bkr_NAME view must be bkr_cntr_id.

LGl View Name (Legal)

In order to create a view that would populate the Lgl View Name drop down, such view must be named ltr_lgl_NAME.

Fields available for the ltr_lgl_NAME views are dunning letter field numbers 23001 thru 23100.

The first field in a ltr_lgl_NAME view must be demlgl_cntr_id.

LglPj View Name (Post Judgement)

In order to create a view that would populate the LglPj View Name drop down such view must be named ltr_lglpj_NAME.

Fields available for the ltr_lglpj_NAME views are dunning letter field numbers 24001 thru 24100

The first field in a ltr_lglpj_NAME view must be the pjd_demlgl_cntr_id and the second field must be pjd_seq.

Lwh View Name (Post Judgement)

In order to create a view that would populate the Lwh View Name drop down, such view must be named ltr_lwh_NAME.

First field in the view must be the LWH_ID. It allows for selection of account and case level fields only. (Each LWH_ID can appear in the view only one!!)

The field range will be for 100 fields starting with 25001.

A script to create the ltr_dem_sample view follows:

CREATE VIEW LTR_DEM_SAMPLE (DEM_IDTY_NO, ADDRESS1, ADDRESS2, CITY, STATE, ZIP, DEM_NAME, DEM_NAME_LOWER, FIRST_NAME, LAST_NAME, FULLNAME)

AS select

dem_idty_no,

INITCAP(DEM_ADDR1) AS ADDRESS1,

INITCAP(DEM_ADDR2) AS ADDRESS2,

INITCAP(DEM_CITY) AS CITY,

INITCAP(DEM_STATE) AS STATE,

DEM_ZIP AS ZIP,

DEM_NAME,

INITCAP(DEM_NAME) as DEM_NAME_LOWER,

substr(DEM_NAME,instr(DEM_NAME,',')+1) as First_name,

case

       when DEM_NAME not like '%,%'

       then null --DEM_NAME

       else substr(DEM_NAME,1,instr(DEM_NAME,',')-1)

end as Last_name,

case when dem_name is not null

then INITCAP(substr(DEM_NAME,instr(DEM_NAME,',')+1)) || ' ' ||case

       when DEM_NAME not like '%,%'

       then null--INITCAP(DEM_NAME)

       else INITCAP(substr(DEM_NAME,1,instr(DEM_NAME,',')-1))

end

else INITCAP(substr(DEM_NAME,instr(DEM_NAME,',')+1)) || ' ' ||case

       when DEM_NAME not like '%,%'

       then INITCAP(DEM_NAME)

       else INITCAP(substr(DEM_NAME,1,instr(DEM_NAME,',')-1))

end

end as fullname

from dem;

This diagram relates the actual script and the fields it creates to how those fields appear in the IMPACT! Letter Dictionary:

Enter Letter Tab

This is where all letter parameters are set and defined that determine the type of letter, spacing, and information that will go on it.  Information related to the purpose of the letter, such as agency’s name, address, debtor’s address, client, amount, fees (some of the information will vary depending on the type of letter):

Special Codes (not used in HTML or Word Letters)

The Following are codes that can be used in the body of a letter:

[c][-c]         centers the text within the code IE: [c]Collection Solutions Software[-c]

{12}{-12} puts enough characters to the left to make a total of 12 characters (any number can be used instead of 12) IE: {12}$650.00{-12} will show   _ _ _ _ _ $650.00

[12][-12] puts enough characters to the right to make a total of 12 characters (any number can be used instead of 12) IE: {12}$650.00{-12} will show $650.00_ _ _ _ _

S----  if this code is used anywhere within the letter every name will reverse order from Last Name, First Name to First Name Last Name

^--    This will indent any paragraph from this point forward.

****  This will indent only the paragraph where this is used

Links_Start:        Used to enter link accounts information when a letter is requested from a Master. (Enter headers with letter tags in between tags)

Links_End: See Sample Below:        

Charges_Start: Used to insert Medical Charges onto the Letter (Enter headers with letter tags in between Charges_Start and Charges_End tags)

Charges_End:

Notes:

1. The first line of the letter should be left blank.
   
2. Every space between paragraphs need to have at least a space (use space bar), otherwise the spaces in between paragraphs are ignored.
   
3. To add User Windows Definition tables select the field you want to add IE: ~0701 and add the User Window Definition Code following the field so if you wanted to get the field1 from User Window TU the letter code would be ~0701TU

Save - Select it to save a new Letter Text entry

The following dictionary codes will always show up in the Outsource File regardless of being in the letter.

0002	Current Date MM/DD/YY	0133	Debtor Principal Due
0001	Letter Code	0137	Debtor Interest Due
0004	Debtor Number	0159	Debtor Total Due
0103	Debtor Mail Name 1	0242	Promised Amount
0104	Debtor Mail Name 2	0241	Promised Date
0105	Debtor Mail Address 1	0011	Company Number
0106	Debtor Mail Address 2	0061	Desk Code
0107	Debtor Mail Address 3	0063	Desk Alias
0081	Debtor Client Account Number 1	0064	Desk Title
0021	Client Number	0065	Desk Phone
0022	Client Name 1	0066	Desk Phone Extension
0100	Dem Selected Id	0243	Current PDC Amount
		0244	Current PDC Post Date

Edit an existing letter or add a new letter

Once the Letter Template field above is set to WORD, then the Enter Letter Text tab below will show the button to Create/Edit Word Template. It is recommended that there be no Word documents open before clicking on the button.

Letter Dictionary Fields

When the Create/Edit Word Template button is clicked, a blank Word document will be opened, along with a Dictionaries window that holds the letter dictionary fields and user defined window dictionary fields from IMPACT.

Using the mouse, grab the Code field; drag it onto the Word document. Release and the code will show in the document, surrounded with ${}

User Defined Window Fields

The process of uploading the template saves the template in IMPACT, so subsequent edits to the letter on the Enter Letter Text tab will download the template to your local machine for editing. In order for any edits to the template to be saved in Impact, you must chose YES when prompted

Letter Request

Select demographic and click on Letter on Demand or Send Letter

The template is merged with the data in the dictionary fields, and a .pdf document showing the letter as it will print is opened.

Letter on Demand Document Types

When printing a letter on demand it is possible to print documents attached to the account. The documents that will be printed are the ones defined here based on the document type.

Letter Generation

Letters requested from an account can be printed on demand or generated by the dunning process:

Date and time range is used by the system to look in the work history when the letter was requested from accounts.

Recreate Letters – if set to No, will generate letters that have not been generated as indicated in the history table processed field being null. In the work history when the letter was requested, it will not show the ‘(S)’ code after the letter.

If it is set to YES, the system will recreate already generated letters and in the work history it is indicated by the ‘(S)’ code after the letter.

User can filter by letter code or leave blank to generate all letter codes.

Outsource Format File Option – when set to 1-Original will create an outsource letter file where the letter tags start with 4 characters and some are 5 characters. When set to 2-5, DigitCodes will create an outsource letter file that left pad 4 character letter tags with 0 so all letter tags are 5 characters.

When dunning process is completed, the non-outsourced letters will be in the Print Queue and the outsource letter file can be exported from System File Access:

In addition, a master report of all letters generated will be in the Print Queue with LTR QueueID:

Credit Reporting

CSS Impact reports to the credit bureaus using the Metro 2 Export Format

1. Verify that you have filled out your subscriber codes on your company/companies set up. Each company that you report must have a subscriber code filled in on the Credit Bureau ID Tab.

The figure below illustrates navigation to the Company table:

2. Review Credit Reporting set-up on all client codes – found on the Coding tab, verify all clients are set up as you require.

NOTE: Loan Servicing clients must be set up as CBR TYPE = Retail, In-house First Party and must have payment arrangement type 2 entries to report as loan servicing accounts. Loan type is based upon creditor class.

 The figure below illustrates navigation to the Client table:

• CBR Type must be set to Retail
• The Referral Amount of each account Must Meet or Exceed the Minimum Amount
• The Referral Date of each account must not be greater than Report Thru Date minus the Delay Days (EXAMPLE: Report Thru Date = 1/30/2013, Delay Days = 10, so 1/30/2013 – 10 = 1/20/2013. Account referred 1/25/2013 would not qualify because of the delay days, (Referral Date 1/25/2013 is > 1/20/2013 so account does not qualify. The Credit Report Type on the Debtor (dbt_cbr_type) must be equal to one of the following:

                  Y-Report Debtor to CBR

                  D-Dispute, CCC Required

                  O-Account Transferred

                  L-Purchased by Another Lender

• Missed Pmt Delay Days If the account has never been reported and the Missed Pmt Delay is filled in: The system takes the Last Payment Date if filled in otherwise it takes the Referral Date and takes the difference of the Report Thru Date. If the calculated days are >= greater than or equal to the Missed Pmt Delay Days, the account gets put into the bureau report from then on.

3. Review set up of SYSTEM PARAMETERS – STS Classes TAB – RPT CBR column for appropriate entries for the corresponding class.

The figure below illustrates navigation to the System Parameters:

To create an exception report

The figure below illustrates navigation to the System Parameters:

1. Under CREDIT REPORTING – CREDIT REPORTING TO BUREAU CYCLE – choose from the drop downs as follows:

• COMPANY: ALL or only the company you want to report in this file
• On the client table, client codes where CBR TYPE that equals Y (report to bureaus) are the only client that will be part of ALL. You may also choose the company you want provided that the CBR TYPE on the client table is equal to Y.
  • A user fills out the CBR Reporting to Bureau Cycle screen, entering a REPORT THRU date. This date is used to calculate what is referred to below as the up-to-date. The up-to-date is equal to the Date thru from the screen less the delay days as listed on the client code. So, if DATE THRU on screen is 12-31-12, and delay days for client is 30, then up-to-date = 12-1-12. NOTE: The DATE THRU is only used to determine what accounts to report, it has nothing to do with the status or balance of the account. CURRENT DATE would refer to the actual date the file is being requested.
  • Then the debtors are pulled for the client codes that are on the list. The class of the status the account is in is compared to the System Parameters - Stats Class tab to determine if this class is reported to the CBR.
  • If No, the account is skipped. If Yes, then the account is reviewed to meet the following requirements:

• Referral amount > minimum amount
• Referral date <= up-to-date (defined above)
• cbr_type = Y (Report Debtor to CBR), C (Cancel), D (Disputed, CCC Required) , O (Account Transferred), L (Purchased by another Lender)
  • The balance reported is the balance at the time the file is run (CURRENT DATE), the DATE THRU is not referenced.  
  • ***EXCEPTION - LOAN SERVICING ACCOUNTS - payment arrangement type 2 exists, are reported as of the DATE THRU balance and date of last payment. This requires extra processing time by reading thru the transaction history on all accounts reporting to the bureau.
  • The account will be reported as of the status it has at the time the file is run (CURRENT DATE). The DATE THRU is not referenced.

2. REPORT THRU: Enter the date you want to report through.

3. Choose RUN TYPE:

• SCAN FOR EXCEPTIONS.
• This will create a report in the queue – queue id:
  • CBRE, description: Credit Bureau Reporting Exceptions.
  • Review the report for accounts that will not report for the reason stated in the Exception column.

Include SC & 7 Year Statute Exceptions on Exception Report: Option to include all accounts that will not report because the Status Class in the System Parameters is set not to report and all accounts that will not report because it is past 7 years from last charge date or payment prior referral date or first delinquency date

5. LOAN SERVICING HISTORY PROFILE TYPE: This setting is not applicable to RUN TYPE:

• SCAN FOR EXCEPTIONS - see below for settings to use when actually creating a file.

6. Include User Defined Dems V0-ZZ: Option to include user defined dems V0 – ZZ to the credit report in addition to the default A0 to D0 demographics

7. Review the Exception Report created in the queue

Common reasons include:

• No demographics chosen for this account – there is no demographic coded on this account to be reported to the credit bureau
• No 1stDelq or LastChg or PmtPriRf Date – credit bureau requires one of these three dates in order to accept an account.
• Missing Comma in Retail Name – the client is set up to do retail reporting and the name on the account is not in the format of: LastName,FIrstName
• Missing Address or City or State or Zip – the selected demographic does not have all of the required address elements.
• Account Won't Report Because of Status Class – the selected account is in a status class (based upon status code) that is set up under System Parameters - STSCLS tab to not report.
• Reporting Date Later than Referral Date – there is an issue with either the 1stDelq or LastChg or PmtPriRf Date – one of them is later than the referral date and needs to be corrected/removed before the account can report. This most often occurs when there are errors in importing. The date may appear normal when you look at the account, but is actually some like in the year 3907. To see the full year as saved in your database, create an adhoc report and format these dates to show all 4 digits of the year. Display all three dates and filter by the debtor number.

8. Once the exception report has been cleaned up to your satisfaction, proceed.

To create your FIRST file

The figure below illustrates navigation to the Credit Reporting to Bureau Cycle:

9. For your first time file, run the drop down: ALL ACCOUNTS – CREATE FILES FOR BUREAUS.

10. Choose LOAN SERVICING HISTORY PROFILE TYPE: This setting should be changed only by those companies that have the loan servicing plug-in and are reporting first-party loan servicing accounts. Once a month, the Loan Servicing History Profile Type should be set to Advance Payment History Profile (Final Monthly Run). This setting updates the 24 month loan servicing history profile that is reported to the bureau. If the file must be recreated do not choose that setting again.   A note is entered on accounts when the payment history is advanced for CBR reporting so that you can reference accounts and know when this setting has been used for the month.

11. The file will be located in System File Access. A detailed report of what was reported will be in the queue – queue id: CBRR, description: Accounts reported to Bureau(s).

• Please review this report for accuracy. This report does not list each demographic reported for each account, only the debtor number of accounts that are reported. It also listed the A0 name, even though you may not be reporting it, you may be reporting the B0 or C0 demographic. You can verify this by opening and looking at the file, if you would like.

To create additional files

The figure below illustrates navigation to the Credit Reporting to Bureau Cycle:

1. For all files after initial file, run the drop down: UPDATED & NEW ACCOUNTS – CREATE FILES FOR BUREAUS

2. Choose LOAN SERVICING HISTORY PROFILE TYPE: This setting should be changed only by those companies that have the loan servicing plug in and are reporting first-party loan servicing accounts. Once a month, the Loan Servicing History Profile Type should be set to Advance Payment History Profile (Final Monthly Run).

• This setting updates the 24 month loan servicing history profile that is reported to the bureau. If the file must be recreated do not choose that setting again. A note is entered on accounts when the payment history is advanced for CBR reporting so that you can reference accounts and know when this setting has been used for the month.  

3. The file will be located in System File Access. A detailed report of what was reported will be in the queue – queue id: CBRR, description: Accounts reported to Bureau(s). Please review this report for accuracy.

• This report does not list each demographic reported for each account, only the debtor number of accounts that are reported. It also listed the A0 name, even though you may not be reporting it, you may be reporting the B0 or C0 demographic. You can verify this by opening and looking at the file, if you would like.

4. At any time, you can run ALL ACCOUNTS – CREATE FILES FOR BUREAUS – to send your complete file again. It WILL NOT result in duplicate entries.

• The Credit Bureaus will compare the entry in the new file with the entry on the corresponding credit report and if they are identical, not list it again. If not identical, they will only pick up the changes.

Morning Daily Processes

The morning daily process prepares accounts for the day.

The figure below illustrates navigation to the Morning Process:

Once the user hits the Ok button, the system will process the following:

1. Updating Work Dates: When accounts are assigned to a desk, it updates the desk with the first work date so users can pull these accounts in their Work List.
2. Recurring Phnpays Process: Generates phone pays from payment arrangements if System Parameters → Main tab → MORNING DAILY RECURRING PHNPAY field is set to YES.  If it is set to NO, this process is included in the Afternoon Daily Processing.
3. Scoring Accounts: Accounts get their internal score (dbt_is_score) based on the Scoring Rule attached to the Client Table → Coding tab → SCORING RULE field.
4. Updating Interest: Interest on the accounts get updated if the System Parameters → Main tab → MORNING DAILY ACCRUE INTEREST field is set to Yes.  If set to No, this will not show in the Morning Daily Process queue report.
5. Updating Last Activity: Last Activity date gets updated when there is a change made in the State Compliance Table → Compliance Mgt tab; stf_upd fields gets updated to Y.  This is processed by State alphabetically and then by debtor number.       Last Activity Date is used by the system to calculate Statute of Limitation date on an account
6. Auto Delete Queue    - Print Queue Reports are automatically deleted based on the number of days in the System Parameters → Main tab → QUE AUTO DELETE DAYS field.

When completed, a report on the Print Queue is generated:

Afternoon Daily Processes

The figure below illustrates navigation to the Afternoon Process:

Once the user hit the Ok button, the system will process the following:

1. Processing Client PC Threshold: It looks at the Client Table → Special tab → PRECOLLECT THRESHOLD COUNT and CURRENT PRECOLLECTCOUNT fields and lists the numbers on those fields in the separate queue report named ACCOUNTS PROCESSED IN DAILY PROCESSING.  

2. Processing Letter Series: Requests the letter from accounts that is the next on the letter series and the next letter date is the current date and letter series is not on hold on the account.  It also applies Letter Series Completion result code when Impact has requested the last letter on the letter series and removes letter series code from the account.  The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report shows the account number, activity type and completion result code applied.

3. Processing Rollout: Precollect and House accounts are rolled out if DBT_PC_HSE_ROLL_DATE is the current date.

4. Processing PDC Letters: Company Table → Company Info tab → PDC LTR or PDC CC LTR or PDC MASTER LTR or PDC MASTER CC LTR letter code is requested from accounts if the post dated phone pay post date is 4 to 8 days from the current date.

5. Processing Promises: Company Table → Promise Logic tab is applied to all promises where the promise break date is the current date and applies Broken Promise Result code if promise breaks.  The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report show the account number, activity type and result code applied:

6. Processing Work Flows: Legacy workflows are processed. The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report shows the account number, activity type and result code applied:

7. Processing Pmt Arrangements: Payment Arrangements get processed. 

• Completion result codes are applied to accounts when the Total Collected amount is equals to or greater than Total Payments amount.
• Broken result codes OR Past Due codes are applied when the current date is today plus the number of grace days and the Next Payment Amount has not been made.  Reminder letter is requested from accounts.
• Late fees are incurred. Next work dates are changed on accounts to the Next Payment Date plus number of grace days. The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report shows the account number, activity type and result code applied 

8. Processing Legal Accounts: Legal Accounts get processed.

• System Parameters → Legal tab → Legal Service Required Result Code is executed when demographic date served is null, demographic service type is H (Home) or W (Work) and it is 45 days from file date OR when demographic date server is null, demographic service type is not H or W and it is 30 days from file date.
• System Parameters → Legal tab → Legal Default Result Code is executed when serve date is not null, answer date is less than the current date and no answer received date yet.
• System Parameters → Legal tab → Legal Hearing Date Reminder Result Code is executed 5 days prior to hearing date
• The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report shows the account number, activity type and result code applied     

9. Processing Pending Recalls: If account forward status is P for Pending Recalls and the Recall Date is less than or equals to the current date, then the Forward Status is changed to R for Recalled and Recall Date changes to the current date .

• The ACCOUNTS PROCESSED IN DAILY PROCESSING queue report shows the account number and history type applied

10. Processing Phn Prog: Phone Progression get processed.