Data processing technique for scoring bank customer relationships and awarding incentive rewards6424951Abstract A Relationship scoring and Incentive Reward awarding process determines a Relationship score for the Relationships between a Bank and each of its customers. Such Relationships may include deposit accounts, loan accounts, and customer referrals. Customer data describing the Relationship between the Bank and its customers is furnished by the customers and extracted from a Bank customer information file. Incentive Rewards, such as reduced loan rates or increased deposit account interest, are awarded to customers based on the Relationship scores. Management reports summarize the Relationships between the Bank and its customers and provide marketing information. Claims The invention claimed is: Description This invention pertains to data processing techniques useful in Banks. More particularly this invention pertains to a data processing technique for determining the number of different Relationships that a customer has with the Bank, scoring the Relationships and awarding Incentive Rewards based on the Relationship score. As used herein the term "Bank" is intended to mean all types of financial service institutions, including banks, savings and loan associations, credit unions and the like, which offer a variety of financial and investment services to customers; the term "Relationship" is intended to mean each type of financial transaction, account or interaction which the customer may establish with the Bank, such as a checking account, savings account, consumer loan, credit card, mortgage, investment, certificate of deposit, insurance policy, new customer referral or the like; and the term "Incentive Reward" is intended to mean some type of consideration or recognition established and given by the Bank to the customer in recognition of the number and characteristics of the customer's Relationships, such as an increased interest rate on deposit accounts, a reduced interest rates on loan accounts, reduced Banking service fees or the like.
TABLE A
Field Field Dec. Rela- Add
Field Name Type Length Places Point tion Joint Fixed
Customer Name C 25 0 0 N N Y
Deposit Accts N 3 0 1 Y N N
Loans N 3 0 2 Y Y N
Safe Deposit L 1 0 5 Y N N
Years D 8 0 1 N N N
SSN N 9 0 0 N N Y
Table B illustrates an example of a customer database file of the RBF 108, defined in accordance with the master dictionary file of the SPF 104 illustrated in Table A.
TABLE B
Social
Deposit Safe Security
Customer Name Accts Loans Deposit Years Number
Anderson 2 1 Y 10/11/85 123456789
Wilson 0 1 N 11/01/75 234567891
Jones 4 0 Y 01/01/62 345678912
Tables A and B are exemplary of the information which may be contained in each file, so these Tables are not intended to present a comprehensive compilation of all information that may be available in the files. In Tables A and B, and subsequent tables, the term "row" refers to each horizontal grouping of informational elements illustrated in each Table, and the term "column" refers to each vertical grouping of informational elements illustrated in the Table. Each row of the master dictionary file (Table A) defines one of the fields of the customer database file of the RBF 108. Each column of the master dictionary file (Table A) defines an attribute of the field defined by the row. Each row of the customer database file (Table B) is a customer record. Each column of the customer database file (Table B) is a separate field. Each customer record in the customer database file (Table B) is formed by the information pertinent to that customer obtained from all of the fields of information in the customer database file as defined by the master dictionary file (Table A). The definition for each customer record is therefore obtained from the master dictionary file. The row of the master dictionary file (Table A) entitled "Field Name" identifies the type of information presented in a field of the customer data base file (Table B). The examples shown in this column are Customer Name, Deposit Accounts such as savings accounts, Loans, Safe Deposit for safe deposit boxes rented from the Bank by the customer, Years for the date on which the customer first established a Relationship with the Bank used to determine the years of longevity of the Relationship between the customer and the Bank, and SSN for the customer's social security number. The "Field Type" column identifies the character of the of data contained in the field: "C" meaning comment or text information; "N" meaning a numerical value; "L" meaning a logical value such as "yes" or "no"; and "D" meaning a date. The "Field Length" column defines the size, or number of characters, of the field. The "Dec. Places" column defines the number of decimal places allowed for numerical fields, with "0" denoting integer values. The number of points which the Bank management has determined shall be credited for each type of Relationship is defined by the numerical value in the column labeled "Point." The "Relation" column specifies whether the Relationship is one which will be reported as a relationship in management reports, with "Y" denoting "yes" and "N" denoting "no." The "Add Joint" column denotes the method for calculating points for joint accounts, with "Y" denoting a type of account for which the customer's points are additive with a joint owner's points, and "N" denoting an account for which the points are not additive. The "Fixed" column specifies whether a field is to be counted in determining a Relationship score, with "Y" indicating yes and "N" indicating no. The customer database file exemplified in Table B contains information about three hypothetical customers enrolled to participate in the Relationship scoring and Incentive Reward awarding process 20. In actuality a typical customer database file may contain data about many more customers. The master dictionary file (Table A) "Field Name" column defines the six fields of each customer record as containing information about the name of the customer, the number of deposit accounts the customer has, the number of loan accounts the customer has, whether the customer has a safety deposit box, the date the customer first became a customer of the Bank and the customer's social security number. An example taken from Tables A and B illustrates the interrelationship between the master dictionary file and the customer database file in calculating the Relationship score. The customer named "Anderson," social security number 123-45-6789, has two deposit account Relationships, one loan Relationship and a safety deposit box Relationship with the Bank. For each deposit Relationship, defined by the master dictionary table "Field Type" column as a numerical value, and by the "Fixed" column to be used in determining the relationship score, Anderson is entitled one point. Similarly Anderson is entitled to two points for each loan Relationship. Anderson is also entitled to five points for having a safety deposit box Relationship based on the information in the "Safe Deposit" field and one point for each year that Anderson has had a Relationship with the Bank, based on the date in the "Years" column. The points for loan Relationships held by Anderson's joint owner, if any, are additive to Anderson's points, but the points for other Relationships of Anderson's joint owner are not additive with Anderson's points. These fields and information contained in Tables A and B are exemplary. The parameters established in the master dictionary field may define additional or different fields, which will then be present in each customer record of the customer database file. For example, instead of including information about the customer's loans in a single field, several separate fields may be established, such as for car loans, home mortgages and credit card accounts. Similarly, separate fields could be established for checking accounts, pass book savings accounts and certificates of deposit, instead of using the single field "Deposit Accounts." Further, the dates when each type of Relationship is opened or established and the number of other customers which a specific customer may refer to the Bank may constitute additional fields. An example of a typical scale file of the SPF 104, which is used to establish the relationship between the Relationship score and the degree or vesting of the Incentive Reward awarded, is illustrated in Table C below.
TABLE C
Above Percent
10 15
25 30
40 75
60 100
In the example of Table C, the number of points in the customer's Relationship score is compared to the point values in the column marked "Above." The row in Table C is identified in which contains the greatest number in the "Above" column that is exceeded by the customer's Relationship score. The customer is awarded that percentage of the Incentive Reward indicated in the column marked "Percent" that is present in this same row. By using the vesting or scoring concept represented by Table C, Incentive Rewards such as a percentage point increase in a deposit account or a percentage point decrease in a loan rate may be partially awarded. Of course, other types of Incentive Rewards may not admit to being divided, and in which case the vesting or scoring concept would simply be a selected limit of points which the Relationship score would have to exceed to entitle the customer to receive the non-divisible Incentive Reward. The procedures executed during the manual updating state 106 and the parameter establishing state 102 of the Relationship scoring and Incentive Reward awarding process 20 shown in FIG. 4 are generally illustrated by the procedures chart illustrated in FIG. 5. As shown in FIG. 5, a conventional program control procedure 120 and a conventional edit main menu procedure 122 establish an environment in the computer 22 (FIG. 1) in which the Relationship scoring and Incentive Reward awarding process 20 (FIG. 4) operates. The parameter establishing state 102 involves the execution of a conventional data table building procedure comprising a parameter maintenance handling procedure 124 which receives the parameter information and a SPF updating procedure 126 which updates the SPF 104 (FIG. 4) in response to the parameter maintenance handling procedure 124. The parameter establishing state 102 also includes a conventional screen data editing procedure 128 to create and revise information displayed on a visual display screen. One procedure executed in the manual updating state 102 is a score transaction handling procedure 130 which receives information and identifies the type of transaction to be performed. The possible transactions include a query about the score or vesting of a particular customer or group of customers, adding a customer record to the customer database file, changing information in a record of the customer database file, and deleting a customer's record from the customer database. A query procedure 132 activates a RBF retrieving procedure 134 which retrieves information from the RBF 108 (FIG. 4) and further activates a SPF retrieving procedure 136 which retrieves information from the SPF 104 (FIG. 4). Based on the information retrieved the screen data editing procedure 128 displays current information regarding the customer's Relationship score and vesting in the Incentive Rewards. Each one of an add procedure 138, a change procedure 140 and a delete procedure 142 activates the RBF retrieving procedure 134 and the SPF retrieving procedure 136. The information retrieved is modified by a RBF updating and storing procedure 144 in accordance with the information received to add a new customer database record, delete an existing customer database record or change information in an existing customer database record. The customer's Relationship score and vesting are then determined by a score determining and vesting procedure 146. The new or updated information, or confirmation of a delete transaction, is then displayed by the screen editing procedure 128. Steps involved in the execution of the procedures occurring during the manual updating state 106 are shown in the flow chart of FIGS. 6A, 6B and 6C. The execution of the procedures of the manual updating state 106 is started 150 manually by a member of the Bank staff who enters customer data 32 (FIG. 1) or performs a query 40 (FIG. 1). The staff member enters 152 information identifying whether the transaction to be performed is a query about customer information, a change to the customer information, an addition of customer information or a deletion of customer information. The operator then enters 154 a field of the customer database (Table B) by which customer information is to be located. The field may be specified as either the name of the customer, the account number of the customer or the social security number of the customer. Alternatively searching for customers by account number may not be permitted, in which case searching may only be accomplished by the customer's name or social security number. In the case where searching by account number is permitted, if the search is to be performed by account number 156 the customer's social security number is retrieved 158 from cross-reference file 160 in the RBF 108 (FIG. 4). If the customer is not to be located by account number 162, or if locating by account number is not permitted, it is then determined whether the customer is to be located by its name. If the customer is to be located by its name 164 the customer's social security number is retrieved 166 from the cross-reference file 160 of the RBF 108 (FIG. 4). If the customer is not to be located by name 168 then it must be located 170 by social security number. An actual search 170 of the customer database file (Table B) 172 of the RBF 108 (FIG. 4) to locate the customer's record is performed by social security number. Of course, any field of the customer database file 172 having a value unique to a particular customer may alternatively be used as a search field for locating a customer's record in the customer database file. The customer database file 172 is searched 170 by social security number to determine whether a record exists for that customer. If the social security number of that customer is not found 174 a new customer record is created 176, and data provided by the customer is entered 178 into the new record. The customer data in the new record is defined and organized by reference to the master dictionary file 180 of the SPF 104 (FIG. 4). The new record is then stored in the customer database file 172 of the RBF 108 (FIG. 4). If the social security number of the customer is found 182, indicating that a record exists in the customer database file 172 for the customer, and after a new record has been created 176 for the customer, the record for the customer is retrieved 184 from the customer database file 172 of the RBF 108 (FIG. 4). The data in the record is then updated 186 from information furnished by the customer and entered 188 by the staff. Alternatively the customer's record may be further updated 186 by information extracted from the CIF 30 by the CIF information extracting state 112 of the process 20 (FIG. 1). The updated customer record is then stored in the customer database 172 of the RBF 108 (FIG. 4). The customer's Relationship score is determined 190 from the updated customer's record and point values assigned to the Relationships represented by the customer's record by reference to the "point" attribute of the master dictionary file (Table A) 180 of the SPF 104 (FIG. 4). The customer's vesting in the Incentive Rewards to be awarded is determined 194 based on the Relationship score by reference to the scale file 196 (Table C) in the SPF 104 (FIG. 4). The customer's Relationship score and vesting in Incentive Rewards are stored in the customer database file 172 after they are determined. Alternatively the Relationship score is determined for each query and is not stored. After the customer vesting is determined 194 the updated information including the new Relationship score and Incentive Reward vesting are displayed 198 by the screen data editor 128 (FIG. 5). Also, a written report may be printed 200, either on request by the staff member entering the data or automatically. Further, the Incentive Reward may be automatically credited to the customer by entering the Reward awarding state 114 and making appropriate adjustments to information in the CIF 30. The operator specifies 202 that a new inquiry is to be made for the same customer or another customer, or that the procedures of the manual updating state 106 are at an end. If another transaction is desired 204 the operator then enters 152 the type of transaction desired to continue the procedures of the manual updating state 106. If no additional transaction is desired 206 the manual updating state 106 ends 208. A more detailed description of the steps involved in executing the customer score determining step 190 (FIG. 6B), is illustrated in FIGS. 7A, 7B and 7C. The customer's Relationship score is initially set 212 to zero. The customer's record (row in Table B) from the customer database file 172 (FIG. 6B) which has been updated 186 (FIG. 6B) is read sequentially field-by-field (column-by-column in Table B) to determine the points for the Relationships in each field. Information regarding the attributes of the field is retrieved 214 from the master dictionary file (Table A) 180 of the SPF 104 (FIG. 4). If the "fixed" attribute of the master dictionary file 180 designates a field as a fixed field 216 it is not considered in determining the Relationship score. If the field is not designated as fixed 218 it is used in determining the Relationship score. If the "field type" attribute from the master dictionary file (Table A) 180 designates the field as a numeric field 220 the numeric value of the field is multiplied 222 by a number of points set for that field by the "points" attribute from the master dictionary file (Table A) 180 to produce the points for that Relationships. If the "field type" attribute designates the field as a logical field the value of the field is a logical value, i.e., "yes" or "no". If the value of the field is "yes" 226 the points for the Relationship of that field are set 228 to the point value defined by the "points" attribute from the master dictionary file 180. If the field is designated by the "field type" attribute in the master dictionary file 180 as a date 230 the date value of the field is subtracted 232 from a present date 234 to calculate a number of years between the date value of the field and the present date 234. The point value defined by the "points" attribute from the master dictionary file 180 is multiplied 236 by the number of years to determine the points for the number of years represented by the date. If the customer is not a joint customer with another customer of the Bank 238 the point value thus determined is the point value for the field. If however, the customer is a joint Relationship owner with another customer 240, a field of the other joint owner's database record which is the same field as the field of the customer database file 172 being read, is read and a point value is determined 242 for the corresponding field of the joint owner's record. If the master dictionary file 216 (Table A) "add joint" attribute defines the field as one for which a joint owners'points are to be added 244, the points value for that particular field to be used in calculating the customer's Relationship score is determined by adding 246 the points value for the customer's fields to the points determined for the joint owner's fields. If however the field is designated as one for which joint owner's points are not to be added 248, the customer's points value is compared 250 to the joint owner's points value for the same field. The points value assigned 252, 254 to the customer for that field is the greater of the customer's or the joint owner's points. Alternatively, a joint owner's Relationship score may not be considered in calculating the customer's points, at the option and decision of management. The points determined for the field is then added 256 to create a running total of the Relationship score. This process repeats 258 for each field (column of Table B) of the customer database record (row of Table B) until the last field 260 has been read. The Relationship score is the total of the component Relationship scores for all of the fields of the customer's record. The Relationship score is then stored 262 in the customer database file 172 of the RBF 108 (FIG. 4). The customer's Relationship score is then evaluated to determine 194 customer vesting. FIG. 8 illustrates details of the customer vesting determining step 194 of the manual updating state 106 (FIG. 6B). The scale file (Table C) 196 of the SPF 104 (FIG. 4) is retrieved and scanned 266 starting with the bottom row of the scale file (Table C). The value in the "above" column (Table C) retrieved from a row is compared 268 in the "above" column is compared to the customer's Relationship score. If the value on the "above" column is less than or equal to 220 the Relationship score for the customer the vesting for the customer is set 272 at the value retrieved from the "percent" column that is in the same row of the scale file (Table C) 196 as the value from the "above" column that was less than or equal to the Relationship score. The vesting percentage is then stored 274 in the customer database file 172 of the RBF 108 (FIG. 4). The procedures performed by executing the automatic updating state 110 and the CIF information extracting state 112 of the process 20 are generally illustrated by the procedural chart in FIG. 9. The conventional program control procedure 120 establishes the operating environment in the computer 22 (FIG. 1). Data is extracted from the CIF 30 (FIG. 4) by a read CIF procedure 226 of the CIF information extracting state 112. In the automatic updating state 110 an RBF retrieving procedure 278 retrieves the customer database files and cross reference files from the RBF 108 (FIG. 4) and a system parameter retrieval procedure 280 retrieves the master dictionary file (Table A) and scale file (Table C) from the SPF 104 (FIG. 4). The information from the customer database file (Table B) is merged by a merging procedure 282 with the CIF information in accordance with parameters established by the master dictionary file (Table A) of the SPF 104 (FIG. 4). A RBF updating and storing procedure 284 and a score and vesting determining procedure 286 update the customer database and cross reference files, determine Relationship score and vesting, and store the updated customer database and cross reference files and the scores and vesting in the RBF 108 (FIG. 4). The steps involved in executing the procedures shown in FIG. 9 of the automatic update state 110 are shown in detail in FIGS. 10A and 10B. The procedures of the automatic updating state 110 may be initiated manually 288 by member of the Bank staff, or initiated automatically 290 based on a timed schedule. For example, an automatic updating state 110 could be entered automatically each month immediately prior to preparing customers' monthly Bank statements. After the automatic updating state 110 is initiated 288 or 290 either manually or based on a time schedule, the social security numbers of the customers are retrieved 292 from the customer database file 172 of the RBF 108 (FIG. 4). For each social security number a customer record (row in Table B) is retrieved from the customer database file 172. The master dictionary file 180 is retrieved from the SPF 104 (FIG. 4) and used to define and organize the customer's record. The customer data to automatically update the record is extracted from the CIF 30 by a transition to the CIF information updating state 112 and performing the read CIF procedure 276 (FIG. 9). The record is then updated 296 in accordance with the data extracted from the CIF 30. The updated customer data record is stored in the customer database file of the RBF 180 (FIG. 4). The updated customer data record forms the basis for determining 190 the customer Relationship score from information in the master dictionary file 180 of the SPF 104 (FIG. 4), in the same manner as described above in conjunction with FIGS. 7A, 7B and 7C for the score determining step 190 of the manual updating state 106 (FIG. 4). The customer's vesting is determined 194 from the customer's Relationship Score and from information in the scale file 196 of the SPF 104 (FIG. 4) in the same manner as described above in conjunction with FIG. 8 for the vesting determining step 194 of the manual updating state 106 (FIG. 4). The Relationship score and vesting percentage are stored in the customer database file 172 of the RBF 108 (FIG. 4). As with the manual updating state 106 (FIG. 4), the Relationships scores and vesting percentages may alternatively be determined only upon a query. If scores and vesting are only determined on query, the scores and vesting are not stored in the customer database 172. The updated information may also be printed 298 in an update report. Further, the Incentive Reward may be automatically credited to the customer by entering the Reward awarding state 114 and making appropriate adjustments to information in the CIF 30. Of course, printing 298 the reports and the automatic awarding of rewards 114 may take place on a batch basis, with the information being accumulated in temporary files (not shown) for downloading to the printer 56 (FIG. 2) or 86 (FIG. 3) or to the CIF 30. If the social security number of the record updated is the last social security number 302 in the customer database 172, the procedures of the automatic updating state 110 end 304. If it is not the last social security'number 306 the record for the next social security number is retrieved 294 and the procedures of the automatic updating state 110 are repeated. The steps involved in executing the procedures of the report producing state 116 of the process 20 (FIG. 4) are shown in detail in the flow chart of FIGS. 11A and 11B. When a report is requested 42 (FIG. 1) by management, the procedures of the report producing state 116 are initiated by manual input 308 and 310 by a member of the Bank's staff. The staff member starts 308 the procedure then manually selects 310 the type of report to be generated. Typical reports may include: lists of all of the enrolled Relationship customers and their Relationship scores and vesting; lists identifying the Bank Relationships such as accounts, safety deposit boxes, credit cards, etc. used by each enrolled Relationship customer; form letters with information from the customer database file included by merging the information into a word processing program using a conventional mail merge operation; reports on Bank customers who are not enrolled in the program; comparisons of product usage by various categories of customers; and graphical reports. A desired report format is retrieved 312 from a report format file 314 in the SPF 104 (FIG. 4). If the report format requires 316 information about customers who are enrolled in the program the social security numbers of the enrolled customers are retrieved 318 from the customer database file 172 of the RBF 108 (FIG. 4). For each social security number a customer record (row of Table B) is retrieved 320 from the customer database file 172 and updated 322 by data extracted from the CIF 30 by the procedures of the CIF information extracting state 112. The Relationship scores are determined 190 in the same manner as for the score determining step 190 (FIG. 6B) of the manual updating state 106 (FIG. 4) described above in conjunction with FIGS. 7A, 7B and 7C. Customer vesting is determined 194 in the same manner as described above in conjunction with FIG. 8 for the vesting determining step 194 (FIG. 6B) of the manual updating state 106 (FIG. 4). The information required by the report format retrieved 312 from the report format file is printed 324 in a written report 44 (FIG. 1) in the format specified. If the last social security number has not been reached 326, the steps repeat from the step of retrieving 320 the customer record. When the last social security number is reached 328, if it is not desired 330 to include non-Relationship Banking customers the operation ends 332. If it is desired 334 to include non-Relationship Banking customers in the report, the social security numbers of the non-Relationship Banking customers are retrieved 336 from the CIF 30 by the procedures of the data extraction state 112. For each social security number the desired information for the report formats selected 310 is retrieved 338 from the CIF 30 by the procedures of the data extracting state 112. The information is printed 340 in the desired report format. If the last social security number has not been reached 342 the next social security number is retrieved 338 and the steps repeated. When the last social security number is reached 344 the procedures of the report producing state end 332. Alternatively, the information about the customers not participating in the program may be present in the customer database file 172 and be identified by a field of the record as being a non-Relationship Banking customer. Under that alternative, data about non-Relationship Banking customers is extracted from the CIF 30 during an automatic updating state 110 of the process 20 (FIG. 1). The non-Relationship Banking customer data is then retrieved in the report producing state 116 from the customer database files 172 rather than the CIF 30. Also, the data to be printed in the report may be placed in a temporary file (not shown) and held there for batch printing after the last customer record had been processed. The Relationship scoring and Incentive Reward awarding process 20 (FIG. 1) advantageously implements a technique for scoring Relationships that a customer has with a Bank and awarding Incentive Rewards to the customer based on specified parameters selected by the Bank management related to these Relationships. Direct access to information in the CIF 30 (FIG. 1) is provided to accurately and efficiently extract customer data 32 (FIG. 1) needed to execute the process 20. The labor required to establish, maintain and update the necessary information records is greatly reduced over a manual system and data transfer errors are substantially eliminated. The Relationship scoring and Incentive Reward awarding process of the present invention automatically determines and tracks the Relationship score and vesting of each customer. The customer information, score and vesting are automatically updated whenever new information is furnished by the customer or Bank staff for manual input, and is further automatically updated to reflect changes in the CIF of the Bank operations computer. The Relationship scoring and Incentive Reward awarding process can be customized to the needs of individual Banks. This customization allows the Bank to utilize a customer Incentive Reward program effectively as a management and marketing tool, providing incentives to customers for "loyalty." The Relationship scoring and Incentive Reward awarding process is customized by modifying the SPF 104 (FIG. 4) to establish that information in the RBF 108 (FIG. 4) about Relationships between the Bank and its customers that the Bank believes is most important, and to assign Relationship score point values to those Relationships with consideration given to the marketing goals of the individual Bank. Furthermore the Relationship score required to achieve various incentive rewards can be adjusted to meet the individual needs of the Bank. The SPF 104 (FIG. 4) can also be customized to provide those management reports that the Bank management believes are most useful, and to place them in a format usable by management. In addition to being initially customizable, the values and features established in the SPF 104 (FIG. 4) can be changed by Bank's management as the Banks marketing needs change. A preferred embodiment of the present invention has been described with some particularity. It will be understood by those skilled in the art that many variations of the described embodiment are possible, beyond those specifically mentioned. It should be understood this description has been made by way of preferred example, and that the invention is defined by the scope of the following claims.
|
Same subclass Same class Consider this |
||||||||||
