Escheat Processing - DNAappstore - Home page Escheat Processing application package combines two...
17
Escheat Processing PS_ESCHEAT 3434 PS_TDESCHEAT 3435 Application 46d74d43-71aa-431f-b0e6-aa63d1df8818 CONFIDENTIAL-LIMITED: Distribution restricted to: Clients using or considering purchase of the product described in this document Fiserv associates
Transcript of Escheat Processing - DNAappstore - Home page Escheat Processing application package combines two...
Escheat Processing PS_ESCHEAT 3434 PS_TDESCHEAT 3435 Application 46d74d43-71aa-431f-b0e6-aa63d1df8818
CONFIDENTIAL-LIMITED: Distribution restricted to:
Clients using or considering purchase of the product described in this document
Fiserv associates
Escheat Processing Fiserv
PS_ESCHEAT 2 05/10/2018
© 2004-2018 Fiserv, Inc. or its affiliates. All rights reserved. This work is confidential and its use is strictly limited. Use is permitted only in accordance with the terms of the agreement under which it was furnished. Any other use, duplication, or dissemination without the prior written consent of Fiserv, Inc. or its affiliates is strictly prohibited. The information contained herein is subject to change without notice. Except as specified by the agreement under which the materials are furnished, Fiserv, Inc. and its affiliates do not accept any liabilities with respect to the information contained herein and is not responsible for any direct, indirect, special, consequential or exemplary damages resulting from the use of this information. No warranties, either express or implied, are granted or extended by this document. http://www.fiserv.com Fiserv is a registered trademark of Fiserv, Inc. Other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such.
Escheat Processing Fiserv
PS_ESCHEAT 3 05/10/2018
Overview: The Escheat Processing application package combines two applications which update the Date of Last Contact on all Deposit Accounts including Time Deposits. The two applications are the Custom Escheatment Processing Application (PS_ESCHEAT) and the Time Deposit Escheatment Application (PS_TDESCHEAT). Key Benefits: This application helps financial institutions to reduce the number of escheatable accounts, by updating the date of last contact on all of a customer’s or member’s accounts to the most recent contact date on any of that person’s accounts. Custom Escheatment Processing Application Overview: The PS_ESCHEAT application updates the Date of Last Contact on all Deposit Accounts (Accounts with a Major Account Type Code of ‘CK’, ‘SAV’,’RTMT’ or ‘TD’) based on most current Date of Last Contact or Last Statement Date for related accounts. The application also updates the person/organization user field “Entity Date of Last Contact” (8EDC) with the most current Date of Last Contact for any account owned by the person/organization. Processing: To determine the most recent Date of Last Contact, the application checks all accounts owned by the same tax owner to see if the Date of Last Contact has been updated on any accounts in the specified time period (based on the “Start Date” (SD) Parameter described below) where the account’s status code is within one of the codes provided in the application parameter, “Account Statuses To Include” (DRST). If an account or accounts are found with Date of Last Contact in the current time period with a qualifying status code, all related Deposit Accounts owned by the same tax owner that have a status code provided in the application parameter, “Current Acct Status Code” (CASC) are updated to the most current Date of Last Contact found. The “Entity Date of Last Contact” (8EDC) user field is also updated. All changes are written to the DNA activity tables. When the Update for Statement Production parameter is set to ‘Y’, the application selects accounts with a Date Last Contact less than the account’s most recent statement production and update the Date Last Contact to the statement production date. If the account has an active warning flag as specified in the Bad Address Warning Flag Code runtime parameter, account is not updated. If a deposit account’s Date of Last Contact is updated by this application and has a current account status of Inactive (IACT) or Dormant (DORM), the status is updated to Active (ACT). Loan accounts and external accounts can be evaluated by this application (if they are specified in the “Major Account Type Code” (MJCD) parameter) when selecting the most current Date of Last Contact for a tax owner, but they are not updated by this application. If an account’s Date of Last Contact, or an entity’s “Entity Date of Last Contact” User Field, is equal to the most current date of last contact, no updates are performed.
Escheat Processing Fiserv
PS_ESCHEAT 4 05/10/2018
In addition to updating the Date of Last Contact and user fields, the application can also set Warning Flags on all Dormant Accounts, based on runtime parameter options. Each time the application is run, the “Dormant Deposit Accounts” (8DSA) warning flag is set on all Accounts with a Current Account Status of Dormant (DORM) and no active 8DSA warning flag. The application also inactivates the 8DSA warning flag on all Accounts where the Current Account Status is no longer Dormant. The Warning Flag functionality is activated via the “Set Warning Flags” (8SWF) Parameter. The products to evaluate for the warning flag are set via the “Warning Flag Mj Acct Type Code” (8WMJ) Parameter defined below. All modifications (both new flags and inactivating existing flags) to 8DSA warning flags are written to the DNA activity tables.
Specific Minors may be excluded from this application using the standard DNA™ Exclude Application functionality on the product set-up. Excluded minors are excluded both from evaluation and updates.
Parameters:
Parameter Code Description (how used) Required Default Start Date SD Beginning date to check for Date of Last
Contact. If left blank, then default value will be considered as Queue Effective Date.
No Queue Effective Date
RptOnly_YN RPT Y = Produce a report of the projected changes but do not update the DNA database. N = Process the prescribed changes and produce a report. If left blank, then default value will be considered as Y.
No Y
Current Acct Status Code
CASC Comma-separated list of status codes for which to update accounts. If left blank, accounts with any current account status code may have the Date of Last Contact updated. See example 1
No <Blank>
Account Statuses To Include
DRST Comma-separated list of status codes for which to evaluate accounts’ Date of Last Contact. If left blank, the CASC value is used for this parameter. See example 1
No <Blank>
Parallel Process YN
PARA To enable parallel processing, set this parameter to Y
No N
SET Warning Flags
8SWF Y = Set/inactivate ‘8DSA’ warning flags as applicable. N = Do not set/inactive ‘8DSA’ warning flags. If left blank, then default value will be considered as N.
No N
Escheat Processing Fiserv
PS_ESCHEAT 5 05/10/2018
Parameter Code Description (how used) Required Default Warning Flag Mj Acct Type Code
8WMJ Comma-separated list of Major Account Type Codes. Indicates the accounts to be evaluated for the 8DSA warning flag. Used only when 8SWF parameter = Y. If left blank, then default value will be considered as SAV.
No <Blank>
Print Tran Type YN
8SPT Y = Identify and print the Transaction Type Code of the transaction that last updated the Date of Last Contact. N = Do not identify and print the Transaction Type Code. If left blank, then default value will be considered as N. Note: Selecting Y may add significant run time
No N
Major Account Type Code
MJCD Comma-separated list of major account types to evaluate for the most recent date of last contact. When the most recent date of last contact is found, only accounts within these majors are updated with the most recent date of last contact. If left blank, then default value will be considered as SAV, CK, TD. Note: Although EXT is a valid value for this parameter, it should be noted that externally serviced accounts’ Date of Last Contact may not be a true reflection of customer contact.
No SAV, CK, TD
Roles To Include
ROLI Comma-separated list of account role codes. When this parameter is populated, the application includes additional accounts that have the tax owner in the role(s) specified here. These additional accounts are handled by the application the same as if they had the same tax owner. If left blank, only the tax owner will be considered.
No <Blank>
User Field Code
8UFC The single user field code that identifies the person/organization level user field to check for a non-null value. Any non-null value will cause the accounts owned by the tax owner person/organizations to have their date of last contact updated to the effective date of the queue.
No <Blank>
Escheat Processing Fiserv
PS_ESCHEAT 6 05/10/2018
Parameter Code Description (how used) Required Default User Calculation Variables
8UCV Y = Check the ‘8POE’ (Prevents owner Escheatment) account level variable. If Y and current account status = ACT, update the person/organization’s Date of Last Contact to the System Post Date. N = Do not use the ‘8POE’ variable. If left blank, then default value will be considered as N.
No <Blank>
Escheatment Eligibility Age
8EEA Minimum age for escheatment eligibility. If the person being evaluated is younger than the number of years specified in this parameter, the persons “Date of Last Contact” is updated to the system post date. If left blank, then default value will be considered as 0.
No 0
Require Account Ownership
8RAO Yes = A member must be the tax owner of an account to allow updates to the Date of Last Contact, based on the roles they hold on other accounts when the “Roles to Include” parameter is populated. No = A member is not required to be a tax owner of an account to allow updates to the Date of Last Contact, based on the roles they hold on other accounts when the “Roles to Include” parameter is populated. If left blank, then default value will be considered as Y. See example 2
No Y
Update for Statement Production
8USP Y = Update Date Last Contact for Statement Production N = Do not update Date Last Contact for Statement Production If left blank, then default value will be considered as N.
No N
Bad Address Warning Flag Code
8AFW Comma-separated list of warning flags which, when active on an account, will exclude the account’s Date Last Contact from being updated for statement processing Used only when Update for Statement Production = Y
No <Blank>
Escheat Processing Fiserv
PS_ESCHEAT 7 05/10/2018
‘Current Account Status Code’ vs. ‘Account Statuses To Include’ example 1
The purpose of these 2 parameters is to allow the application to use one status when looking at accounts to determine the most recent Date of Last Contact and another status when considering which accounts to update. For example, if the ‘Closeout Withdrawal’ transaction is configured to update an account’s Date of Last Contact, the financial institution may wish to include accounts with a ‘Closed’ status when evaluating the most recent Date of Last Contact for the tax owner. Since it would not be desirable to have the application update Closed accounts to an Active status, however, separate parameters are used to differentiate the two functions. ‘Require Account Ownership’ example 2 Assuming PS_ESCHEAT is run with the “Roles to Include” parameter set to ‘OWN,SIGN’ and the following accounts are evaluated: Dormant Savings Active Loan
Joe Tax Owner N/A
Jane OWN SIGN
Jill N/A Tax Owner
When ‘Require Account Ownership’ = Y, Joe’s account will remain dormant (and the date of last contact will not be updated). When ‘Require Account Ownership’ = N, Joe’s account is made active (and the date of last contact is updated) because Jane has a role on Jill’s active account even if Jane herself is not currently a tax owner on an account with the Financial Institution. Variables: The following variable is located under the “Escheatment Processing” calculation type at the major/minor level.
Calculation Category
Code
Escheatment Processing 8ESC
Calculation Variable Code Description (how used)
Data Type Default
Prevents Owner Escheatment
8POE Y = Set Date of Last Contact to System Post Date for any person/organization having an active account in this minor product.
YN <Blank>
Exclude from Updates
8EFU Y = Accounts in this product will not be updated, but their dates are still included when searching for the latest date if this product is included in the parameters. N = Accounts in this product are updated and their dates are used if this product is included in the parameters. If not set, “N” is used.
YN <Blank>
Calculation Type
Code
Escheatment Processing 8ESC
Escheat Processing Fiserv
PS_ESCHEAT 8 05/10/2018
User Fields:
Code Description DataTypCd PersYN OrgYN AcctYN PropYN
8EDC Entity Date of Last Contact
DATE Y Y N N
Warning Flags:
Warning Flag Code AcctFlagYN PersFlagYN Description (how used) Dormant Deposit Account
8DSA Y N
Scheduling (for batch applications): This application may not be run back in time, and should be run after all batch applications and procedures that may modify Date Last Contact have completed. Also prior to the MS_DIUPD application found in the standard Post Cycle queue.
Escheat Processing Fiserv
PS_ESCHEAT 9 05/10/2018
Report(s): This application produces a report containing two sections. The Date Last Contact Update section is always printed. The Warning Flag section is only printed when the “Set Warning Flags” (8SWF) Parameter is set to Yes.
Field Listing: Field Description
Date Last Contact/Status Account Updates
Name The name of Tax Owner.
Escheat Processing Fiserv
PS_ESCHEAT 10 05/10/2018
Field Description
Most Current Date Last Contact/Stmnt
The most current date of last contact/statement.
Acct Nbr of Most Curr Dt Lst Contact/Stmnt
The account number of account with most current date of last contact/statement.
Role Either TAX for the tax owner, or ROLE indicating the account is linked via one or more of the roles to include.
Tran Type Transaction Type Code of the Transaction causing the Date Last Contact update. This field is blank when the Date Last Contact is manually updated, rather than transaction-triggered, and when the “Print Tran Type YN” (8SPT) Parameter is not set to Yes.
Account Number The account number which will be updated with most current date of last contact.
Major Major Account Type Code of the updated account.
Minor Minor Account Type Code of the updated account.
Orig Stat Original Current Account Status Code of the updated account.
Upd Stat Updated Current Account Status Code (blank if not updated) of the updated account.
Original Date Last Contact
Previous Date of Last Contact of the updated account.
Summary
Total Number of People Affected
Total Number of People Affected by this application.
Total Number Accounts Owned by People Updated
Total Number of Accounts Owned by People Updated by this application.
Total Number of Organizations Affected
Total Number of Organizations Affected by this application.
Total Number Accounts Owned by Organizations Updated
Total Number of Accounts Owned by Organizations Updated by this application.
Warning Flags on Dormant Accounts
Account Number The Dormant account on which Warning Flag will be set.
Major Major Account Type Code of the Dormant account.
Minor Minor Account Type Code of the Dormant account.
Status The current Account Status Code of the dormant account.
Modification Type This will show whether warning flag is added or inactivated.
Warn Flag Effect Date The Effective Date of the warning flag.
Warn Flag Inactive Date The Inactive Date of the warning flag.
Summary
Total Number of Warning Flags Set
Total Number of accounts on which Warning Flag is added.
Total Number of Warning Flags Inactivated
Total Number of Accounts on which Warning Flag is inactivated.
Time Deposit Escheatment Application Overview:
Escheat Processing Fiserv
PS_ESCHEAT 11 05/10/2018
This application updates the Date of Last Contact on all Time Deposit accounts (accounts with a Major Account Type Code of ‘TD’) based on most current Date of Last Contact for all related deposit and loan accounts (regardless of Major). All accounts are linked based on tax owner.
Processing: This application selects all Time Deposit accounts having a Date of Last Contact less than ‘X’ months in the past, where ‘X’ represents the value of the “Number of Months” (MTHS) parameter. For each account selected, the application searches all deposit and loan accounts having the same tax owner. If an account is found having a Date of Last Contact greater than that of the Time Deposit account, the Time Deposit’s Date of Last Contact is updated to the most current one found. If a related account with a greater Date of Last Contact cannot be located, the Time Deposit account is listed in the exceptions section at the end of the report.
The following example assumes an application postdate of 6/1/2004. Based on a “Number of Months” parameter = 36, all Time Deposit accounts with a Date of Last Contact less than or equal to 6/1/2001 are selected for evaluation. If the Time Deposit Account in question has a Date of Last Contact of 1/18/2001, and one of the following three scenarios occurs:
Another account with the same tax owner is found with a Date of Last Contact of 4/7/2003. The Date of Last Contact on the Time Deposit Account is updated to reflect the 4/7/2003 date.
Another account with the same tax owner is found with a Date of Last Contact of 3/28/2001. The Date of Last Contact on the Time Deposit Account is updated to reflect the 3/28/2001 date. However, since this is also outside of the 36-month window the account still appears on the exception section of the report.
No other account is found with a more current Date of Last Contact. No updates are performed, and the account is listed in the exception section of the report.
This application does not update account statuses or the “Entity Date of Last Contact” User Field.
Parameters:
Parameter Code Description (how used) Required Default Number of Months
MTHS The number of months in the past a Time Deposit’s Date of Last Contact must be for this application to evaluate it.
Yes <Blank>
RptOnly_YN RPT Y = Produce a report of the projected changes but do not update the DNA database. N = Update the applicable accounts and produce a report. If left blank, then default value will be considered as Y.
No Y
Escheat Processing Fiserv
PS_ESCHEAT 12 05/10/2018
Parameter Code Description (how used) Required Default Current Acct Status Code
CASC Comma-separated list of Account Status Codes. Only accounts with a Current Account Status Code equal to a code listed in this parameter are evaluated and updated by this application. Status applies to both deposit/loan accounts evaluated and time deposit accounts updated. If left blank, then all accounts will be considered for evaluation/updation.
No <Blank>
Scheduling (for batch applications): This application may not be run back in time, and should be run after all batch applications and procedures that may modify Date Last Contact have completed. Also prior to the MS_DIUPD application found in the standard Post Cycle queue.
Escheat Processing Fiserv
PS_ESCHEAT 13 05/10/2018
Report(s):
Field Listing:
Field Description
Time Deposit Accounts Modified
Name The name of Tax Owner.
Account Number The TD account number which will be updated with most current date of last contact.
Major Major Account Type Code of the updated TD account.
Minor Minor Account Type Code of the updated TD account.
Status Original Current Account Status Code of the updated TD account.
Original Date Last Contact
Original Date of Last Contact of the updated TD account.
Updated Date Last Contact
Updated Date of Last Contact of the updated TD account.
Acct Nbr of Most Curr Dt Lst Contact
The Account Number of Related Account with Most Current Date of Last Contact.
Escheat Processing Fiserv
PS_ESCHEAT 14 05/10/2018
Field Description Most Current Date Last Contact
Date of Last Contact of Related Account.
TD Maturity Date The maturity date of TD account.
Summary
Total Number of Accounts Updated
Total Number of TD accounts updated.
Time Deposit Exception Accounts
Name The name of Tax Owner.
Account Number The TD account number which will be updated with most current date of last contact.
Major Major Account Type Code of the updated TD account.
Minor Minor Account Type Code of the updated TD account.
Status Original Current Account Status Code of the updated TD account.
Original Date Last Contact
Original Date of Last Contact of the updated TD account.
Updated Date Last Contact
Updated Date of Last Contact of the updated TD account.
Acct Nbr of Most Curr Dt Lst Contact
The Account Number of Related Account with Most Current Date of Last Contact.
Most Current Date Last Contact
Date of Last Contact of Related Account.
TD Maturity Date The maturity date of TD account.
Summary
Total Number of Exception Accounts Updated
Total Number of TD accounts where Date of Last Contact updated but the updated Date of Last Contact is less than Application Run Date – “Number of Months” parameter value.
Total Number of Exception Accounts Not Updated
Total Number of TD accounts where Date of Last Contact not updated and the Date of Last Contact is less than Application Run Date – “Number of Months” parameter value.
Additional Requirements:
Requires DNA 4.0 or higher.
There are several steps a financial institution should take prior to using this functionality to ensure a successful implementation. They are: o Review and understand how the current system settings for dormancy, inactivity, fee
processing, letters and abandoned reporting. This will help in deciding whether or not to use the new “Set Warning Flags” option in PS_ESCHEAT. Some beta clients felt that this flag would be more confusing to the Tellers since the current processing/procedures are sufficient.
o Review the transaction codes under System Operations – Transaction Category – Update Last Contact to ensure that the correct values are on each transaction.
o Determine where in the nightly production batch queues to add these new applications. It is important to run it after any application that could update the Date Last Contact field and prior to the MS_DIUPD application found in the standard Post Cycle queue.
o First time execution considerations:
Escheat Processing Fiserv
PS_ESCHEAT 15 05/10/2018
The first time that PS_ESCHEAT is run; there will be some “system catch up” that needs to be done that will require the start date to be back one or more months. This will add run time to the program and it is recommended that it be done on the weekend or another time with an extended processing window.
The first time that PS_TDESCHEAT is run will need to be run back in time for several months. After that, the program frequency may only be quarterly.
Installation: For institutions using UC4 (Automic) for batch processing, please confirm the Adhoc Tax ID Decryption (AHTX) Institution Option is set to “Y,” and the Adhoc Oracle User (AHUS) Application is set-up for the Automic Oracle User. This must be confirmed, even if you got the application from the DNAappstore. Note: If you obtained this application from the DNAappstore, please disregard the installation instructions below. If you did not obtain this application from the DNAappstore, please complete the installation instructions below.
Run the PS_ESCHEAT.WTS, PS_ESCHEAT_DDL.SQL and PS_TDESCHEAT.WTS scripts to
register the application. If not defined already, edit the institution option BATP (PS Batch
Report Directory) with the designation of a custom program directory (ex:
G:\OSI\BANK\BAT_EXE\PS\).
Copy the PS_ESCHEAT.SQT and PS_TDESCHEAT.SQT to the Professional Services (PS)
directory. Once PS_ESCHEAT.WTS, PS_ESCHEAT_DDL.SQL and PS_TDESCHEAT.WTS
script has been successfully run, PS_ESCHEAT.SQT and PS_TDESCHEAT.SQT can be
executed in Batch.
Load pack_PS_COMMON_PACK_wrap.SQL and pack_PS_COMMON_PBOD_wrap.SQL
(Oracle package and package body) with Oracle Object Manager.
Load pack_PS_ESCHEAT_PACK_wrap.SQL and pack_PS_ESCHEAT_PBOD_wrap.SQL
(Oracle package and package body) with Oracle Object Manager.
This application includes custom stored procedures that need to be loaded on the database. As with any stored procedure, please do not load it while the system is in ONLINE mode, or while batch is running. To load the stored procedures please use the Oracle Object Manager in the SAF Resource Kit. To download Resource Kit: On Extranet, go to Core --> SAF --> SAF Resource Kit Releases --> ‘latest release’ --> Download File. This will install the resource kit.
Escheat Processing Fiserv
PS_ESCHEAT 16 05/10/2018
To run the utilities: Start --> All Programs --> Open Solutions Resource Kit will open windows explorer showing various utilities. Open OracleObjectManager and launch OSI.SafRk.OracleObjectManager.exe.
The SAF Resource Kit tools use Oracle client and therefore should preferably be run from App Server -- or at least from a machine that has Oracle client installed on it.
In the System Module of DNA, go to Institution > Applications and enter the supplied
Authorization Key for this application.
To enter the Authorization Key, go to Services >> System >> Institution >> Applications >>
Application Manager.
Configuration Checklist:
Item Test Environment
Production Environment
Parameters
Variables
User Field
Warning Flag
Revisions:
Date App Version #
Change
05/2018 1.0.0.6 Upgraded DNAX to V4
03/2018 1.0.0.5 Updated DNA required version to 4.0 in additional requirement section.
02/2018 1.0.0.5 Code modified to update the Date of Last Contact on accounts that have had a cycled statement produced, except when an institution-defined flag is present on the account in PS_ESCHEAT.
08/2017 1.0.0.5 Corrected handling of time values in the date of last contact fields when using PS_TDESCHEAT.
01/2016 1.0.0.4 Modified proc_RepairData to delete 8EDC user field if value is null for the condition where the user field exists but is null eliminating ORA-00001: unique constraint (OSIBANK.PK_PERSUSERFIELD) violated because it's trying to insert instead of updating
09/2015 1.0.0.3 Implement parallel processing for performance optimization
10/2014 1.0.0.2 Modified for performance optimization
03/2014 1.0.0.1 Documentation Format Updates
08/2013 1.0.0.1 Resultant User field Update/Insert message moved to the correct place for each entity
05/2013 1.0.0.1 Added EXT major to Process-Accounts so that DateLastContact will not be updated as per documentation.
08/2012 1.0.0.1 Re-Packaged and Re-documented for DNAappstore.
07/2012 1.0.0.1 Modified data type of User Field (8EDC) from STR to DATE.
08/2011 1.0.0.0 Case 1483843 corrections made to prevent a blank Date of Last Contact.
05/2011 1.0.0.0 New logo
Escheat Processing Fiserv
PS_ESCHEAT 17 05/10/2018
05/2011 1.0.0.0 Documentation change only. Updated formatting and clarified content. Applied DNAappstore installation verbiage.
01/2011 1.0.0.0 Removed “Update Status Codes” parameter – originally added in error.
01/2011 1.0.0.0 Added new parameter – “Update Status Codes”. Added the ability to exclude specific products from processing using the DNA™ Exclude Application Assignment” screen.
09/2010 1.0.0.0 Added new parameter – “Require Account Ownership”. Fixed bug where the date of last contact on non-deposit accounts would be updated.
08/2010
1.0.0.0 Added new parameters – “Use Calculation Variables”, “Escheatment Eligibility Age”, and “User Field Code”. Added new calculation variable – “Prevents Owner Escheatment”.
